Self-Hosted SMTP vs AWS SES: The Real Tradeoffs

A Different Comparison

Unlike comparing self-hosted to premium providers (SendGrid, Mailgun), AWS SES is already cheap. This changes the math.

AWS SES: $0.10/1,000 emails + some AWS overhead Self-hosted: $20-50/month fixed + maintenance time

At SES prices, self-hosting rarely wins on cost alone.

Cost Comparison

AWS SES Costs

Volume/Month	SES Cost	Dedicated IP (optional)	Total
50,000	$5	$24.95	$30
100,000	$10	$24.95	$35
500,000	$50	$24.95	$75
1,000,000	$100	$24.95	$125
5,000,000	$500	$24.95	$525

Plus SNS costs for bounce/complaint handling (~$0.50/million notifications).

Self-Hosted Costs

Component	Monthly Cost
VPS (8GB RAM)	$20-40
Backup	$5-10
Monitoring	$0-20
Your time (4 hrs @ $75/hr)	$300
Total (with time)	$325-370
Total (ignoring time)	$25-70

Break-Even Analysis

If ignoring maintenance time:

• Self-hosted beats SES at ~500K emails/month
• At 1M emails: SES ~$125, self-hosted ~$40 → $85/month savings

If valuing time at $75/hour (4 hrs/month):

• Self-hosted almost never beats SES
• At 5M emails: SES ~$525, self-hosted ~$370 → barely break-even

Practitioner note: AWS SES is so cheap that the self-hosting cost case is hard to make. I only recommend self-hosted over SES for non-cost reasons.

What AWS SES Provides

For $0.10/1,000 emails:

1. Massive scale capacity — Millions daily, no infrastructure to manage
2. AWS infrastructure — Global, redundant, highly available
3. Pay-per-use — No commitment, no minimums (after sandbox)
4. API and SMTP — Standard integration options
5. Configuration sets — Separate tracking for different use cases
6. Dedicated IPs — $24.95/month when you need reputation control
7. Integration — Native with AWS services (Lambda, SNS, CloudWatch)

What SES doesn't provide:

• Bounce/complaint handling (DIY via SNS)
• Analytics dashboard (basic, need CloudWatch for more)
• Email templates (basic, less sophisticated than competitors)
• Dedicated support (AWS support tiers apply)

What Self-Hosting Provides

Complete control:

1. Data sovereignty — Email data never leaves your servers
2. No vendor dependency — AWS can't change terms or suspend you
3. Full feature control — Receive email, custom processing
4. Compliance flexibility — Meet any data residency requirement
5. Custom infrastructure — Build exactly what you need

What self-hosting requires:

• Server administration skills
• Email deliverability knowledge
• Ongoing maintenance commitment
• Security expertise
• 24/7 responsibility for issues

When AWS SES Wins

Choose AWS SES if:

1. Cost efficiency at scale — SES is extremely cheap
2. Already on AWS — Native integration with your stack
3. Minimal maintenance wanted — AWS handles infrastructure
4. Variable volume — Pay-per-use scales perfectly
5. Standard transactional email — No exotic requirements
6. Team should focus elsewhere — Email isn't core product

For most use cases, SES is the better choice.

When Self-Hosted Wins

Choose self-hosted if:

1. Data sovereignty is required — Data must stay on your servers
2. Regulatory compliance — Specific requirements AWS can't meet
3. AWS avoidance — Strategic vendor diversification
4. Receiving email needed — SES is send-only; you need both
5. Custom processing — Need to manipulate mail in transit
6. Already have infrastructure — Email fits existing server estate

These are legitimate reasons—they're just less common than people think.

Setup Complexity Comparison

AWS SES Setup

1. Request sandbox exit (1-3 business days)
2. Verify domain (SPF, DKIM via Route 53 or manual)
3. Set up SNS topics for bounces/complaints
4. Create Lambda functions or handlers for notifications
5. Configure suppression list handling
6. Warm dedicated IPs if using (2-4 weeks)

Moderate complexity, well-documented.

Self-Hosted Setup

1. Provision VPS with clean IP
2. Install MTA (Mailcow, Postal, Postfix)
3. Configure DNS (SPF, DKIM, DMARC, PTR)
4. Set up TLS (Let's Encrypt)
5. Configure security (fail2ban, firewall, hardening)
6. Set up monitoring (uptime, queue, reputation)
7. Warm IP (2-4 weeks)
8. Ongoing maintenance (updates, monitoring, troubleshooting)

Higher initial complexity, ongoing commitment.

Deliverability Comparison

AWS SES Deliverability

• Shared IPs have variable reputation
• Dedicated IPs ($24.95/month) give full control
• Good deliverability when properly configured
• Reputation dashboard available
• Must handle bounces/complaints or suffer

SES deliverability is good—problems are usually user configuration issues.

Self-Hosted Deliverability

• Fresh IP (no reputation)
• Must warm over 2-4 weeks
• Full control over reputation
• Manual blacklist monitoring
• Success depends on your expertise

Same ceiling, higher effort to reach it.

Practitioner note: I've seen excellent deliverability from both SES and self-hosted. The difference is that SES deliverability problems are usually configuration issues (fixable), while self-hosted deliverability problems can be fundamental (bad IP range, VPS provider reputation).

Self-Hosted Options

For Transactional (SES Replacement)

Postal — Open-source transactional email platform

• API and SMTP
• Click/open tracking
• Webhooks
• Web management UI

Best SES replacement for transactional use cases.

For Full Email Server

Mailcow — Complete email solution

• Send and receive
• Webmail included
• Docker-based
• More than just sending

For organizations wanting complete email infrastructure.

For High Volume

KumoMTA — High-performance MTA

• Handles millions daily
• Advanced queue management
• Lua scripting
• Enterprise-grade

For massive volume operations.

Migration Considerations

AWS SES to Self-Hosted

If switching for data sovereignty:

1. Set up self-hosted infrastructure
2. Configure DNS (won't conflict with SES initially)
3. Warm new IP over 2-4 weeks
4. Run parallel during warmup
5. Gradually shift traffic
6. Complete cutover when deliverability matches
7. Update DNS to remove SES authentication

Self-Hosted to AWS SES

If simplifying:

1. Exit SES sandbox
2. Verify domain in SES
3. Set up bounce/complaint handling
4. Point application to SES
5. Warm dedicated IP if using
6. Decommission self-hosted

Hybrid Approach

Unusual but possible:

• AWS SES for bulk sending (cost efficiency)
• Self-hosted for receiving or custom processing

Or:

• AWS SES for us-east-1 latency-sensitive sends
• Self-hosted in EU for GDPR compliance sends

Match infrastructure to specific requirements.

The Honest Assessment

AWS SES is usually the right choice:

• Extremely cost-effective
• Scales infinitely
• Minimal maintenance
• Good deliverability

Self-hosted makes sense for:

• Data sovereignty requirements
• AWS avoidance strategy
• Need to receive email
• Custom processing requirements

Don't self-host just because you can. Do it because you have a specific reason AWS SES can't satisfy.

If you're evaluating email infrastructure options and want help determining the right architecture for your requirements, schedule a consultation for expert guidance.

Sources

• AWS SES Pricing
• AWS SES Developer Guide
• AWS SES Dedicated IPs
• Postal Documentation
• KumoMTA

---

v1.0 · March 2026