Resend
Resend is wiring itself into every agent runtime it can reach, and now adding the controls to stop a send.
A side-by-side editorial comparison of Skipper and Strimzi — release velocity, themes, recent moves, and the top alternatives to consider.
Zalando's ingress proxy finally speaks HTTP/2 cleartext end to end
Skipper ships patch tags almost daily, and most carry a single dependency bump or a one-line auth fix. The substance in this window is v0.27.57, which enables h2c on the server handler, the proxy client, and the net client, with a new h2c:// route scheme and Kubernetes appProtocol wiring. Everything else in the window is Dependabot traffic and two narrow fixes to token introspection and grant auth.
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.
Skipper ships patch tags almost daily, and most carry a single dependency bump or a one-line auth fix. The substance in this window is v0.27.57, which enables h2c on the server handler, the proxy client, and the net client, with a new h2c:// route scheme and Kubernetes appProtocol wiring. Everything else in the window is Dependabot traffic and two narrow fixes to token introspection and grant auth.
The release cadence is a stream of small, individually unremarkable tags where the occasional protocol or load-balancing change is the only thing worth reading. Recent substance has clustered on the data path: leastRequests balancing in v0.27.53, h2c now. The auth filters are being maintained rather than extended, with fixes rather than new capability.
Expect the h2c work to generate follow-up fixes as it meets real gRPC backends, since the release notes already show HTTP Upgrade negotiation failing while direct prior knowledge works.
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 Skipper or Strimzi.
Resend is wiring itself into every agent runtime it can reach, and now adding the controls to stop a send.
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
See all Skipper 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. Skipper and Strimzi 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. Skipper and Strimzi 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 Skipper alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Skipper alternatives" section above for the current picks, or visit /alternatives/skipper 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.