GravityKit
GravityKit ships weekly across a whole plugin suite, with an MCP server now part of the lineup.
Comparison · Infra & APIs
Casdoor vs Firecracker
A side-by-side editorial comparison of Casdoor and Firecracker — release velocity, themes, recent moves, and the top alternatives to consider.
Casdoor vs Firecracker: at a glance
What is Casdoor?
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.
What is Firecracker?
Firecracker's microVMs can now grow and shrink devices while running.
1.16.0 in June added developer-preview hotplug and hot-unplug for PCI virtio block, pmem and net devices on a live microVM, with the guest responsible for rescanning the bus and removing the device first since no notification mechanism exists yet. The same release added vsock Unix socket path overriding on snapshot restore, rate limiting for serial console output with a dropped-bytes metric, and per-callsite log rate limiting. 1.16.1 followed with a vsock fix for connections timing out after restore when a snapshot caught an in-flight TX descriptor. Earlier in the window, 1.15.0 added the VMClock device and Intel Granite Rapids support, and the April patches hardened the PCI transport against CVE-2026-5747.
Casdoor vs Firecracker: editorial side-by-side
Casdoor
5.0INFRA · APIS
Casdoor ships a version per commit — three tags in one day, one feature each.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
Firecracker
0.0INFRA · APIS
Firecracker's microVMs can now grow and shrink devices while running.
◆ Current state
1.16.0 in June added developer-preview hotplug and hot-unplug for PCI virtio block, pmem and net devices on a live microVM, with the guest responsible for rescanning the bus and removing the device first since no notification mechanism exists yet. The same release added vsock Unix socket path overriding on snapshot restore, rate limiting for serial console output with a dropped-bytes metric, and per-callsite log rate limiting. 1.16.1 followed with a vsock fix for connections timing out after restore when a snapshot caught an in-flight TX descriptor. Earlier in the window, 1.15.0 added the VMClock device and Intel Granite Rapids support, and the April patches hardened the PCI transport against CVE-2026-5747.
◆ Where it's heading
The through-line is snapshots and the PCI transport maturing together. Firecracker's value has always been fast boot from a snapshot, and the recent fixes are all in the seams that opens up — TX descriptors in flight when a snapshot is taken, vsock paths that change on restore, virtio device state machines that must be validated the same way on PCI as on MMIO. Hotplug extends the same idea from restore-time to run-time: a microVM that can change shape is one you can keep rather than replace.
◆ Prediction
Hotplug shipped explicitly as a developer preview requiring manual guest bus rescans, so the stated gap is an automatic notification mechanism. That is the obvious next step before the feature leaves preview.
Alternatives to Casdoor and Firecracker
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 Firecracker.
LibreSpeed
After a two-year redesign, LibreSpeed is adding tests instead of polishing pixels.
Nautobot
A security advisory cycle forced Nautobot to break its REST API on both supported branches at once.
Gatekeeper
Gatekeeper grew a package manager for policies — and a benchmark to prove they are not too slow.
GoCD
GoCD's changelog is one maintainer keeping a 2010s CI server running on current runtimes.
Incus
Incus settled its 7.0 LTS, then went straight back to a monthly feature cadence.
See all Casdoor alternatives → · See all Firecracker alternatives →
Recent activity from Casdoor and Firecracker
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agoCasdoorCasbin group rules follow a user through a rename
- 1d agoCasdoorCaptcha refresh and cancelled-add cleanup fixes
- 1d agoCasdoorProducts gain a properties field
- 3d agoCasdoorRecord retention becomes configurable per organization
- 3d agoCasdoorProvider.Scopes column widened to varchar(200)
- 4d agoCasdoorRFC 8707 resource indicator preserved in fast auto-signin
- 1mo agoFirecrackerVsock timeout after snapshot restore, and jailer symlink revert
- 2mo agoFirecrackerFirecracker v1.16.0 ⚡
- 4mo agoFirecrackervirtio-rng entropy cap and PCI transport hardening (CVE-2026-5747)
- 4mo agoFirecrackerCVE-2026-5747 hardening on the 1.15 branch
- 4mo agoFirecrackerTCP SYN options length validation with MMDS enabled
- 5mo agoFirecrackerVMClock device and Intel Granite Rapids support
Frequently asked questions
What is the difference between Casdoor and Firecracker?
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.
Is Casdoor better than Firecracker?
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.
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 Firecracker?
Top Firecracker alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Firecracker alternatives" section above for the current picks, or visit /alternatives/firecracker for the full list with editorial commentary on each.