Self-hosted email costs $5-40/month regardless of volume but requires ongoing maintenance, IP reputation management, and technical expertise. AWS SES costs $0.10 per 1,000 emails with near-zero maintenance but gives you less control over IP reputation and deliverability tuning. The break-even point is around 100K-200K emails/month — below that, SES is cheaper and simpler. Above that, self-hosted saves thousands per year if you have the skills to manage it.
Self-Hosted Email vs. AWS SES: Which Is Right for You?
Self-Hosted vs. AWS SES: The Real Comparison
This isn't about which is "better" — it's about which matches your situation. For other comparisons, see self-hosted vs SendGrid and our SMTP relay comparison. Self-hosted email and AWS SES solve different problems, and the right choice depends on your volume, technical team, and how much control you need.
Cost Comparison
AWS SES Pricing
- $0.10 per 1,000 emails (sending)
- $0.10 per 1,000 emails (receiving, if used)
- $24.95/month per dedicated IP (optional)
- Free tier: 3,000 messages/month (if sending from EC2)
- Data transfer: Additional charges for attachments over 10KB
Self-Hosted Pricing
- VPS: $5-40/month (Hetzner CAX11 at ~$4, DigitalOcean at $6-24)
- Volume: Unlimited (bounded by server capacity)
- Dedicated IP: Included (it's your server)
- Hidden cost: Your time for maintenance (1-4 hours/month)
Break-Even Analysis
| Monthly Volume | AWS SES Cost | Self-Hosted Cost | Winner |
|---|---|---|---|
| 10,000 | $1 | $5-10 | SES |
| 50,000 | $5 | $5-10 | Tie |
| 100,000 | $10 | $5-10 | Tie/Self-hosted |
| 500,000 | $50 | $10-20 | Self-hosted |
| 1,000,000 | $100 | $10-20 | Self-hosted |
| 5,000,000 | $500 | $20-40 | Self-hosted |
Note: Self-hosted costs exclude your time. If your time costs $100/hour and maintenance takes 2 hours/month, add $200/month to self-hosted costs. The break-even shifts significantly higher.
Deliverability Comparison
| Factor | AWS SES | Self-Hosted |
|---|---|---|
| IP reputation | Shared pool (variable) or dedicated ($25/IP) | Your own IP (fully controlled) |
| Authentication | Automatic SPF/DKIM | Manual configuration |
| Feedback loops | Built-in via SNS | Manual FBL setup |
| Bounce handling | Automatic | Manual or tool-based |
| Blacklist management | AWS handles shared IPs | You handle everything |
| Warmup | Required for dedicated IPs | Required for new IPs |
When SES Wins on Deliverability
- You're a small sender and SES shared IPs have better reputation than your untested IP
- You don't have the expertise to manage PTR records, DKIM rotation, and blacklist monitoring
- You need automatic bounce processing and complaint handling
When Self-Hosted Wins on Deliverability
- You've warmed your IP properly and maintain clean sending practices
- SES shared IPs are degraded due to other senders' behavior
- You need fine-grained control over retry logic, queue priority, and delivery timing
Control Comparison
| Capability | AWS SES | Self-Hosted |
|---|---|---|
| Queue management | Limited | Full control |
| Retry logic | SES-managed (opaque) | Configurable |
| Rate limiting | SES-imposed limits | You set limits |
| IP selection | Request more IPs ($25 each) | Your IP(s) |
| Sending rules | SES policies apply | No restrictions |
| Data residency | AWS regions | Your server location |
| Account risk | SES can suspend you | No third-party control |
Practitioner note: The biggest SES risk nobody talks about is account suspension. AWS will suspend your SES sending without warning if your bounce or complaint rate spikes — even if the spike was caused by a single bad campaign. Self-hosted gives you a performance conversation with yourself; SES gives you a locked account and a support ticket.
The Hybrid Approach
You don't have to choose one exclusively:
- Self-hosted for mailboxes (receiving email, webmail, IMAP) + SES for outbound relay (use SES infrastructure for sending)
- Self-hosted for transactional email (full control over critical messages) + SES for marketing (volume-based sending)
- SES as failover — route through SES when your self-hosted server is temporarily blacklisted
This hybrid model gives you self-hosted control where it matters and SES reliability where it helps.
Decision Framework
Choose AWS SES if:
- Volume under 100K/month
- No dedicated sysadmin on staff
- You want zero infrastructure management
- Budget for dedicated IPs if needed
Choose self-hosted if:
- Volume over 200K/month
- Technical team comfortable with Linux server management
- You need full control over delivery behavior
- Budget constraints at high volume
- Data residency requirements
Choose hybrid if:
- You want the best of both
- Different email types have different requirements
- You need failover capability
Practitioner note: Most of my consulting clients sending under 200K/month are better served by SES with dedicated IPs. The math changes above that — and dramatically above 1M/month. I've migrated three agencies from SES to self-hosted Postal and saved them $500-2,000/month at scale. But every one of them hired me for ongoing maintenance.
If you need help deciding between self-hosted and SES — or architecting a hybrid setup, schedule a consultation — I'll model the costs and deliverability implications for your specific volume and sending patterns.
Sources
- AWS: SES Pricing
- AWS: SES Deliverability Dashboard
- Hetzner: Cloud Pricing
- M3AAWG: Best Practices for Senders
v1.0 · April 2026
Frequently Asked Questions
Is AWS SES cheaper than self-hosted?
Below ~100K emails/month, yes. SES at $0.10/1K emails costs $10/month for 100K emails. A self-hosted server costs $5-20/month in VPS fees regardless of volume. But at 500K emails/month, SES costs $50 while self-hosted stays at $20. At 1M emails/month, SES costs $100 vs. $20-40 self-hosted.
Is AWS SES deliverability better than self-hosted?
Not inherently. SES shared IPs carry the reputation of all SES senders. A well-maintained self-hosted server with a clean IP can achieve better deliverability than SES shared infrastructure. But SES dedicated IPs ($24.95/month each) with good sending practices match or exceed self-hosted deliverability.
Can I use AWS SES as a relay for my self-hosted server?
Yes. This is a common hybrid approach — run Mailcow or Postal for mailbox management and route outbound email through SES. You get SES's delivery infrastructure with self-hosted control over mailboxes and configuration.
What are the main risks of self-hosted vs. SES?
Self-hosted risk: IP blacklisting, misconfiguration, maintenance burden. SES risk: account suspension for reputation issues, shared IP reputation problems, less control over delivery behavior. Both require active management.
Want this handled for you?
Free 30-minute strategy call. Walk away with a plan either way.