DNSControl
DNSControl v5 is feature-frozen with a ship date, and rc9 is pure provider cleanup
A side-by-side editorial comparison of GravityKit and Strimzi — release velocity, themes, recent moves, and the top alternatives to consider.
GravityKit's exporter stops producing files and starts keeping a spreadsheet in sync.
GravityKit ships weekly across a suite of Gravity Forms add-ons, publishing a Launch Log digest alongside dedicated announcements for the larger items. This window covers Google Sheets export in GravityExport, unions in Multiple Forms, rich text inline editing in GravityEdit, and a long tail of Gravity Forms 3.0 and WordPress 7.0 compatibility fixes.
Strimzi's 1.2.0 candidate closes with a logging fix and nothing else
The 1.2.0 release cycle has reached its second candidate, and it is a small one: a single fix for incorrect CA logging on top of rc1. Everything substantive in this release landed in rc1 — Kafka 4.3.1 support, per-pod volume templates, and server-side apply now permanently enabled. This feed publishes only release candidates and never the finals, so an rc is the record of what shipped.
GravityKit ships weekly across a suite of Gravity Forms add-ons, publishing a Launch Log digest alongside dedicated announcements for the larger items. This window covers Google Sheets export in GravityExport, unions in Multiple Forms, rich text inline editing in GravityEdit, and a long tail of Gravity Forms 3.0 and WordPress 7.0 compatibility fixes.
The suite is shifting from displaying form data to moving it. Unions stack entries from several forms into one View, Google Sheets export keeps an external sheet current, and the MCP add-ons in the same window expose theme and entry data to agents. Taken together, Gravity Forms entries are being treated as a data source other systems consume rather than something rendered on a WordPress page.
Expect additional live-sync destinations following the Google Sheets pattern, and continued compatibility work while Gravity Forms 3.0 and WordPress 7.0 adoption spreads.
The 1.2.0 release cycle has reached its second candidate, and it is a small one: a single fix for incorrect CA logging on top of rc1. Everything substantive in this release landed in rc1 — Kafka 4.3.1 support, per-pod volume templates, and server-side apply now permanently enabled. This feed publishes only release candidates and never the finals, so an rc is the record of what shipped.
Post-1.0 Strimzi is spending its cycles on how the operator manages Kubernetes resources rather than on new Kafka surface. ServerSideApplyPhase1 has gone alpha to GA and is now always on, and 1.2.0 changes install-time defaults toward Restricted Pod Security Standard security contexts and volume-mounted Service Account tokens. A second candidate carrying one logging fix says the cycle is converging rather than still absorbing change — the CRD v1-only requirement from 1.0.0 remains the loudest thing in every release body.
Expect 1.2.0 final shortly with no further candidates, and the next cycle to advance one of the open feature gates — UseBackgroundPodDeletion is the likeliest to move from alpha to beta.
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 Strimzi.
DNSControl v5 is feature-frozen with a ship date, and rc9 is pure provider cleanup
Casdoor is spending its release cadence moving auth checks from the client to the server
ESPHome ships on a calendar, and the August beta train is now five builds deep
Prowler's assistant decides what to do with findings; the patches keep the scanner honest
NetBox adds a cooling data model — the first new infrastructure domain since power
Two parallel trains, and the 'maintenance' label is now hiding real feature work
See all GravityKit alternatives → · See all Strimzi 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 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. GravityKit 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 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 Strimzi alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Strimzi alternatives" section above for the current picks, or visit /alternatives/strimzi for the full list with editorial commentary on each.