Bitwarden
Bitwarden's server releases are all plumbing right now — flags cleared, billing untangled, invites hardened.
A side-by-side editorial comparison of Sanity and Laravel — release velocity, themes, recent moves, and the top alternatives to consider.
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.
Laravel runs two release trains at once, and 13.x is where anything interesting lands.
Releases alternate between the 12.x and 13.x branches on a roughly weekly cadence, each a flat list of merged pull requests. 12.x receives fixes almost exclusively — lost-connection detection, Postgres whereDate crashes, deprecation logging, schedule:list timezone handling. 13.x gets the additions: a monthly log driver, first-party image handling, modelKeys() on the query builder, an array_keys validation rule, and a steady stream of queue-fake testing improvements.
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.
Releases alternate between the 12.x and 13.x branches on a roughly weekly cadence, each a flat list of merged pull requests. 12.x receives fixes almost exclusively — lost-connection detection, Postgres whereDate crashes, deprecation logging, schedule:list timezone handling. 13.x gets the additions: a monthly log driver, first-party image handling, modelKeys() on the query builder, an array_keys validation rule, and a steady stream of queue-fake testing improvements.
The split is doing exactly what a maintenance branch is supposed to do, which makes the framework's direction readable from 13.x alone. Two clusters dominate there: queue and job testing ergonomics (fakes that understand delays, reserved jobs, and immutable timestamps) and small ergonomic additions to Collection, Str and Storage. Route cache lookup work and worker memory reporting suggest performance attention on the runtime side.
Expect 13.x to keep accumulating small API additions between minor releases while 12.x stays fix-only, with the queue and testing surface the most likely place for the next batch given how consistently it shows up.
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 Sanity or Laravel.
Bitwarden's server releases are all plumbing right now — flags cleared, billing untangled, invites hardened.
PlanetScale is building out Postgres while making every control reachable without the dashboard.
Confluent Platform 8.2 gives Kafka native queueing, removing a standing reason to run a second broker.
With AIRO generally available, Workato is tuning the document and API plumbing beneath it.
Cloudflare is making itself a cloud that agents can sign up for, pay for, and deploy to unassisted.
Postman is claiming the space between your app's tests and the APIs it actually depends on.
See all Sanity alternatives → · See all Laravel 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 6.3 vs 5.0), with 1 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 6.3 vs 5.0), with 1 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 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.
Top Laravel alternatives in DevOps are ranked by recent ship velocity. Browse the "Laravel alternatives" section above for the current picks, or visit /alternatives/laravel for the full list with editorial commentary on each.