GravityKit
GravityKit ships weekly across a whole plugin suite, with an MCP server now part of the lineup.
Comparison · Infra & APIs
werf vs Gatekeeper
A side-by-side editorial comparison of werf and Gatekeeper — release velocity, themes, recent moves, and the top alternatives to consider.
werf vs Gatekeeper: at a glance
What is werf?
Werf is running a v3 rewrite and a v2 maintenance line side by side, on four release channels.
Werf publishes into parallel channels — alpha, beta, ea, stable, and dev — and the recent entries show two lines moving at once. The 2.75.x releases are maintenance: a host-cleanup fix that stopped it wiping other werf versions' git cache, buildah retries when a cached image id is missing, serialized concurrent base-image pulls. The v3 line is where features land, with 3.0.0 alphas, a 3.0.2 patch, and a 3.1.0 dev build carrying embedded kubeconform schemas, additional patch files, and a per-project meta-repo safeguard.
What is Gatekeeper?
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.
werf vs Gatekeeper: editorial side-by-side
werf
5.0INFRA · APIS
Werf is running a v3 rewrite and a v2 maintenance line side by side, on four release channels.
◆ Current state
Werf publishes into parallel channels — alpha, beta, ea, stable, and dev — and the recent entries show two lines moving at once. The 2.75.x releases are maintenance: a host-cleanup fix that stopped it wiping other werf versions' git cache, buildah retries when a cached image id is missing, serialized concurrent base-image pulls. The v3 line is where features land, with 3.0.0 alphas, a 3.0.2 patch, and a 3.1.0 dev build carrying embedded kubeconform schemas, additional patch files, and a per-project meta-repo safeguard.
◆ Where it's heading
The v3 work is a deploy-engine change more than a version bump: nelm is being pulled in and bumped, values-schema validation is becoming optional to stop service values breaking values.schema.json, and a meta-repo migration path is being built. Meanwhile the build layer is being hardened against concurrency — serialized pulls, retry on missing cached ids, Dockerfile COPY semantics fixed for --parents and --exclude in staged builds. The two lines share build fixes, with the same commits appearing in both 2.75.4 and 3.1.0.
◆ Prediction
Expect the v3 line to keep absorbing build fixes from 2.75.x while nelm and the meta-repo migration stabilise ahead of a wider v3 push. The 2.75.x channel looks like it will stay on bug fixes only.
Gatekeeper
2.5INFRA · APIS
Gatekeeper grew a package manager for policies — and a benchmark to prove they are not too slow.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
Alternatives to werf and Gatekeeper
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 werf or Gatekeeper.
LibreSpeed
After a two-year redesign, LibreSpeed is adding tests instead of polishing pixels.
Nautobot
A security advisory cycle forced Nautobot to break its REST API on both supported branches at once.
GoCD
GoCD's changelog is one maintainer keeping a 2010s CI server running on current runtimes.
Incus
Incus settled its 7.0 LTS, then went straight back to a monthly feature cadence.
Firecracker
Firecracker's microVMs can now grow and shrink devices while running.
See all werf alternatives → · See all Gatekeeper alternatives →
Recent activity from werf and Gatekeeper
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agowerfSignature note appended to the latest release artifacts
- 1d agowerf2.75.3: host cleanup stops wiping other werf versions' git cache
- 1d agowerf2.75.4 alpha: buildah pull retries and serialized base-image pulls
- 1d agowerf3.1.0 dev: embedded kubeconform schemas and meta-repo safeguards
- 8d agowerf3.0.2: build-log progress indices follow real start order
- 8d agowerf3.0.0-alpha.2: deploy flags restored, staged Dockerfile COPY fixes
- 24d agoGatekeeperDeterministic VAP generation stops a reconcile loop
- 1mo agoGatekeeperStatus routing for remote cluster mode; mutation ApplyTo operations
- 4mo agoGatekeeperCI and dependency updates only
- 5mo agoGatekeepergator policy and gator bench: policy as an installable, benchmarked artefact ⚡
Frequently asked questions
What is the difference between werf and Gatekeeper?
They serve adjacent needs but don't currently overlap on shipped themes. werf is currently shipping more aggressively (velocity 5.0 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.
Is werf better than Gatekeeper?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. werf is currently shipping more aggressively (velocity 5.0 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.
What are the best alternatives to werf?
Top werf alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "werf alternatives" section above for the current picks, or visit /alternatives/werf for the full list with editorial commentary on each.
What are the best alternatives to Gatekeeper?
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.