GravityKit
GravityKit ships weekly across a whole plugin suite, with an MCP server now part of the lineup.
Comparison · Infra & APIs
GoCD vs Nautobot
A side-by-side editorial comparison of GoCD and Nautobot — release velocity, themes, recent moves, and the top alternatives to consider.
GoCD vs Nautobot: at a glance
What is GoCD?
GoCD's changelog is one maintainer keeping a 2010s CI server running on current runtimes.
The visible work is almost entirely platform upkeep, and nearly all of it is authored by a single contributor. The baseline has been walked forward repeatedly — Java 17 minimum, then building and packaging on Java 21, then Java 21 as the hard minimum with macOS x64 support dropped — while container images moved from Alpine and CentOS Stream to Wolfi and Chainguard, Rails went from 6.1 through 7.1, and Hamcrest was replaced by AssertJ across the test suite. 26.1.0 is the exception in substance: it carries security fixes described as affecting all prior GoCD versions, with an explicit recommendation to upgrade as soon as possible.
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.
GoCD vs Nautobot: editorial side-by-side
GoCD
5.0INFRA · APIS
GoCD's changelog is one maintainer keeping a 2010s CI server running on current runtimes.
◆ Current state
The visible work is almost entirely platform upkeep, and nearly all of it is authored by a single contributor. The baseline has been walked forward repeatedly — Java 17 minimum, then building and packaging on Java 21, then Java 21 as the hard minimum with macOS x64 support dropped — while container images moved from Alpine and CentOS Stream to Wolfi and Chainguard, Rails went from 6.1 through 7.1, and Hamcrest was replaced by AssertJ across the test suite. 26.1.0 is the exception in substance: it carries security fixes described as affecting all prior GoCD versions, with an explicit recommendation to upgrade as soon as possible.
◆ Where it's heading
This is a mature product in custodial maintenance rather than development. The pattern across releases is dependency deduplication, dead code removal, deprecation cleanup and base image swaps — the work that keeps a large Rails and Java codebase installable and patchable on current operating systems. Feature entries are rare enough that their absence, rather than any particular change, is the signal.
◆ Prediction
Given the security advisory in 26.1.0 covers all earlier versions and the release notes point offsite for detail, the practical next step for operators is that upgrade. The entries show no queued feature work to project from.
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.
Alternatives to GoCD and Nautobot
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 GoCD or Nautobot.
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.
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.
runc
runc now publishes an end-of-life calendar, and three branches shipped the same CVE fix in two days.
See all GoCD alternatives → · See all Nautobot alternatives →
Recent activity from GoCD and Nautobot
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 3d agoNautobotCable termination filter and GraphQL OpenTelemetry corrections
- 4d agoNautobotMany-to-many change logging and GitRepository sync permissions
- 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
- 23d agoGoCDJava 21 minimum, macOS x64 dropped, and security fixes
- 23d agoGoCDJava 17 baseline and Wolfi container images
- 23d agoGoCDJava 21 LTS by default; CentOS Stream images removed
- 23d agoGoCDPassword toggle fix and Sass deprecation cleanup
- 23d agoGoCDDependency and container image housekeeping
- 23d agoGoCDTest suite migrated from Hamcrest to AssertJ
Frequently asked questions
What is the difference between GoCD and Nautobot?
They serve adjacent needs but don't currently overlap on shipped themes. GoCD and Nautobot 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 GoCD better than Nautobot?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. GoCD and Nautobot 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 GoCD?
Top GoCD alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "GoCD alternatives" section above for the current picks, or visit /alternatives/gocd for the full list with editorial commentary on each.
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.