Sanity vs Flux
Side-by-side trajectory, velocity, and editorial themes.
Sanity is quietly wiring its CMS to be operated by agents as much as by humans.
Sanity is shipping on several fronts in parallel: a maturing MCP server and agent tooling, a Media Library growing real asset-management depth, and steady Studio and SDK ergonomics. The recent run is incremental but coherent — richer Media Library metadata and reference tracking, searchable reference fields, and a stream of MCP tool fixes. Nothing here reshapes the product; it is compounding polish on an already broad platform.
The clearest theme is agent-operability. The MCP server, a skills-install CLI command, agent-focused doc quickstarts, and copy-paste commands 'for humans and agents' all point at Sanity treating AI coding agents as a first-class way to drive the CMS. In parallel, Media Library is being built out toward a full DAM, and @sanity/presets is trimming schema boilerplate.
Expect the MCP and agent surface to keep expanding and Media Library to keep gaining DAM-grade features; the presets package suggests more ready-made schema building blocks ahead.
Flux 2.9 turns the mature GitOps engine into an extensible, plugin-driven platform.
Flux, the CNCF GitOps controller, is a decade-old project shipping steady minor GAs. The feed mixes those releases with community and case-study blog posts (a 10-year retrospective, a Morgan Stanley scaling story, a Terraform bootstrap guide). On the product side, the 2.7–2.9 line has moved from GA-ing image update automation to Helm v4 support and now a first-class CLI plugin system.
Flux is investing in extensibility and keyless, quantum-resistant security: a plugin architecture that lets capabilities ship independently of the core CLI, post-quantum SOPS decryption, Workload Identity across more backends, and finer server-side apply control. The arc is toward a composable GitOps toolkit that large regulated fleets can extend without forking.
Expect the plugin catalog to grow beyond the initial Mirror and Schema plugins and the post-quantum and Workload Identity work to expand to more providers, with field-ignore and post-render controls becoming defaults as they stabilize.
See more alternatives to Sanity →
See more alternatives to Flux →