ESPHome
ESPHome opens the 2026.11 beta days after its second October patch.
A side-by-side editorial comparison of Apideck and Gatekeeper — release velocity, themes, recent moves, and the top alternatives to consider.
Apideck rebuilds its SD Worx connector after the old login method is switched off.
Apideck added an SD Worx web service connector on November 3 that uses certificate-based OIDC credentials, because SD Worx no longer activates the username and password access the SOAP connector relied on. Existing connections keep working, and the old connector now points to the new one as its migration target. It covers employees and daily time-off records, within SD Worx's limit of 1,000 employee-months per day.
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.
Apideck added an SD Worx web service connector on November 3 that uses certificate-based OIDC credentials, because SD Worx no longer activates the username and password access the SOAP connector relied on. Existing connections keep working, and the old connector now points to the new one as its migration target. It covers employees and daily time-off records, within SD Worx's limit of 1,000 employee-months per day.
After a summer of new European accounting and HRIS connectors, the newest entry is maintenance driven by a vendor's auth change. Apideck now handles migrations inside the catalog by marking legacy connectors with a target.
The entries show a six-week gap before this one, so the cadence of new connectors is unclear; expect more migrations as vendors retire password-based access.
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.
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 Apideck or Gatekeeper.
ESPHome opens the 2026.11 beta days after its second October patch.
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.
Dragonfly opens a 2.1 line with metrics that explain why replicas drop.
See all Apideck alternatives → · See all Gatekeeper alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Apideck and Gatekeeper are shipping at a similar cadence (velocity 2.5 vs 2.5, both within Sparkpulse's "active" band). 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. Apideck and Gatekeeper are shipping at a similar cadence (velocity 2.5 vs 2.5, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
Top Apideck alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Apideck alternatives" section above for the current picks, or visit /alternatives/apideck for the full list with editorial commentary on each.
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.