NetBird
NetBird's second v0.82 candidate keeps the MySQL removal and deprecates Rosenpass.
Comparison · Infra & APIs
Hatchet vs Liveblocks
A side-by-side editorial comparison of Hatchet and Liveblocks — release velocity, themes, recent moves, and the top alternatives to consider.
Hatchet vs Liveblocks: at a glance
| Feature | Hatchet | Liveblocks |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 6.3 | 4.4 |
| Sparks · 30d | 0 | 0 |
| Top themes | durable execution, serverless, task queues, rate limiting | multiplayer, ai-agents, react-flow, storage-engine |
| Last editorial update | 15h ago | 5mo ago |
| Website | Visit → | — |
What is Hatchet?
Hatchet takes durable tasks serverless, with handlers for Cloudflare Workers, Vercel and Node.
Hatchet's new @hatchet-dev/serverless 0.1.0 runs tasks on Cloudflare Workers, Vercel and Node. An in-engine operator delivers them by signed POST or by an invocation websocket that also carries durable sleeps, waits and child runs. Around it, the engine shipped three patches in a day: DAG replays no longer take an advisory lock, worker shutdown now waits for durable tasks, and status queries use partition pruning. The API now declares 429 with Retry-After on every authenticated call.
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.
Hatchet vs Liveblocks: editorial side-by-side
Hatchet
6.3INFRA · APIS
Hatchet takes durable tasks serverless, with handlers for Cloudflare Workers, Vercel and Node.
◆ Current state
Hatchet's new @hatchet-dev/serverless 0.1.0 runs tasks on Cloudflare Workers, Vercel and Node. An in-engine operator delivers them by signed POST or by an invocation websocket that also carries durable sleeps, waits and child runs. Around it, the engine shipped three patches in a day: DAG replays no longer take an advisory lock, worker shutdown now waits for durable tasks, and status queries use partition pruning. The API now declares 429 with Retry-After on every authenticated call.
◆ Where it's heading
Until now, running Hatchet meant running long-lived workers. The serverless package removes that requirement, so durable execution can run where JavaScript teams already deploy. The engine work points the same way: rate limits declared in the spec, safer worker acks, cheaper status queries. Patch cadence is still very high, often several engine tags a day, and much of it fixes durable-task edge cases.
◆ Prediction
Expect quick 0.1.x serverless releases as early users hit edge cases on each platform, and possibly matching Python handlers. More engine patches on durable-task shutdown and replay are likely.
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.
Alternatives to Hatchet and Liveblocks
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 Hatchet or Liveblocks.
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.
Jackett
Jackett ships a daily build to keep hundreds of torrent indexers working as sites move and close.
See all Hatchet alternatives → · See all Liveblocks alternatives →
Recent activity from Hatchet and Liveblocks
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 21h agoHatchetHatchet v0.115.0: contributor list update, no product notes
- 22h agoHatchetHatchet v0.114.15 fixes migration deadlocks
- 1d agoHatchetHatchet v0.114.14 builds its own continuous aggregates
- 1d agoHatchetHatchet v0.114.13 quiets noisy DAG operator errors
- 1d agoHatchetPython SDK 1.43.2 parses 429 rate-limit errors
- 1d agoHatchetHatchet v0.114.12 adds a Concurrency dashboard page
- 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 Hatchet and Liveblocks?
They serve adjacent needs but don't currently overlap on shipped themes. Hatchet is currently shipping more aggressively (velocity 6.3 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.
Is Hatchet better than Liveblocks?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Hatchet is currently shipping more aggressively (velocity 6.3 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.
What are the best alternatives to Hatchet?
Top Hatchet alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Hatchet alternatives" section above for the current picks, or visit /alternatives/hatchet for the full list with editorial commentary on each.
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.