Technology
Resend
Resend is how we send the messages the product owes people: the receipt, the invite, the reset. The template is designed, not leftover from a vendor.
What it is
Resend is a transactional email API built for developers who already live in Next.js: send a receipt, a magic link, an invite, with React as the template language. It is not a consumer mailbox. It is how the product writes to people without standing up Mailgun folklore.
The dashboard shows deliveries. DNS (SPF, DKIM, DMARC) is still your domain's job. React Email is the companion for templates that look like the product instead of like 2008 HTML.
What it does
Teams use Resend for auth mail, invoices, notifications, and marketing that is still transactional in spirit. Next.js route handlers call it. Templates live in the repo.
We send from a domain you own. We do not bury transactional mail in a studio account. If it is a campaign newsletter, we say so and pick a tool that is actually for that.
Why we use it
Transactional mail that looks like the product.
A receipt that still looked like the brand. An invite that opened the right first-run. DNS you can see. SPF and DKIM in the handover. Deliverability is not a mystery.
If people wonder who emailed them, the template failed, or the domain did.
Built on it
Cal.com
Sends booking mail through a modern transactional stack in the Resend generation.
Dub
A link product using Resend for product email.
Loops
Works alongside Resend in the same Next.js email ecosystem.
Bun
Has used Resend in public examples and product mail.
Next.js teams
Resend is a default recommendation in Vercel's email examples.
Tell us what needs to ship.
You use a working prototype before the production build goes ahead.