evaluate
The engine under every knitted R document reached 1.0 by making evaluation behave like the console.
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, one standard at a time
Almost every recent entry is 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 now support for the Agent Plugins Standard. The email product still gets attention — suppressions, template folders, a compatibility checker in the code editor — but it is the smaller half of the feed. 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, one standard at a time
◆ Current state
Almost every recent entry is 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 now support for the Agent Plugins Standard. The email product still gets attention — suppressions, template folders, a compatibility checker in the code editor — but it is the smaller half of the feed. 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: first authenticate third parties (OAuth), then be callable (MCP), then be installable per vendor (Codex, Claude), and now be installable by standard. The developer-experience work — secret scanning, email-client compatibility warnings, Message-ID threading — keeps the human-facing product credible while that shift happens.
◆ Prediction
Having covered authorization and discovery, the gap left is what an agent is permitted to send once connected; scoped, per-agent sending limits or approval controls 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.
carrier
carrier's 0.3.0 quietly rewrites how crated functions see each other — and breaks code that relied on the old rules.
watcher
watcher is a thin filesystem-events binding whose releases are mostly build work.
gh
gh spent its last two releases making failures and interruptions recoverable.
checkhelper
checkhelper grew from a check wrapper into a CRAN pre-submission auditor.
dockerfiler
dockerfiler's 1.0.0 changes what its generated Dockerfiles actually contain.
Recent activity from Resend and rush
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agoResendAgent Plugin Support ⚡
- 2d agoResendEmail Compatibility Checker
- 8d agoResendRemote MCP Supports the 2026-07-28 Spec
- 11d agoResendTemplate Folders
- 17d agoResendEmail Suppressions
- 21d agorushWorkers start in their own mirai call so they can create local daemons
- 23d agoResendResend Plugin for Codex
- 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
- 4mo 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.