Hatchet
Hatchet takes durable tasks serverless, with handlers for Cloudflare Workers, Vercel and Node.
Comparison · Infra & APIs
Liveblocks vs Payload CMS
A side-by-side editorial comparison of Liveblocks and Payload CMS — release velocity, themes, recent moves, and the top alternatives to consider.
Liveblocks vs Payload CMS: at a glance
| Feature | Liveblocks | Payload CMS |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 4.4 | 6.3 |
| Sparks · 30d | 0 | 1 |
| Top themes | multiplayer, ai-agents, react-flow, storage-engine | headless-cms, major-release, upload adapters, graphql |
| Last editorial update | 5mo ago | 1d ago |
| Website | — | Visit → |
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 Payload CMS?
Payload 4.0 beta 5 is a fix release with one adapter-facing breaking change.
Payload v4.0.0-beta.5 is a short fix list: password validation on reset, hidden fields excluded from GraphQL mutation inputs, plugins able to override other plugins' options, and signed upload receipts. Its one breaking change moves extra upload fields into clientData for adapters running without receipts, which no first-party adapter does. Beta releases now ship per-package SBOMs.
Liveblocks vs Payload CMS: 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.
Payload CMS
6.3INFRA · APIS
Payload 4.0 beta 5 is a fix release with one adapter-facing breaking change.
◆ Current state
Payload v4.0.0-beta.5 is a short fix list: password validation on reset, hidden fields excluded from GraphQL mutation inputs, plugins able to override other plugins' options, and signed upload receipts. Its one breaking change moves extra upload fields into clientData for adapters running without receipts, which no first-party adapter does. Beta releases now ship per-package SBOMs.
◆ Where it's heading
The 4.0 beta lands every three to five days, and each one is smaller than the last. beta.0 shipped the admin redesign, TanStack support and the new MCP. Later betas covered adapters, Next.js cache components and accessibility, and beta.5 is mostly correctness and supply-chain hygiene, which suggests a release candidate is close.
◆ Prediction
Expect one or two more fix-only betas, then a 4.0 release candidate. The SBOM addition suggests supply-chain artifacts will carry over to stable releases.
Alternatives to Liveblocks and Payload CMS
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 Payload CMS.
NetBird
NetBird's second v0.82 candidate keeps the MySQL removal and deprecates Rosenpass.
GitHub
At Universe, GitHub folds Copilot into Enterprise seats and lets Copilot Fusion pick the model.
incident.io
incident.io's agent now runs your team's own tools, with a human approval before any change.
Apache Airflow
Airflow 3.4 reaches its first release candidate, a week after the 10-20 provider wave.
Redocly
Redocly's reunite.agent gets per-duty cron schedules, rules and source repos.
See all Liveblocks alternatives → · See all Payload CMS alternatives →
Recent activity from Liveblocks and Payload CMS
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 2d agoPayload CMSPayload 4.0 beta 5: GraphQL, upload and password-reset fixes
- 7d agoPayload CMSPayload 4.0 beta 4: accessibility fixes, Node 24.22.1 minimum
- 9d agoPayload CMSPayload 4.0 beta 3 adds Next.js cache components support
- 13d agoPayload CMSPayload 4.0 beta 2 moves to stable TanStack Start
- 15d agoPayload CMSPayload 4.0 beta 1: codemod and docs fixes
- 19d agoPayload CMSPayload 4.0 beta: admin redesign, TanStack support, new MCP ⚡
- 6mo agoLiveblocksWeek 17
- 6mo agoLiveblocksWeek 16 ⚡
- 6mo agoLiveblocksWeek 15 ⚡
- 6mo agoLiveblocksWeek 14 ⚡
- 7mo agoLiveblocksWeek 13
- 7mo agoLiveblocksWeek 12
Frequently asked questions
What is the difference between Liveblocks and Payload CMS?
They serve adjacent needs but don't currently overlap on shipped themes. Payload CMS 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 Payload CMS?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Payload CMS 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 Payload CMS?
Top Payload CMS alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Payload CMS alternatives" section above for the current picks, or visit /alternatives/payload-cms for the full list with editorial commentary on each.