GravityKit
GravityKit ships weekly across a whole plugin suite, with an MCP server now part of the lineup.
Comparison · Infra & APIs
werf vs GoCD
A side-by-side editorial comparison of werf and GoCD — release velocity, themes, recent moves, and the top alternatives to consider.
werf vs GoCD: at a glance
What is werf?
Werf is running a v3 rewrite and a v2 maintenance line side by side, on four release channels.
Werf publishes into parallel channels — alpha, beta, ea, stable, and dev — and the recent entries show two lines moving at once. The 2.75.x releases are maintenance: a host-cleanup fix that stopped it wiping other werf versions' git cache, buildah retries when a cached image id is missing, serialized concurrent base-image pulls. The v3 line is where features land, with 3.0.0 alphas, a 3.0.2 patch, and a 3.1.0 dev build carrying embedded kubeconform schemas, additional patch files, and a per-project meta-repo safeguard.
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.
werf vs GoCD: editorial side-by-side
werf
5.0INFRA · APIS
Werf is running a v3 rewrite and a v2 maintenance line side by side, on four release channels.
◆ Current state
Werf publishes into parallel channels — alpha, beta, ea, stable, and dev — and the recent entries show two lines moving at once. The 2.75.x releases are maintenance: a host-cleanup fix that stopped it wiping other werf versions' git cache, buildah retries when a cached image id is missing, serialized concurrent base-image pulls. The v3 line is where features land, with 3.0.0 alphas, a 3.0.2 patch, and a 3.1.0 dev build carrying embedded kubeconform schemas, additional patch files, and a per-project meta-repo safeguard.
◆ Where it's heading
The v3 work is a deploy-engine change more than a version bump: nelm is being pulled in and bumped, values-schema validation is becoming optional to stop service values breaking values.schema.json, and a meta-repo migration path is being built. Meanwhile the build layer is being hardened against concurrency — serialized pulls, retry on missing cached ids, Dockerfile COPY semantics fixed for --parents and --exclude in staged builds. The two lines share build fixes, with the same commits appearing in both 2.75.4 and 3.1.0.
◆ Prediction
Expect the v3 line to keep absorbing build fixes from 2.75.x while nelm and the meta-repo migration stabilise ahead of a wider v3 push. The 2.75.x channel looks like it will stay on bug fixes only.
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 werf 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 werf 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.
Firecracker
Firecracker's microVMs can now grow and shrink devices while running.
Recent activity from werf and GoCD
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agowerfSignature note appended to the latest release artifacts
- 1d agowerf2.75.3: host cleanup stops wiping other werf versions' git cache
- 1d agowerf2.75.4 alpha: buildah pull retries and serialized base-image pulls
- 1d agowerf3.1.0 dev: embedded kubeconform schemas and meta-repo safeguards
- 8d agowerf3.0.2: build-log progress indices follow real start order
- 8d agowerf3.0.0-alpha.2: deploy flags restored, staged Dockerfile COPY fixes
- 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 werf and GoCD?
They serve adjacent needs but don't currently overlap on shipped themes. werf 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.
Is werf better than GoCD?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. werf 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.
What are the best alternatives to werf?
Top werf alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "werf alternatives" section above for the current picks, or visit /alternatives/werf 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.