Resend
Resend is wiring itself into every agent runtime it can reach, and now adding the controls to stop a send.
Comparison · Infra & APIs
BorgBackup vs Merge
A side-by-side editorial comparison of BorgBackup and Merge — release velocity, themes, recent moves, and the top alternatives to consider.
BorgBackup vs Merge: at a glance
| Feature | BorgBackup | Merge |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 6.3 | 6.3 |
| Sparks · 30d | 1 | 1 |
| Top themes | backup, deduplication, repository-format, dual-branch | unified api, agent handler, mcp connectors, ai gateway |
| Last editorial update | 14d ago | 14h ago |
| Website | Visit → | — |
What is BorgBackup?
Borg's long-running 2.0 beta finally landed packs — and warned it dropped back to alpha quality.
Borg runs two trains in the same feed. The 1.4.x line is explicitly a refreshed 1.2 — same features and behaviour, with the riskier changes isolated so they could be tested before shipping — and it has taken over as the recommended branch since 1.2.9 was called the final 1.2 release. The 2.0 line has been in beta since well before this window, at b22 as of July 2026, with every release carrying a do-not-use-on-production warning. b22 introduced packs and the maintainers told users to expect alpha stability despite the beta number.
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.
BorgBackup vs Merge: editorial side-by-side
BorgBackup
6.3INFRA · APIS
Borg's long-running 2.0 beta finally landed packs — and warned it dropped back to alpha quality.
◆ Current state
Borg runs two trains in the same feed. The 1.4.x line is explicitly a refreshed 1.2 — same features and behaviour, with the riskier changes isolated so they could be tested before shipping — and it has taken over as the recommended branch since 1.2.9 was called the final 1.2 release. The 2.0 line has been in beta since well before this window, at b22 as of July 2026, with every release carrying a do-not-use-on-production warning. b22 introduced packs and the maintainers told users to expect alpha stability despite the beta number.
◆ Where it's heading
The split is the story: one branch exists purely to keep existing users safe and current, while the other rewrites how data is stored on disk. Packs are the kind of change that determines whether 2.0 ever ships — repository layout affects performance, resumability and every recovery path at once, and the honesty about stability regressing suggests the shakeout is still ahead. The 1.4 line will keep absorbing fixes and low-severity security work in the meantime, and the b18 corruption bug shows why the two trains are kept firmly apart.
◆ Prediction
Expect further 2.0 betas focused on packs stability before anything resembling a release candidate, with 1.4.x continuing to carry routine fixes for production users.
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 BorgBackup 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 BorgBackup 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 BorgBackup alternatives → · See all Merge alternatives →
Recent activity from BorgBackup and Merge
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 12d agoMergeGitHub connector hits 145 tools; Gateway adds per-project guardrails
- 19d agoBorgBackup1.4.5: fixes, a low-severity security fix and small features
- 19d agoMergeHundreds of generic MCP connectors land in Agent Handler ⚡
- 26d agoMergeLink setup flow becomes configurable per integration
- 28d agoBorgBackup2.0.0b22 introduces packs — and warns stability regressed to alpha ⚡
- 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
- 4mo agoBorgBackup1.4.4 maintenance release
- 5mo agoBorgBackup2.0.0b21 beta, testing only
- 7mo agoBorgBackup2.0.0b20 beta, testing only
- 8mo agoBorgBackup1.4.3 maintenance release
Frequently asked questions
What is the difference between BorgBackup and Merge?
They serve adjacent needs but don't currently overlap on shipped themes. BorgBackup and Merge are shipping at a similar cadence (velocity 6.3 vs 6.3, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is BorgBackup better than Merge?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. BorgBackup and Merge are shipping at a similar cadence (velocity 6.3 vs 6.3, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
What are the best alternatives to BorgBackup?
Top BorgBackup alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "BorgBackup alternatives" section above for the current picks, or visit /alternatives/borgbackup 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.