DNSControl
DNSControl v5 is feature-frozen with a ship date, and rc9 is pure provider cleanup
A side-by-side editorial comparison of OpenKruise and Resend — release velocity, themes, recent moves, and the top alternatives to consider.
Seven workload APIs graduated to beta — then the feed went quiet for six months.
OpenKruise's tracked releases stop in January 2026, all of them alphas of v1.9.0. The substantive one moved seven APIs — BroadcastJob, AdvancedCronJob, ImagePullJob, ImageListPullJob, NodeImage, Advanced DaemonSet and SidecarSet — from v1alpha1 to v1beta1, updated the Kubernetes dependency to 1.32.6 and Go to 1.23, and added capability across the workload controllers: reserved unschedulable pods in UnitedDeployment, cron-driven ImagePullJob, deadline handling in CloneSet, and PodUnavailableBudget protection for pod resize. Two of the three entries are the same changelog tagged four minutes apart.
Resend is wiring itself into every agent runtime it can reach, and now adding the controls to stop a send.
Most recent entries are about who or what can call Resend rather than about email delivery itself: OAuth 2.1 with PKCE, a remote MCP server tracking the current spec, a Codex plugin, a one-click Claude connector, and support for the Agent Plugins Standard. The email product still gets attention — suppressions, template folders, a compatibility checker in the code editor, and now cancellation of scheduled or queued Broadcasts from the API. Entries are terse one-liners, so the shipping cadence reads faster than the surface area actually changing.
OpenKruise's tracked releases stop in January 2026, all of them alphas of v1.9.0. The substantive one moved seven APIs — BroadcastJob, AdvancedCronJob, ImagePullJob, ImageListPullJob, NodeImage, Advanced DaemonSet and SidecarSet — from v1alpha1 to v1beta1, updated the Kubernetes dependency to 1.32.6 and Go to 1.23, and added capability across the workload controllers: reserved unschedulable pods in UnitedDeployment, cron-driven ImagePullJob, deadline handling in CloneSet, and PodUnavailableBudget protection for pod resize. Two of the three entries are the same changelog tagged four minutes apart.
This is a project consolidating rather than expanding — graduating APIs to beta is a commitment to stop changing their shape, and the accompanying features fill gaps in existing controllers rather than adding new ones. The pod resize protection is the one forward-looking item, tracking in-place resource resizing as it stabilizes upstream in Kubernetes. Whether the v1.9.0 line ever reached a stable release is not visible here.
The obvious next step is a stable v1.9.0 with the v1beta1 APIs finalized. The six-month gap since the last alpha is worth verifying against the project's actual release activity before reading it as a slowdown.
Most recent entries are about who or what can call Resend rather than about email delivery itself: OAuth 2.1 with PKCE, a remote MCP server tracking the current spec, a Codex plugin, a one-click Claude connector, and support for the Agent Plugins Standard. The email product still gets attention — suppressions, template folders, a compatibility checker in the code editor, and now cancellation of scheduled or queued Broadcasts from the API. Entries are terse one-liners, so the shipping cadence reads faster than the surface area actually changing.
Resend is treating agents as the next class of sending client and building the authorization and discovery plumbing they need before that traffic arrives. The progression is legible: authenticate third parties (OAuth), be callable (MCP), be installable per vendor (Codex, Claude), then be installable by standard. The Cancel Broadcast API is the first sign of the next phase — once non-human callers can schedule sends, the ability to revoke one programmatically stops being a convenience.
Authorization and discovery are covered and reversibility has now started; the remaining gap is what an agent is permitted to send in the first place, so scoped per-agent sending limits or approval gates before dispatch are the natural next piece.
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 OpenKruise or Resend.
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
Strimzi's 1.2.0 candidate closes with a logging fix and nothing else
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 OpenKruise alternatives → · See all Resend alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Resend is currently shipping more aggressively (velocity 6.3 vs 0.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. Resend is currently shipping more aggressively (velocity 6.3 vs 0.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 OpenKruise alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "OpenKruise alternatives" section above for the current picks, or visit /alternatives/openkruise for the full list with editorial commentary on each.
Top Resend alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Resend alternatives" section above for the current picks, or visit /alternatives/resend for the full list with editorial commentary on each.