Hatchet
Hatchet takes durable tasks serverless, with handlers for Cloudflare Workers, Vercel and Node.
A side-by-side editorial comparison of Cursor and Liveblocks — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Cursor | Liveblocks |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 7.5 | 4.4 |
| Sparks · 30d | 2 | 0 |
| Top themes | agent-sdk, cloud-agents, agentic-platform, evals | multiplayer, ai-agents, react-flow, storage-engine |
| Last editorial update | 2d ago | 5mo ago |
| Website | — | — |
Cursor's Agent SDK turns custom agents into code projects you can test, then deploy anywhere.
Cursor has grown from an editor into a delivery platform: Projects coordinates cloud agents, Origin hosts repos with a 20+ app marketplace, Rollouts watches deploys, and the Environments API scripts agent sandboxes. On October 20 the Agent SDK went GA. An agent is now a folder with a prompt, typed tools, skills, MCP connections and channels, tested with evals and deployed either to Cursor or to the team's own infrastructure.
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.
Cursor has grown from an editor into a delivery platform: Projects coordinates cloud agents, Origin hosts repos with a 20+ app marketplace, Rollouts watches deploys, and the Environments API scripts agent sandboxes. On October 20 the Agent SDK went GA. An agent is now a folder with a prompt, typed tools, skills, MCP connections and channels, tested with evals and deployed either to Cursor or to the team's own infrastructure.
The last month has been about opening Cursor's agent stack to outside code: partner apps write into Origin, the Environments API exposes sandboxes, and the Agent SDK lets teams build their own bots on the same runtime. Agents that wake on PR, CI, Slack, webhook and cron events push Cursor past the IDE into always-on team automation. Cursor is selling the agent runtime itself, not just its own agents.
Expect more starter templates and SDK-built agents to appear in the app marketplace, and tighter links between SDK agents and Projects or Rollouts. Whether self-hosted deploys get the same dashboard tooling as Cursor-hosted ones is not yet clear from the entries.
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.
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 Cursor or Liveblocks.
Hatchet takes durable tasks serverless, with handlers for Cloudflare Workers, Vercel and Node.
NetBird's second v0.82 candidate keeps the MySQL removal and deprecates Rosenpass.
At Universe, GitHub folds Copilot into Enterprise seats and lets Copilot Fusion pick the model.
incident.io's agent now runs your team's own tools, with a human approval before any change.
Airflow 3.4 reaches its first release candidate, a week after the 10-20 provider wave.
Redocly's reunite.agent gets per-duty cron schedules, rules and source repos.
See all Cursor alternatives → · See all Liveblocks alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Cursor is currently shipping more aggressively (velocity 7.5 vs 4.4), with 2 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. Cursor is currently shipping more aggressively (velocity 7.5 vs 4.4), with 2 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 Cursor alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Cursor alternatives" section above for the current picks, or visit /alternatives/cursor for the full list with editorial commentary on each.
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.