Resend

Resend is an email API for developers, built on the premise that sending transactional email had become needlessly unpleasant and that the fix was better developer experience rather than more features. Transactional email is unglamorous, critical infrastructure. Password resets, receipts, verification links, and notifications have to arrive, arrive quickly, and land in the inbox rather than the spam folder. The established providers solve deliverability well and wrap it in consoles, SDKs, and template systems that accumulated over a decade of enterprise requirements, so a task that should take an afternoon routinely takes a week and a support ticket about domain authentication. Resend's answer is to treat the developer as the customer rather than the marketing department. Setup is a domain, a DNS record set the dashboard generates for you, an API key, and a few lines of code. The API surface is small and predictable, SDKs cover the common languages and frameworks, and the dashboard shows what was sent, what bounced, and what was marked as spam without hunting through report builders. Webhooks cover delivery, open, bounce, and complaint events for teams that need to react to them. The piece that spread furthest is React Email, an open-source component library the team maintains for building email templates as React components. It exists because HTML email remains genuinely hostile - nested tables, inconsistent client rendering, inline styles - and writing templates as components with a preview server is a substantial improvement over maintaining hand-tuned HTML. It is usable independently of Resend, and for many teams it was the introduction to the company. Deliverability is the part that cannot be shortcut, and the honest position is that reputation is earned by sending behaviour over time regardless of provider. Resend handles the mechanics - SPF, DKIM, DMARC guidance, dedicated IPs on higher tiers, separate sending domains - but a young domain sending to a poorly sourced list will land in spam anywhere. Pricing is free for a modest daily and monthly volume, which covers side projects and early products outright, then scales by send volume rather than by seat. How it compares: Postmark is the closest peer on transactional reliability and has a longer deliverability track record, with a more conservative product. SendGrid and Mailgun are the incumbents - more features, more configuration, more legacy surface. Amazon SES is dramatically cheaper at volume and gives you no product around it, which is the right trade only if you are prepared to build one. Loops and Customer.io sit further toward marketing and lifecycle campaigns. It suits developers who want transactional email working correctly today rather than configured thoroughly next week.