GravityKit
GravityKit folds every GravityView extension into one Pro plugin.
A side-by-side editorial comparison of Clair and Gatekeeper — release velocity, themes, recent moves, and the top alternatives to consider.
Clair 4.10 RC can read SBOMs to match Java vulnerabilities.
Clair cut its first 4.10.0 release candidate on November 13, eleven months after 4.9.0. Its Java indexers can now read CycloneDX SBOM files and treat them as the source of truth, and Red Hat's VEX data now covers Maven advisories, so Java packages in Red Hat images can be matched. It also reduces memory use when many packages share a source package.
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.
Clair cut its first 4.10.0 release candidate on November 13, eleven months after 4.9.0. Its Java indexers can now read CycloneDX SBOM files and treat them as the source of truth, and Red Hat's VEX data now covers Maven advisories, so Java packages in Red Hat images can be matched. It also reduces memory use when many packages share a source package.
Since 4.8 Clair has moved from Red Hat's older OVAL data to VEX, and each release follows Red Hat's security data more closely. 4.10 adds SBOMs as an input, so Clair can match what an image's own manifest declares, not only what it finds on disk.
More 4.10 release candidates and then a final are likely; the long gap between releases suggests that could take weeks.
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 Clair or Gatekeeper.
GravityKit folds every GravityView extension into one Pro plugin.
Payload's v4 beta.9 keeps every past image crop and raises the Node floor again.
Nautobot 3.3 alpha 2 adds test helpers and a cable location filter after 3.2.9's token-leak fix.
Shuffle tags builds almost daily, but the notes are empty.
KrakenD's community edition is shipping only dependency bumps.
Velociraptor's recent releases are mostly about patching CVEs.
See all Clair 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. Clair 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. Clair 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 Clair alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Clair alternatives" section above for the current picks, or visit /alternatives/clair 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.