The July 2026 pricing change
AWS restructured SES pricing on 21 July 2026, and most guidance written before that date is now wrong in two ways.
New accounts no longer default to the $0.10 rate. Accounts opened from that date start on the Essentials plan at roughly $0.16 per 1,000 emails — about 60% higher. À la carte pricing at $0.10 still exists, and there are now paid tiers above Essentials (Pro at roughly $105 a month per region, Enterprise at roughly $500) that buy support and higher-volume rate reductions rather than different deliverability.
The SES free tier is gone. The old 3,000-messages-a-month-for-twelve-months offer has been replaced by up to $200 in general AWS Free Tier credits spread across eligible services over six months.
Neither change alters the conclusion below — SES is still by a distance the cheapest option at volume — but it does move the break-even against a bundled platform, and it removes the free runway new accounts used to get.
When SES is the right call
Choose SES when per-message cost is the constraint that actually binds. At a few thousand messages a month the difference between providers is rounding; at several million a month it is the largest line in your email budget, and nothing else here comes close.
You are trading money for effort. The setup is genuinely more involved than the alternatives, and when deliverability goes wrong you get infrastructure rather than advice.
What SES does not give you
It is a sending API, and deliberately nothing more. There is no campaign builder, no audience management, no consent tracking, no segmentation, and no reporting beyond raw event notifications.
That is exactly why the pairing works. SES is the pipe; SendNectar is the operating layer — brands, audiences, consent evidence, workflows, and reporting on top. Neither is trying to be the other.
Notes for multi-brand senders
Verify a domain per brand. SES will happily send for several brands from one verified identity, and you should not let it. Reputation accrues per domain, so a shared identity means the least careful brand sets the ceiling for all of them.
Watch the account-level reputation dashboard. SES tracks bounce and complaint rates for the whole account, not per brand. One brand with a bad import can put the entire account under review — which is a strong argument for keeping SendNectar’s frequency caps and suppression enforcement in the path.
Consider separate configuration sets for marketing and transactional streams, so event data stays distinguishable at the AWS layer as well as inside SendNectar.