← Back to home
Comparison · Infra & APIs

Merge vs Spacelift

A side-by-side editorial comparison of Merge and Spacelift — release velocity, themes, recent moves, and the top alternatives to consider.

Merge vs Spacelift: at a glance

FeatureMergeSpacelift
SectorInfra & APIsInfra & APIs
Velocity score6.30.0
Sparks · 30d10
Top themesunified api, agent handler, mcp connectors, ai gatewayiac, agentic-deploys, mcp, policy-governance
Last editorial update13h ago13d ago
WebsiteVisit →

What is Merge?

Merge is turning its weekly integration digest into an agent control plane — the news is always at the bottom.

Merge publishes one dated digest a week, and the structure is consistent: unified Accounting, ATS, CRM, File Storage and HRIS reliability work up top, then Agent Handler and Gateway at the end, where the directional changes live. The feed now also carries per-product breakout entries (Gateway, Unified, Agent Handler) that restate the same week's items in more detail rather than adding new ones. The Agent Handler catalog carries hundreds of generic MCP connectors alongside Merge's own, on shared authentication and policy, and Gateway has been accumulating model coverage, routing controls and guardrails over the same period.

Read the full Merge trajectory →

What is Spacelift?

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.

Read the full Spacelift trajectory →

Merge vs Spacelift: editorial side-by-side

M
Merge
INFRA · APIS
6.3

Merge is turning its weekly integration digest into an agent control plane — the news is always at the bottom.

◆ Current state

Merge publishes one dated digest a week, and the structure is consistent: unified Accounting, ATS, CRM, File Storage and HRIS reliability work up top, then Agent Handler and Gateway at the end, where the directional changes live. The feed now also carries per-product breakout entries (Gateway, Unified, Agent Handler) that restate the same week's items in more detail rather than adding new ones. The Agent Handler catalog carries hundreds of generic MCP connectors alongside Merge's own, on shared authentication and policy, and Gateway has been accumulating model coverage, routing controls and guardrails over the same period.

◆ Where it's heading

The through-line is that Merge is repositioning from data plumbing to the layer agents pass through. Each week adds either reach (more connectors, more tools per connector, more models) or control (guardrails, per-project policy, access configuration). This window is reach-and-efficiency: the GitHub connector expanded to 145 tools, Outlook payloads were cut substantially, and Gateway guardrails became configurable per project rather than per account.

◆ Prediction

Expect the per-project granularity applied to guardrails to spread to the rest of Gateway's controls, and the connector catalog to keep absorbing hosted third-party MCP servers the way Axiom was added.

S
Spacelift
INFRA · APIS
0.0

Spacelift's AI stopped explaining infrastructure and started deploying it.

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

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.

Alternatives to Merge and Spacelift

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 Merge or Spacelift.

See all Merge alternatives → · See all Spacelift alternatives →

Recent activity from Merge and Spacelift

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 12d agoMergeGitHub connector hits 145 tools; Gateway adds per-project guardrails
  2. 13d agoSpaceliftAPI will return HTTP 500 on internal errors instead of 200
  3. 19d agoMergeHundreds of generic MCP connectors land in Agent Handler
  4. 26d agoMergeLink setup flow becomes configurable per integration
  5. 1mo agoMergeEmbedded Routing Stack gives Gateway per-customer model controls
  6. 1mo agoMergeGateway breakout page for the week already covered by Week 2
  7. 1mo agoMergeUnified breakout page for the week already covered by Week 3
  8. 1mo agoSpaceliftAsk Spacelift Intelligence to deploy a module by name
  9. 2mo agoSpaceliftSCIM provisioning available in Spacelift!
  10. 2mo agoSpaceliftLearning Certificates now available in Spacelift!
  11. 3mo agoSpaceliftAnnouncing the Spacelift Remote MCP Server!
  12. 4mo agoSpaceliftLaunchpad Learn: Structured hands-on training for Spacelift

Frequently asked questions

What is the difference between Merge and Spacelift?

They serve adjacent needs but don't currently overlap on shipped themes. Merge is currently shipping more aggressively (velocity 6.3 vs 0.0), 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 Merge better than Spacelift?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Merge is currently shipping more aggressively (velocity 6.3 vs 0.0), 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 Merge?

Top Merge alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Merge alternatives" section above for the current picks, or visit /alternatives/merge-dev for the full list with editorial commentary on each.

What are the best alternatives to Spacelift?

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.