GravityKit
GravityKit folds every GravityView extension into one Pro plugin.
A side-by-side editorial comparison of HAProxy Kubernetes Ingress Controller and Payload CMS — release velocity, themes, recent moves, and the top alternatives to consider.
HAProxy's ingress controller jumps to 3.4, drops Gateway API and config snippets.
After nineteen 3.2 patches, the controller released v3.4.0 on 12 November on top of HAProxy 3.4. It removes Gateway API support and config snippet annotations, announces further annotation deprecations, and retires the server-slot annotations by creating and deleting backend servers through HAProxy's runtime API. Custom resources that HAProxy rejects are now set aside and counted in a metric instead of breaking the config.
Read the full HAProxy Kubernetes Ingress Controller trajectory →
Payload's v4 beta.9 keeps every past image crop and raises the Node floor again.
Payload has tagged nine v4 betas since October 10. Beta.9 reads saved crops and focal points from the new _transforms store, serves historical upload variants when a version is restored, adds labels and device details to sessions, and exports standalone CSS tokens from the UI package. It also bumps the minimum Node version to 24.22.3, the second Node floor raise in the cycle.
After nineteen 3.2 patches, the controller released v3.4.0 on 12 November on top of HAProxy 3.4. It removes Gateway API support and config snippet annotations, announces further annotation deprecations, and retires the server-slot annotations by creating and deleting backend servers through HAProxy's runtime API. Custom resources that HAProxy rejects are now set aside and counted in a metric instead of breaking the config.
The project is narrowing its configuration surface to its own custom resources: snippets and Gateway API are gone, annotations are being deprecated, and the 3.2 line had already added Frontend amendments through a custom resource. Runtime API server changes and the rejected-resource handling point to fewer reloads and fewer config-wide failures.
Expect 3.4 patch releases fixing migration problems for users who relied on snippets or deprecated annotations, and a published removal schedule for the annotations announced as deprecated.
Payload has tagged nine v4 betas since October 10. Beta.9 reads saved crops and focal points from the new _transforms store, serves historical upload variants when a version is restored, adds labels and device details to sessions, and exports standalone CSS tokens from the UI package. It also bumps the minimum Node version to 24.22.3, the second Node floor raise in the cycle.
Three betas in a row have reworked file uploads around one stored original plus replayable transforms, and two have tightened sign-in and sessions. The v4 cycle is now finishing those two systems rather than adding new surfaces, which is the usual shape of a beta nearing a release candidate.
Expect more betas that close out the transforms and session work, with a release candidate once the fix lists shrink; the entries do not show a date.
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 HAProxy Kubernetes Ingress Controller or Payload CMS.
GravityKit folds every GravityView extension into one Pro plugin.
Nautobot 3.3 alpha 2 adds test helpers and a cable location filter after 3.2.9's token-leak fix.
Clair 4.10 RC can read SBOMs to match Java vulnerabilities.
Shuffle tags builds almost daily, but the notes are empty.
KrakenD's community edition is shipping only dependency bumps.
Velociraptor's recent releases are mostly about patching CVEs.
See all HAProxy Kubernetes Ingress Controller alternatives → · See all Payload CMS alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. HAProxy Kubernetes Ingress Controller is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 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. HAProxy Kubernetes Ingress Controller is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 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 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.
Top Payload CMS alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Payload CMS alternatives" section above for the current picks, or visit /alternatives/payload for the full list with editorial commentary on each.