AWS SES vs Managed Email APIs

Amazon SES is excellent infrastructure. It is also incomplete product.

Managed email APIs (Notify, Resend, Postmark, SendGrid, …) charge a margin on top of delivery so you don’t assemble IAM, SNS topics, bounce handling, dashboards, and webhook plumbing yourself.

The question isn’t “is SES good?” — it is. The question is when the margin is worth it. Deeper take: Why SES is great — and when it isn’t. Side-by-side: Notify vs AWS SES.

The honest split

The startup killer: SES production access

New AWS accounts often start in the SES sandbox: low daily caps, limited recipients. Getting out can take weeks or months. During that time your “cheap email” plan cannot ship password resets to real users.

If your launch is next Tuesday, SES’s ~$0.10/1k rate is fictional. A managed API that lets you verify a domain and send this week is cheaper than a delayed launch.

What you must build on SES

A non-exhaustive list teams forget in the spreadsheet:

• Domain identity + DKIM in SES
• Configuration sets
• Bounce and complaint SNS → Lambda/SQS → your DB suppressions
• CloudWatch alarms that humans understand
• A per-message debug UI (or acceptance that support will suffer)
• IAM least-privilege for every environment
• Retry/idempotency semantics for your app

None of that is hard for an SRE team. All of it is slow for a two-person startup.

What you buy with a managed API

Using Notify as the concrete example:

await fetch('https://notify.cx/api/email/send', {
  method: 'POST',
  headers: {
    'Content-Type': 'application/json',
    'x-api-key': process.env.NOTIFY_API_KEY
  },
  body: JSON.stringify({
    from: 'noreply@your-verified-domain.com',
    to: user.email,
    subject: 'Your receipt',
    message: html
  })
});

You still verify DNS. You still own HTML. You get logs (48h on Free, permanent on paid) and webhooks on Pro/Scale. Pricing: Free 1,000 · Pro $10 / 10,000 · Scale $50 / 100,000 (pricing).

Other managed options: Resend (DX ecosystem), Postmark (deliverability premium), SendGrid (suite). Same category of tradeoff vs SES. First send on Notify: Quick start.

Cost intuition (shape, not a quote)

At low volume (under ~50k/mo), engineer-hours dominate. Paying $10–50 for a managed API is usually correct — Notify’s Pro ($10 / 10k) and Scale ($50 / 100k) sit in that band.

At high volume (hundreds of thousands to millions), SES’s unit price wins if you already operate the glue. Some teams still keep a managed API for DX and accept the margin. Others move to SES and build the control plane.

Never pretend a $10 Pro plan beats SES at 5M emails/month. That’s not the pitch.

Decision tree

Migration paths

• SES → managed: Stop fighting sandbox/ops; point app at HTTPS API; keep domain DNS updated. Migrate from AWS SES
• Managed → SES: Export suppression habits, rebuild webhooks on SNS, load-test, cut over carefully

Compare page: Notify vs AWS SES

When Notify specifically is worth the margin

• You want the smallest transactional API
• You want Pro pricing that’s easy to explain ($10 / 10k)
• You don’t want a template studio or marketing suite
• You refuse to wait on SES production access to ship auth email

When it isn’t: pure unit-cost optimization at massive scale with an AWS team on payroll.

Pipeline context if you’re assembling the stack from scratch: Email pipeline.

Bottom line

SES is great infrastructure. Managed APIs are great products on top of email infrastructure. Pay the margin when time-to-production, logs, and webhooks are worth more than pennies per thousand — which is most early SaaS teams, most of the time.

Resources

• Notify vs AWS SES
• Why SES is great — and when it isn’t
• Migrate from AWS SES
• Pricing
• Quick start
• Email pipeline