The research in brief
Mailgun is a good fit for developer transactional email API use, especially for teams sending roughly 10,000 to 50,000 application emails per month that value API breadth, SMTP fallback, and event-driven monitoring. Five of the six included platforms named Mailgun during the ranking stage, and it landed at an average listed rank of 3.4 with a best rank of 2. The strongest reason to consider it is the combination of a documented REST Send API, SMTP relay, signed webhooks, and usage-based Basic and Foundation plans. The main limitation is that no reviewed source independently verified a transactional deliverability rate, and log-retention, SLA, and cancellation terms remain unclear or inconsistent.
Research Snapshot
| Field | Finding |
|---|---|
| Platform mentions in ranking stage | 5 of 6 included platforms (DeepSeek, Gemini, Kimi, ChatGPT, Perplexity) |
| Share of included platform responses | 83.3% |
| Average listed rank | 3.4 |
| Best listed rank | 2 (Perplexity) |
| Software offering | Mailgun Send Email API on the Basic or Foundation plan |
| Overall use-case fit | Good |
| Research date | 2026-10-02 |
Why Mailgun Qualified for This Study
Questions explored
- Is Mailgun a good choice for developer transactional email api?
- Why did AI platforms rank Mailgun for sending application emails like password resets?
Mailgun qualified because it is a purpose-built transactional email API service rather than a general marketing suite, and because five of the six included platforms named it during ranking discovery. It was described as a transactional email and email API provider with developer tooling and deliverability features [15], and as an API-first service with RESTful sending, tracking, and inbound messaging capabilities [26].
The ranking-stage statistics show Mailgun at an average listed rank of 3.4 across the five platforms that named it, with a best rank of 2 from Perplexity and a worst rank of 5 from Gemini. That spread matters: it indicates broad recognition rather than uniform placement at the top of the category.
Fit ratings were consistent across the six included platforms: five rated Mailgun "good" and one (Gemini) rated it "strong." No platform rated it below good, and no platform rated it conclusively best-in-class. This is a consensus of adequacy for the developer transactional email API use case, not proof of product quality.
The software offering in focus
Questions explored
- Which Mailgun plan should a buyer choose for a production workload near 50,000 application emails per month?
- Is the Mailgun Send API on the Basic plan enough for password resets and order confirmations?
The relevant product is the Mailgun Send Email API, delivered through the Basic or Foundation plan depending on volume. Platforms described the relevant plan slightly differently - ChatGPT and Perplexity pointed to Basic or Foundation, Grok to Basic or Foundation, Kimi to Basic, Foundation, or Scale, and Gemini to Basic, Foundation, and Scale - so buyers should treat the plan name as volume-dependent rather than fixed.
Basic is listed at $15 per month with 10,000 included emails, no daily email limit, RESTful email APIs and SMTP relay, one custom sending domain, tracking, analytics, webhooks, and five inbound routes [17]. Foundation is listed at $35 per month after a free first month with 50,000 included emails and expands domains, retention, templates, and inbound-routing access [17].
For a production workload near 50,000 emails per month, Foundation is the closest published match. For lower-volume production use, Basic is the entry point. Mailgun's own pricing page states that since it exposes both an HTTP API and an SMTP endpoint, senders can choose either method, and that it recommends the HTTP API for application builders [17].
What the AI Platforms Agreed About
Questions explored
- What do AI platforms agree Mailgun does well for developer transactional email api?
- Does Mailgun support both REST API and SMTP relay for application-triggered emails?
The platforms agreed unanimously on four capabilities: REST API sending, SMTP relay, webhook and event support, and volume-tiered self-serve plans.
On API and developer workflow, the Send API accepts text, HTML, attachments, templates, recipient variables, tags, custom variables, scheduling options, TLS requirements, and test mode, and a successful request returns a queued message identifier [4]. HTTP sending supports messages up to 25 MB [7]. Mailgun publishes API reference documentation and supports sending and receiving through US and EU API regions [2].
On SMTP relay, Mailgun supports SMTP in addition to HTTP API sending, with endpoints on ports 25, 465, 587, and 2525 and a recommendation to use port 587 where port 25 is blocked or throttled [9]. Kimi reported SMTP relay available on every plan including the free tier, with TLS authentication and IPv4/IPv6 support [21].
On webhooks and events, documented event types include accepted, delivered, temporary failure, permanent failure, rejected, unsubscribed, and complained [6]. Webhooks can be configured at account or domain level with up to three URLs per event type, and requests are signed for verification [10]. Webhooks send HTTP or HTTPS POST requests with JSON payloads and can be created, retrieved, updated, and deleted programmatically [5].
On pricing structure, the platforms agreed that Mailgun uses volume-tiered self-serve plans with published overage rates rather than a single flat fee [17].
Where the AI Platforms Disagreed or Were Uncertain
Questions explored
- Is Mailgun's transactional deliverability rate independently verified for application emails?
- How long does Mailgun retain logs and event data on the Basic and Foundation plans?
The platforms disagreed or stayed silent on deliverability verification, log retention, SLA terms, and support quality.
On deliverability, no platform established an independently verified transactional deliverability rate or inbox-placement guarantee. Mailgun documents bounce classification, suppression management, authentication protocols, tracking, and deliverability-related products [18], but company materials describing deliverability capabilities do not establish a neutral, independently audited rate for this use case. Grok characterized Mailgun's position as mixed versus pure transactional specialists [19].
On retention, the sources conflict. Mailgun's pricing page lists Foundation with five days of log retention, while its tracking documentation states that paid-account event data is stored for at least 30 days [3]. Google reported 1 day of retention on Basic, 5 days on Foundation, and up to 30 days on Scale [13]. Kimi reported 72-hour message retention with an endpoint to resend a stored message to a new recipient without rebuilding the payload [20]. These figures describe different things - log searchability, event storage, and message storage - but the reviewed sources do not reconcile them.
On SLA and contracts, the reviewed public pricing and help pages did not establish complete cancellation, refund, renewal, or annual-commitment terms, and did not establish a general uptime SLA applicable to Basic or Foundation (ChatGPT). Kimi flagged that whether the Scale plan requires an annual commitment is unclear from public sources [21].
On support, Gemini reported that support on Free, Basic, and Foundation is limited to a ticket-based system that can slow resolution during delivery issues, with live chat requiring the Scale plan [25]. No other platform independently corroborated this.
Features for this workload
Questions explored
- Does Mailgun support inbound email parsing and email validation alongside transactional sending?
- What are Mailgun's batch size and attachment limits for application-triggered email?
Mailgun's strongest differentiators for this use case are inbound routing, validation, and message resend, which most transactional competitors lack or charge separately for.
Inbound routing and parsing: Mailgun routes inbound mail, parses it, and stores raw MIME for programmatic fetching [20]. Google reported routing limits of 1 custom rule on Basic, 5 on Foundation, and full routing on higher plans [13].
Email validation: Mailgun validates addresses in real time at signup or in bulk from CSV, priced as an add-on at $1.80 per 1,000 on Basic with 5,000 included on Foundation [20].
Message resend: Mailgun stores messages and provides an endpoint to post a stored message to a new recipient without rebuilding the payload [20].
Batch and size limits: batch sending is capped at 1,000 emails per request, matching Brevo, SendGrid, and Amazon SES, while Resend limits to 100 and Mailtrap to 500 [14]. Maximum attachment size is 25 MB [14]. The Send API documents a 16 KB combined limit for certain send options and a maximum of 1,000 recipients per batch [4].
SDK coverage: official SDKs exist in six languages - Go, Node.js, PHP, Java, Ruby, and Python - while Resend offers eight including Rust and.NET [14]. Kimi also flagged that Mailgun does not offer native idempotent sending, whereas Brevo (UUID, 30-minute TTL) and Resend (dedicated header, 24-hour TTL) do [14].
Data hosting: Mailgun offers both EU and US data hosting options [14].
Pricing, renewal terms, and ongoing costs
Questions explored
- How much does Mailgun cost per month for 10,000 or 50,000 application emails, and what are the overage rates?
- Are there setup, dedicated IP, or cancellation fees a buyer should budget for with Mailgun?
Published self-serve pricing is free up to 100 emails per day, then Basic at $15 per month for 10,000 emails per month, and Foundation at $35 per month after a free first month for 50,000 emails per month [17]. Scale is listed at $90 per month for 100,000 emails [28].
Overage pricing is published as starting rates: $1.80 per 1,000 emails on Basic, $1.30 per 1,000 on Foundation, and $1.10 per 1,000 on Scale [17]. Grok reported a range of $1.10 to $1.80 per 1,000 emails across tiers [27]. Overage charges are automatically billed and cannot be disabled according to help documentation (ChatGPT).
Dedicated IP addresses are listed at $59 per month as an add-on on lower plans and included in Scale 100k+ plans [24]. Email validation is billed separately at $1.20 per 100 validations on Foundation and $0.80 per 100 validations on Scale [17]. Mailgun Optimize, a separate deliverability suite, is listed at $49 per month and $99 per month tiers after a free first month, with custom contract pricing above that [18].
Billing mechanics: upon signup, only the prorated amount of the selected plan for the current month is billed; afterward, monthly plan cost plus extra emails and validations are billed at the start of each month for the previous month, and any remaining balance is charged before an account can be closed [17].
Contract terms are not fully established. Grok reported month-to-month plans with no long-term contracts mentioned and a 30-day trial on some plans [27]. Google reported pay-as-you-go monthly subscriptions with no long-term contract requirement for standard tiers, with enterprise plans requiring custom contracts [24]. Kimi flagged that Scale plan annual commitment or minimums are not explicitly verified [21]. Pricing confidence varied by platform: high for Grok and Gemini, moderate for ChatGPT, Perplexity, and Kimi, and low for DeepSeek, which did not confirm current US prices at all [17].
Best Suited For
Questions explored
- Who gets the most value from Mailgun for developer transactional email api?
- Is Mailgun a good fit for a team that needs inbound email routing and validation, not just outbound sending?
Mailgun is best suited to engineering teams sending automated application messages at moderate volume that want API flexibility plus SMTP fallback.
The platforms converged on these buyer profiles: application receipts, password resets, alerts, and other automated transactional messages; teams preferring a REST API but requiring SMTP relay compatibility; developers needing delivery, bounce, complaint, and failure events; and teams sending approximately 10,000 to 50,000 emails per month (ChatGPT). Deepseek added teams wanting a purpose-built transactional sending API plus SMTP relay in one provider, and developers who value API docs, SDKs, and a sandbox or test mode for integration [15].
Kimi identified a narrower high-value segment: teams needing inbound email routing and parsing, developers requiring email validation before sending, applications needing to resend stored messages to new recipients without rebuilding payloads, and teams wanting both EU and US data hosting [20]. Google emphasized multi-tenant SaaS platforms needing high-volume REST APIs and organizations prioritizing delivery logging and immediate webhook notifications [22].
Probably Not Best Suited For
Questions explored
- Who should not choose Mailgun for developer transactional email api?
- Is Mailgun a poor fit for buyers who need a written deliverability guarantee or a published uptime SLA?
Mailgun is probably not the best choice for buyers whose primary requirement is independently verified deliverability, a published uptime SLA, or the lowest possible per-email cost.
Buyers requiring a publicly verified deliverability benchmark or guaranteed inbox placement should look elsewhere, because no reviewed source established an independently audited rate for this use case (ChatGPT). Teams requiring extensive dedicated-IP or enterprise deliverability services at lower volumes face a $59 per month add-on rather than bundled infrastructure [24].
Very low-volume hobby projects are a poor fit: the free tier is capped at 100 emails per day, which Kimi noted is smaller than Brevo's 300 per day and other testing tiers [21]. Cost-sensitive teams seeking the lowest per-email price should note that Amazon SES and sendvia are described as cheaper at scale [20].
Developers requiring built-in idempotency or duplicate-send protection will not find it natively in Mailgun, unlike Brevo and Resend [14]. Teams prioritizing the widest SDK language coverage should note Resend offers eight languages including Rust and.NET versus Mailgun's six [14]. Buyers who need a full marketing-automation suite rather than a focused transactional email API are also outside the core fit [15].
When Another Option May Be Better
Questions explored
- What is a better alternative to Mailgun for a buyer who needs the lowest per-email cost at high volume?
- When should a buyer pick Postmark, Resend, or Amazon SES instead of Mailgun for application emails?
Another option may be better in five specific situations the platforms identified.
When pure transactional focus and top deliverability matter most, Grok pointed to Postmark [19]. When lower per-email cost at high volume is the priority, Grok and Kimi pointed to Resend or Amazon SES, with Amazon SES listed at $0.10 per 1,000 emails and sendvia at a flat $19 plus SES costs [19]. When simpler onboarding and a dedicated IP on the entry plan matter, Grok pointed to SendGrid [19].
When native idempotency is required, Kimi pointed to Brevo (UUID, 30-minute TTL) or Resend (dedicated header, 24-hour TTL) [14]. When the largest free testing tier is needed, Kimi pointed to Brevo at 300 per day, Mailapi.dev at 5,000 free for testing, or Elastic Email's free plan [14]. When a marketing and transactional blend with SMS or WhatsApp is needed, Kimi pointed to Brevo or SendGrid [14].
Openai framed the alternative decision differently: choose another provider when independently benchmarked deliverability or a clearly documented uptime commitment is the primary buying requirement, choose a lower-cost provider when monthly volume is well below 10,000 and the free 100-email-per-day limit is inadequate, and choose an enterprise-focused provider when extensive managed deliverability, dedicated infrastructure, or contractual service commitments are needed (ChatGPT).
Questions to ask before choosing a provider
Questions explored
- What should a buyer confirm with Mailgun before signing a contract for application email sending?
- Which Mailgun terms are unclear in public sources and must be confirmed directly?
The reviewed sources left several commercially material questions open. Buyers should confirm each of the following directly with Mailgun before committing.
Retention: what exact event and log-retention period applies to the selected Basic or Foundation account, given the conflict between the pricing page and tracking documentation [3].
Limits and bursts: whether API, webhook, SMTP, and sending limits are sufficient for expected peak bursts and retry behavior, and what the current overage rates are for the buyer's expected monthly volume, including whether overages or hard spend limits can be configured (ChatGPT).
Dedicated IP: whether a dedicated IP is available at the expected volume, what additional fee applies beyond the listed $59 per month, and whether IP warm-up service is included [24].
SLA and support: what uptime, support-response, and service-credit commitments apply to the selected plan, and whether ticket-only support on Basic and Foundation is adequate for the team's incident response needs [25].
Contracts: current cancellation, refund, renewal, and trial-conversion terms, and whether the Scale plan requires an annual commitment or minimum [21].
Regions and DNS: which US or EU sending region is appropriate for the application's data and operational requirements, and what DNS, SPF, DKIM, DMARC, tracking-domain, and domain-verification work is required before production sending [14].
The consensus assessment
Mailgun is a good, practical fit for developer transactional email API use, especially for teams sending 10,000 to 50,000 messages monthly that value API breadth, SMTP compatibility, and event-driven monitoring. Five of six included platforms named it during ranking, with an average listed rank of 3.4 and a best rank of 2. Select Foundation for a production workload near 50,000 emails per month and Basic for lower-volume production use.
The verdict is rated good rather than strong because the public evidence reviewed does not independently verify deliverability rates, clearly resolve retention discrepancies, or establish plan-level SLA and cancellation terms. Platform agreement on features and pricing structure is not evidence of product quality or delivery performance.
How This Review Was Produced
This review was generated from a structured research run dated 2026-10-02 in which six AI platforms were asked which providers they would recommend for a software team needing reliable automated, application-triggered email such as password resets, order confirmations, and system alerts, separate from marketing campaigns. The platforms evaluated API reliability and documentation, transactional deliverability rates, webhook and event support, pricing per email volume, and SMTP relay options.
Mailgun was named by five of the six included platforms during the ranking stage. Each platform's fit-research response, citations, pricing findings, limitations, and verification questions were collected and compared. Claims are attributed to the platform that supplied them using parenthetical citation IDs. Company-owned sources are distinguished from independent sources in the Sources section. No product testing, customer interviews, or independent verification was performed.
Research limitations
Several limitations apply to this review.
Platform-reported research dates differ from the authoritative run date. Deepseek's response is dated 2026-02-14 while the run research date is 2026-10-02; platform-reported dates are provenance metadata and do not independently prove freshness (DeepSeek).
Platform mentions count only platforms that named Mailgun during ranking discovery. All included platforms evaluated fit, but not all named the entity in the ranking stage.
Company-owned citations materially outnumber independent citations in the supplied evidence. Company claims should not be described as independently verified.
The supplied URLs were collected from platform responses and were not independently validated by the writer stage.
Citations are platform-reported evidence, not independently verified facts. Deepseek's response was produced with search disabled, so its pricing and plan claims require explicit verification before being treated as current.
Conflicting product names, pricing, and capabilities were not resolved by guessing. Where sources conflicted - particularly on log retention, Scale plan commitment terms, and overage rates - the conflict is described and buyers are directed to verify.
No independently verified deliverability percentage, inbox-placement guarantee, or plan-level uptime SLA was established for this use case.
See the broader Developers Sending Application Emails consensus index for comparisons across qualified options.
Explore more marketing automation and email marketing software guidance in the category directory.
Sources
Company-Owned Sources
- Mailgun Documentation: https://documentation.mailgun.com/
- Mailgun API Overview: https://documentation.mailgun.com/docs/mailgun/api-reference/api-overview
- Configuring Webhooks: https://documentation.mailgun.com/docs/mailgun/user-manual/webhooks/configuring-webhooks
- Free Email API for Developers | Brevo: https://www.brevo.com/features/email-api/
- Mailgun: Transactional Email API Service for Developers: https://www.mailgun.com/
- Free Email API Service: Send Email: https://www.mailgun.com/features/email-api/
- Mailgun Email Delivery and API Pricing Plans: https://www.mailgun.com/pricing/
- Mailgun Optimize Pricing: https://www.mailgun.com/pricing/optimize/
Independent Sources
- SendGrid vs Postmark vs Mailgun Email API 2026: https://apiscout.dev/guides/sendgrid-vs-postmark-vs-mailgun-transactional-email-2026
- sendvia - the honest transactional email API on Amazon SES: https://sendvia.io/
- Compare email APIs – Notix: https://usenotix.dev/compare
- Mailgun Pricing in 2026: 4 Plans Compared: https://www.itechguides.com/products/mailgun/pricing/
- Mailgun Pricing 2026 - Plans from Free to Scale $90/mo: https://www.stackscored.com/pricing/transactional-email/mailgun/
ChatGPT
Claude
DeepSeek
Grok
Perplexity
Kimi
Gemini