werf
Four release channels, one build engine — werf's changelog is mostly concurrency bugs.
A side-by-side editorial comparison of authentik and Casdoor — 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.
One commit, one release: nine tags in a week, tightening org-level control and credential handling.
Casdoor ships a release per merged change — nine tags between 3.140.0 and 3.148.0 in eight days, each carrying a single feature or fix under conventional-commit headings. The work in this window clusters in three places: organization-scoped configuration (default token format, record retention days, LDAP visibility), credential and session handling (master password hashing, RFC 8707 resource preservation, captcha input), and the DingTalk identity provider. Nothing here is a large change; the volume is the shape.
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.
Casdoor ships a release per merged change — nine tags between 3.140.0 and 3.148.0 in eight days, each carrying a single feature or fix under conventional-commit headings. The work in this window clusters in three places: organization-scoped configuration (default token format, record retention days, LDAP visibility), credential and session handling (master password hashing, RFC 8707 resource preservation, captcha input), and the DingTalk identity provider. Nothing here is a large change; the volume is the shape.
The pattern is an identity server pushing settings down to the organization level so multi-tenant deployments can diverge — token format, retention window and LDAP exposure are all now per-org rather than global. Alongside that runs a steady grind on the seams where records and authorization go inconsistent: casbin group rules following a user rename, records created on save instead of on click, cancelled adds cleaning up after themselves. It reads as an operationally mature project fixing what multi-tenant use surfaces.
Expect the per-organization configuration surface to keep widening and the per-provider error handling started with DingTalk to reach other social and enterprise providers. Nothing in these entries points to a major version or an architectural change.
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 Casdoor.
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.
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 Casdoor 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 Casdoor 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 Casdoor 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 Casdoor alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Casdoor alternatives" section above for the current picks, or visit /alternatives/casdoor for the full list with editorial commentary on each.