Hotjar
Hotjar's update feed stops in April 2025 — the arc it captures ended mid-sentence.
Comparison · Infra & APIs
Liveblocks vs Merge
A side-by-side editorial comparison of Liveblocks and Merge — release velocity, themes, recent moves, and the top alternatives to consider.
Liveblocks vs Merge: at a glance
| Feature | Liveblocks | Merge |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 4.4 | 6.3 |
| Sparks · 30d | 0 | 1 |
| Top themes | multiplayer, ai-agents, react-flow, storage-engine | unified-api, agent-infrastructure, mcp, llm-routing |
| Last editorial update | 3mo ago | 1h ago |
| Website | — | — |
What is Liveblocks?
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.
What is Merge?
Merge is becoming the governance layer for agent tool access, not just a unified data API.
Merge ships a weekly digest split across three lines: the original unified API (HRIS, ATS, CRM, accounting, file storage, ticketing), Agent Handler for AI agent connectors, and Gateway for LLM routing. The unified-API half reads as a maintenance grind — every week is dominated by SharePoint, SAP SuccessFactors, Workday and Dayforce sync reliability, pagination and mapping fixes. All of July's directional news came from the other two lines, ending with hundreds of generic MCP connectors folded into the Agent Handler catalog and an AI Guardrails surface with PII detection.
Liveblocks vs Merge: editorial side-by-side
Liveblocks
4.4INFRA · APIS
Liveblocks is rebuilding multiplayer collaboration around AI agents as first-class users.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
Merge
6.3INFRA · APIS
Merge is becoming the governance layer for agent tool access, not just a unified data API.
◆ Current state
Merge ships a weekly digest split across three lines: the original unified API (HRIS, ATS, CRM, accounting, file storage, ticketing), Agent Handler for AI agent connectors, and Gateway for LLM routing. The unified-API half reads as a maintenance grind — every week is dominated by SharePoint, SAP SuccessFactors, Workday and Dayforce sync reliability, pagination and mapping fixes. All of July's directional news came from the other two lines, ending with hundreds of generic MCP connectors folded into the Agent Handler catalog and an AI Guardrails surface with PII detection.
◆ Where it's heading
The unified API is being maintained, not expanded — new objects arrive at a trickle (expense reports in early July) while the bulk of each week goes to sync stability across existing connectors. Attention has moved to sitting between agents and the tools they call: Merge now offers auth, access control, governance and guardrails over connectors it did not build. Gateway is moving the same way, from a routing product to multi-tenant infrastructure customers resell, via Embedded Routing Stack, bring-your-own keys and per-customer complexity classifiers.
◆ Prediction
Expect the guardrails surface to deepen — PII detection and pre-run/post-run rule labels shipped in the same month, and the generic MCP connectors currently arrive without the tool safety hints Merge applied to its own catalog. The likely next step is extending that governance tooling to the imported MCP servers.
Alternatives to Liveblocks and Merge
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 Merge.
Tailscale
Tailscale is turning the tailnet into something you provision by API, not configure by hand.
Daytona
Ten releases in a month, all pointed at making agent sandboxes safe to run in production.
Dashy
After the 4.5.0 drag-and-drop release, Dashy has settled into translations and dependency patches
Jackett
Jackett ships daily, and every release is tracker definitions chasing sites that moved
Quay
Quay ships nothing but CVE remediation, mirrored across two supported branches
See all Liveblocks alternatives → · See all Merge alternatives →
Recent activity from Liveblocks and Merge
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 12d agoMergeHundreds of generic MCP connectors land in Agent Handler ⚡
- 19d agoMergeLink setup flow becomes configurable per integration
- 26d agoMergeEmbedded Routing Stack gives Gateway per-customer model controls
- 1mo agoMergeGPT-5.6, Grok 4.5 join Gateway; new Professional Plan pricing
- 1mo agoMergeiTrent and OmniHR connectors; Slackbot gets its own agent identity
- 1mo agoMergeExpense reports endpoint, iTrent and OmniHR join HRIS
- 3mo agoLiveblocksWeek 17
- 3mo agoLiveblocksWeek 16 ⚡
- 4mo agoLiveblocksWeek 15 ⚡
- 4mo agoLiveblocksWeek 14 ⚡
- 4mo agoLiveblocksWeek 13
- 4mo agoLiveblocksWeek 12
Frequently asked questions
What is the difference between Liveblocks and Merge?
They serve adjacent needs but don't currently overlap on shipped themes. Merge 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.
Is Liveblocks better than Merge?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Merge 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.
What are the best alternatives to Liveblocks?
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.
What are the best alternatives to Merge?
Top Merge alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Merge alternatives" section above for the current picks, or visit /alternatives/merge-dev for the full list with editorial commentary on each.