Compare · Email infrastructure
KumoMTA vs Mailgun
Mailgun and KumoMTA both deliver transactional mail, but one is a managed API you rent and the other is a free engine you own. Mailgun is developer-first: a clean REST API and SMTP relay run by Sinch, billed per recipient with overage past your plan. KumoMTA is open-source under Apache 2.0 — no licence, no per-email fee, just a server you run, with full control of the IPs and reputation. Pick Mailgun for a fast, low-ops start with a polished API at modest volume; pick a self-hosted KumoMTA when volume makes per-recipient pricing hurt, or when you need to own your reputation and control your stack. Neither ships marketing tools. MCSNET hosts KumoMTA managed in Toronto, removing the server burden while keeping it free to own.
- Cost: KumoMTA has no licence and no per-email fee — only the server; Mailgun bills per recipient (~$0.70–1.80/1,000) plus overage.
- Category: both are delivery-only — neither has a campaign builder, so marketing tooling is a separate choice for either.
- Setup: Mailgun is an API integration in minutes; KumoMTA needs a server and Lua configuration, a day or two to learn.
- Control: KumoMTA gives you the IPs, the reputation, and the open-source engine; Mailgun is a managed black box with shared-pool reputation by default.
- MCSNET runs KumoMTA managed in Toronto — turnkey delivery, a free engine you own, no per-recipient meter, data in Canada under PIPEDA.
Who should read this comparison?
If you are choosing between renting a managed sending API and running a free, open-source engine, this page is for you. The two are not direct substitutes: Mailgun is delivery-as-a-service with a developer-friendly API, while KumoMTA is software you operate. The decision turns on volume, control, and whether a per-recipient meter or a fixed server cost fits your trajectory.
Two readers get the most value. The first is a developer or small team that wants reliable transactional sending through a clean API with no servers — Mailgun is built for them. The second is a higher-volume sender watching per-recipient charges and overage climb, and weighing a free engine on owned servers against them. If marketing campaigns are your real need, note up front that neither tool answers it; both are delivery layers under a separate campaign platform, so the comparison is purely about how your mail gets sent and priced.
There is a third reader this page serves: the team that cares about owning its stack on principle, not only on price. Because KumoMTA is open source, choosing it means the engine, the configuration, and the IP reputation are yours to inspect and keep, with no vendor between you and your own infrastructure. For some that is a philosophical preference; for others — regulated senders, resellers, anyone who has been burned by a platform decision they could not appeal — it is a hard requirement. Mailgun cannot offer it, because the point of a managed API is that the provider holds the parts you would otherwise own.
What each one actually is
Mailgun is a developer-first transactional email service, launched in 2011 and owned by Sinch since a roughly two-billion-dollar acquisition in 2021, powering email for more than a hundred and fifty thousand companies including GitHub, Slack, and Lyft. You send through a REST API or SMTP relay, and Mailgun handles infrastructure, bounce processing, analytics, and validation. Plans run from a free tier at 100 emails a day through Basic, Foundation, and Scale, with a dedicated IP on Scale and extra IPs at fifty-nine dollars a month. It counts each recipient at submission — bounced mail still counts — and charges overage per thousand past your plan. It is not a marketing platform, by design.
KumoMTA is an open-source, outbound delivery engine written in Rust with Lua scripting, released under Apache 2.0 and built by veterans of the commercial MTA world — the team behind PowerMTA and Momentum. It runs on your own Linux servers with no licence fee and no per-message cost, designed for high volume with built-in traffic shaping, per-tenant queuing, IP-pool management, and native Prometheus and Grafana metrics. Paid support and enterprise features exist, but the core engine is free. The real work is its Lua configuration, which most operators take a day or two to learn — and, like Mailgun, it leaves the marketing layer to a separate tool.
What does the side-by-side look like?
The table sets the managed developer API against the free self-hosted engine. Wins land on both sides.
| Factor | KumoMTA (self-hosted) | Mailgun (managed API) |
|---|---|---|
| Licence / fee | Free (Apache 2.0), no per-email fee | Per recipient + overage |
| Cost at low volume | Server overhead dominates | Cheap, simple start |
| Cost at high volume | Marginal cost ~ zero | $0.70–1.80/1,000 adds up |
| Developer experience | Lua config; you build the API layer | Clean REST API + SDKs, fast start |
| Ops burden | You run it (or a host does) | None — Sinch runs it |
| IP reputation | You own it fully | Shared pool; dedicated IP on Scale |
| Visibility / control | Full — every connection, the source | Managed black box |
| Overage / suspension risk | None — fixed cost, your rules | Overage bills; rate-limit/account risk |
| Data residency | Wherever you host (e.g. Toronto) | Sinch/cloud region |
| Marketing tools | None — bring your own EMS | None — bring your own EMS |
Mailgun plan prices and overage rates are perishable — verify current rates and model your own volume; verify price as of date.
Where Mailgun is the better choice
A page about a free engine still has to say it plainly: for many senders Mailgun is the right pick, and not as a compromise.
Its developer experience is genuinely good — a clean REST API, SMTP relay, SDKs for every major language, and documentation built over a decade of billions of sends. There are no servers to run, no Lua to learn, and reputation on shared pools is managed for you, with validation, routing, and analytics built in. At low to mid volume it is inexpensive and an integration takes minutes. For a team that wants reliable transactional email without owning infrastructure or learning an engine, that convenience is the product, and it is a good one.
The honest version: if your volume is modest, you value a polished API, and you do not want to run or learn infrastructure, Mailgun is the rational choice and a self-hosted engine is more than you need. The open-source case is about cost, control, and ownership, which only start to matter as volume grows.
Where a self-hosted KumoMTA pulls ahead
KumoMTA’s case rests on cost, control, and openness — sharpened by the fact that it is free. On cost, KumoMTA has no licence and no per-recipient fee, so against Mailgun’s per-thousand pricing the gap widens with every message until it is dramatic; because the software is free, the crossover where it wins arrives sooner than for a paid engine. On control and openness, you own the IPs and reputation, you can see and tune every connection, and the engine is yours to modify — no platform policy, no rate-limit surprise, no account suspension able to pause your sending. On residency, KumoMTA runs wherever you host it, so data can stay in Canada and outside US legal reach. The price of all this is the operational work and the Lua learning curve, plus a younger ecosystem than Mailgun’s decade-plus of operation.
There is a deliverability note to handle honestly too. Independent trackers have reported a decline in Mailgun’s inbox placement over a recent year, which is a reason to test rather than assume — and a reminder that on a shared platform your placement depends partly on the provider and pool, while on owned IPs it depends on you. Neither guarantees the inbox; they put the control in different hands.
What does the cost gap look like?
The shapes are opposite, and the zero-licence engine makes the contrast stark. Mailgun is metered: you pay per recipient and pay overage past your plan, so the bill rises with volume and never stops. KumoMTA is flat and free of software cost: a server, no licence, no per-message fee. The sketch shows the shape — placeholders, not a quote.
# Mailgun: plan + per-recipient + overage — verify current rates 50K /mo -> Foundation ~$35 200K /mo -> ~$230 # overage past the tier (~6x sticker) 2M+ /mo -> climbs fast # every recipient metered, every month # KumoMTA: $0 licence, $0 per email — server + infra only any /mo -> server $ # flat; marginal cost ~ 0 -> lower crossover than a paid engine
Figures are illustrative placeholders for the cost shape, not a quote — verify current Mailgun plan and overage rates and model your own volume.
The structural point survives any specific numbers: a metered API turns volume into recurring cost, while a free engine turns it into a one-time capacity question answered by hardware. That is why the crossover for KumoMTA sits lower than for a licensed engine — there is no software line item to recover before the savings begin. Above it, the free engine wins by a margin that grows every month.
Both are delivery-only: the marketing layer
This comparison is about delivery, not campaigns, and saying so spares confusion. Mailgun is a transactional API; KumoMTA is a transactional engine. Neither ships a drag-and-drop builder, list management, or marketing automation. If your team needs those, that is a separate choice on top of whichever delivery option you pick — a marketing platform, or an email management system such as MailWizz or Mautic feeding the engine underneath. Judge KumoMTA against Mailgun on delivery merits alone — cost shape, reputation ownership, control, residency, and operational fit — and choose a campaign tool separately if you need one.
Where MCSNET fits
The objection to a self-hosted engine is the one Mailgun answers with its API: who wants to run a mail server and learn Lua? MCSNET removes that half. It hosts KumoMTA as a managed dedicated server in Toronto — installation, Lua configuration, IP warming, reverse DNS and SPF/DKIM/DMARC alignment, and ongoing deliverability monitoring all handled — so the engine arrives turnkey and stays free to own. What it does not replace is Mailgun’s ready-made API; you integrate against your own stack, and bring your own campaign tool for the marketing layer neither product includes. The trade is deliberate: you give up the minutes-to-integrate API and gain a free engine, your own IP reputation, no per-recipient meter or overage, full control, data in Canada under PIPEDA, and a named engineer when deliverability slips. The managed build is on the PowerMTA server hosting page, where KumoMTA is offered on the same basis. At low volume Mailgun’s API is the easier path — that is the honest line — and the free self-hosted engine wins as volume, control, and residency come to dominate.
Which should you pick?
Clean API, minutes to send
You want reliable transactional sending through a polished REST API with no servers and no Lua, and your volume is modest. Mailgun’s developer experience wins.
Small team, no infrastructure
You have no appetite to run an engine and value managed reputation, validation, and routing out of the box. Mailgun bundles the infrastructure.
Free engine, owned at scale
High volume where per-recipient pricing and overage sting, and you want a no-licence engine, your own IP reputation, and full visibility, with your own integration on top.
Control + Canadian residency
You need full delivery control, open-source ownership, or data kept in Canada under PIPEDA, plus a human on deliverability. Managed KumoMTA in Toronto fits.
A practical test: weigh your volume against your appetite to run infrastructure, and check whether a polished API is central to your build. Modest volume with a clean-API requirement points to Mailgun; high volume where per-recipient cost, control, and ownership dominate points to a KumoMTA stack. Because KumoMTA carries no licence, that crossover sits lower than it would for a commercial engine — and hosting the engine managed removes the only serious objection to it, letting the decision rest on economics and control rather than on who runs the server.
Common questions
Is KumoMTA a replacement for Mailgun?
For the delivery job, yes, at a different layer. Mailgun is a managed API; KumoMTA is a free, open-source engine you host. Both are transactional delivery tools with no marketing builder. Replacing Mailgun with KumoMTA means taking on the infrastructure Mailgun runs for you, in exchange for owning the IPs, dropping the per-email meter, and building your own integration.
Is KumoMTA cheaper than Mailgun?
At volume, dramatically — KumoMTA has no licence and no per-email fee, only the server. Mailgun bills per recipient, roughly $0.70 to $1.80 per thousand plus overage. Because KumoMTA’s software cost is zero, the crossover where it undercuts Mailgun is lower than for a commercial engine. At low volume Mailgun is cheaper and simpler.
Does either KumoMTA or Mailgun include marketing tools?
No. Both are delivery-focused — Mailgun a transactional API, KumoMTA a transactional engine. Neither ships a campaign builder, list management, or automation, so those are a separate choice on top of whichever you pick.
How much harder is KumoMTA to set up than Mailgun?
Considerably, at the start. Mailgun is an API integration in minutes; KumoMTA needs a Linux server, DNS and authentication setup, a few hours for a basic install, and a day or two to learn its Lua configuration. A managed host removes that gap by running the engine for you.
Can MCSNET run KumoMTA so I get Mailgun-like convenience?
Partly. MCSNET hosts KumoMTA managed in Toronto — installation, Lua configuration, IP warm-up, authentication, and monitoring included — so the engine is turnkey and stays free to own. You integrate against your own stack rather than Mailgun’s API, but you keep a no-licence engine, own your reputation, escape per-recipient pricing, and keep data in Canada.
Related match-ups: Postfix vs Sendmail · PowerMTA vs Postal · KumoMTA vs Postal.
Go to the managed product: PowerMTA / KumoMTA server hosting · glossary: IP warming.