The developer email platform, built by developers
HQ: San Francisco, CA, United States (fully remote team of ~50) | Founded: 2023 | Employees: 50-55 (company-stated, September 2026) | Stage: Series A; $21.5M total raised; profitable since 2025 | Website: https://resend.com
Resend exists because its founders found email infrastructure unpleasant to build against. Zeno Rocha and Bu Kinoshita started the project in August 2022 as a side effort aimed at building “the Stripe of email,” motivated by marketer-built tooling that ended up in spam folders. The validation moment came in September 2022, when a friend put the minimum viable product into production and paid a $10 payment link for it. Both founders quit their jobs, pitched to Y Combinator in November 2022 and joined the W23 batch. They open-sourced React Email in December 2022, incorporated in January 2023, and shipped the first “Launch Week” in March 2023 — seven features in seven days. Public launch came in June 2023 after roughly 20,000 waitlist signups.
The product is now much wider than transactional email. The core API sends through REST, an SMTP relay or eight first-party SDKs — Node and TypeScript, Python, Ruby, PHP, Go, Java, .NET and Rust — with idempotency keys, batch sends of up to a hundred messages, natural-language scheduling, and signed webhooks. Broadcasts covers marketing with segments, unsubscribe topics and an AI email editor. Automations, added in April 2026, handles event-triggered lifecycle sequences and includes 10,000 automation runs a month on every plan including the free tier. Inbound, which went generally available in November 2025 and was “our most-requested feature ever,” lets companies receive email on their own domain and route it into their application.
The delivery itself is the hard part, and Resend has been unusually public about it. The company runs its own message-transfer-agent layer — SMTP delivery, routing, retries, bounce and deferral classification, shared and dedicated IP pools, automatic warmup and reputation-aware routing — and is hiring explicitly to build and operate that layer. Underneath it sits Amazon SES, evidenced by the include and DKIM records Resend generates and by …amazonses.com… in delivery headers. Four sending regions are offered — North Virginia, Ireland, São Paulo and Tokyo — though all account data is stored in the United States. The company completed a deliberate migration off two cloud providers in April 2025, rebuilt the storage layer for millions of email events, and acquired two companies to help: Mergent for serverless background jobs in April 2025, which became the foundation of Automations, and Briefer, a Y Combinator S23 data analytics platform, in August 2025, which brought the data engineering needed to process terabytes a week.
The most interesting development of 2026 is that Resend has partly stopped thinking of itself as an email company. A hosted MCP server with OAuth, official plugins for Claude Code, Cursor, Codex and Grok, a Claude connector, and five installable agent skills make email a primitive that agents can call directly. The CEO has argued that products without an MCP server “won't be used” by agents and that walled-up data becomes a liability rather than a moat. The resend npm package runs at roughly 42 million monthly downloads against SendGrid's 17.6 million, Mailgun's 4.3 million and Postmark's 4.1 million — the clearest quantitative evidence that the developer default has moved.
Resend is the clearest case in recent infrastructure history of a small company winning on developer experience while everyone else competed on scale. Fifty-three people have built an email platform that sends tens of millions of messages a day, serves 100,000 paying customers, and is quietly becoming the default choice for AI agents that need to email a human — and it has done so on $21.5 million of total funding, with no Series B and, by the company's own account, profit since 2025.
The strategy has three parts and they reinforce each other. First, an open-source wedge: React Email, now at version 6 with roughly 19,000 GitHub stars, lets developers build emails as React components before they have ever chosen a provider. Second, a relentless launch cadence — six numbered “Forward” launch weeks, each shipping several features over five days — which keeps a 50-person company shipping at the pace of a platform. Third, and most current, agent distribution: a hosted MCP server with OAuth, plugins for Claude Code, Cursor, Codex and Grok, and five installable skills. The company says agents account for roughly 40% of monthly signups and that LLMs recommend Resend about 70% of the time.
Two structural facts matter for anyone underwriting it. First, the delivery backbone is Amazon SES — strong evidence from DNS records and headers, acknowledged publicly by the CEO, though not marketed by the company — with Resend operating its own message-transfer-agent layer, IP warmup and reputation-aware routing on top. That is a real dependency: a change in SES policy or an account suspension would flow straight through. Second, reputation risk is existential in email. A shared IP pool carries the aggregate complaint rate of every customer on it, and Gmail, Yahoo and Microsoft now hard-reject non-compliant senders outright.
The signal worth watching is the competitive one. Twilio merged SendGrid and Segment into Twilio.com in February 2026 and did not mention SendGrid at all in its Q2 2026 results. The category leader stopped telling its email story at exactly the moment a 50-person company became the default answer.
Browse: Home | Blog | About | All Startups A-Z | View full profile on StartupWiki