Postmark vs Resend vs Amazon SES (2026): Which to Pick

Postmark vs Resend vs Amazon SES (2026): Which to Pick

Ask ten solo founders where their receipt emails come from and eight will say “whatever my app scaffolded.” That works until the first password reset lands in a promotions tab, or a Stripe webhook fires and the customer never sees the invoice. Transactional email is the least glamorous line item in a startup budget, and it is also the one that quietly decides whether people can log in.

This is a comparison of the three providers that come up in almost every founder thread: Resend, Postmark, and Amazon SES. I run my own newsletter on Buttondown, which handles the broadcast side, so the question here is narrower: who sends the app mail. Passwords, receipts, invites, magic links, dunning notices.

Why transactional email is a different job than your newsletter

Broadcast tools optimize for list growth and beautiful templates. Transactional providers optimize for latency and inbox placement on a single message triggered by an API call. Mixing the two in one account is the mistake I see most often, and it’s expensive in a way that’s hard to see: a bad campaign send drags down the reputation of the IP that also delivers your password resets.

Postmark sells this as “message streams,” and it is the single most useful concept in this whole category. Marketing mail goes out on one stream, transactional on another, each with its own reputation and its own suppression list. If you’re on a provider that doesn’t separate them, one 5,000-recipient promo can take your login emails down with it.

The second thing that matters: do you own the sending domain reputation, or does the shared pool? On cheap shared infrastructure you’re renting reputation from strangers. On a dedicated IP you own it, including the damage. Most founders under 50,000 emails a month should stay on shared and not think about it.

The 2026 price table

All figures below come from each vendor’s public pricing page, checked in October 2026. Monthly billing, USD.

Provider Free tier Entry paid Cost at 50k/mo Cost at 100k/mo Dedicated IP
Resend 3,000/mo (100/day) $20 for 50,000 $20 $35 On Scale tier
Postmark 100/mo (dev only) $15 for 10,000 $55 (Basic) $115 (Basic 125k) From $50/mo, Pro and up, 300k+ volume
Amazon SES None Pay as you go ~$5 ~$10 plus $24.95 if you want a dedicated IP $24.95/mo

SES at $0.10 per 1,000 outbound emails is not a typo, and it is roughly twenty times cheaper than Postmark at the same volume. That gap is the whole reason this comparison exists, and it’s also why so many people who switch to SES end up switching back.

Resend: the one most new projects start on

Resend’s pitch is the developer experience. React Email components, a clean dashboard, an API that reads like the docs you wish every vendor wrote. The free tier of 3,000 emails a month with a 100-per-day cap covers a pre-launch product comfortably. Pro at $20 for 50,000 with $0.90 per 1,000 overage is honest pricing for something you’ll grow into.

Two things to know before you commit. The 100/day cap on free is tighter than it looks once you add verification emails and test traffic, and several comparison write-ups in 2026 put Postmark ahead on raw API latency and on support responsiveness. Those are secondhand observations, not my own benchmarks, and I’d weight them lightly at your volume.

The bigger practical point: Resend’s reputation is good but it is younger than Postmark’s. If you’re sending password resets to enterprise customers who notice, that maturity gap is worth something. If you’re sending receipts to consumers, it isn’t.

Postmark: the one that costs more and tells you why

Postmark is the boring answer, and boring is the point. It has been the default recommendation for transactional deliverability for years, it keeps marketing and transactional streams apart by default, and the dashboard tells you what happened to a specific message instead of making you guess. Free is 100 emails a month, which is a testing allowance, not a plan.

Real entry pricing is $15 for 10,000 on Basic. At 50,000 you’re at $55, at 125,000 it’s $115. Overage on Basic runs $1.80 per 1,000, which is steep, so you want to size the tier correctly. Dedicated IPs start at $50/month and only make sense past 300,000 emails, on Pro or Platform.

Where Postmark annoys people: Basic caps you at 5 domains and 4 users, and the price climbs fast compared to Resend and SES. A founder sending 100,000 a month pays $115 versus $35. Whether that $80 buys you anything depends entirely on how much a missed invoice costs you. For most B2B products it does. For a side project it doesn’t.

The feature I’d miss most if I left is message retention and search. Being able to pull up a specific email from three weeks ago and see the delivery event is worth real money during a support ticket.

Amazon SES: cheapest by an order of magnitude, priced in your time

SES is $0.10 per 1,000 outbound emails plus $0.12 per GB of attachments, with no monthly minimum. At 100,000 emails a month you’re looking at about ten dollars. That’s not a rounding error against your other costs; it’s noise.

What you pay instead is setup. New accounts start in a sandbox capped around 200 messages a day and one per second, and getting out means a support ticket describing your sending practices. You configure IAM permissions, verify domains, wire up event destinations if you want bounce and complaint tracking, and build your own suppression handling. There is no nice template editor and no “why did this one bounce” button. Some founders enjoy this. Most don’t.

SES also has the least forgiving reputation model. Bounce rates above roughly 5% or complaint rates above 0.1% get accounts reviewed or paused, and you find out by email. If nobody on your team watches that dashboard weekly, SES is a liability with a good price tag.

One honest note on the cheap tier: the price advantage is real, but the difference between $10 and $55 a month is not what kills a startup. Time spent debugging a rejected send at 11pm is.

The hidden line items

  • Inbound email. If you accept replies or parse forwarded mail, check whether the provider charges per received message. Postmark counts inbound as email volume; SES bills separately for receiving.
  • Dedicated IP warm-up. Buying an IP before you have volume makes deliverability worse, not better. Under 100,000 a month, skip it.
  • Analytics retention. Postmark keeps 45 days by default, with longer retention as a paid add-on. Resend’s limits are tighter on the free tier.
  • Vendor lock-in in your code. Whichever you choose, keep the send call behind one function in your codebase. Migrating 40 scattered API calls is a weekend you’ll never get back.

What I’d actually pick

For a solo founder shipping an MVP this month: Resend. The free tier is real, the SDK takes ten minutes, and you can revisit the decision when volume makes the price gap matter.

For a product where a missing email means a support ticket or a churned customer: Postmark. Pay the extra and stop thinking about it. This is the same logic behind choosing a slightly pricier host for something that must stay up, which is the tradeoff I walked through in the Ghost versus WordPress comparison.

For anyone already deep in AWS with someone watching CloudWatch: SES, without hesitation. The cost advantage compounds as you grow, and the operational burden is something you already carry.

What I would not do is run transactional mail through a newsletter platform. When your list is separate from your app mail, a bad campaign can’t poison your login flow. Keep them apart even if it costs another ten dollars a month.

Deliverability basics nobody escapes

Whichever provider you pick, the setup work is the same and it is not optional since the major mailbox providers tightened bulk sender requirements. Publish SPF and DKIM records for your sending domain. Add a DMARC record, starting at p=none if you want to watch reports before enforcing. Use a subdomain like mail.yourdomain.com for app mail so a deliverability problem never touches your primary domain’s reputation.

And send a real email to yourself at Gmail, Outlook, and one corporate address before you announce anything. I’ve watched a launch go out with a broken DKIM record twice now, and both times the founder found out from a customer.

If your product also needs a newsletter or a launch list, that’s a separate tool. Beehiiv and Kit both handle broadcasts well, and Beehiiv’s referral program pays a recurring cut if you recommend it to your own audience. Just keep it out of the path that resets passwords.

Key Takeaways

  • Transactional and marketing email belong on separate streams. This matters more than which vendor you choose.
  • Resend wins on developer experience and price for small volumes: free to 3,000 a month, $20 at 50,000.
  • Postmark costs three to four times more and earns it on deliverability reputation, message search, and stream isolation.
  • Amazon SES is around $0.10 per 1,000 emails, and the savings are paid for in setup work and reputation monitoring.
  • Size your tier correctly. Overage rates of $1.80 per 1,000 can erase the savings of a cheaper plan.
  • Wrap your send call in one function so switching providers stays a one-file change.

If you’re still assembling the rest of your stack, the zero to $10K MRR roadmap covers the tools that sit around this decision, from hosting to payments.

Similar Posts