Mailgun alternative

A Mailgun alternative for app email, for much less

Warmerly is a cheaper Mailgun alternative for apps that send password resets, receipts and notifications over an API: $15 a month for 50,000 emails against $35 on Mailgun Foundation, and $29 for 100,000 against $90 on Mailgun Scale. At 10,000 both cost $15. Mailgun is the better pick if you need SMTP, delivery webhooks, templates, inbound routing or up to 30 days of logs; Warmerly doesn't have those yet.

Start sending free Compare prices

When Mailgun is the better pick

Honestly, in these cases we would stay with Mailgun.

You send through SMTP: Mailgun has an SMTP relay on every plan. Warmerly is REST only for now, so a framework that can only speak SMTP has to stay put.
You rely on webhooks or templates: Mailgun pushes delivery events to your endpoints and stores templates (from Foundation). On Warmerly you read an email's status from the API and render the HTML yourself.
You process inbound email: Mailgun's routes turn incoming mail into HTTP calls (five routes on Basic, full access from Foundation). Warmerly's transactional API only sends.
You need weeks of logs: Mailgun keeps 30 days of logs on Scale. Warmerly keeps each email's record and delivery events, but clears the content after 30 days.
You send about 10,000 a month: At that volume both cost $15, and Mailgun's tooling makes it the easier choice.

Warmerly vs Mailgun: price at 4 volumes

Compared with Mailgun's published monthly plans (Basic, Foundation and Scale). At 10,000 emails the two cost the same; above that, Warmerly's larger allowances pull ahead. Mailgun's overage rates and any plan above 100,000 are not priced here, so the 500,000 row is left open rather than guessed.

Monthly list price in USD, Warmerly and Mailgun
Emails a month	Warmerly	Mailgun
10,000	$15Starter	$15Basic 10k
50,000	$15Starter	$35Foundation 50k
100,000	$29Growth	$90Scale 100k
500,000	$279Scale 500k	see vendor site

List prices, monthly billing, USD: the cheapest published plan that includes that many emails, overage left out on both sides. Mailgun prices from mailgun.com as of September 2026; check their site for current rates. Shaded cells are the cheaper side.

Side by side

What each one does today. Where Warmerly says "not yet", it means it: those are on the roadmap, not built.

Feature comparison, Warmerly and Mailgun
Feature	Warmerly	Mailgun
API shape	REST, JSON over HTTPS, bearer key, Idempotency-Key header	REST, form-encoded POST to /v3/{domain}/messages, HTTP Basic auth with your API key
SMTP relay	Not yet (on the roadmap)	Yes
Delivery webhooks	Not yet. Read each email's delivery timeline from GET /emails/{id}	Yes
Templates	Not yet. You send your own HTML and text	Yes, from the Foundation plan
Dedicated IP	$29/mo on Scale plans	One included on Scale; $59/mo for each extra IP
Suppression list	Automatic on hard bounce and spam complaint, shared with Warmerly outreach	Bounces, complaints and unsubscribes are suppressed automatically
Free tier	5,000 a month (200 a day), no time limit, no card	100 emails a day, with 1 day of logs
Log retention	Content 30 days; the email record and its delivery events are kept	1 day on Free and Basic, 5 on Foundation, 30 on Scale
SDKs	None. One HTTP request from any language	Official libraries for several languages (see mailgun.com)
Support	Email (support@warmerly.com), plus a 99.9% monthly uptime commitment with service credits	See mailgun.com

Moving from Mailgun

Most of the work is DNS. The code change is small, but it is a change.

Step 1: Verify your domain in Warmerly
Add the domain and publish the DKIM CNAMEs, bounce MX, SPF and DMARC records it shows. Mailgun's records can stay in place until you switch.
Step 2: Change the endpoint and the auth
POST to https://app.warmerly.com/api/v1/transactional/emails with Authorization: Bearer wm_tx_... instead of HTTP Basic auth against /v3/{domain}/messages.
Step 3: Send JSON, keep the field names
from, to, cc, bcc, subject, text and html keep their names. Mailgun's form fields become a JSON body, h:Reply-To becomes reply_to and o:tag becomes tags.
Step 4: Render templates in your app
Warmerly has no template store. Render the HTML where you build the email today and send html and text.
Step 5: Leave out what Warmerly doesn't take
Attachments, scheduled delivery (o:deliverytime) and custom variables (v:) are not accepted yet, so keep those sends on Mailgun until they are.

Mailgun messages to Warmerly
Mailgun	Warmerly
POST /v3/{domain}/messages (form-encoded)	POST /api/v1/transactional/emails (JSON)
HTTP Basic auth, user api	Authorization: Bearer wm_tx_...
from	from
to	to
cc / bcc	cc / bcc
subject	subject
html	html
text	text
h:Reply-To	reply_to
o:tag	tags

Mailgun alternative questions

Is Warmerly cheaper than Mailgun?

Above 10,000 emails a month, yes, on list prices as of September 2026: $15 against $35 for 50,000 and $29 against $90 for 100,000. At 10,000 both are $15. Mailgun's overage rates and larger plans are not compared here.

What does Mailgun include that Warmerly doesn't?

SMTP relay, delivery webhooks, stored templates, inbound routing, attachments and scheduled delivery. Warmerly's transactional API sends one email per request over REST and records its delivery events for you to read.

Does Warmerly have a free plan like Mailgun's?

Yes: 5,000 emails a month, up to 200 a day, with no time limit and no card. Mailgun's free plan is 100 emails a day with 1 day of logs.

How long does Warmerly keep sent emails?

Each email's content (html and text) is kept for 30 days and then cleared. The email record and its delivery events stay. Mailgun keeps between 1 and 30 days of logs depending on the plan.

Can I use Mailgun's libraries with Warmerly?

No. The endpoint and auth are different. The send fields keep their names, so the change is small, but it is a code change.

Try it before you move anything off Mailgun

Create a free account, verify a sending domain and send a test from the dashboard. 5,000 emails a month free, no card.

Start sending free Continue with Google API docs

Or book a free 15-minute setup call →

Warming up

A Mailgun alternative for app email, for much less

When Mailgun is the better pick

Honestly, in these cases we would stay with Mailgun.

You send through SMTP

Mailgun has an SMTP relay on every plan. Warmerly is REST only for now, so a framework that can only speak SMTP has to stay put.

You rely on webhooks or templates

Mailgun pushes delivery events to your endpoints and stores templates (from Foundation). On Warmerly you read an email's status from the API and render the HTML yourself.

You process inbound email

Mailgun's routes turn incoming mail into HTTP calls (five routes on Basic, full access from Foundation). Warmerly's transactional API only sends.

You need weeks of logs

Mailgun keeps 30 days of logs on Scale. Warmerly keeps each email's record and delivery events, but clears the content after 30 days.

You send about 10,000 a month

At that volume both cost $15, and Mailgun's tooling makes it the easier choice.

Emails a month

Warmerly

Mailgun

10,000

$15Starter

$15Basic 10k

50,000

$15Starter

$35Foundation 50k

100,000

$29Growth

$90Scale 100k

500,000

$279Scale 500k

see vendor site

Side by side

What each one does today. Where Warmerly says "not yet", it means it: those are on the roadmap, not built.

Feature comparison, Warmerly and Mailgun
Feature	Warmerly	Mailgun
API shape	REST, JSON over HTTPS, bearer key, Idempotency-Key header	REST, form-encoded POST to /v3/{domain}/messages, HTTP Basic auth with your API key
SMTP relay	Not yet (on the roadmap)	Yes
Delivery webhooks	Not yet. Read each email's delivery timeline from GET /emails/{id}	Yes
Templates	Not yet. You send your own HTML and text	Yes, from the Foundation plan
Dedicated IP	$29/mo on Scale plans	One included on Scale; $59/mo for each extra IP
Suppression list	Automatic on hard bounce and spam complaint, shared with Warmerly outreach	Bounces, complaints and unsubscribes are suppressed automatically
Free tier	5,000 a month (200 a day), no time limit, no card	100 emails a day, with 1 day of logs
Log retention	Content 30 days; the email record and its delivery events are kept	1 day on Free and Basic, 5 on Foundation, 30 on Scale
SDKs	None. One HTTP request from any language	Official libraries for several languages (see mailgun.com)
Support	Email (support@warmerly.com), plus a 99.9% monthly uptime commitment with service credits	See mailgun.com

Moving from Mailgun

Most of the work is DNS. The code change is small, but it is a change.

Step 1: Verify your domain in Warmerly

Add the domain and publish the DKIM CNAMEs, bounce MX, SPF and DMARC records it shows. Mailgun's records can stay in place until you switch.

Step 2: Change the endpoint and the auth

POST to https://app.warmerly.com/api/v1/transactional/emails with Authorization: Bearer wm_tx_... instead of HTTP Basic auth against /v3/{domain}/messages.

Step 3: Send JSON, keep the field names

from, to, cc, bcc, subject, text and html keep their names. Mailgun's form fields become a JSON body, h:Reply-To becomes reply_to and o:tag becomes tags.

Step 4: Render templates in your app

Warmerly has no template store. Render the HTML where you build the email today and send html and text.

Step 5: Leave out what Warmerly doesn't take

Attachments, scheduled delivery (o:deliverytime) and custom variables (v:) are not accepted yet, so keep those sends on Mailgun until they are.

Mailgun messages to Warmerly

Mailgun

Warmerly

POST /v3/{domain}/messages (form-encoded)

POST /api/v1/transactional/emails (JSON)

HTTP Basic auth, user api

Authorization: Bearer wm_tx_...

from

cc / bcc

subject

html

text

h:Reply-To

reply_to

o:tag