The best email platforms of 2026.

Eleven platforms, tested against the questions that actually decide the choice: what a real month costs, whether marketing and transactional email share one contact, and who still lands in the inbox now that the bulk-sender rules have teeth.

19 min read11 platformsPrices tracked July–August 2026
Fig. 1Eleven platforms, three architectures, one act: handing a message to a mail server on somebody else's behalf.

There has never been a better time to send email and never a more confusing time to pick who sends it. The category split into three shapes years ago and most comparison articles still pretend it is one: transactional APIs that move a receipt in under a second, marketing suites built for someone who designs campaigns in a browser, and a newer middle group arguing that the split was always artificial because the person receiving both is the same person.

Choosing badly is not a small mistake. Email is the one part of your stack that reaches into somebody else's inbox, which means the cost of getting it wrong is not a refactor — it is a domain reputation you spend months rebuilding, or a bill that grows every month whether you send anything or not. Two of the most common regrets in this market are structural rather than technical: picking a transactional-only API and discovering in month eight that the welcome series needs a second vendor, and picking a per-contact platform and watching the invoice climb on a list you barely mail.

So this is not a feature matrix with eleven rows of green ticks. Each platform below gets the same treatment: what it is genuinely best at, what a real month costs at three volumes, and the specific circumstances in which it is the wrong answer. Where a competitor beats us, we say so and link to their strengths, because a comparison you cannot trust is worth nothing to you and nothing to us.

Where we stand

We make one of the eleven. Volanea is our product, this is our blog, and pretending otherwise would insult your intelligence.

Two things follow from that. First, Volanea is not ranked first — the platforms are grouped by what they are for, not scored against each other, because a single ranking would let us put ourselves at the top on criteria we picked. Second, its review carries the same honest list of drawbacks as everyone else's, including the ones that cost us customers: no visual builder, no long deliverability record, no SOC 2 yet. Competitor pricing comes from public pricing pages tracked in July and August 2026; if you spot something out of date, it is an error rather than a thumb on the scale, and we will fix it.

01 — The short answer

If you only read one section.

Price shown is the monthly bill at 50,000 emails. Cards are grouped, not ranked — jump to any review for the full account, including where each one is the wrong choice.

02 — Context

What actually changed in 2026.

The single largest shift in this market was not a product launch. In February 2024 Google and Yahoo began enforcing bulk-sender requirements, and by 2026 those rules have hardened from a compliance exercise into the thing that decides whether your mail arrives at all. Any domain sending meaningful volume now needs SPF and DKIM alignment, a published DMARC record, one-click unsubscribe honoured within two days, and a spam complaint rate held under 0.3 percent — with 0.1 percent as the number to actually aim for.

That last figure changed the economics quietly. A complaint rate is a ratio, so it punishes sending to people who did not ask far more than it punishes sending too much. Platforms that make it easy to mail a stale imported list are now actively dangerous to your domain, and platforms that keep one authoritative suppression state across every kind of message have a structural advantage that has nothing to do with their feature list.

Second, the pricing conversation moved. Per-contact billing — where you pay for people stored rather than messages sent, and unsubscribed contacts keep counting until someone archives them — has been the marketing-suite default for a decade, and it is now the most common reason teams migrate away. A large list that you email twice a quarter is the single most expensive shape in that model and the single cheapest in a per-send one. Nothing about your sending changed; only who you bought from.

Third, the middle filled in. In 2021 you genuinely had to choose between a good API and a real campaign tool. In 2026 several platforms do both competently on one contact record, which removes the old excuse for running two systems and syncing them with a CSV export that somebody forgets. That is the interesting part of this market right now, and it is why the reviews below are grouped by architecture rather than by brand size.

Spam complaint rate — the number that decides everything0.10%aim below this0.30%Google throttles above here0%0.5%Table stakes since February 2024 — non-negotiable in 2026SPF + DKIMon every sending domainDMARC recordp=none is the minimumOne-click unsubscribeList-Unsubscribe-Post
Fig. 2The bulk-sender baseline. Complaint rate is a ratio, so it punishes mailing people who never asked far harder than it punishes mailing often.

Not sure where your domain stands? Our free DMARC checker reads your live DNS and tells you what is missing, and the email verifier catches the addresses that would bounce before you send to them.

03 — Method

How we judged them.

Every platform here was assessed against the same five questions, weighted toward the ones you cannot easily change your mind about later.

01

What a real month costs

Published list price at 1,000, 10,000, 50,000 and 100,000 emails a month, including overage. Not the headline number — the number on the invoice, with the shape of the billing model stated plainly, because per-contact and per-send bills diverge enormously on the same list.

02

Whether one person is one record

Do transactional sends, campaigns, and automation share a contact and a consent state, or are they separate systems joined by an export? This is the decision that is expensive to reverse, so it carries the most weight.

03

Deliverability posture

Track record, whether marketing and transactional traffic are separated, what happens automatically when bounces or complaints spike, and how much of that you are expected to build yourself.

04

How long the first send takes

Time from signing up to a real message in a real inbox, including domain verification. A platform you can adopt in an afternoon has a genuine advantage over one that needs a week and a support ticket.

05

The exit

How hard it is to leave — whether contacts, templates, suppression lists, and event history come out in a usable form. A platform that is difficult to leave should have to earn your stay every month.

04 — Transactional-first APIs

Transactional-first APIs.

Built to move one message to one person the moment your code says so: receipts, password resets, alerts. They are judged on latency, inbox placement, and how little of your week they cost.

01

Resend

Best developer experience

A modern transactional email API from the team behind React Email, known for a famously clean dashboard and SDKs in nearly every language.

Free tier

3,000/mo (100/day cap)

Entry plan

$20/mo — Pro

50,000 / mo

$20

Resend is the platform that made everyone else redesign their dashboards. The onboarding is three steps, the API is a single well-documented POST to /emails, and the event log is legible enough that you can debug a failing send at 2am without opening a support ticket. If you have ever fought a decade-old email console, the difference is not cosmetic — it is hours of your life.

React Email is the genuine moat. Writing your templates as React components, previewing them in your own dev server, and rendering them at send time removes the worst part of transactional email: maintaining table-based HTML that renders differently in Outlook. Nothing else on this list has an equivalent that is as polished, and if your team already lives in React the productivity gain is real.

The limits show up when your email stops being purely transactional. Broadcasts exist but are deliberately light — no automation workflows, no dynamic segments, and contact limits that bite on the lower plans. The free tier is generous at 3,000 emails a month but capped at 100 per day, which is exactly the wrong shape for a launch day. And at 50,000 emails Resend Pro and a mid-tier all-in-one now cost the same $20, so the price argument has quietly evaporated.

Strengths

  • The cleanest developer experience of any email API, by a distance
  • React Email is a genuinely better way to build templates
  • SDKs in every major language, not just one
  • Established deliverability record and SOC 2

Trade-offs

  • No automation workflows or dynamic segments
  • Contact limits on lower plans (1,000 on Free)
  • The 100/day cap on the free tier breaks launch days
  • Broadcasts are a feature, not a marketing product
02

Postmark

Best deliverability record

The transactional specialist, now part of ActiveCampaign — fifteen years of running separate infrastructure for application mail and nothing else.

Free tier

100/mo

Entry plan

$15/mo — 10,000

50,000 / mo

≈$87est.

Postmark's whole argument is one number: how long it takes a password reset to land, and how reliably it lands at all. They keep transactional traffic on infrastructure that never carries bulk marketing mail, publish their delivery times openly, and have spent fifteen years refusing the temptation to bolt a campaign builder onto the side. It is the closest thing to a safe institutional answer for a product where a late email is a support ticket.

The tooling around that focus is quietly excellent. Message streams separate your application mail from your broadcasts so a promotional send can never poison the reputation your receipts depend on. Inbound processing — parsing replies into your app via webhook — is first-class in a way most competitors treat as an afterthought. The templating system with layouts is sensible, and the activity log tells you what a remote mail server actually said.

The catch is the bill above the tier. Basic is $15 for 10,000 emails, and overage runs $1.80 per 1,000 — so 50,000 emails lands near $87 and 100,000 near $177, several times what a flat-tier provider charges for the same volume. There is no automation, no segmentation, and the free tier stops at 100 emails a month, which is not enough to build against. You pay a real premium here, and what it buys is consistency.

Strengths

  • The best-documented transactional deliverability record in the market
  • Message streams keep marketing mail away from your receipts
  • First-class inbound email parsing
  • Support that actually understands email

Trade-offs

  • $1.80 per 1,000 overage compounds hard above the tier
  • No automation workflows or segments at all
  • 100 emails/month free tier is barely a demo
  • Dedicated IPs need a 300k/month minimum
03

Amazon SES

Best raw cost at scale

AWS's email sending service — the wholesale layer a surprising share of this list quietly resells, priced at roughly $0.10 per thousand messages.

Free tier

3,000/mo, first 12 months

Entry plan

Pay as you go

50,000 / mo

≈$5est.

SES is not really a competitor to the rest of this list; it is the pipe several of them run through. At about $0.10 per 1,000 emails it is an order of magnitude cheaper than anything else here — 100,000 messages costs roughly $10, against $65 to $177 for the same volume elsewhere. If you send millions and you have an engineer who enjoys this problem, nothing beats it on price and nothing ever will.

What you buy at that price is capability without product. There is no dashboard worth the name, no template versioning, no campaign tool, no contact store, and no automation. Bounce and complaint handling is an SNS topic you subscribe to and a state machine you write yourself. Getting out of the sandbox requires a written request describing your sending practices, and reputation management is entirely your responsibility — SES will suspend an account whose complaint rate drifts, and it will be right to.

The honest framing: SES is infrastructure, and the platforms above it charge for the six months of engineering you would otherwise spend building suppression lists, retry logic, webhook fan-out, and a log you can search. That trade is excellent at very high volume and terrible at low volume, where the engineering cost dwarfs the savings. Below roughly 200,000 emails a month, you are paying an engineer's afternoon to save fifteen dollars.

Strengths

  • Roughly $0.10 per 1,000 — nothing else is close
  • Effectively unlimited scale and AWS-grade reliability
  • Deep IAM, VPC, and CloudWatch integration if you already live in AWS
  • Configuration sets give real per-stream control

Trade-offs

  • No contact store, campaigns, automation, or usable dashboard
  • You build suppression, retries, and event handling yourself
  • Sandbox exit is a manual approval process
  • Reputation management is entirely on you
04

Mailgun

Best for high-volume infrastructure teams

One of the longest-running transactional email APIs, now under Sinch — built for teams that measure sending in millions and care about validation and routing.

Free tier

100/day, 1-day logs

Entry plan

$15/mo — 10,000

50,000 / mo

$35

Mailgun has been delivering email since before most of this list existed, and the maturity shows in the unglamorous places. Inbound routing with regex rules, an email validation service that has seen enough addresses to be genuinely accurate, detailed suppression management, and per-domain sending controls are all there and all battle-tested. For a team running high-volume transactional traffic with compliance requirements, it is a rational default.

Pricing is tiered with overage: $15 a month for 10,000 on Basic, $35 for 50,000 on Foundation, $90 for 100,000 on Scale — reasonable in the middle, genuinely competitive at the top where dedicated IPs and longer log retention come into play. The free tier is the weak point at 100 emails a day with one-day log retention, which is not enough to develop against without hitting the wall on your first load test.

The gap is everything after the send. Mailgun is transactional only; campaigns and marketing automation mean buying Mailjet, a separate product under the same corporate roof with a separate contact store and a separate bill. If your roadmap has a welcome series on it, you are choosing a two-system architecture on day one — which is fine if you know it, and expensive if you find out in month eight.

Strengths

  • Mature, accurate email validation at scale
  • Powerful inbound routing rules
  • Dedicated IPs and long log retention on higher tiers
  • Competitive above 50,000 emails a month

Trade-offs

  • Transactional only — campaigns are a separate product and bill
  • 100/day free tier with 1-day log retention
  • The console shows its age next to newer entrants
  • Support quality varies by plan tier
05

SendGrid

Best for enterprise procurement

Twilio's email arm and one of the largest senders on the internet, moving billions of messages a month for companies of every size.

Free tier

None — 60-day trial

Entry plan

$19.95/mo — Essentials

50,000 / mo

$19.95

SendGrid's advantage is institutional. It has fifteen-plus years of deliverability data, dedicated IP pools, subuser accounts for multi-tenant products, SOC 2 and ISO certifications, enterprise SLAs, and a Twilio-sized company behind the invoice. When a procurement team asks who else runs on this, SendGrid has the longest answer of anyone on this list, and for large organisations that is frequently the deciding factor.

The volume economics are still strong. Essentials runs $19.95 a month and covers up to 50,000 emails; the next tier up carries 100,000 for around $29.95. Past that, per-message pricing keeps falling in a way most flat-tier providers simply do not offer. If your baseline is hundreds of thousands of transactional messages a month, SendGrid remains one of the cheapest credible options that comes with a support contract.

For everyone smaller, 2026 looks different than 2020. SendGrid retired its permanent free plan in 2025 — new accounts get a 60-day trial at 100 emails a day and then face a $19.95 floor, which is a hard sell against providers giving away 1,000 to 3,000 emails a month forever. Marketing Campaigns is a separate, contact-priced product, so the all-in-one story requires two line items. And the console remains the most complicated on this list.

Strengths

  • Enormous scale with genuine enterprise support and SLAs
  • Subuser accounts are excellent for multi-tenant products
  • Cheapest credible option well above 100,000 emails/month
  • Certifications procurement teams ask for

Trade-offs

  • No permanent free plan since 2025 — $19.95 floor after a 60-day trial
  • Marketing Campaigns is a separate, contact-priced product
  • The most complex console of anything reviewed here
  • Deliverability varies more on shared IPs than specialists

05 — Unified platforms

Unified platforms.

One system for the receipt and the newsletter, sitting on a single contact record. The pitch is that a person is a person — the same unsubscribe, the same event history, whichever kind of mail you are sending.

Two systemsTransactional APIMarketing toolContacts Aapp databaseContacts Blist in the toolCSV export, when someone remembersunsubscribes drift out of syncOne contact graphTransactionalCampaignsAutomationOne contact recordstatus, events, consentone unsubscribe, honoured everywhere
Fig. 3The architectural difference the middle group is selling. On the left, two contact stores and a synchronisation problem; on the right, one record that every kind of message reads and writes.
06

Volanea

Best one-API all-in-one for small teamsOur product

Transactional email, campaigns, and automation on a single contact graph, billed by emails sent rather than contacts stored.

Free tier

1,000/mo, no daily cap

Entry plan

$5/mo — 7,500

50,000 / mo

$20

Disclosure first, because it matters for how you read the rest: we build Volanea, and this is our blog. What follows is the same account we give on our comparison pages, including the parts that lose us the sale.

The design premise is that splitting a person across two systems is the root of most email pain. One contact record carries the transactional history, the campaign engagement, and the consent state, so an unsubscribe from a newsletter is honoured everywhere immediately and a segment can be built from a product event without an export. Campaigns get A/B subject tests, scheduling, and resend-to-non-openers; automation runs event-triggered workflows with delays and branches; templates are versioned with rollback. Billing is by emails sent — 1,000 free every month with no daily cap, $5 for 7,500, $20 for 50,000, $149 for 200,000 — with unlimited contacts on every plan and hard spending caps you set yourself.

What you give up is real. The visual editor is newer and plainer than Mailchimp's gallery of designed templates, so a marketer who lives in a template library will miss it. There are no dedicated IPs, the SDK story is TypeScript plus REST rather than every language, sending runs over Amazon SES rather than our own infrastructure, and the product is new in 2026 — it does not have Postmark's fifteen-year record or SendGrid's certifications, and no amount of writing makes that untrue. If procurement needs a decade of history, or a marketer who wants a large gallery of ready-made designs owns your campaigns, one of the other names here is the better answer.

Strengths

  • Transactional, campaigns, and automation on one contact record
  • Unlimited contacts on every plan, including free
  • 1,000 free emails a month with no daily cap
  • Template versioning with rollback, and hard spending caps

Trade-offs

  • Visual editor is young next to Mailchimp-style template galleries
  • New in 2026: no long deliverability record, no SOC 2 yet
  • TypeScript and REST only; no dedicated IPs
  • Above 200,000 emails a month you are on a custom plan
07

Customer.io

Best behavioural messaging at scale

A lifecycle messaging platform built around event streams, where email, push, SMS, and in-app all hang off the same behavioural data.

Free tier

None — trial only

Entry plan

≈$100/mo

50,000 / mo

≈$100+est.

Customer.io is what a serious lifecycle programme graduates into. You stream product events in, and the workflow builder lets a growth team compose genuinely sophisticated journeys — multi-branch conditions, wait-until-event steps, frequency caps, holdout groups, and per-message A/B tests — without an engineer in the loop for every change. The data model treats a person's behaviour as the primary object, which is exactly right for retention and onboarding work.

The multi-channel story is the other draw. The same journey can send an email, then a push notification, then an SMS, with the suppression and frequency logic applied across all of them rather than per channel. Most of this list makes you assemble that from parts; Customer.io ships it, and the reporting understands it.

The cost of entry is steep. Pricing is profile-based and starts around $100 a month for a few thousand profiles, climbing quickly with list size — an order of magnitude above the transactional APIs on this page, and it is billed on people stored rather than messages sent. There is a real implementation cost too: the platform assumes you have clean, well-named events flowing in, and a team that has not done that groundwork will get a very expensive workflow builder full of nothing. It is the right tool for a growth team, and overkill for a side project.

Strengths

  • The strongest visual journey builder in this comparison
  • Email, push, SMS, and in-app on shared suppression and frequency rules
  • Event-driven data model built for retention work
  • Reporting a growth team can actually run on

Trade-offs

  • Starts around $100/month and scales on profiles stored
  • Needs clean event instrumentation before it pays off
  • Overkill for pure transactional sending
  • Meaningful implementation and onboarding effort
08

Loops

Best lightweight SaaS product email

A deliberately opinionated email platform for software companies — transactional and marketing in one place, with a small, elegant surface area.

Free tier

Small list, free tier

Entry plan

≈$49/mo

50,000 / mo

≈$49+est.

Loops made a bet most of this market avoided: that a SaaS team wants fewer options, not more. The editor is clean, loops (their term for automated sequences) are quick to assemble, and the whole product can be understood in an afternoon. Sending a transactional email is a short API call; setting up a welcome series is a few clicks; there is no wall of settings between you and either. For a small product team that wants good email without an email project, that restraint is the feature.

The audience model is contact-based with custom properties, and it handles the ordinary SaaS jobs well — trial nudges, onboarding sequences, feature announcements, and the receipts in between, all on one list with one unsubscribe. Deliverability has been solid, and the team ships steadily.

The same restraint is the limitation. Segmentation is simpler than Customer.io's or a mature marketing suite's, the automation branching is shallower, and pricing is contact-tiered — starting free for a small list and climbing from roughly $49 a month — which means a large, lightly-mailed list costs more here than on a per-send platform. There is no self-hosting, and the reporting is adequate rather than deep. It is a very good fit for its exact shape of customer and a poor one just outside it.

Strengths

  • Genuinely pleasant to use — understandable in an afternoon
  • Transactional and marketing on one contact list
  • Sensible defaults instead of a settings maze
  • Well suited to ordinary SaaS lifecycle email

Trade-offs

  • Contact-tiered pricing punishes large, rarely-mailed lists
  • Shallower segmentation and branching than specialists
  • Reporting is adequate rather than deep
  • Small feature surface by design — you will hit edges
09

Plunk

Best open-source and self-hosted option

An open-source email platform combining transactional sending, campaigns, and automations, priced at a flat $0.001 per email on the hosted version.

Free tier

1,000/mo

Entry plan

$0.001/email

50,000 / mo

≈$50est.

Plunk is the answer when self-hosting is a requirement rather than a preference. The source is open, the deployment is documented, and running it on your own infrastructure over your own SES credentials puts every contact record inside your perimeter — which for regulated products, EU data-residency requirements, or teams with a firm no-third-party-PII rule is not a nice-to-have but the whole decision.

The hosted version prices purely per email at $0.001 with no base fee and no tiers, which is the most honest pricing shape on this page: you pay for exactly what you send and nothing else. Contacts are unlimited, 1,000 emails a month are free, and the product covers transactional sending, campaigns, and automations from the same contact list. For volumes in the eight to twenty thousand range, that metered bill undercuts most flat $20 tiers.

It is a smaller product than the funded platforms around it, and that shows in depth rather than direction. Segmentation is lighter, there is no template versioning or rollback, campaign A/B testing is not there, and the analytics are basic. Self-hosting also means you inherit the operational load — queue health, IP warm-up, bounce processing, upgrades. That is a fair trade for control, but it is a trade, and it costs someone's time every month.

Strengths

  • Genuinely open source and self-hostable
  • Flat $0.001 per email with no base fee — cheapest at mid volume
  • Unlimited contacts, transactional and marketing in one place
  • No vendor holding your contact data

Trade-offs

  • Lighter segmentation, no template versioning or A/B tests
  • Self-hosting means you own the operational load
  • Basic analytics compared with funded competitors
  • Smaller team and ecosystem

06 — Marketing-first suites

Marketing-first suites.

Campaign tools with an API attached rather than the other way round. Strong visual builders, list management, and reporting; developer ergonomics are the trade.

Billed per contact storedThe list grows. The bill grows with it.JFMAMJsent nothing —still billed $78Billed per email sentStore what you like. Pay for what leaves.JFMAMJquiet month —billed $0
Fig. 4The same list, two billing models, six months. Per-contact bills track how many people you store; per-send bills track how much mail actually left.
10

Mailchimp

Best for marketer-designed campaigns

The best-known email marketing brand in the world, owned by Intuit, built around a drag-and-drop campaign editor for non-technical teams.

Free tier

500/mo, 250 contacts

Entry plan

≈$13/mo

50,000 / mo

≈$75–100est.

If a person who does not write code is responsible for your email, Mailchimp is still the strongest answer on this page and it is not especially close. The drag-and-drop builder is the best in class, the template gallery is enormous, and the surrounding product — landing pages, signup forms, e-commerce integrations with Shopify and everything else, an AI-assisted content assistant — means a marketer can run a whole programme without opening a ticket. Fifteen years of polish is visible in every screen.

The problem for a developer-led team is the billing model. Mailchimp charges for contacts stored, not emails sent, and unsubscribed contacts keep counting until someone manually archives them. That means a list that grows produces a bill that grows even in a month you send nothing at all — a 5,000-contact list on a mid tier lands somewhere around $75 to $100 a month. The free plan has shrunk to 250 contacts and 500 emails with Mailchimp branding attached, which is closer to a trial than a tier.

The developer story is secondary throughout. Transactional email is a separate add-on product (formerly Mandrill), the API is clearly built to serve the app rather than the other way round, and advanced automation and segmentation features are gated behind higher tiers. For an engineering team it is an expensive way to send API-triggered mail; for a marketing team it is a genuinely capable tool that people enjoy using.

Strengths

  • The best drag-and-drop email builder available
  • Landing pages, forms, and deep e-commerce integrations
  • Enormous template gallery and mature reporting
  • A non-technical marketer can run everything unaided

Trade-offs

  • Billed per contact stored — including unsubscribed ones
  • Free plan is 250 contacts / 500 emails with branding
  • Transactional email is a separate add-on product
  • Advanced automation and segments gated behind higher tiers
11

Brevo

Best all-round SMB suite

The platform formerly called Sendinblue — email, SMS, WhatsApp, a small CRM, and a transactional API sold as one European suite.

Free tier

300/day, unlimited contacts

Entry plan

≈$9/mo

50,000 / mo

≈$29–39est.

Brevo's pitch is breadth at a small-business price. Email campaigns, SMS, WhatsApp messaging, a lightweight CRM, shared inbox, and a genuinely usable transactional API all sit in one account, and crucially the billing is by emails sent rather than contacts stored — so an agency or shop with a large list and modest sending volume pays far less here than on a per-contact platform. The free tier is 300 emails a day with unlimited contacts, which is enough to run a small operation indefinitely.

Being French-owned and EU-hosted also makes it the straightforward answer for teams whose legal department cares about where subscriber data lives. GDPR posture is a first-class feature rather than a compliance page, and support is available in several European languages.

The trade is depth everywhere. The campaign editor is decent but a clear step behind Mailchimp's, automation is capable but fiddlier than Customer.io's, the transactional API is fine but not a joy compared with Resend's, and deliverability on shared IPs has a more mixed reputation than the specialists on this list. Daily sending limits on lower tiers can surprise you mid-campaign. Nothing here is bad; nothing here is best. For an SMB that wants one bill and several channels, that is often exactly the right shape.

Strengths

  • Billed by emails sent, with unlimited contacts
  • Email, SMS, WhatsApp, and a light CRM in one account
  • EU-hosted with a strong GDPR posture
  • 300 emails/day free tier, indefinitely

Trade-offs

  • Every module is good rather than best-in-class
  • Shared-IP deliverability reputation is mixed
  • Daily sending caps on lower tiers
  • Interface density can be overwhelming

07 — The money

Pricing at a glance.

Prices below are published list prices for the transactional or core sending plan, tracked in July and August 2026. Two caveats worth reading before you use this table to make a decision.

Entries marked with a tilde are approximate because the platform does not sell in email-volume tiers at all: Mailchimp, Customer.io, and Loops bill on contacts stored, so the figure shown assumes a list of roughly five thousand people mailed a few times a month, and your number will differ with the shape of your list. Postmark and Plunk are exact but computed — Postmark's is a base tier plus overage, Plunk's is a pure per-email meter.

And the pattern that matters more than any single row: the spread between the cheapest and most expensive credible option at 50,000 emails a month is roughly seventeen to one. That gap is not buying you seventeen times the deliverability. It is buying different amounts of product around the same fundamental act of handing a message to a mail server.

PlatformFree tierEntry plan50,000 / moMarketing built in
Resend3,000/mo (100/day cap)$20/mo — Pro$20No
Postmark100/mo$15/mo — 10,000≈$87No
Amazon SES3,000/mo, first 12 monthsPay as you go≈$5No
Mailgun100/day, 1-day logs$15/mo — 10,000$35No
SendGridNone — 60-day trial$19.95/mo — Essentials$19.95No
Volanea1,000/mo, no daily cap$5/mo — 7,500$20Yes
Customer.ioNone — trial only≈$100/mo≈$100+Yes
LoopsSmall list, free tier≈$49/mo≈$49+Yes
Plunk1,000/mo$0.001/email≈$50Yes
Mailchimp500/mo, 250 contacts≈$13/mo≈$75–100Yes — it is the product
Brevo300/day, unlimited contacts≈$9/mo≈$29–39Yes — it is the product

Monthly bill, USD

Published list price at four sending volumes — transactional plans only.

$0$45$90$135$1801,00010,00050,000100,000emails sent per monthAmazon SES — $10custom plan
  • Postmark
  • Mailgun
  • Resend
  • SendGrid
  • Volanea
  • Amazon SES
Fig. 5Monthly bill against volume. Volanea, Resend and SendGrid all land within a dollar of each other between 10,000 and 50,000 — Volanea is drawn dashed so the overlapping lines stay readable. The climb on the right is Postmark's overage.

08 — Getting delivered

Deliverability, honestly.

Deliverability is the only part of this decision where the platform you choose matters less than what you do with it. Every provider on this page can land mail in a primary inbox, and every one of them can be made to land in spam by a sender who imports a purchased list. The provider controls the IP reputation and the sending infrastructure; you control the domain reputation, and the domain reputation is the part that follows you when you switch vendors.

The practical division is worth being precise about. Shared IP pools mean your neighbours' behaviour affects your delivery, which is why specialists like Postmark keep transactional traffic on infrastructure that never carries bulk marketing mail, and why message streams — a hard separation between your receipts and your announcements — are one of the more valuable features on this page regardless of who you buy from. A promotional send that generates complaints should never be able to slow down a password reset.

What to actually do, in order: authenticate the domain properly with SPF and DKIM before your first real send and publish a DMARC record even if it starts at p=none; warm a new domain gradually rather than sending fifty thousand messages on day one; keep the list clean by removing hard bounces immediately and long-term non-openers periodically; and make unsubscribing trivially easy, because someone who cannot find the link uses the spam button instead and that single click costs you far more than the subscriber did.

Then watch the number that decides everything. Complaint rate above 0.3 percent draws throttling from Google; sustained above that draws blocking. If your platform does not surface that figure prominently, or does not throttle you automatically when it spikes, you are relying on noticing it yourself — which people reliably do about a week too late.

09 — Moving

Switching is smaller than you think.

Migrating between any two platforms on this page is smaller work than people expect, and the order matters more than the effort. Nearly all of them are REST APIs taking a from, a to, a subject, and some HTML, so the send call itself is usually an afternoon.

Verify your domain on the new platform first and let the DNS propagate, because fresh DKIM keys need to be live before anything real goes out. Export contacts with their subscription status intact — this is the step people rush, and importing unsubscribed people as subscribed is how a migration turns into a complaint spike on day one. Move templates next, then re-point webhooks, then run both platforms in parallel for a week with a small percentage of traffic on the new one before cutting over properly. Keep the old account open for a billing cycle so you can read the historical logs when something looks odd.

The one genuine trap is suppression history. Bounce and complaint records are what stop you from re-mailing an address that already rejected you, and they do not always export cleanly. Ask the new platform how it imports suppression lists before you commit, not after.

10 — The decision

How to actually choose.

What are you sending?Transactional onlyInbox speed is the productPostmarkCost at real scaleAmazon SESBest developer experienceResendTransactional + lifecycleOne API, one audienceVolaneaBehavioural at scaleCustomer.ioMust self-hostPlunkMostly campaignsA marketer designs themMailchimpSMB suite with SMSBrevoSaaS product emailLoops
Fig. 6Start with what you send, not with who is cheapest. The billing model is easy to change later; a two-system contact architecture is not.

If a single question has to decide it, make it this one: in two years, will this product send email that is not triggered by a user action? If the honest answer is yes — a welcome series, a re-engagement campaign, a product announcement — then choosing a transactional-only API today means choosing a two-system architecture with a synchronisation problem, and you should either accept that deliberately or pick something that covers both now.

If the answer is genuinely no, buy the specialist. Postmark for a product where inbox speed is the feature, Resend if developer experience is what you optimise for, Amazon SES if you send enough that a tenth of a cent per thousand messages is worth an engineer's attention.

And if a person who does not write code owns your email, none of the API-first arguments on this page outweigh the fact that they need a builder they can use on a Tuesday afternoon without you. That is Mailchimp's job, and it is still very good at it.

11 — Questions

Questions people ask.

What is the best email platform in 2026?

There is no single best one, which is why this comparison groups platforms by what they are for. For pure transactional sending where inbox speed is the product, Postmark has the strongest record. For developer experience, Resend. For raw cost at very high volume, Amazon SES. For transactional and marketing on one contact record, Volanea for small teams and Customer.io for larger behavioural programmes. For campaigns designed by a non-technical marketer, Mailchimp.

What is the cheapest way to send email at scale?

Amazon SES, at roughly $0.10 per 1,000 emails — about $10 for 100,000 messages, an order of magnitude below anything else here. The saving is real but so is the cost: no contact store, no campaigns, no automation, and you build suppression handling, retries, and event processing yourself. Below roughly 200,000 emails a month the engineering time usually outweighs the difference.

Should transactional and marketing email use the same platform?

It depends on whether you can keep one authoritative consent state. Using one platform makes that automatic — an unsubscribe is honoured everywhere and segments can be built from product events without an export. Using two is defensible if you separate the streams deliberately so a promotional send cannot affect the reputation your receipts depend on, but you own the synchronisation problem forever, and drifting unsubscribes are the most common way it fails.

Why is per-contact pricing a problem?

Because it bills you for storage rather than sending, so the invoice grows with your list even in months you send nothing, and on most per-contact platforms unsubscribed contacts keep counting until someone manually archives them. A large list you mail occasionally is the most expensive shape in that model. Per-send pricing inverts it: store as many contacts as you like and pay only when a message leaves.

What do Google and Yahoo require from bulk senders now?

SPF and DKIM authentication on your sending domain, a published DMARC record with at least p=none, one-click unsubscribe honoured within two days, and a spam complaint rate held below 0.3 percent — with 0.1 percent as the practical target. These have been enforced since February 2024 and are now the baseline for reaching the inbox at any real volume.

How long does migrating between email platforms take?

For most pairs on this list, an afternoon of code and about a week of care. The send call is a straightforward swap between REST APIs. What takes the week is verifying your domain and letting DNS propagate, exporting contacts with their subscription status intact, importing suppression history, re-pointing webhooks, and running both platforms in parallel on a slice of traffic before cutting over.

Do I need a dedicated IP address?

Almost certainly not unless you send consistently high volume — roughly 100,000 or more emails a month, steadily. A dedicated IP with low or irregular volume performs worse than a well-managed shared pool, because reputation is built from sustained sending patterns and an IP that goes quiet for a fortnight has to earn its standing again. Below that threshold, the shared pool of a reputable provider is the better outcome.

How much does email deliverability depend on the platform I choose?

Less than most comparisons imply. The provider controls IP reputation and sending infrastructure; you control domain reputation, list quality, and complaint rate, and those are what follow you between vendors. Choose a provider that separates transactional from marketing traffic and surfaces your complaint rate honestly, then do the unglamorous work: authenticate the domain, warm it gradually, remove hard bounces immediately, and make unsubscribing easy.

If the middle group is your shape

One API. One audience. Nothing bolted together.

Transactional email, campaigns, and automation on a single contact graph. 1,000 emails free every month with no daily cap, unlimited contacts on every plan, and no card to find out whether it fits.