Pick Resend when you want the shortest path from a Next.js route to a sent email, with React Email templates and a free tier that covers a side project. Pick Postmark when transactional mail is part of what you sell (password resets, receipts, magic links) and you want a vendor whose whole pitch is inbox placement and long message history. Pick Amazon SES when volume is high, you already run on AWS, and you can live with doing the deliverability work yourself. For most client apps I start on Resend and keep a thin adapter so moving to SES later is a one-file change.
I checked every price below on November 20, 2026, on each vendor's own pricing page.
What each one costs at real volumes
Resend has a free plan with 3,000 emails a month but a hard cap of 100 per day. Pro is $20 for 50,000 emails and $35 for 100,000, with overage at $0.90 per 1,000. Resend offers no annual discount and no plan between Free and Pro.
Postmark gives you 100 free emails a month for testing, then jumps straight to 10,000. Basic is $15, Pro is $16.50 and Platform is $18 at that tier. Extra emails cost $1.80, $1.30 or $1.20 per 1,000 depending on the plan. Inbound email processing starts on Pro.
Amazon SES is pay-as-you-go. À la carte sending is $0.10 per 1,000 plus $0.12 per GB of attachments. One change to watch in 2026: new SES accounts now start on the Essentials plan at $0.16 per 1,000, because AWS moved fresh accounts onto plans from July 21, 2026. You can switch back to à la carte at any time, but it does not happen on its own.
Quick math for 100,000 emails a month:
- Resend Pro: $35.
- Amazon SES: about $10 à la carte, $16 on Essentials.
- Postmark: you pay for a larger volume tier from the slider on the pricing page; the entry tier alone is the wrong comparison at this size.
At 10,000 emails a month the gap barely matters: Postmark Basic is $15, Resend Pro is $20 and SES is around a dollar. At a million a month it decides the vendor.
Setup time is the hidden cost
Resend is the fastest. Verify a domain, set RESEND_API_KEY, install the resend package and pass a React component through the react field. The Resend Next.js guide covers it in one route handler. It also ships test addresses such as bounced@resend.dev and complained@resend.dev, so you can exercise your bounce handling without hurting your domain.
Postmark takes about the same time. Its sandbox mode and message streams are the parts I value: transactional and broadcast mail travel on separate streams, so a newsletter spike does not drag down the reputation of your password reset emails.
SES is slower to start. Every new account sits in a sandbox per region: verified recipients only, 200 messages per 24 hours, one message per second. Getting out means filing a production access request, and AWS says the first response can take up to 96 hours. On a client project with a launch date, plan for that week. You also wire bounce and complaint handling through SNS or EventBridge yourself.
Deliverability is mostly your DNS, not the vendor
Since 2024, Gmail's sender guidelines require SPF or DKIM for everyone, and SPF, DKIM and DMARC for anyone sending more than 5,000 messages a day to Gmail. Marketing mail needs one-click unsubscribe, and the spam rate must stay under 0.3%.
All three vendors give you the DKIM records. None of them can fix a domain that mixes cold outreach with login codes. The practical rules I follow:
- Send transactional mail from a subdomain such as
mail.example.com, and keep newsletters on a different one or a separate stream. - Start with a DMARC policy of
p=none, read the reports for two weeks, then tighten. - Ask for a dedicated IP only when the volume justifies it. Resend sells one for $30 a month on Scale above 3,000 emails a day; Postmark starts at $50 for senders above 300,000 a month. Below that, a shared pool with good neighbours usually lands better than a cold IP.
Keep the provider behind one function
Your app should call sendEmail(), not a vendor SDK. Auth flows are where this matters most; if you followed my Better Auth vs Auth.js comparison, both libraries want a single callback for verification and reset emails.
1// lib/email.ts2import { Resend } from 'resend'3import { SESv2Client, SendEmailCommand } from '@aws-sdk/client-sesv2'45type Mail = { to: string; subject: string; html: string; text: string; key: string }67const provider = process.env.EMAIL_PROVIDER ?? 'resend'8const resend = new Resend(process.env.RESEND_API_KEY)9const ses = new SESv2Client({ region: process.env.AWS_REGION })10const from = 'App <no-reply@mail.example.com>'1112export async function sendEmail(m: Mail) {13 if (provider === 'ses') {14 await ses.send(new SendEmailCommand({15 FromEmailAddress: from,16 Destination: { ToAddresses: [m.to] },17 Content: { Simple: {18 Subject: { Data: m.subject },19 Body: { Html: { Data: m.html }, Text: { Data: m.text } },20 } },21 }))22 return23 }24 const { error } = await resend.emails.send({25 from, to: m.to, subject: m.subject, html: m.html, text: m.text,26 idempotencyKey: m.key,27 })28 if (error) throw new Error(error.message)29}
Render templates with React Email once, and pass plain HTML and text into this function. Then the template code does not care who delivers it. The key field matters: Resend keeps idempotency keys for 24 hours, so a retried server action will not send the same receipt twice. With SES you store that key yourself before sending.
Two limits to plan for. Resend's default API rate is 10 requests per second per team, and it does not grow when you upgrade. Use the batch endpoint (up to 100 emails per request) or a queue. SES limits depend on your account quota. In both cases, do not send from inside a request that the user is waiting on; push the job to a queue or a background function. If you host outside Vercel, my Vercel vs Coolify guide covers where those workers can run.
My pick by project type
- Side project or MVP: Resend Free. Watch the 100 per day cap during launch week.
- SaaS with logins and receipts: Resend Pro or Postmark Pro. Choose Postmark if you need inbound email parsing or long message history for support tickets: 45 days by default, up to 365 on Pro.
- High volume, already on AWS: SES à la carte, plus a person who owns bounce rates and DMARC reports.
- Agency managing many client domains: Postmark Platform for unlimited domains, or Resend Scale with its 1,000-domain limit.
Whichever you choose, test the unhappy paths before launch: a bounced address, a spam complaint and a provider outage. My Vitest vs Jest post shows how I mock this kind of adapter in unit tests, so the tests cover the fallback path as well as the happy one.