The use case: how Better Auth deploys Resend
Better Auth uses Resend to send the emails that its authentication flows depend on, such as magic links, password resets, OTPs and account verifications. It also uses Resend for internal and external communications like infrastructure invites, marketing broadcasts and investor updates, and includes it in its demos and example stack for its users.
In the customer’s words
Resend is built by people who care. It offers the best DX and UX, making it effortless to send emails both for us and for the developers building on Better Auth.Resend users in DevTools & Infrastructure
Companies in the same sector, with public evidence.
See all Resend customers
Go straight to the source
Based on Resend’s published case study. We check the public evidence; the results are reported by the vendor.
resend.com- Last checked
- Nov 12, 2026
Open source capture What the story claims, and what we checked
What we compared with the page.
- The passage quoted aboveChecked
Copied word for word from the page, near the name of Better Auth.
- Better Auth uses ResendChecked
Confirmed line.
- The result itselfNot checked
We quote it; we did not measure it.
We first started using Resend with our initial waitlist confirmation flow. The experience was so seamless that we started integrating Resend into our official demos and internal products until it became our default choice for email.