Sending 2 million emails a month costs roughly $200 to $4,000, and the gap is almost entirely about which layer of service you are paying for. Amazon SES charges about $200 in raw send fees. Mid-market relays land at $700 to $1,400. Full platforms with contact-based pricing reach $1,500 to $4,000. A dedicated server removes the per-email fee entirely and becomes a fixed cost.
At this volume the pricing model matters more than the per-email rate, so it is worth seeing the whole picture before optimising the wrong number.
The comparison at 2 million a month
| Option | Monthly cost | What you also get | What you handle |
|---|---|---|---|
| Amazon SES | ~$200 | Raw sending only | Everything else |
| SMTP2GO | ~$650 | Reporting, support | List hygiene |
| Mailgun | ~$900 | API, validation, logs | Reputation |
| SendGrid | ~$1,100 | Full platform, templates | List hygiene |
| Brevo | ~$1,500 | Campaigns, CRM, automation | Little |
| Klaviyo | $2,500-4,000 | Ecommerce automation, contact pricing | Little |
| Dedicated SMTP | one-time build | IPs are yours, no per-email fee | Warm-up, hygiene |
Two things stand out. First, SES is 5x cheaper than SendGrid on send fees while doing genuinely less. Second, the platforms at the bottom charge by stored contacts rather than sends, so their cost keeps climbing even in a month when you send nothing.
Why the pricing model matters more than the rate
At 25,000 emails a month the difference between providers is a few dollars, so the per-email rate is the whole story. At 2 million it stops being the story, because the model determines how your bill behaves as you grow.
| Model | Bill in a heavy month | Bill in a quiet month | Bill as list grows |
|---|---|---|---|
| Per email | high | low | flat per email |
| Per contact | same | same | rises with list |
| Flat / owned | same | same | same |
Per-contact pricing is the one that catches people at this scale. A 500,000-contact list on Klaviyo costs the same in a month you send one campaign as in a month you send twenty. If you send infrequently to a large list, you are paying the highest effective cost per email in the market.
Per-email pricing is honest but unbounded. It scales linearly forever, which is fine until the line crosses what a build would cost, and at 2 million a month it already has.
What the headline prices leave out
The advertised rate is rarely what appears on the invoice at this volume.
Dedicated IPs. Most relays charge $25 to $80 per IP per month, and at 2 million a month you need several. That is $200 to $800 on top before you have sent anything.
Overage. Exceeding a plan tier costs meaningfully more per email than the tier itself. One campaign that runs long can add several hundred dollars. Details in hidden costs of ESP overage fees.
Contact-based pricing. Klaviyo and similar charge for contacts stored, not emails sent. A 500,000-contact list costs the same in a quiet month as a heavy one.
Validation. Charged per address on most platforms. Cleaning a 500,000-address list is a real line item.
Support tiers. Response-time SLAs are often a paid add-on, and at 2 million a month a blocked campaign is expensive to wait on.
The self-hosted and dedicated routes
| Item | Self-hosted | Managed dedicated |
|---|---|---|
| Server + IPs | $150-400/mo | one-time build, from $549 |
| Setup time | 40-60 hrs, yours | included |
| Daily running | yours | included |
| Warm-up | 4-8 weeks, yours | included |
| Monitoring | yours | included |
Self-hosting genuinely is the cheapest recurring cost, and it is the right answer if you have someone who will own it daily. What kills self-builds is not the setup, which is a weekend. It is the 4 to 8 week warm-up and the ongoing reputation monitoring, both of which need a person who is not busy with something else.
Against a mid-market relay at $900 to $1,100 a month, a one-time build pays for itself in under two months and then keeps not charging you. That is the whole argument, and at 2 million a month it is a strong one.
The deliverability cost nobody prices
At 2 million a month, a delivery problem costs more than the infrastructure decision.
Gmail's published bulk sender rules require SPF, DKIM and DMARC, a one-click unsubscribe, and a spam complaint rate kept under 0.3%, with 0.1% as the target (Google's sender guidelines). Those are not provider features, they are your responsibility on any option in the table.
What differs is who owns the consequences:
| Scenario | Shared pool | Dedicated IPs |
|---|---|---|
| Another sender's spam run | slows your mail | cannot touch you |
| Your complaint spike | provider suspends you | your problem, your recovery |
| Reputation you build | stays with the provider | yours, moves with you |
| Visibility into the pool | none | not applicable |
At 2 million a month a week of degraded delivery is a substantial revenue event, and on a shared pool you have no visibility into why it happened or when it will clear.
Sizing it properly
2 million a month is about 65,000 a day averaged, but nobody sends evenly. Size for the peak.
| Sending shape | Peak day | IPs needed |
|---|---|---|
| Steady daily | ~65,000 | 5-8 |
| Weekday-heavy | ~120,000 | 8-12 |
| Weekly campaigns | ~400,000 | 15+ |
Under-provisioning IPs does not stop the mail, it just means per-destination throttling at Gmail and Microsoft during peaks, which shows up as deferrals and a slow-motion send. See how many emails per day per IP for the per-IP limits.
The real total cost of self-hosting
The $150-400 figure is server and IPs. It is not the total.
| Item | First year |
|---|---|
| VPS and IPs | $1,800-4,800 |
| Setup, 40-60 hrs | at your loaded rate |
| Warm-up management, 8 weeks | daily attention |
| Ongoing monitoring | 2-4 hrs/week |
| One burned IP set, if warm-up is rushed | restart, 8 weeks |
Self-hosting is genuinely the cheapest recurring cost and the right answer when you have someone who will own it. It goes wrong when it is nobody's actual job. The setup is a weekend; the warm-up is two months of someone watching deferral rates and resisting the urge to scale faster.
That last row is the one that turns a cheap option expensive. Rushing warm-up burns the IPs, and you start over on new ones with a damaged domain reputation behind you.
Which route fits
Choose SES if you have engineers, need only sending, and will build monitoring yourself.
Choose a mid-market relay if you want the platform features and $900 a month is easier to approve than a build project.
Choose dedicated if you are staying at this volume or growing, want the reputation to be yours, and have someone who will own warm-up and hygiene.
Choose a full platform only if the automation and CRM features are what you are actually buying. At 2 million a month you are paying a large premium for them.
For the adjacent tiers, see 1 million emails a month and 500,000 a month.
What 2 million a month looks like in practice
Volume is half the picture. How that volume is shaped determines what you need.
| Sending pattern | Typical sender | Daily peak | Difficulty |
|---|---|---|---|
| Daily transactional | SaaS product, ecommerce receipts | ~65,000 | easiest, high engagement |
| Weekday marketing | B2B newsletter, publisher | ~120,000 | moderate |
| Weekly campaign | retail promotions | ~400,000 | hardest, needs IP headroom |
| Mixed | most real businesses | varies | split the streams |
Transactional mail at this volume is the easy case. People expect it, open it, and rarely complain, so reputation looks after itself as long as authentication is correct.
Weekly campaign sending is the hard case. The same 2 million arrives in four bursts, each one a spike that receiving networks read as unusual. That pattern needs more IPs than the monthly average suggests and a warm-up that rehearses the peak rather than the average.
If you send both, separate them. Transactional on its own subdomain and IPs, marketing on another, so a campaign that draws complaints cannot stop order confirmations arriving. See subdomain vs root domain for email sending.
Worked example: the same list on three routes
A 400,000-address list, mailed five times a month. That is 2 million sends.
On SendGrid. The volume tier lands around $900. Three dedicated IPs at roughly $30 each adds $90. Validating the list quarterly adds a few hundred spread over the year. Call it $1,000 a month, $12,000 a year, and it rises with volume.
On Amazon SES. Send fees are about $200. Dedicated IPs are roughly $25 each per month. But SES gives you no campaign builder, no subscriber management and no bounce dashboard beyond the API, so you are either writing that or bolting on software. Budget the engineering honestly: if it takes 100 hours to build and maintain, the cheap option is not cheap in year one.
On a dedicated server. A one-time build, then server costs. No per-email fee, no per-IP monthly charge, no overage. Against SendGrid's $12,000 a year, payback arrives in the first two months and the gap compounds every year after.
The pattern holds across most senders at this volume: SES wins on raw cost if you have engineering capacity, dedicated wins on total cost if you do not, and the mid-market relays win on convenience if $12,000 a year is easier to approve than a project.
Questions to settle before you choose
How spiky is your sending? Size for the peak day, not the monthly average. A 400,000-recipient campaign needs the IPs to absorb it in a morning.
Who owns deliverability? If nobody watches complaint rates weekly, stay on shared infrastructure. Dedicated IPs degrade quietly without an owner and the saving is not worth a damaged domain.
How clean is the list? Dedicated IPs amplify list quality in both directions. Move a stale list onto your own IPs and the damage is permanent and yours.
Do you need the platform layer? If your team lives in the campaign builder and automation, a dedicated server does not replace that. You would pair it with self-hosted software such as MailWizz, Sendy, Mautic or Listmonk.
What happens when you grow? At 2 million a month you are close to tiers where per-email pricing gets genuinely painful. Check what 5 million would cost on each option before committing.
How BulkEmailSetup helps
We build the dedicated route as a one-time job: your own server, your own IPs, full SPF/DKIM/DMARC/PTR configuration, MTA tuning, bounce handling and a warm-up plan sized for your peak day rather than your average.
Basic starts at $549 one-time, covering 1 SMTP server, 3 dedicated IPs, 25,000 emails/day and unlimited contacts. Higher tiers scale to 15 IPs and 200,000 emails/day, which covers 2 million a month with headroom for campaign peaks. See pricing for the full breakdown.
Frequently asked questions
How much does it cost to send 2 million emails a month?
Between roughly $200 and $4,000 a month depending on the route. Amazon SES is cheapest at about $200 in send fees, mid-market relays like SendGrid and Mailgun land between $700 and $1,400, and full-service platforms such as Brevo or Klaviyo run $1,500 to $4,000 once contact-based pricing applies. A dedicated SMTP server is a one-time build with no per-email fee.
Is Amazon SES really the cheapest at 2 million emails?
On send fees alone, yes, at roughly $0.10 per 1,000 which is about $200 a month. The figure people miss is everything SES does not include: no list management, no campaign builder, no bounce dashboard, dedicated IPs cost extra at around $25 each per month, and you are responsible for reputation monitoring. Budget engineering time on top.
At 2 million emails a month, is a dedicated SMTP server cheaper?
Almost always, yes. A one-time build handling that volume removes the per-email fee entirely, so the comparison is a fixed cost against $700 to $4,000 every month on a relay. Payback against a mid-market relay is usually under two months. The trade is that you own warm-up, monitoring and list hygiene.
What hidden costs appear at 2 million emails a month?
Overage fees when you exceed a plan tier, dedicated IP charges of $25 to $80 per IP per month, contact-based pricing that charges for stored contacts rather than sends, validation add-ons, and dedicated support tiers. On several platforms the add-ons cost more than the base plan at this volume.
Does 2 million emails a month need a dedicated IP?
Yes. At that volume you are well past the threshold where dedicated IPs make sense, which sits around 100,000 a month. Shared pools at 2 million mean your delivery depends on other senders you cannot see, and most relays charge $25 to $80 per dedicated IP per month anyway, so you are paying for them without owning them.
How many IPs do I need for 2 million emails a month?
Roughly 2 million a month is 65,000 a day averaged, but real campaigns are spiky, so size for the peak day not the average. That usually means 8 to 15 dedicated IPs once warmed. Fewer IPs will send the volume but you will hit per-destination throttling at Gmail and Microsoft during peaks.
