GitHub
Security and governance controls catch up to the Copilot build-out
A side-by-side editorial comparison of Astro and Sanity — release velocity, themes, recent moves, and the top alternatives to consider.
Astro 7.0 lands a Rust compiler and advanced routing as the framework chases build speed
Astro shipped its 7.0 major release, headlined by a new Rust compiler, Vite 8, advanced routing, and structured logging — the culmination of a long run of 6.x releases that incrementally introduced advanced routing (with Hono and Cloudflare support), a pluggable and Rust-based Markdown processor, and better logging. The throughline is build performance and routing flexibility. Around the releases, Astro keeps up heavy community and partnership activity (TinaCMS, CloudCannon, events, even merch).
Sanity ships across every package at once, and the agent-facing surface moves fastest.
Sanity releases as a fleet: MCP server, Studio, JavaScript client, Media Library and UI all cut versions within days of each other, and the changelog reads as one stream of package releases. The current window is dominated by two lanes — the MCP server steadily gaining tools agents can call, and a round of modernization breakage in the client libraries (ESM-only, Node 22.12 floor). Studio v6.10.0 now bundles the App SDK, so custom Studio tools can call SDK hooks without wiring their own provider.
Astro shipped its 7.0 major release, headlined by a new Rust compiler, Vite 8, advanced routing, and structured logging — the culmination of a long run of 6.x releases that incrementally introduced advanced routing (with Hono and Cloudflare support), a pluggable and Rust-based Markdown processor, and better logging. The throughline is build performance and routing flexibility. Around the releases, Astro keeps up heavy community and partnership activity (TinaCMS, CloudCannon, events, even merch).
The engineering focus is speed and architecture: moving compilation and Markdown processing to Rust, adopting Vite 8, and stabilizing the advanced routing system that spent the 6.x cycle behind experimental flags. Expect the Rust toolchain to expand and advanced routing to graduate from experimental. The steady partnership and CMS integrations point to Astro entrenching as the content-site framework of choice.
Next releases will likely build on the 7.0 Rust compiler with further build-speed gains and move advanced routing toward stable. Continued CMS and hosting partnerships are probable as Astro defends its content-and-docs niche.
Sanity releases as a fleet: MCP server, Studio, JavaScript client, Media Library and UI all cut versions within days of each other, and the changelog reads as one stream of package releases. The current window is dominated by two lanes — the MCP server steadily gaining tools agents can call, and a round of modernization breakage in the client libraries (ESM-only, Node 22.12 floor). Studio v6.10.0 now bundles the App SDK, so custom Studio tools can call SDK hooks without wiring their own provider.
The MCP server is where the capability surface is actually growing — asset upload, schema discovery, CORS management — each release handing agents another operation that previously needed a human in the dashboard. The library work underneath is consolidation: one module system, one supported Node line, fewer dependencies, and now one SDK shared between Studio extensions and standalone apps. Read together, Sanity is narrowing the number of ways to build against it while widening what an agent can do unattended.
Expect the MCP tool list to keep absorbing dashboard operations — deploy, dataset and role management are the obvious remaining gaps — and the ESM-only floor to propagate to the packages that have not taken it yet. The releases are per-package, so a single dated entry rarely tells the whole story of a given week.
Other DevOps products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Astro or Sanity.
Security and governance controls catch up to the Copilot build-out
The 29.0 line is stabilizing in public; 29.1 opens with load-tool work rather than engine work.
Tigris keeps publishing its architecture, and the newest post opens up the storage engine itself.
WeWeb is turning the apps it builds into AI products, and metering the AI as it goes.
Workato is dismantling the assumptions that tied a Genie to one chat window at a time.
Laravel's queue work has turned from correctness into operator controls, next to Cloud-named APIs.
See all Astro alternatives → · See all Sanity alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Sanity is currently shipping more aggressively (velocity 7.5 vs 6.3), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Sanity is currently shipping more aggressively (velocity 7.5 vs 6.3), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other DevOps products to evaluate alongside.
Top Astro alternatives in DevOps are ranked by recent ship velocity. Browse the "Astro alternatives" section above for the current picks, or visit /alternatives/astro for the full list with editorial commentary on each.
Top Sanity alternatives in DevOps are ranked by recent ship velocity. Browse the "Sanity alternatives" section above for the current picks, or visit /alternatives/sanity for the full list with editorial commentary on each.