← Back to home
Comparison · Infra & APIs

Merge vs Skipper

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

Merge vs Skipper: at a glance

FeatureMergeSkipper
SectorInfra & APIsInfra & APIs
Velocity score6.35.0
Sparks · 30d10
Top themesunified api, agent handler, mcp connectors, ai gatewayreverse-proxy, kubernetes, http2, load-balancing
Last editorial update12h ago16h 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 Skipper?

Zalando's ingress proxy finally speaks HTTP/2 cleartext end to end

Skipper ships patch tags almost daily, and most carry a single dependency bump or a one-line auth fix. The substance in this window is v0.27.57, which enables h2c on the server handler, the proxy client, and the net client, with a new h2c:// route scheme and Kubernetes appProtocol wiring. Everything else in the window is Dependabot traffic and two narrow fixes to token introspection and grant auth.

Read the full Skipper trajectory →

Merge vs Skipper: 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
Skipper
INFRA · APIS
5.0

Zalando's ingress proxy finally speaks HTTP/2 cleartext end to end

◆ Current state

Skipper ships patch tags almost daily, and most carry a single dependency bump or a one-line auth fix. The substance in this window is v0.27.57, which enables h2c on the server handler, the proxy client, and the net client, with a new h2c:// route scheme and Kubernetes appProtocol wiring. Everything else in the window is Dependabot traffic and two narrow fixes to token introspection and grant auth.

◆ Where it's heading

The release cadence is a stream of small, individually unremarkable tags where the occasional protocol or load-balancing change is the only thing worth reading. Recent substance has clustered on the data path: leastRequests balancing in v0.27.53, h2c now. The auth filters are being maintained rather than extended, with fixes rather than new capability.

◆ Prediction

Expect the h2c work to generate follow-up fixes as it meets real gRPC backends, since the release notes already show HTTP Upgrade negotiation failing while direct prior knowledge works.

Alternatives to Merge and Skipper

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 Skipper.

See all Merge alternatives → · See all Skipper alternatives →

Recent activity from Merge and Skipper

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

  1. 18h agoSkipperFix token introspection handling
  2. 18h agoSkipperFix grant auth flow
  3. 23h agoSkipperUpdate outdated golang.org/x dependencies
  4. 1d agoSkipperh2c enabled for server handler, proxy client and net client
  5. 2d agoSkipperBump protobuf off a pre-release pin
  6. 2d agoSkipperBump the CodeQL upload-sarif action
  7. 12d agoMergeGitHub connector hits 145 tools; Gateway adds per-project guardrails
  8. 19d agoMergeHundreds of generic MCP connectors land in Agent Handler
  9. 26d agoMergeLink setup flow becomes configurable per integration
  10. 1mo agoMergeEmbedded Routing Stack gives Gateway per-customer model controls
  11. 1mo agoMergeGateway breakout page for the week already covered by Week 2
  12. 1mo agoMergeUnified breakout page for the week already covered by Week 3

Frequently asked questions

What is the difference between Merge and Skipper?

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

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

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