Dashy
The self-hosted dashboard finally let you drag things around instead of editing YAML.
Comparison · Infra & APIs
AdGuard Home vs BorgBackup
A side-by-side editorial comparison of AdGuard Home and BorgBackup — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:dual-branch
AdGuard Home vs BorgBackup: at a glance
What is AdGuard Home?
AdGuard Home is spending most of its release capacity on DNS protocol vulnerabilities.
Two trains run in parallel: the 0.107.x stable line and a long-running 0.108.0 beta series now at b.90. Security dominates both — one stable release opened by admitting security changes take up over half its changelog. The reported issues cluster in the encrypted-DNS stack: JIGGLE attacks, loose validation of DoH upstream responses, unbounded reads on QUIC connections, DNS-over-QUIC resource exhaustion, and a path traversal in GLiNET-mode authorization. Feature work in the window is minor: comments in bootstrap server configuration, removing a static lease hostname via the HTTP API, day units in YAML durations.
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.
AdGuard Home vs BorgBackup: editorial side-by-side
AdGuard Home
5.0INFRA · APIS
AdGuard Home is spending most of its release capacity on DNS protocol vulnerabilities.
◆ Current state
Two trains run in parallel: the 0.107.x stable line and a long-running 0.108.0 beta series now at b.90. Security dominates both — one stable release opened by admitting security changes take up over half its changelog. The reported issues cluster in the encrypted-DNS stack: JIGGLE attacks, loose validation of DoH upstream responses, unbounded reads on QUIC connections, DNS-over-QUIC resource exhaustion, and a path traversal in GLiNET-mode authorization. Feature work in the window is minor: comments in bootstrap server configuration, removing a static lease hostname via the HTTP API, day units in YAML durations.
◆ Where it's heading
The 0.108 beta has been running long enough that its interesting signal is the edge channel switching to the new UI and versioning scheme — the rewrite is reaching users before the beta closes. Meanwhile the security cadence is community-driven: nearly every fix credits an external reporter, and fixes land in a beta and its stable counterpart within days or the same day. That is a project whose attack surface is its protocol implementations, and whose defence is a fast disclosure-to-patch loop rather than architectural change.
◆ Prediction
Expect the encrypted-DNS transports to keep generating reports and same-week patches on both branches, and the new UI to widen from the edge channel toward beta as 0.108 approaches release.
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.
Alternatives to AdGuard Home and BorgBackup
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 AdGuard Home or BorgBackup.
RSS-Bridge
The web's duct-tape RSS layer, now quiet for a year after flipping every bridge on by default.
Jackett
A daily-shipping indexer proxy whose entire product is a scraper definition file that never stops rotting.
Sonarr
Sonarr's release feed is a two-month run of one-line fixes, most of them about qBittorrent auth.
k0s
k0s ships one fix four times a day — the cost of keeping four Kubernetes branches current.
Microcks
Microcks is quietly wiring LLM example generation into an API mocking tool built for Kubernetes.
See all AdGuard Home alternatives → · See all BorgBackup alternatives →
Recent activity from AdGuard Home and BorgBackup
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 4d agoBorgBackup1.4.5: fixes, a low-severity security fix and small features
- 5d agoAdGuard HomeAdGuard Home v0.108.0-b.90
- 13d agoBorgBackup2.0.0b22 introduces packs — and warns stability regressed to alpha ⚡
- 21d agoAdGuard HomeAdGuard Home v0.108.0-b.89
- 21d agoAdGuard HomeAdGuard Home v0.107.78
- 2mo agoAdGuard HomeAdGuard Home v0.108.0-b.88
- 2mo agoAdGuard HomeAdGuard Home v0.107.77
- 2mo agoAdGuard HomeAdGuard Home v0.108.0-b.87
- 4mo agoBorgBackup1.4.4 maintenance release
- 4mo 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 AdGuard Home and BorgBackup?
Both compete on the same themes — dual-branch — within Infra & APIs. BorgBackup 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 AdGuard Home better than BorgBackup?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. BorgBackup 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 AdGuard Home?
Top AdGuard Home alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "AdGuard Home alternatives" section above for the current picks, or visit /alternatives/adguard-home for the full list with editorial commentary on each.
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.