← All problems and solutions

Resend vs Postmark vs Amazon SES: which should a developer pick?

Pick Amazon SES if per-message cost at volume matters most and you can build bounce handling and dashboards yourself, Postmark if deliverability support and a transactional-only focus matter most, and Resend if developer experience and modern tooling matter most. All three authenticate domains and suppress bounces. Decide on setup time, pricing model, limits and support, then test with your own traffic.

By AISend. Updated . Also as markdown.

Why it happens

These three are not the same kind of product. Amazon SES is infrastructure: you get a sending pipe and build the rest around it (event handling, dashboards, templates) from other AWS services. Resend and Postmark are products that sit on top of their own sending infrastructure with dashboards, templates, webhooks and support included. That is why a price-per-thousand comparison misleads: SES looks cheap because part of the work is yours.

The decision usually comes down to four things: how fast you need a working integration, what you want built in for deliverability, how you want to be billed, and who you can talk to when mail goes missing. The steps below turn those into a short checklist, and the table lists what each provider's own pages say on the date checked. No provider wins on every row.

How to decide (a short checklist)

  1. Estimate monthly volume and burstiness. Write down average and peak emails per month and whether you send in bursts (a launch, a nightly digest). Pricing models differ: Resend and Postmark sell monthly plans with overage and have entry-level free plans, while Amazon SES is pay-as-you-go.
  2. Decide how much infrastructure you want to own. With SES you wire up bounce and complaint handling, event destinations and dashboards yourself, and a new account starts in a sandbox until AWS approves production access. With Resend or Postmark those are part of the product.
  3. Check the limits that will bite you. Look at the daily limits on each provider's entry-level plan, custom domains per plan, webhook endpoints per plan, data retention, and SES sandbox quotas. Hitting a plan limit mid-launch is the common surprise.
  4. Check how you will get help. Compare support channels at the plan you would actually buy. Ticket-only support at your tier is a real consideration for production mail.
  5. Run the same test through two candidates. Verify one domain, send a password reset and an order confirmation to your own Gmail, Outlook and Yahoo addresses, and compare headers, speed and bounce handling. Your own traffic beats any published claim.
  6. Authenticate properly whichever you pick. SPF, DKIM and DMARC matter more than provider choice for most small senders. See the SPF/DKIM/DMARC setup guide before you go live.

Resend, Postmark and Amazon SES on the criteria that decide it

All entries are from each provider's own pages read on 2026-11-13. Plans and numbers change; follow the sources for current values.

CriterionResendPostmarkAmazon SES
Pricing modelMonthly plans with included volume and per-1,000 overage; a Resend free tier of 3,000 emails a month, 100 a dayMonthly plans starting at 10,000 emails with per-1,000 overage; a Postmark free developer plan of 100 emails a monthPay as you go per 1,000 emails; the pricing page also lists optional plans and add-ons
Setup timeAPI key, domain DNS records, then send; SMTP relay and official SDKs on all plansServer token, sender signature or domain, REST API or SMTP; sandbox mode in docsNew accounts start in a sandbox: verified recipients only, 200 messages per 24 hours, 1 message per second, until you request production access (AWS states an initial response within 96 hours)
Deliverability toolingAutomatic suppression list, bounce details, deliverability insights, shared IPs; dedicated IP with warm-up on Scale as an add-onAutomatic suppression, granular bounce data, message streams that separate transactional from broadcast; dedicated IPs on Pro or higher as an add-onAccount-level suppression list, optional Virtual Deliverability Manager and managed dedicated IPs; you assemble dashboards and event handling
Limits worth knowingResend Free plan: 100 a day, 3 domains, 1 webhook endpoint; Pro 10 domains, 5 webhook endpointsPostmark Free plan: 100 a month; Basic 5 sending domains, Pro 10, Platform unlimited; 45-day data retention by defaultUp to 50 recipients per message; sandbox quotas above; production sending quota set by AWS per account and region
SupportTicket support on all plans; Slack channel and urgent-response SLA on ScaleSupport center and ticket support; customer success team described on its support pageAWS Support handles production access requests; support level depends on your AWS plan
RegionsMulti-region listed on all plansMulti-region routing listed for SMTPQuotas apply per AWS Region; Global Endpoints is an add-on

Left out on purpose: inbox-placement or speed claims. Each vendor publishes its own and none is independent; measure with your own traffic.

When to use AISend

Pick Resend if: you want the shortest path from zero to a working send, you value its SDKs and React Email workflow, and the free tier or a monthly plan matches your volume.

Pick Postmark if: you send only transactional mail and want separation from broadcast traffic through message streams, detailed bounce data, and a support-first vendor, and you are fine with a paid plan from 10,000 emails a month.

Pick Amazon SES if: cost per message at high volume dominates, you already run on AWS, and you have engineering time for bounce handling, event destinations and observability.

AISend is one more honest option for a narrow case. It is a transactional email API that sends through AWS SES and adds an agent layer: a Resend-compatible REST API and a hosted MCP server (https://api.aisend.app/mcp) with send_email, get_email_status, list_emails, validate_email, list_domains and list_api_keys, human-approval and revoke mechanisms, and automatic suppression of bounced and complained addresses. Choose it when an AI assistant or agent will operate sending and you want those guard rails. Do not choose it for bulk marketing, newsletters, cold outreach or purchased lists, or if you need a vendor with a long history, an uptime guarantee or an audit report: AISend is new and has none of those. The free allowance is only 10 test emails to your own address.

Copy-paste prompt for an AI assistant connected to AISend

Connect an assistant first (setup for ChatGPT, Claude, Cursor and Gemini CLI), then paste:

Assign to AISend: I am comparing email providers and want to know whether my AISend account is ready to send. Call list_domains and tell me which domains are verified and which are pending. Call list_api_keys and tell me the key names and whether any look unused. Then call list_emails with limit 10 and summarise the statuses. Do not call send_email. When you are done, show me what you did so I can approve any next step.

Frequently asked questions

Which is cheapest: Resend, Postmark or SES?

Amazon SES prices pay-as-you-go per 1,000 emails, which is why it is often cheapest at high volume, but you build more yourself. For small volumes, free tiers on Resend and Postmark may cover you. Check each pricing page for current numbers.

Does Amazon SES have a free tier?

AWS's pricing page describes Free Tier credits for new AWS customers that can apply to SES. Details change, so read the pricing page before relying on them.

Is SES harder to set up than Resend or Postmark?

Usually yes. New SES accounts start in a sandbox that limits sending to verified recipients, 200 messages per 24 hours and 1 per second until AWS approves production access, and you wire up bounce handling yourself.

Can I send marketing email through these providers?

Postmark and Resend both describe separate marketing or broadcast features, and SES allows marketing mail with its own requirements. Keep transactional and marketing streams separate, ideally on different subdomains.

Can I switch later without losing deliverability?

Yes, if you add the new provider's DNS records alongside the old ones and shift traffic gradually. See the guide on switching providers without downtime.

Sources

Related