DNSControl
DNSControl v5 is feature-frozen with a ship date, and rc9 is pure provider cleanup
A side-by-side editorial comparison of Resend and Statsig — release velocity, themes, recent moves, and the top alternatives to consider.
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.
Statsig is packaging its own workflows as skills for someone else's agent to run.
Statsig's experimentation and feature-flag platform opened a public agent-skills repository holding reusable workflows — create dashboard, create cloud metric — written as instructions an AI agent can execute. Its MCP server extended to Segments and Layers, covering user targeting and experiment configuration, and Metrics Explorer gained the ability to abort long-running queries. The crawled feed captures marketing pages as entries, so several rows carry navigation boilerplate rather than release notes.
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.
Statsig's experimentation and feature-flag platform opened a public agent-skills repository holding reusable workflows — create dashboard, create cloud metric — written as instructions an AI agent can execute. Its MCP server extended to Segments and Layers, covering user targeting and experiment configuration, and Metrics Explorer gained the ability to abort long-running queries. The crawled feed captures marketing pages as entries, so several rows carry navigation boilerplate rather than release notes.
The direction is agent-operated experimentation. MCP covering segments and layers means an agent can configure targeting, and the skills repository means the multi-step workflows around that configuration are distributable artifacts rather than documentation. Statsig is betting the console is not where experiments get set up much longer.
Expect the skills catalog to grow toward the analysis side — reading experiment results and proposing rollout decisions, not just creating objects. The query-abort work suggests warehouse cost control is a live concern as agent-driven usage increases.
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 Resend or Statsig.
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 Resend alternatives → · See all Statsig alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — mcp — within Infra & APIs. 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 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.
Top Statsig alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Statsig alternatives" section above for the current picks, or visit /alternatives/statsig for the full list with editorial commentary on each.