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 Incus and GoCD — release velocity, themes, recent moves, and the top alternatives to consider.
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.
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.
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.
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.
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.
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.
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 Incus or GoCD.
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.
Firecracker's microVMs can now grow and shrink devices while running.
runc now publishes an end-of-life calendar, and three branches shipped the same CVE fix in two days.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Incus and GoCD 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. Incus and GoCD 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 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.
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.