werf
Four release channels, one build engine — werf's changelog is mostly concurrency bugs.
A side-by-side editorial comparison of authentik and oVirt — 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.
A virtualization manager coasting on backports, with releases years apart
oVirt Engine's release feed is sparse and slowing: 4.5.5 in late 2023, 4.5.6 and a pair of 4.5.3.x backports in early 2024, then nothing until 4.5.7 in December 2025. Almost every entry is a list of targeted fixes and backports rather than features — OVF import edge cases, template handling, NVRAM save/restore logic, CA generation as a non-root user, Keycloak group handling. One CVE, CVE-2024-0822, appears in 4.5.6 and its 4.5.3 backport.
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.
oVirt Engine's release feed is sparse and slowing: 4.5.5 in late 2023, 4.5.6 and a pair of 4.5.3.x backports in early 2024, then nothing until 4.5.7 in December 2025. Almost every entry is a list of targeted fixes and backports rather than features — OVF import edge cases, template handling, NVRAM save/restore logic, CA generation as a non-root user, Keycloak group handling. One CVE, CVE-2024-0822, appears in 4.5.6 and its 4.5.3 backport.
This reads as a mature platform in maintenance rather than one being developed. The parallel 4.5.3.x stream exists purely to carry fixes back to deployments that cannot move, and the two-year gap between 4.5.6 and 4.5.7 says more about the project's momentum than any individual change does. Nothing in these entries points toward new capability.
The entries do not support a confident call on where this goes next; the only observable pattern is long gaps punctuated by accumulated fix rollups, so another such rollup is the most that can be inferred.
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 oVirt.
Four release channels, one build engine — werf's changelog is mostly concurrency bugs.
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
See all authentik alternatives → · See all oVirt alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. authentik is currently shipping more aggressively (velocity 5.0 vs 0.0), 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. authentik is currently shipping more aggressively (velocity 5.0 vs 0.0), 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.
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 oVirt alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "oVirt alternatives" section above for the current picks, or visit /alternatives/ovirt for the full list with editorial commentary on each.