RSS-Bridge
The web's duct-tape RSS layer, now quiet for a year after flipping every bridge on by default.
A side-by-side editorial comparison of AdGuard Home and Dashy — release velocity, themes, recent moves, and the top alternatives to consider.
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.
The self-hosted dashboard finally let you drag things around instead of editing YAML.
Dashy tags a release per merged pull request, so the version number climbs several times a week while most tags carry a single dependabot bump or a translation file. The substance sits in 4.5.0, which added drag-and-drop editing of sections, items and widgets, rebuilt the GitHub stats widget on GitHub's own API with optional token authentication, and expanded number formatting in the custom-api widget. Point releases since have been an OIDC post-logout redirect, item sorting options, and an out-of-memory crash fix.
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.
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.
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.
Dashy tags a release per merged pull request, so the version number climbs several times a week while most tags carry a single dependabot bump or a translation file. The substance sits in 4.5.0, which added drag-and-drop editing of sections, items and widgets, rebuilt the GitHub stats widget on GitHub's own API with optional token authentication, and expanded number formatting in the custom-api widget. Point releases since have been an OIDC post-logout redirect, item sorting options, and an out-of-memory crash fix.
The direction is away from configuration-as-a-file toward direct manipulation, which is the friction that has always separated Dashy from simpler homepage dashboards. The supporting work lines up with it: sorting controls, better handling of long titles, richer widget formatting. The auth-adjacent changes — OIDC logout redirect, logout destination — suggest people are running Dashy behind an identity provider for more than one user.
With drag-and-drop editing shipped, the follow-on is most likely persistence and permissions questions around who can edit a shared dashboard, though these notes do not state that. Expect the per-PR release cadence to continue producing mostly dependency tags.
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 Dashy.
The web's duct-tape RSS layer, now quiet for a year after flipping every bridge on by default.
A daily-shipping indexer proxy whose entire product is a scraper definition file that never stops rotting.
Sonarr's release feed is a two-month run of one-line fixes, most of them about qBittorrent auth.
k0s ships one fix four times a day — the cost of keeping four Kubernetes branches current.
Microcks is quietly wiring LLM example generation into an API mocking tool built for Kubernetes.
Borg's long-running 2.0 beta finally landed packs — and warned it dropped back to alpha quality.
See all AdGuard Home alternatives → · See all Dashy alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — self-hosted — within Infra & APIs. Dashy 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Dashy 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.
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.
Top Dashy alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Dashy alternatives" section above for the current picks, or visit /alternatives/dashy for the full list with editorial commentary on each.