Mailgun review

Mailgun is a hosted email delivery service and API, not a library or self-hosted mail server. It sits between an application and recipients’ mail systems: your code sends messages through Mailgun’s API or SMTP service, and the platform provides tools to track and manage delivery. It can also receive and parse incoming messages.

The service targets transactional email and other application-driven sending, with the homepage describing volume ranging from thousands to millions of emails. Its product set extends beyond sending: developers can use email validation through an API or bulk upload, preview messages before sending, and access deliverability tools. The homepage also describes connecting email data to a CRM. That makes Mailgun a broader hosted email suite rather than a minimal send-only endpoint. The trade-off is architectural: delivery depends on a third-party service, and applications that use Mailgun-specific validation, inspection or routing features may need additional work to move those workflows elsewhere.

The integration surface is an email API plus SMTP services for sending, receiving and tracking messages. Mailgun’s site links to API documentation and an SDKs page, and lists integrations among its resources. It also advertises a plugin for Cursor. The homepage does not name SDK languages or describe a CLI, so confirm supported languages and current SDK maintenance in the vendor’s documentation before choosing a stack. Do not assume a particular client library is available for your runtime.

The same platform offers a real-time Email Validation API, bulk list validation, incoming-message parsing and email previews. These services can reduce the number of separate vendors in an email workflow, but each feature adds another integration to account for if you later migrate. The homepage does not describe a specific API style or webhook protocol. Review the API docs for authentication, request and response formats, retry behavior, event delivery, and versioning. Mailgun also links to a Help Center, status page and release notes, which are useful places to check during implementation and operations.

The Free plan costs $0 per month and includes 100 emails per day, one custom sending domain, two API keys, one day of log retention and one inbound route. The daily cap makes it suitable for low-volume testing, not a production workload that may burst above that limit. A 30-day free trial is also listed.

Basic costs $15 per month for 10,000 emails, with no daily email limit. Foundation is $35 for 50,000 emails; Scale is $90 for 100,000 emails and includes 5,000 validations, SAML SSO, 30 days of log retention and dedicated IP pools. Enterprise pricing is custom. The pricing page lists monthly billing and no annual prices.

Usage can add to the base plan: extra emails start at $1.80 per 1,000 on Basic, $1.30 on Foundation and $1.10 on Scale. Extra validations start at $1.20 per 100 on Basic and Foundation, or $0.80 per 100 on Scale. Additional dedicated IPs cost $59 per month each. Model volume and validation needs together before selecting a tier.

Mailgun is presented as a hosted email delivery service. The vendor does not publish an open-source license or a self-hosting option on the vendor's site, so teams requiring either should ask Mailgun directly rather than plan around running the service themselves. Data export details are also not published; ask what message, event, suppression and configuration data can be exported, in what format, and for how long it remains available.

SMTP is a standard integration surface that can make basic sending easier to redirect, but it does not guarantee a drop-in migration. Applications using Mailgun’s API, validation, inbound parsing or deliverability tools may need to replace those functions and adjust their message handling. Keep sending logic behind an internal adapter and retain copies of the data your application needs. Before signing up, confirm termination procedures, export access and any retention period that affects your records.

The pricing details specify email allowances and several retention limits, but they do not publish API rate limits. Check the vendor’s documentation or ask support about request limits, burst behavior, retries, queueing and delivery-event retention for your expected traffic. The homepage promotes reliability, compliance and scale, and links to a status page and Security Portal; those are starting points, not a substitute for reviewing service commitments and security terms.

Reddit reports are mixed and anecdotal. In one web development thread, a user said a free plan became a $35-per-month plan after an email may have been missed. Another poster described a legitimate ecommerce account being permanently disabled after its first newsletter campaign. These accounts do not establish how often such events occur, but they make account review and acceptable-use rules worth checking before sending critical mail. Keep a fallback provider or migration plan, and verify that your sending use case is approved.