LibreSpeed
After a two-year redesign, LibreSpeed is adding tests instead of polishing pixels.
A side-by-side editorial comparison of werf and GravityKit — 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.
GravityKit ships weekly across a whole plugin suite, with an MCP server now part of the lineup.
GravityKit publishes a weekly Launch Log covering releases across its Gravity Forms add-on suite — GravityView, GravityEdit, GravityCalendar, GravityCharts, GravityImport, DataTables, Maps, Multiple Forms, Zero Spam, and a Block MCP server. Recent weeks delivered union support for combining entries from multiple forms into one View, rich text inline editing, drag-to-copy in the View editor, and 3D map viewport work. A large share of every week's notes is Gravity Forms 3.0 and WordPress 7.0 compatibility work.
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.
GravityKit publishes a weekly Launch Log covering releases across its Gravity Forms add-on suite — GravityView, GravityEdit, GravityCalendar, GravityCharts, GravityImport, DataTables, Maps, Multiple Forms, Zero Spam, and a Block MCP server. Recent weeks delivered union support for combining entries from multiple forms into one View, rich text inline editing, drag-to-copy in the View editor, and 3D map viewport work. A large share of every week's notes is Gravity Forms 3.0 and WordPress 7.0 compatibility work.
Two things define this suite right now. First, it is absorbing a major upstream break: Gravity Forms 3.0 fixes appear in nearly every Launch Log, which sets the pace regardless of what the roadmap wanted. Second, the View editor is becoming a data-composition tool rather than a display configurator — unions across forms, field-to-field filtering, distance sorting on radius searches, and searchable DataTables all point at users assembling application-like views over form data. Accessibility shows up consistently too, with row headers for screen readers and editor a11y upgrades.
Expect Gravity Forms 3.0 and WordPress 7.0 compatibility to keep consuming release capacity until the upstream transition settles, with union and filtering work continuing on the View editor underneath it. The Block MCP server is the piece to watch — it is the only part of the suite aimed at agents rather than site builders.
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 GravityKit.
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.
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 GravityKit alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. werf and GravityKit 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. werf and GravityKit 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 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 GravityKit alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "GravityKit alternatives" section above for the current picks, or visit /alternatives/gravitykit for the full list with editorial commentary on each.