← Back to home
Comparison · Infra & APIs

Merge vs Nebula

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

Merge vs Nebula: at a glance

FeatureMergeNebula
SectorInfra & APIsInfra & APIs
Velocity score6.32.5
Sparks · 30d10
Top themesunified api, agent handler, mcp connectors, ai gatewaymesh-vpn, overlay-network, certificates, ipv6
Last editorial update11h ago7d 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 Nebula?

Overlay network that rewrote its certificate format, then spent a year fixing what it exposed.

Nebula is a peer-to-peer mesh VPN built around a certificate authority model. The v1.10.0 release was the pivot: IPv6 and multiple addresses in the overlay, plus a new v2 ASN.1 certificate format with a unified interface for external implementations. Everything since has been consequence management — a P256 signature malleability issue that allowed blocklist bypass, a source-IP acceptance flaw tied to the new multi-address certificates, and a run of fixes around route tables and Windows listeners.

Read the full Nebula trajectory →

Merge vs Nebula: 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.

N
Nebula
INFRA · APIS
2.5

Overlay network that rewrote its certificate format, then spent a year fixing what it exposed.

◆ Current state

Nebula is a peer-to-peer mesh VPN built around a certificate authority model. The v1.10.0 release was the pivot: IPv6 and multiple addresses in the overlay, plus a new v2 ASN.1 certificate format with a unified interface for external implementations. Everything since has been consequence management — a P256 signature malleability issue that allowed blocklist bypass, a source-IP acceptance flaw tied to the new multi-address certificates, and a run of fixes around route tables and Windows listeners.

◆ Where it's heading

The project has moved from single-IPv4-per-node assumptions toward a genuinely flexible addressing model, and the security fixes since v1.10.0 map directly onto that change — the new certificate features widened what the code has to validate. v1.11.0 shifts attention to the operational surface instead: structured logging, corrected firewall reject-versus-drop semantics, and Windows WFP filters installed by default.

◆ Prediction

The stated plan to assert low-s signature form when validating certificates is the concrete next step visible in these entries; expect it to land as a breaking validation change in a future release.

Alternatives to Merge and Nebula

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

See all Merge alternatives → · See all Nebula alternatives →

Recent activity from Merge and Nebula

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

  1. 12d agoMergeGitHub connector hits 145 tools; Gateway adds per-project guardrails
  2. 19d agoMergeHundreds of generic MCP connectors land in Agent Handler
  3. 26d agoMergeLink setup flow becomes configurable per integration
  4. 26d agoNebulaBreaking: slog logging, corrected firewall reject/drop directions, Windows WFP filters
  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. 6mo agoNebulaP256 signature malleability allowed blocklist bypass
  9. 6mo agoNebulaFix panic in use_system_route_table introduced by the previous release
  10. 7mo agoNebulaRoute-reload, handshake, and Windows listener fixes after the v1.10 rework
  11. 8mo agoNebulaIPv6 and multiple addresses in the overlay, plus a v2 certificate format
  12. 10mo agoNebulaPackets accepted from erroneous source IPs with unsafe_routes or multi-IP certificates

Frequently asked questions

What is the difference between Merge and Nebula?

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

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

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