← Back to home
Comparison · Infra & APIs

GoCD vs Incus

A side-by-side editorial comparison of GoCD and Incus — release velocity, themes, recent moves, and the top alternatives to consider.

GoCD vs Incus: at a glance

FeatureGoCDIncus
SectorInfra & APIsInfra & APIs
Velocity score5.05.0
Sparks · 30d00
Top themesci server, maintenance mode, java baseline, container imagescontainer manager, lts branch, live migration, qemu gating
Last editorial update2h ago2h ago
WebsiteVisit →Visit →

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.

Read the full GoCD trajectory →

What is Incus?

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.

Read the full Incus trajectory →

GoCD vs Incus: editorial side-by-side

G
GoCD
INFRA · APIS
5.0

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.

I
Incus
INFRA · APIS
5.0

Incus settled its 7.0 LTS, then went straight back to a monthly feature cadence.

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

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.

Alternatives to GoCD and Incus

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 Incus.

See all GoCD alternatives → · See all Incus alternatives →

Recent activity from GoCD and Incus

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 7d agoIncusNative Windows and macOS installers; QMP command timeouts
  2. 23d agoGoCDJava 21 minimum, macOS x64 dropped, and security fixes
  3. 23d agoGoCDJava 17 baseline and Wolfi container images
  4. 23d agoGoCDJava 21 LTS by default; CentOS Stream images removed
  5. 23d agoGoCDPassword toggle fix and Sass deprecation cleanup
  6. 23d agoGoCDDependency and container image housekeeping
  7. 23d agoGoCDTest suite migrated from Hamcrest to AssertJ
  8. 27d agoIncusFirst patch release on the 7.0 LTS branch
  9. 1mo agoIncusMigration-compatible hypervisor flags for stateful migration
  10. 2mo agoIncusFixes for issues surfaced by the 7.0 release
  11. 3mo agoIncusIncus 7.0 LTS, with runtime-detected QEMU feature gating
  12. 4mo agoIncusVolume snapshots while attached; OVN dhcp gateway option

Frequently asked questions

What is the difference between GoCD and Incus?

They serve adjacent needs but don't currently overlap on shipped themes. GoCD and Incus 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 Incus?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. GoCD and Incus 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 Incus?

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.