Resend
Resend is wiring itself into every agent runtime it can reach, and now adding the controls to stop a send.
Comparison · Infra & APIs
Headscale vs Merge
A side-by-side editorial comparison of Headscale and Merge — release velocity, themes, recent moves, and the top alternatives to consider.
Headscale vs Merge: at a glance
| Feature | Headscale | Merge |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 0.0 | 6.3 |
| Sparks · 30d | 0 | 1 |
| Top themes | self-hosted, tailscale, access-control, acl | unified api, agent handler, mcp connectors, ai gateway |
| Last editorial update | 12d ago | 13h ago |
| Website | Visit → | — |
What is Headscale?
Headscale stops approximating Tailscale's control plane and starts matching it on purpose.
Headscale's visible work is a single long beta line, 0.29.0-beta.1 through beta.4, spread from late May to mid-June. The release notes are cumulative and identical across all four betas, describing a rebuilt ACL packet-filter implementation validated against real Tailscale clients and the official SaaS, plus support for SSH rules using the check action with OIDC or CLI approval. Minimum supported Tailscale client is pinned at v1.80.0.
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.
Headscale vs Merge: editorial side-by-side
Headscale
0.0INFRA · APIS
Headscale stops approximating Tailscale's control plane and starts matching it on purpose.
◆ Current state
Headscale's visible work is a single long beta line, 0.29.0-beta.1 through beta.4, spread from late May to mid-June. The release notes are cumulative and identical across all four betas, describing a rebuilt ACL packet-filter implementation validated against real Tailscale clients and the official SaaS, plus support for SSH rules using the check action with OIDC or CLI approval. Minimum supported Tailscale client is pinned at v1.80.0.
◆ Where it's heading
The project is treating behavioural parity with the hosted service as something to be tested rather than assumed — generating ACL test cases systematically against the SaaS and fixing the differences that surfaced. Adding interactive SSH approval moves headscale past connectivity into access control, which is the harder half of what Tailscale sells. The long beta series without a stable cut suggests the maintainers are unwilling to ship that surface until the packet-filter differences are fully closed.
◆ Prediction
A stable 0.29.0 is the obvious next step once the beta line settles, since the feature set has been frozen across four betas. What remains unclear from these notes is what actually changed between the betas, as each restates the same cumulative text.
Merge
6.3INFRA · APIS
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.
Alternatives to Headscale and Merge
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 Headscale or Merge.
DNSControl
DNSControl v5 is feature-frozen with a ship date, and rc9 is pure provider cleanup
Casdoor
Casdoor is spending its release cadence moving auth checks from the client to the server
ESPHome
ESPHome ships on a calendar, and the August beta train is now five builds deep
Strimzi
Strimzi's 1.2.0 candidate closes with a logging fix and nothing else
Prowler
Prowler's assistant decides what to do with findings; the patches keep the scanner honest
See all Headscale alternatives → · See all Merge alternatives →
Recent activity from Headscale and Merge
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 12d agoMergeGitHub connector hits 145 tools; Gateway adds per-project guardrails
- 19d agoMergeHundreds of generic MCP connectors land in Agent Handler ⚡
- 26d agoMergeLink setup flow becomes configurable per integration
- 1mo agoMergeEmbedded Routing Stack gives Gateway per-customer model controls
- 1mo agoMergeGateway breakout page for the week already covered by Week 2
- 1mo agoMergeUnified breakout page for the week already covered by Week 3
- 2mo agoHeadscaleRegister user-lookup error reworded to match the CLI test
- 2mo agoHeadscalev0.29.0-beta.4
- 2mo agoHeadscalev0.29.0-beta.3
- 2mo agoHeadscalev0.29.0-beta.2
- 2mo agoHeadscale0.29.0 beta: SSH check actions and Tailscale ACL parity ⚡
Frequently asked questions
What is the difference between Headscale and Merge?
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 Headscale better than Merge?
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 Headscale?
Top Headscale alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Headscale alternatives" section above for the current picks, or visit /alternatives/headscale for the full list with editorial commentary on each.
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.