ESPHome
ESPHome opens the 2026.11 beta days after its second October patch.
A side-by-side editorial comparison of Gatekeeper and Redocly — release velocity, themes, recent moves, and the top alternatives to consider.
Gatekeeper grew a package manager for policies — and a benchmark to prove they are not too slow.
3.22.0-rc.0 in February introduced two CLI subcommands that change how policies are handled rather than what they express: gator policy, a brew-inspired tool for discovering, installing, upgrading and uninstalling policies from the gatekeeper-library, and gator bench, which benchmarks Rego and CEL engines with latency percentiles, throughput, memory profiling and baseline comparison for CI regression detection. The same release enabled sync-vap-enforcement-scope by default and gave both CEL and Rego access to namespace context during admission and audit. Since then, 3.23.0-rc.1 added status resource routing for remote cluster mode, and 3.24.0-beta.0 made generated ValidatingAdmissionPolicy output deterministic to stop a reconcile loop.
Redocly forks Markdoc and points Open in Claude at the desktop app.
Redocly's November 4 package release moved its docs stack to @redocly/markdoc, its own fork of Markdoc, with existing custom tags still working. The same release renders GitHub alert syntax as admonitions, sends Open in Claude to a Claude Code session in the desktop app, adds enum menus to the Try it console, and fixes mock servers that leaked earlier responses. The day before, config 0.71.0 made the docs agent opt-out.
3.22.0-rc.0 in February introduced two CLI subcommands that change how policies are handled rather than what they express: gator policy, a brew-inspired tool for discovering, installing, upgrading and uninstalling policies from the gatekeeper-library, and gator bench, which benchmarks Rego and CEL engines with latency percentiles, throughput, memory profiling and baseline comparison for CI regression detection. The same release enabled sync-vap-enforcement-scope by default and gave both CEL and Rego access to namespace context during admission and audit. Since then, 3.23.0-rc.1 added status resource routing for remote cluster mode, and 3.24.0-beta.0 made generated ValidatingAdmissionPolicy output deterministic to stop a reconcile loop.
The centre of gravity is moving from the admission controller to the tooling around it. Policies are becoming artefacts you install from a library at a version, benchmark against a baseline in CI, and test before they reach a cluster — which is the lifecycle application code already has and policy generally has not. Underneath, the ValidatingAdmissionPolicy path keeps maturing as Gatekeeper hands more enforcement to the Kubernetes-native mechanism it now generates.
Remote cluster mode gained status routing but the entries describe only that piece, so how far multi-cluster enforcement extends is unclear from these notes. The releases in this window are all beta and release candidates, so a 3.24.0 stable is the near-term milestone.
Redocly's November 4 package release moved its docs stack to @redocly/markdoc, its own fork of Markdoc, with existing custom tags still working. The same release renders GitHub alert syntax as admonitions, sends Open in Claude to a Claude Code session in the desktop app, adds enum menus to the Try it console, and fixes mock servers that leaked earlier responses. The day before, config 0.71.0 made the docs agent opt-out.
Redocly is taking more of its stack in-house and renaming it around one platform: Reunite options become platform, mcp.docs folds into mcp, and Markdoc is now a fork. The AI hooks point at the desktop agents rather than web chats, which fits the opt-out docs agent shipped a day earlier.
Expect the deprecated reunite and mcp.docs names to become errors in a later config release, and more Markdoc tags only Redocly's fork supports.
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 Gatekeeper or Redocly.
ESPHome opens the 2026.11 beta days after its second October patch.
Apideck rebuilds its SD Worx connector after the old login method is switched off.
Currents lists itself in the Claude and ChatGPT/Codex plugin directories.
Jackett ships a daily build to keep hundreds of torrent indexers working as sites move and close.
Hatchet adds magic-link login and publishes its CLI on npm.
Dragonfly opens a 2.1 line with metrics that explain why replicas drop.
See all Gatekeeper alternatives → · See all Redocly alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Redocly is currently shipping more aggressively (velocity 6.3 vs 2.5), 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 6.3 vs 2.5), 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 Gatekeeper alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Gatekeeper alternatives" section above for the current picks, or visit /alternatives/gatekeeper 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.