DNSControl
DNSControl is rewriting its record internals in public, one release candidate at a time
A side-by-side editorial comparison of Casdoor and Fission — release velocity, themes, recent moves, and the top alternatives to consider.
Casdoor ships a version bump per commit, and the recent run is all tenancy hardening.
Casdoor tags a release on nearly every merge — ten versions between August 4 and August 10, most carrying a single commit. The recent run clusters on two threads: multi-tenant isolation (cross-organization webhook restrictions, organization checks on add APIs, Casbin group rules following user renames) and DingTalk integration repair. Individually each release is small; read together they are a sustained pass over organization boundaries.
Fission's release feed carries only RC tags, and none of them say what shipped
Every entry here is a release candidate — v1.22.0-rc1 and rc2, v1.23.0-rc1, v1.25.0-rc1 — with no final release appearing between them, and the version sequence skips 1.24 entirely. The bodies are whatever the tagging commit said, so what reaches this feed is a dependabot bump, a CLI tool-version refresh, a codegen sync explicitly labelled as having no functional change, and one entry that is nothing but links to an external release-highlights page. The actual release notes live on the project's documentation site, not here.
Casdoor tags a release on nearly every merge — ten versions between August 4 and August 10, most carrying a single commit. The recent run clusters on two threads: multi-tenant isolation (cross-organization webhook restrictions, organization checks on add APIs, Casbin group rules following user renames) and DingTalk integration repair. Individually each release is small; read together they are a sustained pass over organization boundaries.
The organization is becoming the unit of configuration. Record retention days, default token format, master-password hashing and LDAP visibility all became per-organization concerns inside a single week. That is the shape of a project hardening for multi-tenant deployment rather than adding end-user features, and the cross-organization webhook restriction in the newest release is the clearest statement of it so far.
Expect the per-organization configuration surface to keep growing and more cross-organization access checks on the remaining endpoints, since the last week has moved steadily in that direction. The per-commit release cadence means this will arrive as another ten small versions rather than one milestone.
Every entry here is a release candidate — v1.22.0-rc1 and rc2, v1.23.0-rc1, v1.25.0-rc1 — with no final release appearing between them, and the version sequence skips 1.24 entirely. The bodies are whatever the tagging commit said, so what reaches this feed is a dependabot bump, a CLI tool-version refresh, a codegen sync explicitly labelled as having no functional change, and one entry that is nothing but links to an external release-highlights page. The actual release notes live on the project's documentation site, not here.
What can be read from these tags is infrastructure maintenance rather than product direction: Go dependency updates, helm and kind and skaffold and cosign version refreshes, and regenerated swagger and applyconfiguration files kept in sync with CEL and webhook validation comments in the core API types. That last one is the only entry hinting at anything structural — CEL-based validation on the API types implies declarative validation moving into the CRDs — but the commit itself changes only generated output.
This feed does not carry enough to predict product direction; until final releases or their notes appear here rather than only candidate tags, any read of where Fission is heading would be guesswork.
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 Fission.
DNSControl is rewriting its record internals in public, one release candidate at a time
Kaniko's release feed stops dead in June 2024 after a patch that undid its own change
mod_auth_openidc audited itself, found eight holes, and broke every session on the way out
Kubernetes CNI maintaining four release branches at once, mostly to carry CVE fixes back.
KeePass-compatible password manager frozen mid-patch-run since 2021.
Overlay network that rewrote its certificate format, then spent a year fixing what it exposed.
See all Casdoor alternatives → · See all Fission alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Casdoor 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. Casdoor 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 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.
Top Fission alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Fission alternatives" section above for the current picks, or visit /alternatives/fission for the full list with editorial commentary on each.