Drizzle ORM
Drizzle's v1.0 release candidates land a JIT mapper rework, new codecs, and a breaking casing API
A side-by-side editorial comparison of Liveblocks and Ably — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Liveblocks | Ably |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 4.4 | 6.3 |
| Sparks · 30d | 0 | 1 |
| Top themes | multiplayer, ai-agents, react-flow, storage-engine | realtime-infrastructure, ai-agents, pub-sub, developer-sdk |
| Last editorial update | 1mo ago | 3d ago |
| Website | — | — |
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.
Ably builds an AI agent transport on top of its realtime stack — human-in-the-loop and branching land in v0.3
Ably is shipping steady client-SDK maintenance (JS, Cocoa, Dart, CLI) while standing up a new product line: an AI Transport SDK that carries agent conversation streams over its realtime infrastructure. Recent SDK releases improve React channel-hook ergonomics and LiveObjects dashboard visibility, but the distinctive motion is the AI Transport work.
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.
Ably is shipping steady client-SDK maintenance (JS, Cocoa, Dart, CLI) while standing up a new product line: an AI Transport SDK that carries agent conversation streams over its realtime infrastructure. Recent SDK releases improve React channel-hook ergonomics and LiveObjects dashboard visibility, but the distinctive motion is the AI Transport work.
The clear direction is extending Ably's pub/sub and LiveObjects primitives into agentic, real-time AI sessions — session/run models, branching conversations, and human-in-the-loop handoff. The mature client SDKs are being kept stable and incrementally improved while the AI transport layer is where new capability is concentrating.
Expect the AI Transport SDK to march toward a 1.0 with tighter integration of Presence and LiveObjects into agent sessions, while the core client libraries continue their fix-and-refine cadence.
Other Infra & APIs 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 Liveblocks or Ably.
Drizzle's v1.0 release candidates land a JIT mapper rework, new codecs, and a breaking casing API
Warp drops the terminal framing to bet on cloud software factories and agent orchestration
Unleash leans hard into AI-agent governance and self-hosting as its crawled feed fills with thought-leadership.
GitHub spends the week hardening enterprise governance and supply-chain security.
Resend keeps widening from a raw email API into agent-native tooling and audience management.
Very high-cadence sandbox infra building the primitives agents need to run code
See all Liveblocks alternatives → · See all Ably alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — ai-agents — within Infra & APIs. Ably is currently shipping more aggressively (velocity 6.3 vs 4.4), 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. Ably is currently shipping more aggressively (velocity 6.3 vs 4.4), with 1 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 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.
Top Ably alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Ably alternatives" section above for the current picks, or visit /alternatives/ably for the full list with editorial commentary on each.