DNSControl
DNSControl v5 is feature-frozen with a ship date, and rc9 is pure provider cleanup
Comparison · Infra & APIs
Resend vs rush
A side-by-side editorial comparison of Resend and rush — release velocity, themes, recent moves, and the top alternatives to consider.
Resend vs rush: at a glance
What is Resend?
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.
What is rush?
Rush spent 2026 making distributed task ownership correct, starting with a breaking 1.0.
rush is the Redis-backed distributed computing backend behind mlr3's parallel tuning: workers pull tasks, push results and are tracked through heartbeats. Since 1.0.0 in March 2026 it has shipped five releases in four months, almost all correcting how tasks and workers are owned and identified under failure. The most recent lets each worker start in its own mirai call so it can spawn local daemons.
Resend vs rush: editorial side-by-side
Resend
6.3INFRA · APIS
Resend is wiring itself into every agent runtime it can reach, and now adding the controls to stop a send.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
rush
2.5INFRA · APIS
Rush spent 2026 making distributed task ownership correct, starting with a breaking 1.0.
◆ Current state
rush is the Redis-backed distributed computing backend behind mlr3's parallel tuning: workers pull tasks, push results and are tracked through heartbeats. Since 1.0.0 in March 2026 it has shipped five releases in four months, almost all correcting how tasks and workers are owned and identified under failure. The most recent lets each worker start in its own mirai call so it can spawn local daemons.
◆ Where it's heading
The through-line is moving responsibility from the controller to the worker. 1.0.0 rewrote the task lifecycle and dropped the seed mechanism; 1.2.0 moved fail_tasks(), finish_tasks(), pop_task() and push_running_tasks() from Rush onto RushWorker so only the worker that ran a task can mark it done, and gave worker ids random suffixes so they cannot collide. 1.1.0 had already removed phantom failed tasks when a worker crashes between evaluations.
◆ Prediction
With ownership and identity settled, the remaining pressure points are heartbeat and lost-worker detection; expect the next releases to tighten failure recovery rather than add API surface.
Alternatives to Resend and rush
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 rush.
Casdoor
Casdoor is spending its release cadence moving auth checks from the client to the server
ESPHome
ESPHome ships on a calendar, and the August beta train is now five builds deep
Strimzi
Strimzi's 1.2.0 candidate closes with a logging fix and nothing else
Prowler
Prowler's assistant decides what to do with findings; the patches keep the scanner honest
NetBox
NetBox adds a cooling data model — the first new infrastructure domain since power
Recent activity from Resend and rush
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agoResendCancel Broadcast API
- 6d agoResendAgent Plugin Support ⚡
- 7d agoResendEmail Compatibility Checker
- 13d agoResendRemote MCP Supports the 2026-07-28 Spec
- 16d agoResendTemplate Folders
- 22d agoResendEmail Suppressions
- 25d agorushWorkers start in their own mirai call so they can create local daemons
- 1mo agorushTask lifecycle moves onto the worker; worker ids can no longer collide
- 3mo agorushPhantom failed tasks and missed results fixed
- 4mo agorushSmaller Redis payloads and vector-valued task parameters
- 5mo agorushRush 1.0 rewrites the task lifecycle and drops the seed mechanism ⚡
- 9mo agorushwait_for_workers() can target a count or specific ids
Frequently asked questions
What is the difference between Resend and rush?
They serve adjacent needs but don't currently overlap on shipped themes. Resend is currently shipping more aggressively (velocity 6.3 vs 2.5), 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.
Is Resend better than rush?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Resend is currently shipping more aggressively (velocity 6.3 vs 2.5), 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.
What are the best alternatives to Resend?
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.
What are the best alternatives to rush?
Top rush alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "rush alternatives" section above for the current picks, or visit /alternatives/rush for the full list with editorial commentary on each.