Frappe Framework
Two release trains, one direction: v16 absorbs what CRM and Helpdesk built themselves.
A side-by-side editorial comparison of Gradle and Sanity — release velocity, themes, recent moves, and the top alternatives to consider.
Isolated Projects reaches incubating — Gradle's parallel-configuration bet gets a version number
Gradle is deep into the 9.7.0 release-candidate cycle, now at RC3, with three milestone builds preceding it. The headline across the whole line is that Isolated Projects graduates from experiment to incubating, joined by broader Configuration Cache compatibility and richer source locations in problem reports.
Sanity's MCP server stops editing documents and starts running the project.
Sanity is building every surface outside the Studio into a first-class participant. The React App SDK made presence bidirectional so a third-party app joins the same collaboration session as Studio users, Media Library got a rebuilt asset grid, and Manage gained a visual builder for custom roles. The MCP server now runs a bounded set of CLI commands and applies document patches transactionally, while the Studio line spends its releases hardening the structure tool, CLI behaviour and TypeScript schema typings underneath.
Gradle is deep into the 9.7.0 release-candidate cycle, now at RC3, with three milestone builds preceding it. The headline across the whole line is that Isolated Projects graduates from experiment to incubating, joined by broader Configuration Cache compatibility and richer source locations in problem reports.
The 9.x line is a sustained push on configuration-time performance: Configuration Cache hit rates improved through 9.6, and 9.7 promotes the feature that lets projects configure in parallel and in isolation. Each release cycle runs milestone builds into three RCs, so the feature set is locked early and the RCs are stabilisation only.
Expect 9.7.0 final to ship with the same three highlights unchanged, followed by 9.8 milestones continuing the Isolated Projects rollout toward stable.
Sanity is building every surface outside the Studio into a first-class participant. The React App SDK made presence bidirectional so a third-party app joins the same collaboration session as Studio users, Media Library got a rebuilt asset grid, and Manage gained a visual builder for custom roles. The MCP server now runs a bounded set of CLI commands and applies document patches transactionally, while the Studio line spends its releases hardening the structure tool, CLI behaviour and TypeScript schema typings underneath.
The platform is being shaped around non-Studio clients, and agents are now one of them. Giving MCP the CLI and making patches all-or-nothing are the moves you make when something unattended will be operating the project rather than a person clicking through a UI. Media Library and Manage keep accumulating the governance controls enterprise buyers evaluate, so agent reach and administrative control are advancing on the same schedule.
Expect the CLI command allowlist to widen, and role definitions from Manage to start scoping what an MCP client is permitted to do - custom roles and agent access are two halves of the same permission question.
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 Gradle or Sanity.
Two release trains, one direction: v16 absorbs what CRM and Helpdesk built themselves.
Skaffold ships a minor a month and tells you nothing about any of them.
Eclipse Che is answering the one objection to cloud dev environments: your uncommitted work survives.
ActiveMQ is shrinking its own defaults — servlets off, factories blocked, frames capped.
gRPC just made post-quantum key exchange the TLS default — no flag, no opt-in.
Protobuf is loading Edition 2026 with enforced defaults, one release candidate at a time.
See all Gradle 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. Gradle and Sanity are shipping at a similar cadence (velocity 6.3 vs 6.3, both within Sparkpulse's "active" band). 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. Gradle and Sanity are shipping at a similar cadence (velocity 6.3 vs 6.3, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other DevOps products to evaluate alongside.
Top Gradle alternatives in DevOps are ranked by recent ship velocity. Browse the "Gradle alternatives" section above for the current picks, or visit /alternatives/gradle 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.