Sanity
Sanity's MCP server hits v2.33 with safer publishing guards as Studio bug-fix cadence accelerates
A side-by-side editorial comparison of Bun and Rivet — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Bun | Rivet |
|---|---|---|
| Sector | DevOps | DevOps |
| Velocity score | 5.0 | 8.8 |
| Sparks · 30d | 0 | 3 |
| Top themes | javascript-runtime, nodejs-compatibility, rust, http2 | actor-model, byoc, mcp, agent-infrastructure |
| Last editorial update | 7d ago | 1d ago |
| Website | Visit → | — |
Bun rewrote its entire runtime from Zig to Rust and shipped HTTP/2 server support in v1.4.
Bun made two foundational moves in 2026: a complete Zig-to-Rust rewrite announced in July, and a v1.4.1 release that ships HTTP/2 server support in Bun.serve, workspace-scoped node_modules, argon2 in crypto, tree-shaking through dynamic imports, and a 9x throughput gain on Buffer I/O. The runtime now handles most production server workloads that previously required Node.js.
Rivet positions its Actors runtime as the infrastructure layer for enterprise-ready, AI-native application deployment.
Rivet has shipped three substantive capability moves in rapid succession: BYOC (Bring Your Own Cloud, letting enterprises run Rivet's control plane inside their own AWS or GCP VPCs), MCP integration (exposing Rivet Actors as a first-class tool in Claude Code, Cursor, Codex, and Gemini CLI), and Dynamic Apps (a V8-isolate-based runtime for deploying AI-generated applications for end users). Underneath all of this is the Actors model — a durable, stateful compute primitive built on open-source infrastructure. Durable Streams, a zero-disk SQLite storage engine with S3 tiering, and the agentOS execution API round out the technical foundation.
Bun made two foundational moves in 2026: a complete Zig-to-Rust rewrite announced in July, and a v1.4.1 release that ships HTTP/2 server support in Bun.serve, workspace-scoped node_modules, argon2 in crypto, tree-shaking through dynamic imports, and a 9x throughput gain on Buffer I/O. The runtime now handles most production server workloads that previously required Node.js.
Bun is methodically closing Node.js compatibility gaps while building APIs Node.js does not have — Bun.Image, Bun.cron, Bun.WebView, HTTP/2+3 support. The Rust rewrite signals long-term commitment to safety and contributor ecosystem depth that Zig could not provide. At this pace, a v2.0 major is the next logical milestone to formalize the built-in API surface.
A 2.0 major release will likely stabilize the HTTP/2 and HTTP/3 server story and formalize the Bun.Image and Bun.cron APIs as supported. The Rust migration should produce measurably lower crash rates in subsequent releases.
Rivet has shipped three substantive capability moves in rapid succession: BYOC (Bring Your Own Cloud, letting enterprises run Rivet's control plane inside their own AWS or GCP VPCs), MCP integration (exposing Rivet Actors as a first-class tool in Claude Code, Cursor, Codex, and Gemini CLI), and Dynamic Apps (a V8-isolate-based runtime for deploying AI-generated applications for end users). Underneath all of this is the Actors model — a durable, stateful compute primitive built on open-source infrastructure. Durable Streams, a zero-disk SQLite storage engine with S3 tiering, and the agentOS execution API round out the technical foundation.
Rivet is building toward a single answer to a specific question: where does agent-generated, user-facing software actually run? The BYOC move unlocks regulated industries and large enterprises who can't send data to a SaaS control plane. MCP turns Rivet's Actors into something any AI client can discover and call without bespoke integration. Dynamic Apps makes Rivet the runtime, not just the infrastructure, for user-generated software. The through-line is that Rivet wants every AI agent — whether built by a developer or generated at runtime — to run on the Actors primitive with Rivet managing the lifecycle.
BYOC on AWS/GCP is the foundation; Azure support and SOC 2 certification are the logical next steps to close enterprise deals. Expect MCP to expand to more clients (OpenAI Codex, Copilot, Windsurf) as the MCP ecosystem grows, and Dynamic Apps to get versioning and rollback — the missing piece for user-facing production deployments.
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 Bun or Rivet.
Sanity's MCP server hits v2.33 with safer publishing guards as Studio bug-fix cadence accelerates
Speakeasy becomes the enterprise control plane for MCP server access and AI tool governance.
Kubernetes v1.37 matures its memory management and scheduling stack for AI/ML workloads.
GitHub Copilot gets cost-aware inference tiers as enterprise AI tooling tightens across the platform.
CodeRabbit pushes upmarket with enterprise APIs, rate controls, and a CLI that reviews remotely
NATS 2.15 introduces a desired-state reconciliation engine for JetStream, making cluster operations safe to run mid-flight.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Rivet is currently shipping more aggressively (velocity 8.8 vs 5.0), with 3 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. Rivet is currently shipping more aggressively (velocity 8.8 vs 5.0), with 3 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 Bun alternatives in DevOps are ranked by recent ship velocity. Browse the "Bun alternatives" section above for the current picks, or visit /alternatives/bun for the full list with editorial commentary on each.
Top Rivet alternatives in DevOps are ranked by recent ship velocity. Browse the "Rivet alternatives" section above for the current picks, or visit /alternatives/rivet for the full list with editorial commentary on each.