ESPHome
ESPHome 2026.9.0 ships template climate component, OTA encryption with API key, and ESP-NOW for ESP32-P4
A side-by-side editorial comparison of AdGuard Home and Redocly — release velocity, themes, recent moves, and the top alternatives to consider.
AdGuard Home patches a DNS-over-QUIC resource exhaustion advisory and moves edge to the new UI
v0.107.79 is presented as a stability release but carries the security work: a Go update for the vulnerabilities fixed in 1.26.6 and hardening against resource exhaustion over DNS-over-QUIC, published as GHSA-w6v6-f44j-3rj2. Alongside it, bootstrap server config accepts comments, install APIs gain a language property, static lease hostnames can be removed over HTTP, strict_sni_check is deprecated, and DNS64 stops treating unresolved CNAME/DNAME answers as the end of the chain.
Redocly ships a built-in MCP server page across its entire docs platform, with public and authenticated endpoints
Redocly just landed a coordinated 0.137.0 release across Reef, Realm, Revel, and Redoc, anchored by a structural addition: every developer portal now ships a `/mcp` page with setup instructions for Claude, ChatGPT/Codex, and raw JSON config, plus an opt-in `/mcp-public` endpoint for serving anonymous-accessible content without authentication. The MCP code mode got reliability improvements, OAuth discovery was fixed to spec (RFC 8414), and four CVEs were patched in the same release. The breadth of the drop — 20 features and 67+ bug fixes across packages — reflects a team that released a major capability and simultaneously cleared accumulated UX debt.
v0.107.79 is presented as a stability release but carries the security work: a Go update for the vulnerabilities fixed in 1.26.6 and hardening against resource exhaustion over DNS-over-QUIC, published as GHSA-w6v6-f44j-3rj2. Alongside it, bootstrap server config accepts comments, install APIs gain a language property, static lease hostnames can be removed over HTTP, strict_sni_check is deprecated, and DNS64 stops treating unresolved CNAME/DNAME answers as the end of the chain.
Two channels run in parallel — the 0.107 stable line and the 0.108 beta — and the edge channel has now switched to the new UI and versioning scheme, which is the first concrete sign that the 0.108 work is being staged for release. Stable releases keep absorbing protocol correctness fixes and DNS-over-QUIC hardening.
With edge already on the new UI and versioning scheme, the 0.108 line is the likely destination for that switch, and strict_sni_check being deprecated now points to its removal there.
Redocly just landed a coordinated 0.137.0 release across Reef, Realm, Revel, and Redoc, anchored by a structural addition: every developer portal now ships a `/mcp` page with setup instructions for Claude, ChatGPT/Codex, and raw JSON config, plus an opt-in `/mcp-public` endpoint for serving anonymous-accessible content without authentication. The MCP code mode got reliability improvements, OAuth discovery was fixed to spec (RFC 8414), and four CVEs were patched in the same release. The breadth of the drop — 20 features and 67+ bug fixes across packages — reflects a team that released a major capability and simultaneously cleared accumulated UX debt.
Redocly is repositioning every hosted API portal as a first-class AI agent resource, not just a human-readable docs site. The public MCP endpoint especially matters: it enables AI coding assistants to read API docs without credentials, which removes the main friction for developers integrating via LLM tools. Security hardening (audience validation, OAuth compliance, CVE patching) in the same release signals this isn't a prototype feature — it's going into production. The next logical step is deeper programmatic authoring via the MCP surface, not just reading.
Expect Redocly to add MCP write-path features — letting AI agents update API documentation or sync specs directly — once the read-path is fully stable. The visual review check in Reunite suggests a git-workflow integration direction.
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 Redocly.
ESPHome 2026.9.0 ships template climate component, OTA encryption with API key, and ESP-NOW for ESP32-P4
Expo kills its AI agent, SDK 58 beta arrives as EAS observability stack hits GA
Jackett in pure tracker-maintenance mode, daily domain and category updates only
Skipper adds Redis as a distributed L2 cache backend amid a high-frequency patch cadence.
Kubernetes v1.37 matures its memory management and scheduling stack for AI/ML workloads.
GitHub Copilot gets cost-aware inference tiers as enterprise AI tooling tightens across the platform.
See all AdGuard Home alternatives → · See all Redocly alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — security — within Infra & APIs. Redocly is currently shipping more aggressively (velocity 7.5 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. Redocly is currently shipping more aggressively (velocity 7.5 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 Redocly alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Redocly alternatives" section above for the current picks, or visit /alternatives/redocly for the full list with editorial commentary on each.