Selva Mail vs
Mailgun
Billed per email on volume tiers, with a limited free allowance.
What Mailgun does well
A developer-first sending API with strong routing and inbound parsing, plus validation and deliverability tooling that genuinely helps if you are diagnosing list quality problems.
Where the pricing model hurts
Per-email pricing with a subscription floor, and the useful deliverability tooling sits on higher tiers. Costs climb with volume in the usual way.
What it costs at 5k, 10k and 25k
Assumes four emails per contact per month. Selva Mail is a one-time $497 license, then AWS bills you for what you actually send.
| Contacts | Mailgun | Selva Mail (AWS) | Annual saving | Payback |
|---|---|---|---|---|
| 5,000 | $35/mo | ≈$2/mo | $396 | ~15.1 months |
| 10,000 | $35/mo | ≈$5/mo | $360 | ~16.6 months |
| 25,000 | $75/mo | ≈$12/mo | $756 | ~7.9 months |
Public list prices, 2026. Where a competitor is free software, the saving column is blank on purpose — the cost you are comparing is your own server and your own hours, not a license fee.
Selva Mail costs $497 once, then AWS at cost — about $6/mo at 50,000 emails. It is priced per email sent, not per contact, so it does not grow with your list.
Migrating from Mailgun
Repoint the API and re-verify domains against your own SES identities. Inbound routing has no direct equivalent, so check whether you depend on it before moving.
Stop paying for the same contacts
every month.
$497 once. Runs on your infrastructure, sends through your own AWS SES account. Launch buyers get agency rights permanently — unlimited client workspaces. First 100 licenses.