OpenStatus
OpenStatus scopes API keys per resource and lets its MCP server set up monitors.
A side-by-side editorial comparison of AdGuard Home and Pacemaker — release velocity, themes, recent moves, and the top alternatives to consider.
AdGuard Home's 1.0 beta matches stable's security fixes and reworks client settings
AdGuard Home v0.107.80 is a security release on the stable line: a Go update for the 1.27.3 fixes, Multipath TCP disabled for CVE-2026-98432 and macOS 13 dropped. The beta channel moved to the new UI and v1.0.0 numbering at the end of September; v1.0.0-b.2 on November 5 carries the same security changes, splits per-client global settings so blocked services have their own switch, and fixes a run of DHCP and client ID validation bugs.
Pacemaker is putting TLS and X509 auth between its cluster nodes, then hardening the wire code.
Two branches ship in parallel: the 3.0.x line carrying new work and 2.1.x taking backported fixes. The 3.0 series added TLS for Pacemaker Remote nodes, X509 authentication, TLS certificates for remote CIB operations, and then PSK authentication for those same operations, alongside large-IPC and multipart message support. The most recent releases on both branches are the same security train, fixing CVE-2026-10649 and a set of integer overflows and size checks in the remote message code.
AdGuard Home v0.107.80 is a security release on the stable line: a Go update for the 1.27.3 fixes, Multipath TCP disabled for CVE-2026-98432 and macOS 13 dropped. The beta channel moved to the new UI and v1.0.0 numbering at the end of September; v1.0.0-b.2 on November 5 carries the same security changes, splits per-client global settings so blocked services have their own switch, and fixes a run of DHCP and client ID validation bugs.
The two lines are now patched in step on security, while the 1.0 beta absorbs UI corrections and validation fixes ahead of a stable switch. The beta fixes are mostly about settings that did not save or validate correctly, which is the cleanup a new UI needs before it replaces the old one.
Expect more 1.0 betas fixing settings and validation in the new UI; the entries give no date for 1.0 stable.
Two branches ship in parallel: the 3.0.x line carrying new work and 2.1.x taking backported fixes. The 3.0 series added TLS for Pacemaker Remote nodes, X509 authentication, TLS certificates for remote CIB operations, and then PSK authentication for those same operations, alongside large-IPC and multipart message support. The most recent releases on both branches are the same security train, fixing CVE-2026-10649 and a set of integer overflows and size checks in the remote message code.
The cluster's internal transport is being rebuilt on the assumption that the network between nodes is not trusted. Authentication and encryption arrived first, and the fixes that followed, overflow guards and a maximum remote message size, are the hardening pass on the same code paths. Release discipline is heavy and visible: each version ships a release candidate with an identical commit set days earlier, and every 3.0 release documents the regressions it introduced and where they were fixed.
Remote CIB operations now support both X509 certificates and PSK, and the recent fixes all sit in message framing and size limits; further work is most likely to continue in that message-handling code rather than adding another authentication mechanism.
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 Pacemaker.
OpenStatus scopes API keys per resource and lets its MCP server set up monitors.
Hoppscotch adds an enterprise cloud tier and an AI assistant, then turns to desktop trust.
Grype keeps tightening match accuracy while making its database diff tool usable at scale
Snort 3.13.2 is a broad bounds-checking sweep across SMB, HTTP and industrial protocol parsers
DNSimple's origin name servers answer a quarter faster at p90 after erldns work
Scalar's November 5 releases give each API document its own authentication settings
See all AdGuard Home alternatives → · See all Pacemaker alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Pacemaker is currently shipping more aggressively (velocity 6.3 vs 5.0), with 0 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. Pacemaker is currently shipping more aggressively (velocity 6.3 vs 5.0), with 0 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 Pacemaker alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Pacemaker alternatives" section above for the current picks, or visit /alternatives/pacemaker for the full list with editorial commentary on each.