Per-email pricing is a tax on bad senders. You're paying it.

Open your last Mailgun invoice. The line says per email. It isn’t.

A real email, the SMTP handshake, the DKIM signing, the bytes on the wire, costs a fraction of a fraction of a cent in 2026. AWS will rent you SES at roughly $0.10 per thousand. The marginal cost of a sent message has been rounding-error money for years.

So what are you paying for?

You’re paying for the abuse team.

The line item nobody itemizes

Every general-purpose ESP runs an anti-abuse organization. Heuristic detection on outbound traffic. Manual review queues for new accounts. Suppression-list infrastructure. Relationships with mailbox providers and feedback loops with Gmail, Outlook, Yahoo. Lawyers responding to subpoenas. On-call engineers who page when an IP gets blocklisted at 3 a.m. because somebody else on the same shared pool decided to test a list they bought somewhere on the internet.

That work is real and necessary. It’s also expensive, and it has to be paid for somehow. The way it gets paid for is the per-email price.

A useful exercise: line up the public list prices for 100,000 emails a month.

• Mailgun: $75
• Postmark: roughly $134
• SendGrid: $34.95 (no free plan since May 2025)
• Resend: $35, climbing to roughly $650 at one million emails
• Amazon SES: roughly $10–12, if you bring your own AWS account, warm-up, and compliance posture

The infrastructure cost is roughly the same. The variance isn’t bandwidth — it’s how much abuse defense each platform absorbs.

The senders who pay the most

Here’s the part that usually goes unsaid. Clean senders subsidize dirty ones.

If you run a SaaS app sending password resets and receipts, your complaint rate is probably under 0.01%. You generate roughly zero load on the abuse team. And yet you’re paying the same per-message rate as the customer next door who’s blasting a list they “warmed up” by importing it from a bankrupt LinkedIn scraper.

The pricing isn’t malicious. It’s structural. Shared infrastructure means shared cost. The platforms are doing the right thing operationally, pooling abuse defense across their customer base. But pooled costs are pooled by design. You can’t pay less just because you behave better, because the platform has no mechanism to know you behave better until well after the bill has been printed.

Remove the abuse, remove the cost

The way out isn’t a discount code. It’s a different model. GoodSender’s Permission Loop requires recipients to confirm before a sender can mail them, which means purchased lists and cold sequences don’t function and the abuse surface is structurally near-zero.

Once that’s true, the math changes:

• No abuse team rotation to staff.
• No suppression infrastructure to scale.
• No cross-customer reputation contamination to clean up.

The marginal cost of an email drops back to what it actually is — pipe, plus a little metadata. That’s why the first 100,000 emails a month cost $0, and why the curve stays flat at scale: roughly $9 a month at one million, $99 at ten million.¹ The model still doesn’t tax you for someone else’s behavior.

What to look at when you compare

If you’re evaluating email APIs in 2026, don’t compare per-email price first. Compare what’s in the price — whether your reputation is pooled with the worst sender on your tier, whether the platform prevents abuse structurally or polices it with a team, and whether your per-email cost will track infrastructure or anti-abuse overhead as you scale.

The bet

Per-email pricing has held its shape for fifteen years because nobody had a structural reason to break it. The shared-pool model required pooled cost, pooled cost required per-message billing, and the abuse tax stayed embedded in the rate.

That’s the part we think breaks next. Not because senders demanded it — they’ve been paying the tax without complaining for a long time — but because the model that makes the tax unnecessary is finally cheaper to run than the model that requires it.

Whether GoodSender is the platform that proves the point or somebody else is, the per-email rate as a category is on borrowed time.