SES under the hood, a product on top.
Amazon SES is infrastructure-first email sending at $0.10 per 1,000 emails, the cheapest way to send email at scale. SES does offer email templates, basic contact lists via SES topics, and a Virtual Deliverability Manager dashboard. What it doesn't give you is a marketing product: no visual campaign builder, no automation flows with branching and wait-steps, no AI copywriting, no MCP.
nitrosend gives you SES economics plus a product on top. Use SES as your BYO sending provider on Pro or Ultra, pay SES's $0.10/1K to AWS, and pay nitrosend's flat monthly fee for the platform (campaigns, flows, templates, segments, AI, 21-tool MCP). Best of both.
Same volume. Real numbers. Pick the row closest to your scale.
| Scenario | | |
|---|---|---|
| Email cost at volume | SES pricing via BYO | $0.10/1K (cheapest) |
| Platform cost (10K emails) | $20 Pro + ~$1 to AWS | $0 (you build the platform layer) |
| Platform cost (1M emails) | ~$500/mo + ~$100 to AWS | $0 + engineering to build a platform |
| Marketing + flows + AI + MCP | Included | Not included; build or buy separately |
Prices accurate as of April 2026. Check vendor sites for current.
No big-bang migrations. Move the pieces you want, keep what works.
Picking a tool is about fit, not tribalism. Here's where Amazon SES genuinely shines.
You have engineering to build (or already have) a campaign tool, flow engine, AI layer, and MCP surface on top, and absolute lowest cost is the priority.
You want SES economics AND a marketing product on top. The combined bill is usually very close to raw SES once you factor in maintenance of your own platform.
Yes. You pay AWS for sends (~$0.10/1K), and nitrosend a flat monthly fee for the platform. AWS's bill is usually small; nitrosend's fee covers the campaigns/flows/AI/MCP layer.
At volume, yes. Break-even is usually around 50-100K emails/month. Below that, shared infrastructure is simpler and cheaper overall. Above that, BYO SES wins.
It can read SES status, verify domains, and read sending stats via the BYO provider integration. It can't create your AWS account or set up IAM roles; you do that once.
Ongoing sends queued via nitrosend will retry per your configured retry policy. We recommend monitoring AWS SES status alongside nitrosend's status page.