Resend
Resend is wiring itself into every agent runtime it can reach, and now adding the controls to stop a send.
Comparison · Infra & APIs
Helm vs Merge
A side-by-side editorial comparison of Helm and Merge — release velocity, themes, recent moves, and the top alternatives to consider.
Helm vs Merge: at a glance
| Feature | Helm | Merge |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 5.0 | 6.3 |
| Sparks · 30d | 0 | 1 |
| Top themes | kubernetes, package-management, release-engineering, security-patches | unified api, agent handler, mcp connectors, ai gateway |
| Last editorial update | 4d ago | 12h ago |
| Website | Visit → | — |
What is Helm?
Helm runs two release trains in lockstep while v3 walks toward end-of-life.
Helm ships v4 and v3 in paired patch releases, usually minutes apart, with v3 explicitly flagged as approaching end-of-life since v3.21.0. The August patches split along that line: v4.2.4 carries functional fixes — error reporting for helm template --debug --show-only, logs collected from all containers in test pods, a panic on repeated IsReachable calls, missing conflict retry under server-side apply, and registry push token scoping — while v3.21.4 is almost entirely backported dependency bumps closing Go vulnerability advisories. Several releases in this window carry no notable changes at all beyond platform checksums.
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.
Helm vs Merge: editorial side-by-side
Helm
5.0INFRA · APIS
Helm runs two release trains in lockstep while v3 walks toward end-of-life.
◆ Current state
Helm ships v4 and v3 in paired patch releases, usually minutes apart, with v3 explicitly flagged as approaching end-of-life since v3.21.0. The August patches split along that line: v4.2.4 carries functional fixes — error reporting for helm template --debug --show-only, logs collected from all containers in test pods, a panic on repeated IsReachable calls, missing conflict retry under server-side apply, and registry push token scoping — while v3.21.4 is almost entirely backported dependency bumps closing Go vulnerability advisories. Several releases in this window carry no notable changes at all beyond platform checksums.
◆ Where it's heading
The two branches are diverging in kind rather than in version number. New behavior lands on v4; v3 receives security backports and Kubernetes client library alignment, which is what a maintenance branch looks like before it is retired. Within v4, the recurring theme is concurrency and lifecycle correctness — data races between upgrade and rollback, a WaitForDelete watch cancelled too early, a race fix reverted in v4.2.2 and revisited later — suggesting the v4 rewrite surfaced timing behavior the v3 code path never exercised.
◆ Prediction
Expect the v3 line to narrow to security backports only until its end-of-life date lands, with functional work continuing exclusively on the v4.2.x patch series.
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 Helm 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 Helm 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
Recent activity from Helm and Merge
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 4d agoHelmv4 patch: template debugging, test pod logs, apply conflict retry
- 4d agoHelmv3 patch: four Go vulnerability advisories closed via backports
- 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
- 1mo agoHelmHelm v3.21.3
- 1mo agoHelmHelm v4.2.3
- 1mo agoHelmv3 client libraries aligned to Kubernetes v1.36
- 2mo agoHelmv4 patch reverting a WaitForDelete race fix
Frequently asked questions
What is the difference between Helm and Merge?
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 Helm 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 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 Helm?
Top Helm alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Helm alternatives" section above for the current picks, or visit /alternatives/helm 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.