Sanity
Sanity is turning its CMS into agent infrastructure, one MCP patch at a time.
A side-by-side editorial comparison of GitHub and Liveblocks — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | GitHub | Liveblocks |
|---|---|---|
| Sector | DevOps, Collab | Infra & APIs |
| Velocity score | 10.0 | 4.4 |
| Sparks · 30d | 3 | 0 |
| Top themes | copilot, agentic-ai, memory, enterprise-default | multiplayer, ai-agents, react-flow, storage-engine |
| Last editorial update | 12h ago | 4mo ago |
| Website | Visit → | — |
GitHub turns Copilot into an org-wide default, adds memory to agentic security fixes.
GitHub is shipping Copilot capabilities at a pace that makes the product unrecognizable from a year ago. This week alone: Claude Opus joined the model roster, local sandboxing landed in the Copilot app, agentic autofix gained persistent Memory integration, and enterprise Copilot features were switched to opt-out by default. GitHub is no longer selling an AI assistant — it is installing an agent layer across every developer workflow.
Liveblocks is rebuilding multiplayer collaboration around AI agents as first-class users.
Liveblocks shipped a six-week run of directional change: a brand-new React Flow SDK for collaborative node-graph editing, a Chat SDK adapter, a Feeds API explicitly framed for "Agent Workflows," a Python SDK for backend use, and v3.18 with breaking changes plus a mutateFlow() API that lets servers mutate diagrams from Node.js. The accompanying blog stream — "AI agents are becoming native users of software," feeds and APIs for agent workflows, n8n nodes — leaves no doubt about where the team is pointing. Underneath, the v1→v2 storage engine migration is in the long tail.
GitHub is shipping Copilot capabilities at a pace that makes the product unrecognizable from a year ago. This week alone: Claude Opus joined the model roster, local sandboxing landed in the Copilot app, agentic autofix gained persistent Memory integration, and enterprise Copilot features were switched to opt-out by default. GitHub is no longer selling an AI assistant — it is installing an agent layer across every developer workflow.
The product is converging on a fully agentic architecture where Copilot agents carry memory across sessions, execute in isolated local sandboxes, and coordinate work across Slack, Teams, and IDEs without requiring a developer to context-switch. The default-on enterprise policy is the distribution play: adoption no longer requires a decision, it requires an explicit reversal.
Copilot Memory will expand beyond security autofix into code review and issue triage agents. The multi-model roster — currently Claude Opus plus GitHub's own models — will grow as a platform differentiator, with model selection becoming a team-level or repo-level policy rather than a user preference.
Liveblocks shipped a six-week run of directional change: a brand-new React Flow SDK for collaborative node-graph editing, a Chat SDK adapter, a Feeds API explicitly framed for "Agent Workflows," a Python SDK for backend use, and v3.18 with breaking changes plus a mutateFlow() API that lets servers mutate diagrams from Node.js. The accompanying blog stream — "AI agents are becoming native users of software," feeds and APIs for agent workflows, n8n nodes — leaves no doubt about where the team is pointing. Underneath, the v1→v2 storage engine migration is in the long tail.
Liveblocks is no longer just "realtime presence and comments for documents." It is positioning itself as the substrate where humans and AI agents share state — diagrams, chat threads, feeds — with the same primitives. The room.history.disable() API for hiding agent-generated writes from the undo stack is the small detail that gives the strategy away: the team is designing for a world where most edits in a room come from agents, and humans need to be shielded from that noise.
The next two minors should bring more agent-shaped APIs (auth scoping for agents, read-only agent participants, server-driven LiveObjects mutations from non-Node runtimes) and broader framework adapters beyond React Flow and Handsontable. Expect Liveblocks to pitch the Chat SDK adapter as a path off OpenAI's hosted threads when teams want agent conversation state stored on their own infra.
Other Infra & APIs products tracked by Sparkpulse, ranked by recent ship velocity. Tap any card for the full editorial trajectory or compare directly with GitHub.
Sanity is turning its CMS into agent infrastructure, one MCP patch at a time.
Manticore Search adds direct-to-disk bulk import, eliminating RAM staging bottlenecks in large ingestion pipelines.
CodeRabbit launches a cross-repo PR triage queue that ranks every open pull request with evidence.
containerd patches CVE-2026-53493 across five branches the same day 2.4.0 ships 658 commits
Rivet is shipping the complete agentic backend stack: actors, durable streams, BYOC, MCP integration, and a V8 app runtime in one month.
Scalingo ships routine runtime maintenance at high cadence while expanding database observability through its SDK.
Other Infra & APIs products tracked by Sparkpulse, ranked by recent ship velocity. Tap any card for the full editorial trajectory or compare directly with Liveblocks.
Railway's weekly cadence is building a PaaS for AI agents: MCP, Cloud Agents, no-barrier entry.
Redocly ships consent controls and closes an RBAC gap in its AI-powered docs platform
Skipper fixes two silent data-loss bugs — body truncation on large requests and multi-value header drops.
ToolJet ships Custom Component Library and tightens enterprise controls on path to AI-native low-code.
werf's v3 dev track ships multi-namespace cleanup scanning and JSON config schemas in rapid succession
Buildkite ships a caching product with cache-poisoning controls baked in as it builds toward AI-agent-operated CI.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. GitHub is currently shipping more aggressively (velocity 10.0 vs 4.4), 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. GitHub is currently shipping more aggressively (velocity 10.0 vs 4.4), with 3 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
Top GitHub alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "GitHub alternatives" section above for the current picks, or visit /alternatives/github for the full list with editorial commentary on each.
Top Liveblocks alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Liveblocks alternatives" section above for the current picks, or visit /alternatives/liveblocks for the full list with editorial commentary on each.