Cursor
Cursor is becoming a control plane for agent fleets — routed, governed, and driven from a phone.
Comparison · Infra & APIs
Resend vs Depot
A side-by-side editorial comparison of Resend and Depot — release velocity, themes, recent moves, and the top alternatives to consider.
Resend vs Depot: at a glance
| Feature | Resend | Depot |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 6.3 | 7.5 |
| Sparks · 30d | 1 | 2 |
| Top themes | email-api, mcp, oauth, agent-native | ci-acceleration, test-analytics, source-control, ai-diagnostics |
| Last editorial update | 1d ago | 1h ago |
| Website | Visit → | — |
What is Resend?
The developer email API is rebuilding itself as something agents log into, not just call
Resend shipped at a near-weekly pace through July and almost all of it points one direction. A hosted MCP server with built-in OAuth, a one-click Claude connector, and a Codex plugin bundling the MCP server and every Resend skill all landed within three weeks, sitting on OAuth 2.1 with PKCE that arrived alongside them. The rest is platform hygiene: Message-ID exposed on webhooks and email endpoints, CSV contact import at scale, suppression management, and automatic revocation of API keys leaked to GitHub.
What is Depot?
Depot now owns every tier from bare metal to git — build acceleration became a full CI platform.
Depot has expanded well past remote build acceleration. In the last month it moved its CI and Sandboxes onto its own bare-metal compute platform, took test results to general availability with org-wide flaky and slow-test analytics, opened a private beta of its own git hosting, and made its Sherlock AI analysis available on any run rather than only failed ones. The integration surface kept widening in parallel — Tailscale for CI jobs, GitLab OIDC, Datadog CI Visibility, and three more GitHub Actions triggers.
Resend vs Depot: editorial side-by-side
Resend
6.3INFRA · APIS
The developer email API is rebuilding itself as something agents log into, not just call
◆ Current state
Resend shipped at a near-weekly pace through July and almost all of it points one direction. A hosted MCP server with built-in OAuth, a one-click Claude connector, and a Codex plugin bundling the MCP server and every Resend skill all landed within three weeks, sitting on OAuth 2.1 with PKCE that arrived alongside them. The rest is platform hygiene: Message-ID exposed on webhooks and email endpoints, CSV contact import at scale, suppression management, and automatic revocation of API keys leaked to GitHub.
◆ Where it's heading
Resend is moving from a service you hold an API key for to one a third party or an agent authenticates into on a user's behalf. That is why OAuth and the secret scanner arrived in the same window as the agent surfaces — delegated auth is the thing that makes agent access safe, and long-lived static keys are the thing that makes it dangerous. Distribution is following the same logic, with Resend showing up in the Vercel marketplace, the Claude connector directory, and the Codex plugin marketplace rather than waiting to be integrated.
◆ Prediction
Expect the MCP surface to widen past sending into contacts, domains, and analytics, and more of these one-click listings wherever agent tools keep directories. The terse changelog entries make it unclear how much of the OAuth work is generally available versus early access.
Depot
7.5INFRA · APIS
Depot now owns every tier from bare metal to git — build acceleration became a full CI platform.
◆ Current state
Depot has expanded well past remote build acceleration. In the last month it moved its CI and Sandboxes onto its own bare-metal compute platform, took test results to general availability with org-wide flaky and slow-test analytics, opened a private beta of its own git hosting, and made its Sherlock AI analysis available on any run rather than only failed ones. The integration surface kept widening in parallel — Tailscale for CI jobs, GitLab OIDC, Datadog CI Visibility, and three more GitHub Actions triggers.
◆ Where it's heading
The pattern is vertical integration. Depot Metal gives it control of the hypervisor and storage tiers, test results give it the data layer above the job, and Depot Code moves storage of the source itself in-house. Each layer feeds the next: timing data from test reports drives shard splitting, and Depot Code plugs straight into Depot CI. What began as a faster Docker builder is turning into a full replacement for the GitHub Actions stack, with GitHub kept as a mirror rather than the system of record.
◆ Prediction
The Depot Metal post states that GitHub Actions runners and container builds move onto it over the coming months, so expect that migration to finish and the performance claims to be restated against the full product line. Depot Code is the piece to watch next: it is private beta with plain git working today, and the obvious follow-on is CI triggering natively off Depot-hosted repositories instead of GitHub-delivered events.
Alternatives to Resend and Depot
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 Depot.
SigNoz
SigNoz rebuilt its dashboards on an open spec so agents, not just people, can drive them.
Retool
Retool is fitting its app-building agent into a real git workflow, not around it.
Daytona
Ten releases in a month turning agent sandboxes into something you can meter, pause and fork
Auth0
Auth0 is turning B2B workarounds into product, and staking a claim on agent authorization.
Pressable
Pressable is building bulk operations and MCP governance for agencies that manage sites at scale
See all Resend alternatives → · See all Depot alternatives →
Recent activity from Resend and Depot
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agoDepotTest results are now generally available ⚡
- 2d agoResendEmail Suppressions
- 8d agoResendResend Plugin for Codex
- 9d agoDepotAI analysis available for all Depot CI workflows and jobs
- 14d agoResendGitHub Secret Scanner
- 15d agoDepotSplit CI test suites with historical timing data (beta)
- 17d agoResendOAuth Support ⚡
- 19d agoResendResend Connector for Claude
- 20d agoDepotDepot CI now supports Tailscale
- 21d agoDepotDepot Code is now available in private beta ⚡
- 22d agoResendEmail Threading with Message-ID
- 23d agoDepotDepot CI and Sandboxes now run on Depot Metal
Frequently asked questions
What is the difference between Resend and Depot?
They serve adjacent needs but don't currently overlap on shipped themes. Depot is currently shipping more aggressively (velocity 7.5 vs 6.3), with 2 editorial sparks in the last 30 days against 1. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is Resend better than Depot?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Depot is currently shipping more aggressively (velocity 7.5 vs 6.3), with 2 editorial sparks in the last 30 days against 1. 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 Depot?
Top Depot alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Depot alternatives" section above for the current picks, or visit /alternatives/depot for the full list with editorial commentary on each.