GravityKit
GravityKit ships weekly across a whole plugin suite, with an MCP server now part of the lineup.
Comparison · Infra & APIs
Firecracker vs GoCD
A side-by-side editorial comparison of Firecracker and GoCD — release velocity, themes, recent moves, and the top alternatives to consider.
Firecracker vs GoCD: at a glance
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.
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.
Firecracker vs GoCD: editorial side-by-side
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.
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.
Alternatives to Firecracker and GoCD
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 Firecracker or GoCD.
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.
Incus
Incus settled its 7.0 LTS, then went straight back to a monthly feature cadence.
runc
runc now publishes an end-of-life calendar, and three branches shipped the same CVE fix in two days.
See all Firecracker alternatives → · See all GoCD alternatives →
Recent activity from Firecracker and GoCD
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 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
- 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 Firecracker and GoCD?
They serve adjacent needs but don't currently overlap on shipped themes. GoCD 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 Firecracker better than GoCD?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. GoCD 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 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.
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.