GravityKit
GravityKit ships weekly across a whole plugin suite, with an MCP server now part of the lineup.
A side-by-side editorial comparison of Casdoor and Incus — release velocity, themes, recent moves, and the top alternatives to consider.
Casdoor ships a version per commit — three tags in one day, one feature each.
Casdoor is a self-hosted identity and access platform, and its release process is unusually granular: 3.140.0 through 3.144.0 landed in four days, three of them on August 6 alone, each carrying a single commit. The changes in this window are administrative rather than architectural — per-organization record retention, a properties field on products, a column widened for provider scopes, and Casbin group rules following a user through a rename. Titles are bare version numbers, so the feed reads as noise unless you open each tag.
Incus settled its 7.0 LTS, then went straight back to a monthly feature cadence.
7.0.0 LTS landed in early May and became the supported baseline, followed by 7.0.1 as its first patch. The feature branch has not paused: 7.1 in May cleaned up the issues the LTS surfaced, 7.2 in June added migration-compatible hypervisor flags for stateful migration and aligned node-specific network configuration, and 7.3 at the end of July added native Windows and macOS installers to the build workflow, a QMP command timeout, and /32 and /128 addresses for OCI containers. Underneath, QEMU capabilities like SPICE, 9p and virtio audio are increasingly gated on runtime detection rather than assumed.
Casdoor is a self-hosted identity and access platform, and its release process is unusually granular: 3.140.0 through 3.144.0 landed in four days, three of them on August 6 alone, each carrying a single commit. The changes in this window are administrative rather than architectural — per-organization record retention, a properties field on products, a column widened for provider scopes, and Casbin group rules following a user through a rename. Titles are bare version numbers, so the feed reads as noise unless you open each tag.
Two threads are worth separating from the churn. The first is authorization correctness: moving Casbin group rules on rename and cleaning up records on a cancelled add both close gaps where permission state drifts from the objects it describes. The second is OAuth conformance — 3.140.0 preserves the RFC 8707 resource indicator through the fast auto-signin path, which is the parameter that scopes a token to a specific downstream API. Neither is announced as a theme; both are visible in the commit stream.
Expect the same cadence of single-commit releases to continue, with more OAuth and OIDC conformance details filled in as they are reported. Nothing here signals a larger 3.x milestone or a break in versioning.
7.0.0 LTS landed in early May and became the supported baseline, followed by 7.0.1 as its first patch. The feature branch has not paused: 7.1 in May cleaned up the issues the LTS surfaced, 7.2 in June added migration-compatible hypervisor flags for stateful migration and aligned node-specific network configuration, and 7.3 at the end of July added native Windows and macOS installers to the build workflow, a QMP command timeout, and /32 and /128 addresses for OCI containers. Underneath, QEMU capabilities like SPICE, 9p and virtio audio are increasingly gated on runtime detection rather than assumed.
The rhythm is a monthly feature release running alongside a long-term branch, and the recent work leans toward reach rather than new primitives: clients built natively for Windows and macOS, translations updated in nearly every release, feature gating so the same daemon behaves correctly across host configurations. Stateful migration getting migration-compatible CPU flags is the most operationally significant item, since it is what makes live migration work across non-identical hosts.
The cadence in this window is a feature release roughly every four to six weeks with LTS patches interleaved, so a 7.4 is the expected next step. The entries give no indication of a headline feature queued for it.
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 Incus.
GravityKit ships weekly across a whole plugin suite, with an MCP server now part of the lineup.
After a two-year redesign, LibreSpeed is adding tests instead of polishing pixels.
A security advisory cycle forced Nautobot to break its REST API on both supported branches at once.
Gatekeeper grew a package manager for policies — and a benchmark to prove they are not too slow.
GoCD's changelog is one maintainer keeping a 2010s CI server running on current runtimes.
Firecracker's microVMs can now grow and shrink devices while running.
See all Casdoor alternatives → · See all Incus alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Casdoor and Incus 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. Casdoor and Incus 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 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 Incus alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Incus alternatives" section above for the current picks, or visit /alternatives/incus for the full list with editorial commentary on each.