GravityKit
GravityKit folds every GravityView extension into one Pro plugin.
A side-by-side editorial comparison of Liveblocks and Payload CMS — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Liveblocks | Payload CMS |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 4.4 | 5.0 |
| Sparks · 30d | 0 | 0 |
| Top themes | multiplayer, ai-agents, react-flow, storage-engine | headless-cms, v4-beta, file-uploads, auth |
| Last editorial update | 6mo ago | 50m ago |
| Website | — | Visit → |
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.
Payload's v4 beta.9 keeps every past image crop and raises the Node floor again.
Payload has tagged nine v4 betas since October 10. Beta.9 reads saved crops and focal points from the new _transforms store, serves historical upload variants when a version is restored, adds labels and device details to sessions, and exports standalone CSS tokens from the UI package. It also bumps the minimum Node version to 24.22.3, the second Node floor raise in the cycle.
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.
Payload has tagged nine v4 betas since October 10. Beta.9 reads saved crops and focal points from the new _transforms store, serves historical upload variants when a version is restored, adds labels and device details to sessions, and exports standalone CSS tokens from the UI package. It also bumps the minimum Node version to 24.22.3, the second Node floor raise in the cycle.
Three betas in a row have reworked file uploads around one stored original plus replayable transforms, and two have tightened sign-in and sessions. The v4 cycle is now finishing those two systems rather than adding new surfaces, which is the usual shape of a beta nearing a release candidate.
Expect more betas that close out the transforms and session work, with a release candidate once the fix lists shrink; the entries do not show a date.
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.
GravityKit folds every GravityView extension into one Pro plugin.
Nautobot 3.3 alpha 2 adds test helpers and a cable location filter after 3.2.9's token-leak fix.
Clair 4.10 RC can read SBOMs to match Java vulnerabilities.
Shuffle tags builds almost daily, but the notes are empty.
KrakenD's community edition is shipping only dependency bumps.
Velociraptor's recent releases are mostly about patching CVEs.
See all Liveblocks alternatives → · See all Payload CMS alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Payload CMS is currently shipping more aggressively (velocity 5.0 vs 4.4), with 0 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. Payload CMS is currently shipping more aggressively (velocity 5.0 vs 4.4), with 0 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 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 for the full list with editorial commentary on each.