ESPHome
ESPHome opens the 2026.11 beta days after its second October patch.
A side-by-side editorial comparison of Gatekeeper and Home Assistant — 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.
Home Assistant folds HACS into core as a built-in Marketplace for community add-ons.
Home Assistant ships one release a month, and 2026.11 is the largest yet. HACS, the community store for custom integrations, cards and themes, is now built in as the Marketplace under Settings, on every installation type and without a GitHub account. The same release lets targets exclude items, reworks entity naming in a backward-incompatible way, and adds Matter cameras with talk-back, LoRaWAN, local-drive backups, trace tools and 38 integrations.
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.
Home Assistant ships one release a month, and 2026.11 is the largest yet. HACS, the community store for custom integrations, cards and themes, is now built in as the Marketplace under Settings, on every installation type and without a GitHub account. The same release lets targets exclude items, reworks entity naming in a backward-incompatible way, and adds Matter cameras with talk-back, LoRaWAN, local-drive backups, trace tools and 38 integrations.
The 2026 releases keep moving power-user features out of YAML and side installs into the default UI: purpose-specific triggers, trigger IDs, card picker, and now the community store itself. With HACS inside the release process, the project takes on responsibility for third-party code it previously kept at arm's length. Debuggability is the second thread, with traces, per-integration logs and an action record arriving together.
Expect follow-up releases to add curation or quality signals to the Marketplace, since the notes call this its first version. Entity naming fallout will likely drive fixes in 2026.12.
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 Home Assistant.
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.
Redocly forks Markdoc and points Open in Claude at the desktop app.
See all Gatekeeper alternatives → · See all Home Assistant alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Home Assistant is currently shipping more aggressively (velocity 6.3 vs 2.5), 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. Home Assistant is currently shipping more aggressively (velocity 6.3 vs 2.5), 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 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 Home Assistant alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Home Assistant alternatives" section above for the current picks, or visit /alternatives/home-assistant for the full list with editorial commentary on each.