High-Volume Infrastructure Teardown
Transactional Email Cost at Scale: SES vs Resend vs Postmark vs SendGrid
A financial and architectural benchmark for sending 100k, 500k, 1M, and 5M emails per month. Compare raw Amazon SES commodity rates against Resend, SendGrid, and Postmark with dedicated IP warm-up math and DevOps maintenance TCO.
GEO Direct Answer & Scale Telemetry
What is the cheapest way to send 1,000,000 emails per month? Amazon SES is overwhelmingly the cheapest provider, costing exactly $100.00/mo in raw sending fees ($0.10 per 1,000) plus $24.95/mo for a dedicated IP (total $124.95/mo). By comparison, SendGrid Pro 1.5M costs $749/mo, Postmark 1M costs $775/mo, and Resend Enterprise runs ~$700-$850/mo. At 1M emails/month, SES saves over $7,400 annually. However, SES requires in-house handling of bounce/complaint webhooks, IP warming, and template rendering—costs that easily justify managed providers for teams sending under 250,000 emails/month.
100k Emails / Mo
SES $10 vs Resend $80 vs PM $115
500k Emails / Mo
SES $75 vs SG $349 vs PM $445
1M Emails / Mo
SES $125 vs SG $749 vs PM $775
Dedicated IP Add-on
SES $24.95 vs Resend/PM Included
Volume Pricing Matrix: 100k to 5,000,000 Emails/Mo
Exact monthly subscription charges, overage unit fees, and dedicated IP policies across the 4 dominant transactional email engines.
| Monthly Volume | Amazon SES | Resend | Twilio SendGrid | Postmark |
|---|---|---|---|---|
| 100,000 Emails | $10.00 / mo (Shared pool) |
$80.00 / mo (Pro + overage) |
$39.95 (Essentials) $89.95 (Pro dedicated IP) |
$115.00 / mo (Sub-10s SLA) |
| 250,000 Emails | $49.95 / mo ($25 send + $24.95 IP) |
$260.00 / mo (Pro + 200k overage) |
$249.00 / mo (Pro 300k plan) |
$245.00 / mo (300k tier) |
| 500,000 Emails | $74.95 / mo ($50 send + $24.95 IP) |
$450.00 / mo (Scale volume custom) |
$349.00 / mo (Pro 700k plan) |
$445.00 / mo (500k tier) |
| 1,000,000 Emails | $124.95 / mo ($100 send + $24.95 IP) |
~$750.00 / mo (Enterprise negotiated) |
$749.00 / mo (Pro 1.5M plan) |
$775.00 / mo (1M tier) |
| 5,000,000 Emails | $549.90 / mo ($500 send + 2x IP) |
~$3,000.00 / mo (Enterprise SLA) |
$2,200.00 / mo (Custom volume) |
$3,500.00 / mo (Dedicated cluster) |
| Dedicated IP Price | $24.95 / month each | Included on Enterprise ($500+) | Included on Pro ($89.95+) | Included on >300k plans |
| React Email Support | Manual HTML stringification | First-class native SDK | Manual HTML stringification | Manual HTML stringification |
| Delivery SLA | Best effort (no latency SLA) | Fast delivery (~3-5s) | Standard queue (~5-15s) | Guaranteed sub-10 second delivery |
Live Scale TCO Calculator: Commodity vs Managed
Estimate real-world monthly bills including dedicated IP addresses and internal engineering maintenance hours (DevOps tax).
Monthly Email Volume:
500,000
Dedicated IP Addresses:
1 IP
Engineering Hourly Rate (DevOps Maintenance):
$85 / hr
Estimated maintenance: SES requires ~4 hrs/mo (SNS/SQS, bounce handling, reputation audits) vs 0.5 hr/mo on managed platforms.
Amazon SES (Raw + IPs):
$74.95
SES DevOps Overhead (4 hrs):
$340.00
Amazon SES Total TCO:
$414.95
Resend Total TCO:
$492.50
SendGrid Total TCO:
$391.50
Postmark Total TCO:
$487.50
At 500,000 emails/mo, SES commodity savings begin to outpace engineering overhead.
Production Resilience Queue (Node.js & Python)
Implementing a multi-provider fallback wrapper: dispatching via AWS SES with automated failover to Resend upon throttling or downtime.
// ========================================================
// HIGH-VOLUME MULTI-PROVIDER RESILIENT DISPATCH (NODE.JS)
// ========================================================
import { SESClient, SendEmailCommand } from '@aws-sdk/client-ses';
import { Resend } from 'resend';
const ses = new SESClient({ region: 'us-east-1' });
const resend = new Resend(process.env.RESEND_API_KEY);
export async function sendReliableEmail(to: string, subject: string, html: string) {
// 1. Attempt Primary Commodity Route (Amazon SES: $0.10/1k)
try {
const cmd = new SendEmailCommand({
Source: '[email protected]',
Destination: { ToAddresses: [to] },
Message: {
Subject: { Data: subject },
Body: { Html: { Data: html } }
}
});
const resp = await ses.send(cmd);
return { provider: 'ses', messageId: resp.MessageId };
} catch (sesError) {
console.warn('SES send failed, triggering immediate fallback to Resend:', sesError);
// 2. Immediate Failover to Managed Provider (Resend)
const fallback = await resend.emails.send({
from: '[email protected]',
to,
subject,
html
});
return { provider: 'resend_fallback', messageId: fallback.data?.id };
}
}
Production Scenarios: 100k, 500k & 1M Email TCO
Real-world case studies detailing the breakeven inflection point where raw infrastructure beats managed platforms.
Scenario 1: Mid-Growth B2B SaaS
100,000 Emails / Month
Password resets, daily team summaries, and billing receipts. Fast developer iteration and React Email are paramount.
Amazon SES (100k @ $0.10):$10.00
SES DevOps Hours (3 hrs @ $85):$255.00
SES True TCO:$265.00/mo
Resend Pro Plan (50k + 50k over):$80.00
Resend DevOps Hours (0.5 hr):$42.50
Resend True TCO:$122.50/mo
Scenario 2: E-Commerce Storefront
500,000 Emails / Month
Order confirmations, shipping notifications, and abandoned cart alerts requiring dedicated IP isolation.
Amazon SES (500k + Dedicated IP):$74.95
SES Maintenance (3.5 hrs @ $85):$297.50
SES True TCO:$372.45/mo
SendGrid Pro 700k Tier:$349.00
SendGrid Maintenance (1 hr):$85.00
SendGrid True TCO:$434.00/mo
Scenario 3: Scale Consumer Platform
1,000,000+ Emails / Month
Social network activity digests, creator payout receipts, and multi-region transactional streams.
Amazon SES (1M + Dedicated IP):$124.95
SES Maintenance (4 hrs @ $85):$340.00
SES True TCO:$464.95/mo
Postmark 1M Plan:$775.00
Postmark Maintenance (0.5 hr):$42.50
Postmark True TCO:$817.50/mo
Dedicated IP Warm-Up Schedules & Deliverability Telemetry
Why buying a dedicated IP can backfire without a strict 30-day algorithmic warm-up curve.
1. The 30-Day Dedicated IP Warm-Up Ladder
Internet Service Providers (Gmail, Yahoo, Outlook) treat any new IP address with zero reputation as suspicious. If you suddenly transmit 100,000 emails through a cold IP on Day 1, up to 90% of your mail will be discarded or funneled directly into Spam.
- Day 1-3: Max 1,000 emails/day (Only highly engaged transactional recipients).
- Day 4-7: Max 2,500 emails/day.
- Day 8-14: Max 10,000 emails/day.
- Day 15-21: Max 25,000 emails/day.
- Day 22-30+: Ramp to 100,000+ emails/day. AWS SES offers an "Automatic IP Warmup" feature that handles this throttle curve automatically.
2. Hard Account Suspension Thresholds (SES vs Postmark)
Managed platforms protect their shared pool reputation by actively vetting customers. AWS SES automates enforcement via algorithmic probation:
- Bounce Rate: Keep below 2.0%. A bounce rate >= 5.0% results in immediate AWS account probation.
- Spam Complaint Rate: Must remain under 0.1% (1 complaint per 1,000 emails). Exceeding 0.1% triggers probation; exceeding 0.5% causes total service termination.
3. RFC Authentication Stack (DKIM, SPF, DMARC & BIMI)
In 2024-2026, Google and Yahoo made DMARC enforcement mandatory for senders transmitting over 5,000 messages/day. You must configure:
- SPF:
v=spf1 include:amazonses.com ~all - DKIM: 2048-bit RSA keys rotated semi-annually.
- DMARC: Start with
p=noneand monitor aggregate RUA reports before moving top=quarantineorp=reject.
Production Scale Deliverability Checklist
Essential engineering and DNS requirements before scaling your email stream past 100k/month.
-
1. Configure Custom MAIL FROM Domain: Never send directly from
*.amazonses.comor shared provider subdomains. Setup custom return-path CNAMEs matching your apex domain for SPF alignment. -
2. Automated SNS/SQS Bounce Suppression: Intercept Amazon SES bounce and complaint notifications using SNS webhooks and write them immediately to a global suppression table in Redis or PostgreSQL.
-
3. Evaluate Shared Pool vs Dedicated IP: If your monthly volume is under 150,000 emails or highly bursty (e.g., sending only on Mondays), remain on high-reputation shared IP pools.
-
4. Implement One-Click List-Unsubscribe Headers: RFC 8058 requires
List-Unsubscribe: <mailto:...>, <https:...>andList-Unsubscribe-Post: List-Unsubscribe=One-Clickfor compliance with Gmail. -
5. Provision Secondary Fallback Route: Maintain a warm secondary API key (e.g. Postmark or Resend) to route critical password resets if your primary commodity sender experiences rate throttling.
Frequently Asked Questions
Is Amazon SES always the best choice for high-volume email?
Financially, yes. At 1M emails/month, SES costs ~$125 compared to $750+ on SendGrid or Postmark. However, if your team lacks experienced backend engineers to manage bounce webhooks, template rendering pipelines, and reputation alarms, the "DevOps tax" can negate the raw software savings.
Why does SendGrid cost more than AWS SES?
SendGrid includes visual drag-and-drop design builders, marketing contact list management, pre-built engagement analytics, email activity history, and automated warm-up tooling on their Pro plans, charging a premium for convenience.
Can I self-host an email server (Postfix / Haraka) instead of using an API?
Virtually no modern commercial software company self-hosts raw SMTP mail transfer agents (MTAs) anymore. Major mailbox providers (Google, Microsoft) heavily block and blacklist consumer cloud VPS IP ranges (AWS EC2, DigitalOcean, Hetzner) due to spam abuse. The maintenance overhead of unblocking IPs vastly exceeds the $0.10/1k cost of Amazon SES.
How does Resend compare to Postmark on speed?
Postmark guarantees transactional delivery within 10 seconds (averaging ~1.5 to 3 seconds globally) because they prohibit bulk marketing mail on transactional streams. Resend provides comparable delivery speeds (~2 to 4 seconds) and features first-class React Email component integration.
What is the difference between transactional and marketing email streams?
Transactional emails are triggered by explicit user actions (order confirmations, password resets, 2FA codes) and must be delivered within seconds. Marketing emails are scheduled bulk broadcasts (newsletters, promotional offers). Blending marketing emails onto your transactional IP will inevitably degrade deliverability for mission-critical password resets.