Dashy
A release per merged PR, and right now nearly every one is a translation string.
A side-by-side editorial comparison of GravityKit and HAProxy Kubernetes Ingress Controller — release velocity, themes, recent moves, and the top alternatives to consider.
GravityKit ships a weekly Launch Log, and the interesting work is buried inside it
GravityKit publishes a consolidated weekly Launch Log across its whole add-on suite rather than per-product release notes, so a single entry can carry a genuine new capability and a batch of compatibility fixes side by side. The recent run covers Google Sheets export in GravityExport, adaptive DataTables columns, calendar sync fixes, unions in Multiple Forms 0.7.0, rich text inline editing in GravityEdit, and a long tail of Gravity Forms 3.0 and WordPress 7.0 compatibility work. GravityView 3.0 in June, with the Vantage theme and AI-assisted View creation, remains the anchor release the suite is building on.
Nine months into the 3.2 line, HAProxy Ingress is still repairing ssl-passthrough and ingress merge order.
The controller ships a steady patch cadence on the 3.2 branch, roughly one release every two to four weeks. Content is almost entirely correctness work: ssl-passthrough handling and the rules that decide which Ingress object owns a shared backend. Feature additions are absent from the last ten releases; dependency bumps to k8s.io and golang.org/x packages appear in most of them.
Read the full HAProxy Kubernetes Ingress Controller trajectory →
GravityKit publishes a consolidated weekly Launch Log across its whole add-on suite rather than per-product release notes, so a single entry can carry a genuine new capability and a batch of compatibility fixes side by side. The recent run covers Google Sheets export in GravityExport, adaptive DataTables columns, calendar sync fixes, unions in Multiple Forms 0.7.0, rich text inline editing in GravityEdit, and a long tail of Gravity Forms 3.0 and WordPress 7.0 compatibility work. GravityView 3.0 in June, with the Vantage theme and AI-assisted View creation, remains the anchor release the suite is building on.
Two threads persist. One is making Views handle data they previously could not — unions stacking entries from many forms without a shared field or custom code, field-to-field filtering, distance sorting, 3D map viewport loading. The other is compatibility maintenance against a moving platform, with Gravity Forms 3.0 fixes appearing in four consecutive Launch Logs. The MCP work on Block MCP and GravityKit MCP has gone quiet since June, which makes the AI thread the least predictable part of the suite.
Expect the export and data-source work to keep widening now that Google Sheets is wired in, and the Gravity Forms 3.0 fix stream to taper as the compatibility surface is worked through. Whether the MCP add-ons get further investment is not readable from these entries.
The controller ships a steady patch cadence on the 3.2 branch, roughly one release every two to four weeks. Content is almost entirely correctness work: ssl-passthrough handling and the rules that decide which Ingress object owns a shared backend. Feature additions are absent from the last ten releases; dependency bumps to k8s.io and golang.org/x packages appear in most of them.
v3.2.13 is the largest release in the window and marks a shift from patching individual ssl-passthrough bugs to defining the semantics properly: backends are now reconciled rather than recreated, the invariant is applied before anything that can fail, and controller-owned backend state survives a failed transaction. Alongside it, ingress merge order became deterministic — oldest ingress first — and the first Ingress to constitute a backend now owns it, with the annotations a losing Ingress forfeits named explicitly. That pairing suggests the team traced a class of flapping and non-reproducible config bugs back to undefined ordering.
Expect the next few releases to stay on the 3.2 patch line, adding tests around the new ownership and passthrough invariants rather than new annotations.
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 GravityKit or HAProxy Kubernetes Ingress Controller.
A release per merged PR, and right now nearly every one is a translation string.
Talos 1.14 reaches its release candidate with routing and DNS pulled into the OS
v0 is turning a prompt-to-app toy into an addressable build service with a real workspace around it.
cloudflared's release feed is checksums and nothing else — until a release has to warn you off itself.
ToolJet's LTS line is where the features land now, while beta collects single-line fixes.
GitHub is shipping models into Copilot weekly while quietly modernizing the OAuth platform underneath
See all GravityKit alternatives → · See all HAProxy Kubernetes Ingress Controller alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. GravityKit 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. GravityKit 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 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.
Top HAProxy Kubernetes Ingress Controller alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "HAProxy Kubernetes Ingress Controller alternatives" section above for the current picks, or visit /alternatives/haproxy-ingress for the full list with editorial commentary on each.