Looking for a Mailgun alternative that covers inbound mail too?
No per-email markup from us and a smaller, opinionated surface. Mailgun's breadth (optimization, validation, routes, lists) is more than most teams need once they're past MVP.
Mailgun is a great product — it's where most teams land the first time they need transactional email that "just works." But as your stack matures, the calculus often shifts: data residency requirements, predictable cost at higher volumes, and the desire to own the whole mail surface — inbox, route table, events and outbound — behind one API instead of three vendors.
Flowmails is what you ship when those are the things you've started to care about. It connects to your domain provider over OAuth and runs one shared mail worker for every tenant, so your inbox, outbox, and route table live in one place, scoped to your domain. There is no per-email fee on top of your provider's own pricing; the platform subscription is what you see on the /price page.
Mailgun's free tier is 100 emails/day for 1 month; paid plans start at $15 / month for 10,000 emails. Flowmails' Base plan is $0; Pro is $9.9 / month and Enterprise is $39.9 / month.
Mailgun is hosted — sign up, verify domain, call the API. Flowmails connects your domain provider over OAuth and runs the shared mail worker for every tenant.
Mailgun: teams that need its deliverability tooling (inbox placement, validation) and its email-list / routes products. Flowmails: teams that want inbound mail and route tables without the breadth.
Mailgun exposes both an HTTP API and an SMTP relay. Flowmails is REST-only. SDK-wise, the surface areas are similar (send / receive / stats).
Highlights
What Flowmails does differently
Data residency
Flowmails' own storage, scoped by domain id
Inbound routing
Yes (route tables, scoped by domain id)
SMTP relay
No
Email validation
Not bundled
Mailing lists
No (transactional only)
Per-email pricing
No
Migration
How to migrate from Mailgun to Flowmails
Decide whether you need Mailgun's optimisation / validation products
If your team depends on Mailgun's inbox placement reports or email validation, plan for those independently — Flowmails doesn't bundle equivalents. If you only ever used Mailgun for send / receive, the migration is straightforward.
Connect the domain's provider
Same prerequisite as every other Flowmails flow: the zone must be on a supported routing provider — Cloudflare is the one we support today, with the provider SPI open to others.
Replace the SDK
Swap Mailgun SDK calls for Flowmails SDK calls. Templates are plain HTML, so the renderer is unchanged. If you used Mailgun's inbound routes, port them into Flowmails' route tables (an allow-list of exact local parts, not regex).
FAQ
Common questions about switching from Mailgun
Other alternatives