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 werf and LibreSpeed — release velocity, themes, recent moves, and the top alternatives to consider.
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.
After a two-year redesign, LibreSpeed is adding tests instead of polishing pixels.
LibreSpeed is a self-hosted speed test that spent roughly two years landing a new frontend design, shipped it behind a feature switch, then promoted it to default in 6.0.0. With that out of the way, 6.2.0 turns to capability: a standalone connection-stability test with live latency charting, packet-loss tracking, alerts and CSV export, plus PWA metadata so the tool can be installed from a browser. Docker deployment has been reworked in parallel, including a port change and PHP limits that were silently rejecting default upload chunks.
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.
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.
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.
LibreSpeed is a self-hosted speed test that spent roughly two years landing a new frontend design, shipped it behind a feature switch, then promoted it to default in 6.0.0. With that out of the way, 6.2.0 turns to capability: a standalone connection-stability test with live latency charting, packet-loss tracking, alerts and CSV export, plus PWA metadata so the tool can be installed from a browser. Docker deployment has been reworked in parallel, including a port change and PHP limits that were silently rejecting default upload chunks.
The redesign was the blocker; now that it is default, releases are moving outward — a second measurement mode, installability, better multi-server list handling. The Docker thread runs alongside and is where the breaking changes live: default port moved from 80 to 8080 in preparation for rootless operation, post_max_size raised to accept the tool's own 20 MiB chunks, Alpine base updated. Much of the recent throughput comes from outside contributors and automated agents rather than a single maintainer.
Expect the stability test to gain the configuration and server-side plumbing the main speed test already has, and the rootless-container work that the port change was preparation for to land next. Nothing in the entries suggests a change to the project's self-hosted, no-backend-dependency positioning.
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 LibreSpeed.
GravityKit ships weekly across a whole plugin suite, with an MCP server now part of the lineup.
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.
GoCD's changelog is one maintainer keeping a 2010s CI server running on current runtimes.
Incus settled its 7.0 LTS, then went straight back to a monthly feature cadence.
Firecracker's microVMs can now grow and shrink devices while running.
See all werf alternatives → · See all LibreSpeed alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. werf is currently shipping more aggressively (velocity 5.0 vs 2.5), 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. werf is currently shipping more aggressively (velocity 5.0 vs 2.5), 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.
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.
Top LibreSpeed alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "LibreSpeed alternatives" section above for the current picks, or visit /alternatives/librespeed for the full list with editorial commentary on each.