Amazon SES vs SendGrid vs Mailgun: Which Is Cheapest for Developers? (2026)

Amazon SES vs SendGrid vs Mailgun: Which Is Cheapest for Developers? (2026)

Photo by Taylor Vick on Unsplash

Quick Answer: For developers in 2026, Amazon SES is the cheapest at scale (~$0.10 per 1,000 emails), followed by Mailgun (~$0.80 per 1,000) and SendGrid (~$0.90 per 1,000). For free sending, MisarMail offers unlimited emails. Below, the full pricing and feature comparison.

On This Page

• The Three Email APIs at a Glance
• How Transactional Email APIs Actually Work
• Pricing Comparison
• Free Tier Comparison
• Features Comparison
• Deliverability Comparison
• Setup and Developer Experience
• Which Is Cheapest for Developers?
• Common Mistakes When Choosing or Migrating
• Real-World Scenarios
• The Verdict
• Frequently Asked Questions

The Three Email APIs at a Glance

Platform	Best for	Price per 1,000
Amazon SES	High volume, low cost	~$0.10
Mailgun	Developers, analytics	~$0.80
SendGrid	Startups, ease of use	~$0.90
MisarMail	Free sending	$0

All three of these are "email sending infrastructure" — they take a message your application generates (a password reset, an invoice, a newsletter) and get it onto the public internet's mail-routing system with the best possible chance of landing in the inbox. None of them write your copy or design your templates for you (though SendGrid and Mailgun both offer basic template tooling). What you're really buying is delivery infrastructure: IP address pools with an established sending reputation, relationships with mailbox providers, bounce and complaint handling, and an API or SMTP endpoint that scales without you having to run your own mail servers.

How Transactional Email APIs Actually Work

It helps to understand what happens between your POST /send call and the message showing up in someone's inbox, because it explains why these three services can charge such wildly different prices for what looks like the same commodity.

1. Your application calls the API (or connects over SMTP). You send a JSON payload (or an SMTP DATA command) containing the sender, recipient, subject, body, and any attachments. The provider validates the request, checks your account isn't suspended, and queues the message.

2. The provider's Mail Transfer Agent (MTA) takes over. This is the actual software — Amazon uses a heavily customized internal MTA fleet, SendGrid and Mailgun run large clusters of MTA software (both have historically leaned on customized versions of Postfix-family and proprietary queuing systems) — that is responsible for the SMTP conversation with the recipient's mail server. The MTA looks up the destination domain's MX records, opens a TCP connection to the receiving mail server (Gmail's, Outlook's, Yahoo's, or a corporate mail gateway), and negotiates delivery.

3. Authentication headers are attached. Before the message leaves the provider's network, it's signed with DKIM (a cryptographic signature tied to your sending domain), and the provider's sending IP is checked against your domain's SPF record. If you've published a DMARC policy, receiving servers use the DKIM/SPF results to decide whether to trust the "From" address. All three providers handle DKIM signing automatically once you've added their CNAME or TXT records to your DNS — this is the single most important setup step regardless of which provider you pick, because unauthenticated mail increasingly gets deprioritized or junked outright by Gmail and Yahoo's 2024+ bulk-sender requirements.

4. The receiving server responds with an SMTP status code. A 250 OK means accepted. A 550 or similar 5xx is a hard bounce — permanent failure (bad address, blocked). A 4xx is a soft bounce — temporary (mailbox full, greylisting, rate limiting) and the MTA will retry with exponential backoff for a period (often up to 72 hours) before giving up.

5. Feedback loops report back. If a recipient marks the message as spam, participating mailbox providers (Gmail via Postmaster Tools, Yahoo/AOL via their FBL, Microsoft via SNDS/JMRP) send a complaint signal back to the sending provider, which all three services expose to you via webhooks so you can suppress that address going forward.

The price difference between SES, Mailgun, and SendGrid isn't really about the SMTP conversation itself — that part is nearly free at Amazon's scale. It's about everything wrapped around it: dashboards, analytics, template engines, dedicated support, managed IP warm-up, and — critically — the fact that Amazon treats SES as a low-margin infrastructure primitive (the same philosophy behind S3 and EC2 pricing) while SendGrid and Mailgun are selling a full SaaS product with support staff, a polished UI, and marketing features layered on top.

Pricing Comparison

Amazon SES

Volume	Price per 1,000
First 62,000/month	$0.10
62,000-1M	$0.085
1M+	$0.08

Extras: Data transfer, attachments, and dedicated IPs cost extra.

SES pricing is metered per email, billed alongside the rest of your AWS bill. There's no separate "plan" to pick — you pay for what you send, and the per-thousand rate quietly steps down as volume grows because AWS bills by the underlying compute/bandwidth cost model rather than tiered SaaS plans. If you send email from an EC2 instance in the same AWS region as your SES endpoint, there's no data-transfer charge for the outbound SMTP traffic itself, which is part of why teams already living inside AWS gravitate toward SES — the marginal cost of adding email is close to zero.

SendGrid

Plan	Price per 1,000
Free	$0 (100/day)
Essentials	~$0.90 (50K/month)
Pro	~$1.00 (100K/month)

SendGrid's plans are subscription tiers with a fixed monthly allotment rather than pure pay-as-you-go. Go over your plan's cap mid-month and you're either rate-limited or billed for overage, depending on the plan. The Essentials and Pro tiers also gate features — dedicated IPs, sub-user accounts, and advanced analytics typically require the Pro tier or above, so the effective per-email cost for a team that needs those features is higher than the sticker price per thousand suggests.

Mailgun

Plan	Price per 1,000
Free	$0 (100/day trial)
Foundation	~$0.80 (50K/month)
Scale	~$0.60 (100K+/month)

Mailgun sits in the middle: still a tiered SaaS plan structure like SendGrid, but with a materially lower per-email rate at scale, and a stronger emphasis on developer-facing tooling (routing rules, email validation API, detailed logs retained longer) bundled into the higher tiers.

The Cost at 100,000 Emails/Month

Platform	Monthly cost
Amazon SES	~$10
Mailgun	~$80
SendGrid	~$90
MisarMail	$0 (free plan)

The Cost at 500,000 and 1,000,000 Emails/Month

Platform	500K/month	1M/month
Amazon SES	~$43	~$85
Mailgun	~$300-400 (custom/Scale pricing)	~$600
SendGrid	~$450-500 (Pro tier + overage)	~$900
MisarMail	$0	$0

Notice how the gap widens in absolute dollars as volume grows — at 10K emails a month the difference between SES and SendGrid is a rounding error most teams won't notice on an invoice ($1 vs $9). At 1M emails a month, that same ratio is the difference between an $85 line item and a four-figure one. This is the core reason high-volume senders (transactional platforms, e-commerce backends processing order confirmations, SaaS products sending usage notifications) so often end up on SES once they outgrow a few tens of thousands of sends per month, even if they started on SendGrid or Mailgun for the easier onboarding.

Free Tier Comparison

Platform	Free volume	Duration
Amazon SES	3,000/month	12 months
SendGrid	100/day	Forever
Mailgun	100/day	Trial
MisarMail	Unlimited	Forever

A subtlety worth flagging: Amazon SES's "3,000 free emails a month for the first 12 months" only applies when you send from an EC2 instance, and it has historically been scoped per AWS account under the Free Tier program rather than guaranteed indefinitely — check current AWS Free Tier terms before relying on it for a production launch, since Amazon has adjusted Free Tier eligibility rules over time. SendGrid's 100/day free tier, by contrast, is a permanent (if small) allotment that doesn't expire, which makes it a reasonable choice for a side project or a low-volume transactional flow (think: a handful of signup confirmations a day) that you don't want to put a credit card against yet. Mailgun's free tier is explicitly a trial window rather than a permanent allowance, so budget for it converting to a paid plan.

Photo by Lukas Blazek on Unsplash

Features Comparison

Feature	Amazon SES	SendGrid	Mailgun
SMTP	Yes	Yes	Yes
REST API	Yes	Yes	Yes
Webhooks	Yes	Yes	Yes
Templates	Limited	Yes	Yes
Analytics	Basic	Advanced	Advanced
Suppression list	Yes	Yes	Yes
Dedicated IP	Extra	Paid	Paid
IP pools	Yes	Paid	Paid
SDKs	AWS SDK	Many	Many
Marketing features	No	Yes	Limited
Inbound email parsing	Yes (SES + Lambda/S3)	Yes	Yes (strong)
Email validation API	No (third-party needed)	Add-on	Yes, built in
Sandbox/testing mode	Yes	Yes	Yes
Multi-region sending	Yes (choose AWS region)	Limited	Limited
Log retention	Via CloudWatch (configurable)	3-7 days (plan-dependent)	Up to years on higher tiers
Sub-account/tenant support	Via configuration sets	Yes (subusers)	Yes (subaccounts)
Click/open tracking	Yes	Yes	Yes
Native email templates with dynamic content	Basic (Handlebars via API)	Yes (Dynamic Templates)	Yes (templating engine)

A few of these deserve more explanation because they change which tool actually fits your use case:

• Inbound email parsing matters if your app needs to receive mail — e.g., a support desk that turns replies into tickets, or a "reply to this email to comment" feature. SES handles inbound by routing incoming mail into S3 and optionally triggering a Lambda function, which is powerful but requires you to build the parsing logic yourself. Mailgun's inbound routing is the most turnkey of the three, with rule-based forwarding and a parsed JSON payload delivered to your webhook.
• Log retention is an underrated cost driver. SES's raw sending events live in CloudWatch/EventBridge only as long as you configure retention for — which is cheap but you own the pipeline. SendGrid's lower tiers cap activity feed history at just a few days, meaning a bounce that happened two weeks ago may no longer be visible in the dashboard unless you're piping events to your own webhook receiver and storing them. Mailgun's higher tiers retain logs far longer, which matters for compliance-sensitive teams that need to prove delivery history during an audit.
• Sandbox mode exists on all three so you can test integrations without accidentally spamming real addresses (or burning your reputation) before you're verified for production sending — SES in particular requires you to formally request "production access" to move out of a strict sandbox that only allows sending to verified addresses.

Deliverability Comparison

Factor	Amazon SES	SendGrid	Mailgun
Reputation	Strong	Strong	Strong
Warm-up	Manual	Assisted	Manual
Tracking domain	Yes	Yes	Yes
Feedback loop	Yes	Yes	Yes
Postmaster tools	Yes	Yes	Yes
Shared IP pool quality	Variable (depends on other tenants)	Managed, generally strong	Managed, generally strong
Dedicated IP warm-up assistance	Manual (you control the ramp)	IP Warmup feature (automated ramp)	Manual, documented playbook
Bounce classification detail	Good (SNS notifications with diagnostic codes)	Good (categorized bounce types)	Very detailed (granular reason codes)

The note: All three have strong deliverability. Your setup (authentication, list hygiene, content) matters more than the provider.

Deliverability is worth unpacking because it's the single thing people worry about most when comparing these platforms, and the honest answer is: the provider matters less than your practices. Here's what actually determines whether your mail lands in the inbox, the spam folder, or gets rejected outright, regardless of which of these three you use:

1. Domain and IP reputation, built over time by consistent sending patterns, low complaint rates, and low bounce rates. A brand-new sending domain has no reputation at all, which is why "domain warm-up" — gradually ramping volume over 2-4 weeks — matters more than which API you chose.
2. Authentication completeness — SPF, DKIM, and DMARC all correctly aligned to your sending domain. Mailbox providers increasingly treat unauthenticated bulk mail as presumptively spam.
3. List hygiene — sending to addresses that bounce, that were scraped rather than opted in, or that haven't engaged in months drags down your sender score regardless of provider.
4. Content signals — spammy subject lines, excessive links, image-only emails with no text, and URL shorteners all raise flags in modern content-based spam filters (which sit alongside, not instead of, reputation-based filtering).
5. Engagement — Gmail in particular weighs how often recipients open, reply to, and star your messages versus delete them unread or mark them spam. This is measured per-domain and per-IP and follows you across providers if you migrate but keep the same sending domain.

Shared-IP senders on SendGrid and Mailgun benefit from (and are exposed to) the reputation of everyone else sharing that IP pool — both providers actively monitor and rotate/quarantine bad actors to protect the pool, but it's still a shared resource. SES's default sending is also effectively a shared pool (AWS's IP ranges) unless you provision a dedicated IP, and it has historically had a reputation among some deliverability specialists for requiring more hands-on reputation management because AWS provides less "batteries included" tooling around it compared to SendGrid's guided warm-up wizard. None of that means SES delivers worse mail — plenty of very high-volume, well-run senders run entirely on SES — it means you're expected to build more of the reputation-monitoring stack yourself (or use a third-party deliverability monitoring tool) rather than getting it inside the dashboard.

Setup and Developer Experience

This is where the three products diverge the most in practice, even though the comparison tables above make them look similar on paper.

Amazon SES requires an AWS account, which means IAM users/roles, verifying your sending domain via DNS records in Route 53 (or your DNS provider), and — critically — requesting production access by submitting a use-case description to AWS support, since every new SES account starts in a sandbox that can only send to verified addresses at a low rate. This review can take anywhere from a few hours to a couple of days. For a team already comfortable with AWS IAM policies, VPC networking, and CloudWatch, this is a non-issue. For a solo developer who has never touched AWS, it's a genuinely steep first afternoon. The payoff is that once it's running, SES integrates natively with the rest of an AWS stack — Lambda for inbound processing, SNS for bounce/complaint notifications, EventBridge for routing events into your own pipeline — with no separate vendor relationship to manage.

SendGrid is built to get a developer from signup to first successful send in minutes: an API key, a curl request or a five-line snippet in their SDK, and you're sending. Domain authentication (their term for the SPF/DKIM setup) is a guided wizard that generates the exact CNAME records to paste into your DNS provider. This is the reason SendGrid remains the default recommendation in countless "how to send transactional email" tutorials — the time-to-first-email is the shortest of the three.

Mailgun sits close to SendGrid in onboarding friction but leans harder into being a tool built for developers specifically — the docs read more like API reference material and less like marketing copy, the routing rules for inbound mail are genuinely powerful, and the email validation API (checking whether an address is real/deliverable before you send to it) is a meaningfully useful feature that isn't bundled for free on the other two.

Which Is Cheapest for Developers?

The Cost Analysis

Scenario	Amazon SES	SendGrid	Mailgun
10K/month	~$1	~$9	~$8
50K/month	~$5	~$45	~$40
100K/month	~$10	~$90	~$80
1M/month	~$85	~$900	~$600

The Hidden Costs

Cost	Amazon SES	SendGrid	Mailgun
Setup complexity	High	Low	Medium
AWS account needed	Yes	No	No
Attachments	Extra	Included	Included
Dedicated IP	~$24/month	~$40/month	~$60/month
Engineering time to integrate	Higher (IAM, sandbox review, DNS)	Lower	Lower-medium
Support	Community + paid AWS Support plans	Included (plan-dependent)	Included (plan-dependent)
Analytics dashboard	Requires building your own or using CloudWatch	Built-in	Built-in

The "cheapest" answer depends heavily on how you value engineering time versus the invoice line item. A one-person startup burning a weekend to get SES production access approved, IAM policies scoped correctly, and a bounce-handling Lambda deployed might spend more in opportunity cost than the SendGrid subscription would have cost for the first year of the product's life. Conversely, a company already running infrastructure on AWS with a platform team that manages IAM as a matter of course will find SES nearly free to bolt on, both in dollars and in incremental engineering effort — the DNS and IAM patterns are already familiar.

A reasonable rule of thumb: under ~20,000 emails/month, the dollar difference between all three (and even MisarMail's free plan) is small enough that setup speed and feature fit should drive the decision. Above roughly 100,000-200,000 emails/month, the SES discount becomes large enough in absolute terms that it's worth the extra integration effort for most teams, unless the marketing/analytics features of SendGrid or Mailgun are load-bearing for your business (e.g., you rely heavily on their dashboards instead of building your own analytics).

Common Mistakes When Choosing or Migrating

Picking based on the headline per-1,000 price alone. As the hidden-costs table above shows, dedicated IPs, attachment handling, and support tier can shift the real cost meaningfully. Always price out your actual expected volume and feature needs, not just the cheapest listed tier.

Staying in SES sandbox mode in production. Teams sometimes launch believing they're live, only to discover every email to an unverified address is silently being rejected because they never requested (or were denied) production access. Always confirm your SES account status before launch.

Migrating providers without re-establishing authentication records. Moving from SendGrid to SES (or vice versa) means new DKIM selectors and often a new sending subdomain. Forgetting to update DNS — or leaving old provider's DKIM records in place alongside the new ones incorrectly — can break authentication for both old and new mail simultaneously during the transition window.

Ignoring bounce and complaint webhooks. All three providers will happily let you keep sending to addresses that have hard-bounced or complained if you don't wire up their suppression/webhook system to your own database. This is one of the fastest ways to tank sender reputation, and it's entirely avoidable — it just requires actually consuming the webhook events rather than treating "send" as fire-and-forget.

Assuming a "high volume" plan automatically means better deliverability. Paying more for SendGrid Pro or Mailgun Scale buys you features (dedicated IPs, more analytics, longer log retention) — it does not, by itself, buy you a better inbox placement rate. Placement is earned through the practices covered in the Deliverability section above, on any of the three platforms.

Underestimating dedicated IP warm-up time. Provisioning a dedicated IP and immediately blasting full volume through it is one of the most common ways new senders get themselves rate-limited or blocklisted. A dedicated IP starts with zero reputation and needs the same gradual ramp a brand-new domain does — often 2-4 weeks — regardless of which of the three providers issued it.

Real-World Scenarios

A two-person SaaS startup sending password resets, receipts, and a weekly digest (~5,000-15,000 emails/month). At this volume the dollar cost is trivial on any provider. SendGrid's fast setup and built-in analytics dashboard (so you're not building your own) is usually the pragmatic pick, unless the team is already deep in AWS, in which case SES is nearly as easy and slightly cheaper. A team wanting to defer any spend entirely could run this volume on MisarMail at no cost.

An e-commerce store sending order confirmations, shipping updates, and abandoned-cart emails (~80,000-150,000 emails/month, seasonal spikes to 300K+ around holidays). This is the volume band where SES's pricing advantage starts to bite meaningfully, but the seasonal burstiness matters too — SES's pay-per-email model handles a holiday spike gracefully (you just pay for the extra emails sent, no plan upgrade needed), whereas a SendGrid or Mailgun customer might blow through their monthly plan cap in the first week of Black Friday and need to pre-emptively upgrade tiers.

A developer tools company building notification infrastructure for its own customers (multi-tenant sending, needs strong routing and per-tenant analytics). Mailgun's subaccount structure and detailed per-message logs are purpose-built for this — being able to hand each tenant visibility into their own sending activity without exposing the whole account is a genuine differentiator here.

An agency running email marketing/newsletters for multiple small-business clients. None of these three are really marketing-email platforms first (SendGrid has the most marketing tooling of the three, but it's not its core identity the way a Mailchimp or a Brevo is) — a dedicated marketing platform or a free option like MisarMail is usually a better fit for that specific workload, with SES/SendGrid/Mailgun reserved for the transactional side (receipts, password resets) of the same client's stack.

The Verdict

Choose Amazon SES if...

• You send 100K+ emails/month
• You're already on AWS
• Cost is your top priority
• You can handle the setup complexity

Choose SendGrid if...

• You want the easiest setup
• You need marketing features
• You're a startup with low volume
• You want great docs and SDKs

Choose Mailgun if...

• You want advanced analytics
• You need flexible routing
• You're a developer-first team
• You want a middle-ground price

The Free Option

MisarMail offers unlimited free email sending with SMTP and API — the cheapest option for developers who want zero cost. It's a natural fit for the marketing/newsletter side of a stack that uses SES, SendGrid, or Mailgun purely for transactional mail, letting you split spend so you're not paying transactional-API rates for bulk marketing sends.

Related Reads

• SendGrid Free Plan Alternatives: Cheaper Email APIs 2026
• Free SMTP Server for Sending Email: Top Options Compared 2026
• Dedicated IP vs Shared IP for Email: Which Should You Use?
• How to Warm Up an Email Domain the Right Way