A transactional email API, evaluating Mailgun?
Mailgun already covers EU data residency. If you're looking to switch anyway, the reasons are request shape, longer log retention by default, and a price that's locked for 24 months.
A JSON API, not form-encoded
Mailgun's classic API is form-encoded with HTTP Basic Auth. Envello is JSON over Bearer auth to a single endpoint, a shape most teams find easier to test and log.
24-month price lock
Your tier price is fixed at signup. Any change after that gets 6 months' notice and a grandfathering option, published, not buried in a contract.
90-day log retention
Debug a bounce from three months ago, not three weeks ago. Free tier gets 7 days, Pro gets 90, Scale is configurable up to 365, worth checking against whatever tier your current Mailgun retention sits on.
What actually moves, and what doesn't
Mailgun already has an EU region. Why switch?+
Fair point, worth saying up front: api.eu.mailgun.net already covers EU data residency, so that alone isn't the reason to move off Mailgun the way it might be for a US-only provider. The honest reasons are elsewhere: request shape, default log retention, and pricing that doesn't shift under you.
Is this a same-shape SDK swap?+
No, budget more time than that. Mailgun's classic API is form-encoded, authenticated with HTTP Basic Auth using api as the username and your API key as the password. Envello is JSON over Bearer auth to a single endpoint. It's a different request format, not a field rename.
What if I'm already using mailgun.js?+
Less work. The official mailgun.js SDK wraps the form-encoded API in a more familiar client shape (mg.messages.create(domain, data)). If your codebase already goes through that SDK, the migration is mostly swapping the client and adjusting the method signature rather than rewriting raw form-encoded requests.
Full walkthrough: Migrating from Mailgun to Envello