Hatchet
Hatchet takes durable tasks serverless, with handlers for Cloudflare Workers, Vercel and Node.
A side-by-side editorial comparison of Cursor and Spacelift — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Cursor | Spacelift |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 7.5 | 0.0 |
| Sparks · 30d | 2 | 0 |
| Top themes | agent-sdk, cloud-agents, agentic-platform, evals | iac, agentic-deploys, mcp, policy-governance |
| Last editorial update | 2d ago | 2mo ago |
| Website | — | Visit → |
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.
Spacelift's AI stopped explaining infrastructure and started deploying it.
The dated window ends in March with Spacelift Intelligence, first-class Terragrunt support, OIDC subject claim customisation and a self-service Templates release. Everything since sits in undated rows and is the more consequential half: a remote MCP server in May, SCIM 2.0 provisioning in June, and in July the ability to ask Intelligence to deploy a module by name, resolved against the Module Registry. An August notice warns that the API will start returning HTTP 500 on internal errors instead of 200.
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.
The dated window ends in March with Spacelift Intelligence, first-class Terragrunt support, OIDC subject claim customisation and a self-service Templates release. Everything since sits in undated rows and is the more consequential half: a remote MCP server in May, SCIM 2.0 provisioning in June, and in July the ability to ask Intelligence to deploy a module by name, resolved against the Module Registry. An August notice warns that the API will start returning HTTP 500 on internal errors instead of 200.
The arc is easy to trace: Intent opened to everyone in December, Intelligence launched in March, an MCP server exposed the platform to outside assistants in May, and by July the AI is performing deployments rather than describing them. Running underneath is the governance work that makes that defensible — module sharing permissions, OIDC claims, SCIM — because an agent that can deploy is only sellable if the registry and the identity provider bound what it can reach. Terragrunt support and the plan-policy cleanup show the core IaC engine still being maintained rather than neglected for the AI work.
Deployment by name is the narrow case; the obvious next step is Intent handling multi-stack changes with policy checks in the loop, and the permission model being extended to describe what the AI specifically is allowed to deploy rather than what a user is.
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 Spacelift.
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 Spacelift 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 0.0), 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 0.0), 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 Spacelift alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Spacelift alternatives" section above for the current picks, or visit /alternatives/spacelift for the full list with editorial commentary on each.