Compare · Email infrastructure

KumoMTA vs GreenArrow

Researched 2026-06-22 · perishable specs (licensing, versions, vendor status) verify at time of decision

Who should read this comparison?

If you send at high volume and want more control than a SaaS API but more support than hand-rolling Postfix, both of these are on your shortlist — and the choice turns on how much you value openness and price versus integration and a vendor on the hook. They are not far apart in capability; they are far apart in model.

Two readers benefit most. The first is a DevOps-comfortable team that wants a free, modern engine it fully controls, is happy to bring its own campaign front-end, and would rather avoid licenses and lock-in — that is KumoMTA. The second wants a supported, more complete product: a commercial engine with strong hands-on help, an optional campaign layer from the same vendor, and the choice of self-hosting or letting the vendor host it — that is GreenArrow. A shared concern pulls both readers the same way at first: after Bird’s retreat from on-prem with PowerMTA and Momentum, each of these is an independent alternative, and the rest of the decision is about open-versus-commercial and engine-only-versus-integrated.

It is worth being honest that capability is rarely the deciding factor here, because both deliver at the volumes these readers care about — millions of messages an hour, with the throttling, IP-pool, and bounce-handling tooling that high-volume sending demands. GreenArrow even added Prometheus observability recently, narrowing one of the gaps where a modern open engine used to pull clearly ahead. So the decision is not “which can send my volume” — both can — but which model you want to live inside: a free, open engine you own and operate, or a commercial product you license and lean on a vendor to support. Teams that try to decide this on a feature checklist tend to stall, because the checklists look similar; teams that decide on model — openness, cost, integration, support — get to an answer quickly.

Open engine versus integrated platform, and the independence both share

Two distinctions organize this comparison, plus one thing the two have in common. The first distinction is openness and price: KumoMTA is open-source and free under Apache 2.0, while GreenArrow is commercial software you license. That shapes everything downstream — cost, lock-in, who can modify it, and what you are entitled to from a vendor.

The second is scope: KumoMTA is engine-only. It sends, brilliantly, and stops there; the campaign management, list tools, and editor are yours to supply. GreenArrow is modular but can be end-to-end — its Engine handles delivery, its optional Marketing Studio adds campaigns, segmentation, triggers, and a drag-and-drop editor, and its Monitor adds inbox-placement analytics, so one vendor can cover the whole stack. The thing they share is independence from Bird. PowerMTA and Momentum are now both owned by a cloud-focused Bird that has cut their on-prem teams; KumoMTA is an open project by ex-Message Systems veterans, and GreenArrow is built by DRH Internet, an independent company committed to its on-prem and hosted product since 2003. For a sender unsettled by the Bird situation, that shared independence is why these two often end up head to head — and then openness, integration, and support decide it.

The integration distinction deserves a second look, because “engine-only” can sound like a limitation when it is often a choice. A standalone engine like KumoMTA assumes you either already have a campaign front-end or want to choose one freely — and many serious senders do, because they have invested in a particular marketing app, CRM, or in-house tooling and want the delivery engine to slot underneath it. For them, a bundled Studio is not a benefit but a redundancy they would never use. GreenArrow’s integration is the opposite bet: that some teams would rather have delivery, campaigns, and placement analytics from one vendor, with one support contract and one throat to choke, than assemble the pieces themselves. Both bets are reasonable, and they describe genuinely different buyers — which is why the engine-only-versus-integrated question, more than any benchmark, tends to sort people onto one side or the other.

What each one actually is

KumoMTA is an open-source outbound sending engine written in Rust with Lua scripting, released free under Apache 2.0 and built by veterans of the commercial MTA world. It handles millions of messages an hour per server, scales horizontally with Docker and Kubernetes, and integrates natively with Prometheus, Grafana, and Kafka. It is the engine and nothing more — no bundled campaign tool — which keeps it lean and composable but means you provide the front-end. Its cost is the DevOps and Lua expertise to run it; its appeal is a free, modern, fully open engine with no license and no lock-in.

GreenArrow is a commercial, enterprise email delivery platform and MTA from DRH Internet Inc., in development since 2003. Its core is GreenArrow Engine, a high-performance MTA processing millions of messages an hour with SMTP, HTTP API, and pipe injection, throttling and automatic backoff, IP-pool management, bounce and feedback processing, tracking, webhooks, and — recently — Prometheus observability. On top, the optional Marketing Studio adds campaign management and Monitor adds inbox-placement analytics. It runs self-hosted on Linux or as a managed cloud service, with cloud plans from around $250 a month and on-prem editions roughly $600 to $800 a month or $6,000 to $9,000 perpetual, and it is repeatedly praised for hands-on support and being easier and more productized than PowerMTA.

GreenArrow’s origins explain its character. DRH Internet began in 1999 running email servers and moved into open-source email consulting in 2003, repeatedly fielding calls from senders whose outbound servers were overloaded or blocked — and that demand led them to build a fast sending engine, which grew into the product and eventually displaced the consulting work entirely. That history shows in the result: a product shaped by years of hands-on deliverability problem-solving rather than by a platform company bolting on an MTA. It is also why support is so consistently singled out in reviews — the company grew up solving exactly the problems its customers face, and senders describe cost reductions of ninety percent versus a hosted ESP after moving delivery in-house onto it. The trade-off reviewers note is that the campaign side, while capable, is a marketing tool rather than a full CRM, so member-level customer tracking is thinner than a dedicated platform would offer.

What does the side-by-side look like?

The table sets the free open engine against the commercial integrated platform. Wins land on both sides, and the openness and integration rows are the ones to weigh first.

GreenArrow pricing tiers and versions are perishable — verify current terms with the vendor; verify price as of date.

Where GreenArrow has the edge

Where KumoMTA pulls ahead

KumoMTA’s case is free, open, and modern, with control to match. There is no license and no lock-in: the Apache 2.0 engine is yours to run, modify, and keep running regardless of any vendor’s fortunes, which is the strongest possible answer to the commitment worries that surround commercial MTAs. It is built in Rust for cloud-native, horizontally-scaled deployment, with Lua configuration you version and test and native Prometheus, Grafana, and Kafka integration — a fit for teams practising infrastructure-as-code. Because it is engine-only, it composes cleanly with whatever front-end you prefer rather than tying you to one vendor’s campaign tool. And it is built by the same lineage that created the commercial engines, so the deliverability pedigree is there without the price. For a DevOps-capable team that wants maximum control, zero license cost, and total openness, KumoMTA is the more future-proof foundation — and pairing it with managed hosting answers the support gap that is otherwise GreenArrow’s advantage.

The openness point is worth pressing, because it is more than a philosophical preference at this volume. When your sending engine is open source, you are insulated from the single largest risk these comparisons keep surfacing: a vendor changing direction. GreenArrow’s vendor is independent and committed today, which is genuinely reassuring, but it is still one company whose future you cannot control — and the cautionary tale of PowerMTA and Momentum under Bird is exactly what happens when a once-committed vendor’s priorities shift. An Apache 2.0 engine cannot be taken away, repriced, or discontinued out from under you; worst case, the code keeps running and the community or a support partner carries it forward. For an organization whose business depends on sending, that durability is not an abstraction — it is the difference between owning your infrastructure and renting it on terms someone else can rewrite. KumoMTA trades the convenience of a single vendor for the security of owning the engine outright, and for many high-volume senders that trade is the decisive one.

Engine-only or end-to-end?

This is the question that most often separates the two, because it is about how much of the stack you want from one place. KumoMTA is deliberately engine-only: it delivers mail and leaves campaign management, list tools, and editors to a front-end you choose, which suits teams that already have one or want the freedom to pick. GreenArrow can be the whole package: Engine for delivery, Marketing Studio for campaigns and automation, Monitor for placement — useful when you want a single supported vendor across the stack, though its Studio is a campaign tool rather than a full CRM.

Neither model is better in the abstract: composability favours teams who want choice and openness, while integration favours teams who want one vendor and less assembly.

# KumoMTA — free open engine, you compose the rest
license   Apache 2.0, free · Rust + Lua · no lock-in
scope     engine only — bring your own front-end
run       self-host, or managed (e.g. MCSNET)
# GreenArrow — commercial integrated platform (DRH, independent)
license   commercial · cloud ~$250/mo · on-prem ~$600-800/mo
scope     Engine + optional Studio + Monitor
run       self-host or vendor-managed cloud · A+ support

Self-host, managed, or both?

A point of symmetry is worth drawing out: both can be self-hosted, and both can be run for you. GreenArrow offers its own managed cloud alongside its on-prem editions, so you can let DRH host it or run it yourself. KumoMTA is self-hosted by nature, but managed hosting from a provider like MCSNET gives it the same run-for-you option — installation, tuning, warm-up, and monitoring handled. That parallel matters because it neutralizes what might otherwise look like a GreenArrow-only advantage: you do not have to operate either engine by hand. The real difference stays where it belongs — open and free versus commercial and integrated — rather than in who keeps the servers running, since both offer a managed path.

Where MCSNET fits

MCSNET runs the open side of this comparison: it hosts KumoMTA as a managed dedicated server in Toronto, with installation, Lua configuration, IP warming, authentication, and deliverability monitoring handled. That supplies the operational care and human support that are a real part of GreenArrow’s appeal, while keeping a free, open, modern engine with no license and no lock-in, and your own IP reputation with data in Canada under PIPEDA. The honest boundary is integration: GreenArrow can bundle a campaign Studio from the same vendor, and MCSNET does not — it manages the delivery engine, and you pair it with the front-end of your choice, such as MailWizz or a custom app. So the trade is clear. If you want one independent vendor for engine, campaigns, and support in a single commercial package, GreenArrow is a strong, low-risk pick. If you want a free, open engine run for you with your own choice of front-end, managed KumoMTA from MCSNET is the open counterpart — the same modern, Bird-independent deliverability without the license or the lock-in. The managed build is on the PowerMTA server hosting page, with KumoMTA offered on the same basis.

Seen across the three engines this section keeps touching, the landscape resolves into a simple map. PowerMTA and Momentum are the proven commercial incumbents now under a cloud-focused Bird; GreenArrow is the committed independent commercial alternative with its own front-end and support; and KumoMTA is the open, free, modern engine with the same deliverability pedigree. MCSNET’s role is to make that last option as easy to adopt as a commercial product — running the open engine for you so the choice between buying GreenArrow and owning KumoMTA no longer hinges on whether you can operate an MTA yourself. That leaves the decision where it should sit: on whether you want an integrated commercial package or an open engine you own, both delivered without the work of running the servers, and both clear of the vendor risk that started the whole conversation.

Which should you pick?

A practical test: decide how much you value openness and price against integration and a single vendor’s support. A free, open, modern engine you compose and control points to KumoMTA; a supported, integrated commercial platform with an optional campaign layer points to GreenArrow. Both are independent of Bird, both offer a managed path, and the honest tie-breaker is whether you want to own an open stack or buy a supported package — with managed KumoMTA giving the open choice a support layer that closes most of the gap.

Common questions

What is the difference between KumoMTA and GreenArrow?

KumoMTA is a free, open-source sending engine — just the MTA, in Rust, that you operate and pair with your own front-end. GreenArrow is a commercial, integrated platform from independent vendor DRH Internet: a high-performance Engine plus an optional Marketing Studio for campaigns and a Monitor for inbox placement, sold with hands-on support and available self-hosted or as managed cloud. KumoMTA is open and engine-only; GreenArrow is commercial and more complete.

Is GreenArrow owned by Bird like PowerMTA and Momentum?

No, and that matters. GreenArrow is built by DRH Internet Inc., an independent company developing it since 2003 and actively investing in it. Unlike PowerMTA and Momentum, which Bird owns and has de-prioritized for cloud, GreenArrow’s vendor remains committed to its on-prem and hosted product — part of its appeal for senders wary of Bird’s direction.

Is KumoMTA cheaper than GreenArrow?

On software, yes — KumoMTA is free under Apache 2.0, so you pay only for servers and engineers. GreenArrow is commercial, with cloud from roughly $250 a month and on-prem editions around $600 to $800 a month or $6,000 to $9,000 perpetual. GreenArrow’s cost buys support, integration, and a managed option, so it is free-and-self-run versus paid-and-supported, not just a price gap.

Does KumoMTA include campaign management like GreenArrow Studio?

No. KumoMTA is the delivery engine only — it sends, and you bring your own campaign front-end, such as MailWizz or a custom app. GreenArrow optionally bundles Marketing Studio for segmentation, triggers, and a drag-and-drop editor, making it more end-to-end. If you want the campaign layer from the same vendor, that favours GreenArrow; if you prefer your own front-end, KumoMTA leaves it open.

Can MCSNET run KumoMTA so I get GreenArrow-like support?

Largely. MCSNET hosts KumoMTA managed in Toronto — installation, Lua configuration, IP warm-up, authentication, and monitoring included — supplying the operational and support layer that is part of GreenArrow’s appeal, while keeping a free, open engine and your own IPs in Canada under PIPEDA. What it does not bundle is GreenArrow’s Studio campaign layer; you pair managed KumoMTA with the front-end of your choice.