Comparing providers
A Mailgun alternative, with the gaps stated
If you use or are considering Mailgun, this page tells you what Meghly Send does today, what it does not, and what to ask any provider before you move.
What will feel familiar
- A REST API to send mail, with templates, tags and metadata
- An events log you can filter, and analytics by day, hour or month
- Webhooks, suppression lists and unsubscribe handling
- Inbound routes that match on recipient or headers and then forward
- Address validation, with a bulk mode and a sandbox
- SMTP relay with per-domain logins
What is different
- Validate, Send and Receive are one product with one login, not three.
- Validate has its own keys, so a sending key cannot spend validation credits.
- Validate credits include 100 free a day, and bought credits never expire.
- Free tools to check a domain or a message are public and need no account.
- Support comes from the engineers who run the platform.
What Meghly Send does not do yet
- Inbox-placement testing and sender-reputation scores. We do not offer them, and we do not claim to.
- Custom message headers and several addresses in one `to`.
- Per-message required TLS.
- IP warm-up and spreading one domain across several IPs.
- Buying Validate credits inside the dashboard (the free daily credits work today).
- Forwarding of received mail, until the receiving deployment is switched on.
Questions worth asking any provider
- What does the monthly bill look like at your real volume, including logs, validation and dedicated IPs?
- How long are logs and message bodies kept, and what does longer retention cost?
- What happens to your sending when one customer on a shared IP misbehaves?
- Can you export your suppression list and templates if you leave?
- Who answers when something breaks at night, and how fast?
- Check each provider's current pricing page and terms. They change, and this page does not quote anyone else's numbers.
Moving over, step by step
- Add your domain to Meghly Send and put the DNS records in place. Use a sub-domain first if you want to test alongside your current provider.
- Import your suppression list, so you do not mail anyone who already opted out.
- Switch one low-risk stream (for example password resets) to the new API key.
- Watch the events log and the failure chart for a few days before moving the rest.