Ansible
Four maintenance branches move in lockstep, with the actual changes hidden behind a link.
A side-by-side editorial comparison of authentik and werf — release velocity, themes, recent moves, and the top alternatives to consider.
Seven release candidates in eight days, and rc7 quietly carries the endpoint agent.
authentik is deep in the 2026.8.0 release-candidate train — seven RCs, six of them fired on a single day in early August and rc7 a week later. Most of the train is CI plumbing, docs, and cherry-picked fixes, but rc7 is an order of magnitude larger and lands substantive work: an Actors primitive in core, an enterprise Agent that requires a domain join and its own API scope, OAuth2 token exchange delegation, and a CAS source integration.
Four release channels, one build engine — werf's changelog is mostly concurrency bugs.
werf publishes across alpha, beta, ea, stable and dev channels simultaneously, so the same fix often appears under several tags within minutes. The 2.x line is in maintenance: the recurring subject is build concurrency — parallel Buildah recovery failures, serialized concurrent base image pulls, retries when a cached image id is missing, races during Docker builds, and panics on late worker logs. A 3.x line runs alongside on the dev channel, where the feature work actually lands.
authentik is deep in the 2026.8.0 release-candidate train — seven RCs, six of them fired on a single day in early August and rc7 a week later. Most of the train is CI plumbing, docs, and cherry-picked fixes, but rc7 is an order of magnitude larger and lands substantive work: an Actors primitive in core, an enterprise Agent that requires a domain join and its own API scope, OAuth2 token exchange delegation, and a CAS source integration.
Two threads run through the branch. The identity surface keeps broadening at the protocol edge — CAS sources, WS-Fed, token exchange delegation, GitGuardian — while the enterprise tier grows an endpoint story with Agents and Actors, pushing authentik past browser-mediated SSO toward machine and device identity. The heavy CI investment across the RCs (test job split into ten, attestation and metadata fixes, release-branch validation) reads as release engineering being hardened ahead of a major.
2026.8.0 GA is the next step, and it is where the Agents and Actors work becomes a real story rather than a cherry-pick line. Expect the RC train to close out with fix-only candidates.
werf publishes across alpha, beta, ea, stable and dev channels simultaneously, so the same fix often appears under several tags within minutes. The 2.x line is in maintenance: the recurring subject is build concurrency — parallel Buildah recovery failures, serialized concurrent base image pulls, retries when a cached image id is missing, races during Docker builds, and panics on late worker logs. A 3.x line runs alongside on the dev channel, where the feature work actually lands.
Development has effectively split. The 2.x channels get defensive fixes to the existing build path, while 3.1.0 on dev carries the additions — embedded kubeconform schemas, a per-project meta-repo safeguard with migration, additional patch files with an option to disable defaults, and a values-schema validation escape hatch. The dev branch is also where the local-loop work sits, with a persistent dev-index so --dev stops re-reading unchanged files and self-healing for a stale worktree lock left by a killed run.
The 2.x channels look set to keep absorbing build-concurrency and host-cleanup fixes while 3.x accumulates features on dev ahead of promotion. When the 3.x line reaches the stable channel isn't something these entries indicate.
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 authentik or werf.
Four maintenance branches move in lockstep, with the actual changes hidden behind a link.
Depot is expanding from faster builds into the whole CI stack — tests, source control, and its own metal.
Ably is building an agent transport layer on its realtime core, shipping AI SDK versions every ten days.
One commit, one release: nine tags in a week, tightening org-level control and credential handling.
Cronicle has spent 2026 hardening the paths that let a scheduler run arbitrary commands
A virtualization manager coasting on backports, with releases years apart
See all authentik alternatives → · See all werf alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. authentik and werf are shipping at a similar cadence (velocity 5.0 vs 5.0, 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. authentik and werf are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
Top authentik alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "authentik alternatives" section above for the current picks, or visit /alternatives/authentik for the full list with editorial commentary on each.
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.