authentik
Seven release candidates in eight days, and rc7 quietly carries the endpoint agent.
Comparison · Infra & APIs
Casdoor vs werf
A side-by-side editorial comparison of Casdoor and werf — release velocity, themes, recent moves, and the top alternatives to consider.
Casdoor vs werf: at a glance
What is Casdoor?
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.
What is werf?
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.
Casdoor vs werf: editorial side-by-side
Casdoor
5.0INFRA · APIS
One commit, one release: nine tags in a week, tightening org-level control and credential handling.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
werf
5.0INFRA · APIS
Four release channels, one build engine — werf's changelog is mostly concurrency bugs.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
Alternatives to Casdoor and werf
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 Casdoor or werf.
Ansible
Four maintenance branches move in lockstep, with the actual changes hidden behind a link.
Depot
Depot is expanding from faster builds into the whole CI stack — tests, source control, and its own metal.
Ably
Ably is building an agent transport layer on its realtime core, shipping AI SDK versions every ten days.
Cronicle
Cronicle has spent 2026 hardening the paths that let a scheduler run arbitrary commands
oVirt
A virtualization manager coasting on backports, with releases years apart
See all Casdoor alternatives → · See all werf alternatives →
Recent activity from Casdoor and werf
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 10h agoCasdoorMaster password now hashed; LDAPs hidden on organization add
- 10h agowerfv2.76.0 [alpha]
- 11h agoCasdoorDingTalk provider gains API error and HTTP status handling
- 21h agoCasdoorDefault token format configurable per organization
- 1d agoCasdoorRecords created on save rather than on Add click
- 4d agoCasdoorCasbin group rules follow a user rename
- 4d agowerfSignature tag update (not a release)
- 4d agowerfv2.75.3 [beta,ea,stable]
- 4d agowerfv2.75.4 [alpha]
- 4d agoCasdoorCaptcha input cleared on refresh; cancelled adds clean up
- 5d agowerfv3.1.0 [dev]
- 11d agowerfwerf 3.0.2 build-log progress index fix
Frequently asked questions
What is the difference between Casdoor and werf?
They serve adjacent needs but don't currently overlap on shipped themes. Casdoor 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.
Is Casdoor better than werf?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Casdoor 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.
What are the best alternatives to Casdoor?
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.
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.