Amazon SES is the cheapest way to send email, so the right alternative depends on what SES is costing you besides money. If you're tired of building and maintaining bounce handling, suppression and monitoring, or you don't want an AWS account deciding when you can send, a managed mail server on a VPS you own takes all of that off your plate. You'll pay more per month than SES. You'll build and babysit much less.
What Amazon SES does well
SES is cheap, scalable and reliable. At $0.10 per 1,000 outbound emails as of October 2026, nothing else on this site comes close on raw price. If you already run on AWS and have engineers who like wiring services together, SES is a sensible, efficient choice. It's also the engine under a number of other email products.
Amazon SES pricing as of October 2026
From third-party pricing trackers; confirm on the Amazon SES pricing page.
| Item | Price |
|---|---|
| Outbound email | $0.10 per 1,000 |
| Standard dedicated IP | $24.95 per IP per month |
| Managed dedicated IPs | $15 per account per month + per-email fee |
At that rate, 100,000 emails cost about $10, 500,000 about $50 and 2.5M about $250, before dedicated IPs or other AWS charges.
What SES doesn't give you
SES is a sending pipe. Around it, you build:
- Bounce and complaint handling, so you stop mailing addresses that fail or complain.
- Suppression lists to keep bad addresses out.
- Dashboards and logs your team can actually read.
- Monitoring for authentication, blocklists and reputation.
And AWS controls your account:
- Sandbox. New accounts start restricted until AWS grants production access.
- Sending limits. AWS sets how much you can send and how fast.
- Pauses. If complaints or bounces climb, AWS can pause your sending.
None of this is unreasonable. AWS runs shared infrastructure and has to protect it. But it's real work and real dependency, and it's the main reason teams look for an SES alternative.
If you're already on AWS
You don't have to leave AWS for everything to leave SES. Your app can stay on EC2 or anywhere else and relay mail to a mail server on a separate VPS over SMTP on port 587. Submission on 587 isn't affected by AWS's default block on outbound port 25, which only matters for the server that delivers mail to the outside world.
Your options for replacing SES
A hosted API with more built in
Resend, SendGrid, Mailgun and Postmark include dashboards, suppression and support, at a higher price per email than SES. See Resend vs Amazon SES. Note that Resend has historically been built on SES, so it adds a layer rather than replacing AWS.
Open-source tools
useSend and FreeResend are open-source and send through SES, so they help with the dashboard and API but keep you on AWS. Postal (MIT license) runs its own SMTP server and doesn't need SES. Our open-source roundup compares them.
Your own mail server, managed
We build a Postfix server on a VPS you own: OpenDKIM, SRS, TLS, fail2ban, DNS records, DMARC reporting and a warm-up plan. With Managed Server, we monitor DNS drift, blocklists, TLS expiry, the queue and DMARC reports daily, apply updates, fix problems and answer your questions. Your apps send over SMTP on port 587. No sandbox, no account someone else can pause, and the IP is yours.
Cost comparison: SES vs your own server
SES prices as of October 2026; confirm on AWS's pricing page. Our prices are on the pricing page. VPS cost is yours, typically $5–20 a month.
| Monthly emails | SES sending (as of Oct 2026) | SES + 1 standard dedicated IP | Managed Server | Server Setup |
|---|---|---|---|---|
| 100,000 | ~$10 | ~$35 | $99 + VPS | VPS only |
| 500,000 | ~$50 | ~$75 | $99 + VPS | VPS only |
| 2,500,000 | ~$250 | ~$275 | $99 + VPS | VPS only |
| One-time | none | none | $499 setup | $499 |
To be clear: on raw sending, SES is cheaper than a Managed Server at 100k and 500k emails, even with a dedicated IP. Only at very high volume does the flat fee come out ahead on sending cost alone, and a bigger VPS or extra IPs at that scale narrow the gap.
What the SES column leaves out is everything else: the engineering time to build bounce handling and dashboards, the time spent watching reputation, and the risk of a paused account. Managed Server includes setup, monitoring, fixes, support and a monthly report. Whether that's worth $99 a month is a fair question only you can answer. The email cost calculator helps you put numbers on it.
Server Setup is $499 one-time with no monthly fee from us. It's the closest match to SES economics: you pay for the VPS and run the server yourself from our runbook.
Sending 250,000+ a month: Scale plans
SES stays cheaper per email. Our hosted Scale plans ($149 a month for 250,000 emails, $249 for 500,000, $399 for 1,000,000) make sense when you want the parts SES leaves to you, such as bounce handling, suppression lists, warm-up and monitoring, run for you on a dedicated IP. Scale plans are in early access; see high-volume email sending.
When to stay on SES
- Cost is your top priority and you're happy to build the tooling.
- Your team already runs AWS and has SES wired up with bounce handling and monitoring.
- You send very high volume and want SES's scale.
- You've never had account trouble and don't expect to.
If emails from SES are landing in spam, check authentication before moving. Our deliverability fix audits SPF, DKIM, DMARC and reverse DNS on whatever provider you use.
Reasons to move
- No sandbox or account pauses imposed by a third party.
- Nothing to build. Monitoring and fixes come with Managed Server.
- Your own server and IP, with your data on it.
- A person to ask when something goes wrong.
What moving looks like
- Choose a VPS that allows outbound port 25. AWS EC2 blocks it by default, removable on request; check your provider.
- Build the server and publish DNS: SPF, DKIM, DMARC and a PTR record. See our reverse DNS guide.
- Point your app at SMTP on port 587, keeping SES as a fallback.
- Warm up the new IP over two to six weeks with engaged recipients first.
- Monitor blocklists and DMARC reports.
Doing it yourself? Follow our Postfix on Ubuntu guide.
What to look for in an SES alternative
Since you won't beat SES on price, be specific about what you're buying instead:
- Less to build. Does the option include bounce handling, suppression and monitoring, or are you still wiring it up?
- Independence from AWS. Tools that send through SES under the hood still depend on your AWS account.
- Your own IP. A dedicated IP on SES is $24.95 a month as of October 2026; on your own VPS it comes with the server.
- A human. When mail stops, who do you ask?
What you take on with your own server
Getting off SES doesn't remove responsibility; it moves it. On your own server, someone has to:
- Keep authentication correct. SPF, DKIM, DMARC and FCrDNS (the PTR, forward DNS and HELO name agreeing). Start DMARC at
p=none, then move toward quarantine and reject; our DMARC guide explains how. - Warm up the IP over two to six weeks.
- Watch blocklists, knowing that some results are false positives.
- Renew certificates and apply updates. We use certbot with a hook that reloads Postfix after renewal.
That someone is you on Server Setup, and us on Managed Server.
The bottom line
If you want the cheapest possible sending and have the skills to build around it, stay on SES. If you'd rather own the server, skip the plumbing and have someone watch it, a managed mail server is the alternative, at a higher but flat monthly cost.
Want it done for you? See Managed Server and Server Setup pricing, or email hello@ownmailserver.com.