Starter
For your first email program.
$192 billed yearly.
20,000 emails / month
Choose Starter- 5 brands · 3 seats
- 5 custom sending domains
- 500 email verifications/month
- $1.50 / 1,000 extra emails
Seven services that replace or sit on top of Amazon SES, plus Nitrosend, ranked on how well each one works as the email tool for an AI agent in Claude, ChatGPT, Cursor or Codex. Every score has its reason and source. Nitrosend wins: an agent can sign up and send with no dashboard, and it can still send through your own AWS keys.
Nitrosend is the best Amazon SES alternative for teams that send email through an AI agent. Of the eight reviewed here it has the top score, 83.75 out of 100, and 9 out of 10 on working from your AI assistant, the test worth the most points. To send email from an AI agent with Nitrosend, add its MCP server at api.nitrosend.com/mcp to Claude, ChatGPT, Cursor or Codex and sign in with OAuth. A transactional email goes out when the agent calls it, and a campaign or flow waits as a draft until someone approves it. SES hands you sending as a set of API calls, and Nitrosend is the product built on them: its default sender runs on SES. It writes every email in your brand's colors, fonts and voice, and your receipts and newsletters go out on one plan and one bill. On a paid plan it can also keep sending through your own AWS account and keys. At one million monthly emails, Scale including overage is $650; some sending-only services quoted here cost less. Resend comes next at 77.5, then Bird (formerly SparkPost) at 76.
83.75 out of 100Total
Nitrosend
Connect Nitrosend to Claude, ChatGPT, Cursor or Codex, point Brand Kit at your site, and describe the email. Contacts are unlimited on every plan.
Free: 5,000 emails to start, then 500 a month. No credit card.
Start free77.5 out of 100Total
76 out of 100Total
Rank 468.5 out of 100Total
Rank 567.5 out of 100Total
Rank 664.5 out of 100Total
Rank 760 out of 100Total
Rank 859.5 out of 100Total
| What we compared | ||||||||
|---|---|---|---|---|---|---|---|---|
| Works from your AI assistant25 points | 9 out of 10 | 8 out of 10 | 8 out of 10 | 8 out of 10 | 6 out of 10 | 6 out of 10 | 7 out of 10 | 3 out of 10 |
| Receipts and newsletters on one plan15 points | 9 out of 10 | 7 out of 10 | 7 out of 10 | 4 out of 10 | 4 out of 10 | 4 out of 10 | 2 out of 10 | 6 out of 10 |
| Emails in your brand, no designer10 points | 9 out of 10 | 6 out of 10 | 4 out of 10 | 6 out of 10 | 5 out of 10 | 5 out of 10 | 4 out of 10 | 5 out of 10 |
| Free plan10 points | 7 out of 10 | 8 out of 10 | 6 out of 10 | 5 out of 10 | 7 out of 10 | 4 out of 10 | 6 out of 10 | 3 out of 10 |
| Price15 points | 8.5 out of 10 | 9 out of 10 | 10 out of 10 | 8 out of 10 | 8 out of 10 | 8 out of 10 | 9 out of 10 | 9 out of 10 |
| Developer tools15 points | 10 out of 10 | 9 out of 10 | 9 out of 10 | 9 out of 10 | 9 out of 10 | 9 out of 10 | 6 out of 10 | 9 out of 10 |
| Track record and support10 points | 4 out of 10 | 6 out of 10 | 7 out of 10 | 6 out of 10 | 9 out of 10 | 9 out of 10 | 7 out of 10 | 8 out of 10 |
| Total scoreout of 100 | 83.75 out of 100,1st | 77.5 out of 100,2nd | 76 out of 100,3rd | 68.5 out of 100,4th | 67.5 out of 100,5th | 64.5 out of 100,6th | 60 out of 100,7th | 59.5 out of 100,8th |
Here are the seven yes-or-no questions developers usually ask before they pick one of these services. A tick means the service does it, as described on its own pages today. A dash means the answer is not a clean yes or no.
| Service | Answer |
|---|---|
| Yes. Yes, through the MCP server. A single transactional email sends on the call; campaigns and flows stay drafts until approved. | |
| Yes. Yes, once a person has created the account and verified a sending domain. | |
| Yes. Yes, through the hosted MCP server once the workspace exists. Emailing customers needs a verified sending domain. | |
| Yes. Yes, once a person has signed up and authorized the MCP connection. | |
| Yes. Yes, once a person has created the account and handed the MCP server an API key. | |
| Yes. Yes, once a person has set up the account and handed the MCP server a server token. | |
| Yes. Yes, through its MCP server once a person adds an API key. | |
| Not a yes or no. Only by writing code against the API. Twilio's own MCP server searches the docs and does not send. |
| Service | Answer |
|---|---|
| Yes. Yes. A remote server at api.nitrosend.com/mcp, with OAuth sign-in. | |
| Yes. Yes. A remote server at mcp.resend.com/mcp, with OAuth sign-in. | |
| Yes. Yes. mcp.bird.com, with OAuth sign-in. | |
| Yes. Yes. Connect by URL and authorize access to the account. | |
| No. No. Mailgun's docs say the server runs locally and no hosted version exists. | |
| No. No. The official server runs locally through npx with an API token. | |
| Yes. Yes. A remote server at developers.smtp2go.com/mcp, with an API key header. | |
| No. No. Every SendGrid server on the official MCP registry is community built, none hosted by Twilio. |
| Service | Answer |
|---|---|
| Yes. Yes. Signup is an API call, and each brand gets a ready sender on a Nitrosend subdomain. | |
| No. No. Resend's own agent guide says a person must create the account. | |
| Not a yes or no. An agent can sign itself up through the CLI or the API, but it must read the emailed sign-in code, and until a sending domain is verified it can send only to sandbox addresses and its own workspace members. | |
| No. No. A person signs up, with a card even on Free, and verifies a domain. | |
| No. No. A person signs up and verifies a sending domain first. | |
| No. No. A person signs up and confirms a sender signature or domain first. | |
| No. No. A person signs up and verifies a sender domain first. | |
| No. No. A sender or a domain has to be verified before real sending. |
| Service | Answer |
|---|---|
| Yes. Yes, on every plan including Free. | |
| Not a yes or no. Broadcasts and automations are in the same account, on a separate marketing plan. | |
| Not a yes or no. Broadcasts share the email allowance. Email automations are in early access, with a separate run allowance. | |
| No. No. Bulk emailing, but no campaign builder or flows. | |
| No. No. Mailing lists and templates, but no campaign builder or flows. | |
| Not a yes or no. Broadcast streams handle bulk sends. There is no campaign builder or automation flows. | |
| No. No. Sending only. | |
| No. No. Marketing Campaigns is a separate plan, from $15 a month. |
| Service | Answer |
|---|---|
| Yes. Yes. 5,000 emails up front, then 500 a month. | |
| Yes. Yes. 3,000 emails a month, 100 a day. | |
| Yes. Yes. 1,000 emails a month, no time limit. | |
| Yes. Yes. 500 emails a month. | |
| Yes. Yes. 100 emails a day. | |
| Yes. Yes. 100 emails a month on the Developer plan, with no expiry. | |
| Yes. Yes. 1,000 emails a month. | |
| No. No. 100 emails a day for 60 days, then a paid plan. |
| Service | Answer |
|---|---|
| Yes. Yes. Brand Kit scans your site, and AI Memory keeps house style. | |
| Not a yes or no. Its AI features list URL and brand analysis, which its docs do not describe yet. | |
| No. No. Templates and React Email, and you supply the design. | |
| No. No. Templates are built in its editors. | |
| No. No. Templates are built in its builder or in HTML. | |
| No. No. A template library you edit into your own brand. | |
| No. No. Templates are yours to build. | |
| No. No. Templates and a design editor, but you supply the design. |
| Service | Answer |
|---|---|
| Yes. Yes. An agent inbox on your own domain posts incoming mail to your webhook. | |
| Yes. Yes, on every plan. | |
| Yes. Yes. Inbound domains and relay webhooks. | |
| Yes. Yes, through inbound routing. | |
| Yes. Yes, through inbound routes. | |
| Yes. Yes, with inbound processing on Pro and Platform. | |
| No. No inbound email in its developer docs. | |
| Yes. Yes, with Inbound Parse. |
At a glance
8 services, the same 7 tests, 100 points in all. In order: Nitrosend 83.75, Resend 77.5, Bird 76, MailerSend 68.5, Mailgun 67.5, Postmark 64.5, SMTP2GO 60, SendGrid 59.5. Nitrosend has the best score on Works from your AI assistant, Receipts and newsletters on one plan, Emails in your brand, no designer and Developer tools. Every price and feature was read on each company's own pages on September 25, 2026.
Nitrosend does not win every test. Read these before you choose it.
Every service ranked here charges by emails sent. SES itself is metered, at $0.10 per 1,000 a la carte or $0.16 per 1,000 on the Essentials plan that new accounts default to since July 21, 2026. That is $3.20 for 20,000 emails and $160 for a million on Essentials, under a third of the cheapest service on this page.
| Service | 20,000 emails a month | 1,000,000 emails a month |
|---|---|---|
| Nitrosend (pricing page) | $20Starter, contacts unlimited | $650Scale, contacts unlimited, including overage |
| Resend (pricing page) | $20Pro, which covers 50,000 | $650Scale |
| Bird (pricing page) | $15Lowest. Startup, which covers 50,000 | $530Growth |
| MailerSend (pricing page) | $35Starter, the first plan with 50 webhooks and 250 templates. Hobby with overage is $29.50 but has 1 webhook and 10 templates | $600Starter |
| Mailgun (pricing page) | $33Basic, 10,000 included and $1.80 per 1,000 after | $700Scale |
| Postmark (pricing page) | $29.50Pro, 10,000 included and $1.30 per 1,000 after. Basic is $33 | $775Basic, the 1,500,000 plan. Pro is $852.50 |
| SMTP2GO (pricing page) | $27Starter, 10,000 included and $1.20 per 1,000 after | $520Professional |
| SendGrid (pricing page) | $19.95Essentials, which covers 50,000 | $799Pro, the 1,500,000 plan. The 700,000 plan is $499 |
At 20,000 emails a month, Nitrosend is $20. That is the same as Resend, and within a few dollars of Bird at $15 and SendGrid at $19.95. SMTP2GO, Postmark and Mailgun charge for every email past 10,000, which puts them at $27 to $33, and MailerSend is $35 on Starter.
At a million emails a month, Nitrosend is $650. SMTP2GO is $520, Bird $530, MailerSend $600, Resend $650, Mailgun $700, Postmark $775 and SendGrid $799. SMTP2GO, Bird and MailerSend cost less, and so does SES itself, though with SES the segments, campaigns and flows are yours to build.
The right comparison with SES is total cost. At a million emails a month the gap between SES on Essentials and Nitrosend is $490. Count the hours that bounce processing, configuration sets, reputation monitoring and support take each month before you call SES the cheaper option. Nitrosend's $20 includes lists, segments, automated flows, brands, templates and deliverability on the same key as the transactional send. If you would otherwise build those around SES, count the build before you compare.
Every service gets a score out of 10 on the same seven tests. Each test is worth a set number of points, 100 in all. Working from your AI assistant is worth the most, 25 points, because that is where email is heading, and it is where SES itself falls short: AWS's own managed AWS MCP Server runs SES API calls, so an agent can send, but it connects with IAM credentials a person sets up, it is a general AWS tool rather than an email product, and new accounts start in the SES sandbox. Price, developer tools and track record, where the older services are strongest, share 40 points, so a service that is better there gets full credit for it. Amazon SES is not ranked on its own alternatives page.
Each test is a question with one answer per service, checked against the service's own pages on September 25, 2026. A 10 means it does the job fully on its normal plans. A 5 means it does part of it, or only on a higher plan or in a second product.
Works from your AI assistant, 25 points. Can an agent inside Claude, ChatGPT, Cursor or Codex go from nothing to a delivered transactional email, and then read back what happened to it, with no person opening the web app along the way? Scored on the first-party MCP server and what its tools cover, a CLI that works in a non-interactive runner, account and sender setup over the API, and listings in the chat apps people already work in. Scored on one written rule for every vendor: a first-party server the vendor runs and that can send counts fully; a third-party wrapper (Zapier, Composio, Kanopi, community servers) counts for less; a server that only drafts or reads counts for less than one that sends.
Receipts and newsletters on one plan, 15 points. Can receipts and password resets, and the newsletters and automated flows that follow them, go out from one account, on one bill, through one API, with the two streams kept apart?
Emails in your brand, no designer, 10 points. Does the product produce the receipt, reset and welcome emails in your brand's own logo, colors, fonts and voice, or does a developer have to write or buy the HTML template first?
Free plan, 10 points. How far can a developer get on the free plan before paying: the monthly volume, the daily ceiling, any one-off starter allowance, and whether the plan is perpetual or a trial that ends.
Price, 15 points. What does sending cost at 20,000 emails a month, where most teams start, and at 1,000,000, where a busy product ends up? Scored on list prices in US dollars, paid monthly, at the cheapest plan that covers the volume. Every ranking on this site uses the same fixed scale. At 20,000 emails, $20 or less scores 10, then $25 scores 9, $32 scores 8, $40 scores 7, $50 scores 6, $70 scores 5, $100 scores 4 and $140 scores 3. At 1,000,000, $500 or less scores 10, then $625, $800, $1,000, $1,250, $1,750, $2,500 and $3,500 step down the same way. Anything dearer, or a price given only by quote, scores 2. The score is the average of the two.
Developer tools, 15 points. How complete is what a developer builds on: a REST API with an OpenAPI spec, official SDKs across languages, a CLI, an SMTP relay, documented delivery-event webhooks, idempotent sends, a test or sandbox mode, inbound email handling, and how deep the reference docs go?
Track record and support, 10 points. How long has it run transactional sending at scale, which deliverability controls can you own (dedicated IPs, suppression, separate streams, a published uptime SLA), and what support comes with the plan?
One thing is not scored: inbox placement. No two of these services publish a comparable deliverability number, so a score there would be a guess dressed up as a measurement.
Keep it when the raw economics matter more than anything else. AWS's pricing page publishes two structures. A la carte is $0.10 per 1,000 emails sent, plus $0.12 per GB of attachment data, and receiving is another $0.10 per 1,000. The three named plans are $0.16, $0.22 and $0.23 per 1,000 up to 10 million a month, falling to $0.11, $0.12 and $0.13 above 100 million, and Pro and Enterprise add a fixed $105 and $500 per account per region per month, checked October 1, 2026. A standard dedicated IP is $24.95 a month. It scales without a sales call.
What you are buying is a set of parts. SES has stored templates, an account-level suppression list and contact lists with topic-based unsubscribes, all as API calls, and support sits on a separate AWS contract. Nothing in SES decides who gets which email and when. AWS's own layer for that, the segments, campaigns and journeys in Amazon Pinpoint, reaches end of support on October 30, 2026. AWS points those workloads to the outbound campaigns in Amazon Connect, its contact-center product, and keeps SES for high-volume transactional delivery. A team that runs its newsletter through Pinpoint has weeks, not quarters, to choose what replaces it.
So the useful question is what you have been building around it. Bounce and complaint handling, configuration sets, reputation dashboards, template management and a way for marketing to send anything without a deploy each turn into a project you did not plan for.
George Hartley, Nitrosend's co-founder, expects the bare sending layer to keep getting cheaper and simpler, and the value to sit above it. On SaaS Stories in September 2026 he said: "in the future future, there's going to be a bunch of kind of dumb email pipes that these agents will just sit on top of." SES is the cleanest example of that pipe. Keep it if you want the pipe and are ready to build the rest; replace it if the rest is what you were missing.
Those are not optional extras, because SES publishes hard thresholds. Its enforcement FAQ puts an account under review at a 5% bounce rate and allows sending to be paused at 10%. It puts an account under review at a 0.1% complaint rate, with sending paused at 0.5%. SES suppresses an address after it hard-bounces, but the list hygiene that keeps you under those lines has to live in front of SES. The sandbox is set per AWS Region, and until production access is granted in a region you are limited there to 200 messages per 24 hours, one a second, to verified recipients only.
SES Mail Manager is a set of email gateway features for inbound and outbound traffic. It is not a campaign feature, and it will not send your newsletter.
Bringing your own AWS account to Nitrosend takes more IAM than sending does. The connection test builds a feedback pipeline inside your account, an SNS topic and an SES configuration set, so the IAM user needs SES and SNS management permissions from the first test. Nitrosend's SES setup guide names the AmazonSESFullAccess and AmazonSNSFullAccess managed policies and does not publish a trimmed-down policy, because a hand-trimmed one fails the connection test or domain setup in ways that look like an authentication problem. Set the region to the one your SES identities live in, because SES quotas apply per region and count recipients rather than messages.
Yes, and for anyone already at volume it is the sensible answer. Your sending reputation lives in your SES account and the identities you have verified, and moving that is the riskiest part of any migration. On a paid plan, connect your AWS keys to Nitrosend and your mail keeps leaving through your own SES account, at your quota and in your region, while Nitrosend handles composition, audiences, automation, tracking and suppression. The setup is two managed IAM policies and a domain verification rather than a migration, and the DNS records you add come from SES identity verification in your own AWS account. The bring-your-own sending keys page has the mechanics.
Less than you fear on the sending side, and more than you expect everywhere else. The send call itself is an afternoon. The machinery around it takes the time. Export your account-level suppression list with ListSuppressedDestinations before the first send, and know what it leaves out. AWS's own documentation says Gmail does not pass complaint data to SES, so a Gmail user who marks your mail as spam never lands on that list, and only hard bounces are added to it. If the account predates November 25, 2019 and nobody switched the list on, it may be empty. If SES has paused your sending, it deletes the list after 90 days, so a pause is the moment to export, not later. Pair the export with your own unsubscribe records. Bounce and complaint handling has to be repointed from SNS to the new provider's webhooks. Configuration sets and their event destinations have no direct equivalent, and templates stored in SES have to be recreated. Do the suppression list first. A new provider that immediately mails addresses you already knew were dead is the fastest way to damage a domain you spent a year warming.
Swapping the API takes an afternoon. The reputation takes weeks.
p=quarantine belongs.For what happens between your request and the recipient's mail server, the email API hub covers the path itself, and the transactional email guide covers the messages that ride on it.
Nitrosend, with the top score in this review, 83.75 out of 100. It adds contacts, templates, campaigns, flows and analytics on top of sending, an AI assistant can run the account from the chat, and it can send through your own AWS account rather than replacing it. Pick Resend for SDKs across languages, Mailgun for inbound routing, and Postmark for transactional delivery you can debug.
Nitrosend, with 9 out of 10 on working from your AI assistant. It has an official MCP server, account signup over the API and a ready-made sender, so an agent in Claude, ChatGPT, Cursor or Codex reaches a first send with no dashboard, and on a paid plan it can keep sending through your own AWS keys. Resend, Bird and MailerSend score 8 with hosted MCP servers. Resend's agent guide says a human must create the account, and Bird's agent signup runs through its CLI with a six-digit code emailed to an inbox someone has to read. SendGrid scores 3, because Twilio's MCP server searches API docs and does not execute calls.
On unit cost, yes, and it is not close. It is $0.10 per 1,000 emails a la carte, or $0.16 per 1,000 on the Essentials plan that new accounts default to. On total cost it depends on what you build around it. At a million emails a month Essentials is $160 against Nitrosend's $650, and that $490 has to cover every hour spent on bounce handling, segments, campaign tooling and reputation monitoring.
Yes. Its default sender runs on SES, with verified domains carrying SPF, DKIM, DMARC, return path and tracking. On a paid plan you can also bring your own AWS account and send on your own SES quota and reputation. It is the same bring-your-own model Nitrosend supports for SendGrid, Mailgun, Postmark and Resend.
For mail to addresses you set up, yes. Nitrosend has an Agent Inbox on your own domain that posts incoming mail to your webhook, and an AI agent can read and reply over MCP. Mail it quarantines as spam, a virus or a blocked sender is not posted. It does not write to your S3 bucket or invoke Lambda directly, so if an SES receipt rule set feeds those today, keep it.
It depends on the plan and the sender's record, not one number. Nitrosend's write-up on sending at scale publishes the rolling 24-hour recipient allowances: on Starter, 1,000 for a new sender, 10,000 at Standard and 100,000 at Trusted, and 300,000 at Trusted on Pro, 1,000,000 on Growth and 2,500,000 on Scale, with Enterprise on contract. A send goes out at the lowest of the plan, sender, pacing and provider limits. With your own SES account connected, your AWS quota is one of those limits, so raising it is still a request to AWS.
Connect Claude to Nitrosend's MCP server at api.nitrosend.com/mcp and approve the OAuth sign-in; ChatGPT, Cursor and Codex connect the same way. Then ask for the receipt or the newsletter in plain words. A single transactional email is sent by the nitro_send_message tool when Claude calls it, while a campaign or flow is saved as a draft and only goes out once it is approved through nitro_control_delivery. If your mail has to keep leaving through SES, connect your AWS keys on a paid plan first and Claude's sends go through your account. The MCP tool reference lists every tool.
Every plan includes full stack emailing: Flows, Newsletter Campaigns and Transactional Email, plus our NitroWheel LLM and all agent integrations (Claude, ChatGPT, Codex, Cursor and others). Pay for what you send, not who you store.
Every paid plan includes 3 agent inboxes and no Nitrosend footer.
For your first email program.
$192 billed yearly.
20,000 emails / month
Choose StarterFor a growing audience.
$480 billed yearly.
60,000 emails / month
Choose ProFor teams and agencies.
$1,440 billed yearly.
200,000 emails / month
Choose GrowthFor high-volume sending.
$2,880 billed yearly.
500,000 emails / month
Choose ScaleSending 500,000+ emails a month? Get a custom plan designed for you, with volume email pricing and capacity that fits your business.
5,000 emails to start, then 500 emails every month. No expiry on your starter emails.
Daily allowances depend on your plan and sender standing. Strong list, domain and delivery evidence can raise standing, including on day one. Trusted receives the full plan allowance; available email credits, safety checks and delivery pacing still apply.
Free forever. No credit card required. See full comparison →