GravityKit
GravityKit ships weekly across a whole plugin suite, with an MCP server now part of the lineup.
Comparison · Infra & APIs
Nautobot vs Casdoor
A side-by-side editorial comparison of Nautobot and Casdoor — release velocity, themes, recent moves, and the top alternatives to consider.
Nautobot vs Casdoor: at a glance
What is Nautobot?
A security advisory cycle forced Nautobot to break its REST API on both supported branches at once.
3.2.0 and 2.4.38 shipped the same day in late July carrying CVE fixes that the notes state introduce breaking changes, most often surfacing as unexpected TypeError, AttributeError or KeyError for REST and GraphQL clients. The central change, from advisory GHSA-h8rv-c7c8-cvmx, is that the REST API now enforces object-level view permissions when traversing to related objects via ?depth — beyond depth 1 a related object the caller cannot view is reduced to id, object_type, url and display instead of being serialised in full. 3.2.0 also makes job_kwargs required for create_schedule, enqueue_job, execute_job and run_job_for_testing, with a temporary fallback that warns. 3.1.8 closed an authorization bypass letting a user self-approve a workflow, and 2.4.37 fixed stored XSS in Relationship and Module Family fields.
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.
Nautobot vs Casdoor: editorial side-by-side
Nautobot
5.0INFRA · APIS
A security advisory cycle forced Nautobot to break its REST API on both supported branches at once.
◆ Current state
3.2.0 and 2.4.38 shipped the same day in late July carrying CVE fixes that the notes state introduce breaking changes, most often surfacing as unexpected TypeError, AttributeError or KeyError for REST and GraphQL clients. The central change, from advisory GHSA-h8rv-c7c8-cvmx, is that the REST API now enforces object-level view permissions when traversing to related objects via ?depth — beyond depth 1 a related object the caller cannot view is reduced to id, object_type, url and display instead of being serialised in full. 3.2.0 also makes job_kwargs required for create_schedule, enqueue_job, execute_job and run_job_for_testing, with a temporary fallback that warns. 3.1.8 closed an authorization bypass letting a user self-approve a workflow, and 2.4.37 fixed stored XSS in Relationship and Module Family fields.
◆ Where it's heading
Nautobot is running two supported lines in parallel and treating them as equals: 3.2.2 and 2.4.39 both shipped on 3 August with the same many-to-many change-logging fix. The security work in this window is not incidental — the advisories cluster around authorization boundaries that the API had been permissive about, and closing them meant accepting a compatibility break rather than preserving behaviour. The documentation change acknowledging that managing a Git repository grants arbitrary code execution on the worker is the same instinct applied to expectations rather than code.
◆ Prediction
The job_kwargs fallback is explicitly temporary and warns when used, so its removal in a later release is the stated next step. Expect the paired 2.4.z and 3.x releases to continue landing together.
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.
Alternatives to Nautobot and Casdoor
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 Nautobot or Casdoor.
LibreSpeed
After a two-year redesign, LibreSpeed is adding tests instead of polishing pixels.
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.
Firecracker
Firecracker's microVMs can now grow and shrink devices while running.
See all Nautobot alternatives → · See all Casdoor alternatives →
Recent activity from Nautobot and Casdoor
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 23h 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)
- 3d agoNautobotCable termination filter and GraphQL OpenTelemetry corrections
- 4d agoNautobotMany-to-many change logging and GitRepository sync permissions
- 4d agoCasdoorRFC 8707 resource indicator preserved in fast auto-signin
- 9d agoNautobotPublic API constants and a widened cryptography range
- 11d agoNautobotREST API permission enforcement on related objects; job_kwargs required
- 11d agoNautobotSecurity-driven breaking API changes on the 2.4 branch
- 14d agoNautobotDependency updates mitigating CVEs
Frequently asked questions
What is the difference between Nautobot and Casdoor?
They serve adjacent needs but don't currently overlap on shipped themes. Nautobot 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.
Is Nautobot better than Casdoor?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Nautobot 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.
What are the best alternatives to Nautobot?
Top Nautobot alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Nautobot alternatives" section above for the current picks, or visit /alternatives/nautobot for the full list with editorial commentary on each.
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.