Integrations · Mailgun

Mailgun
without the markup.

Developer-shaped, strong on routing, and watch the log retention.

Best for developer teams who need inbound routing
At a glance

Mailgun, in six lines.

Pricing checked against the provider's own page on 1 August 2026 and stated as an approximation — always confirm current rates before you commit.

Provider type
mailgun
Approx. cost
Tiered plans with an included monthly volume and per-1,000 overage above it. Overage rates are comparatively expensive, so pick a tier that covers your actual volume. Confirm on the pricing page.
Log retention
The differentiating spec. As little as one day on the entry tier, rising to around 30 days higher up. One day makes debugging genuinely painful.
Setup effort
Low to medium — domain verification plus API key
Dedicated IPs
Included on the higher tier; available as an add-on below it
Extras sold separately
Email validation and deliverability tooling are separate products with their own pricing
Best fit
Teams who need inbound parsing or routing alongside outbound sending
Honest assessment

Where it wins, where it does not.

Strengths
  • Genuinely good API design, and inbound routing and parsing that most competitors do not offer at all.
  • Flexible routing rules, which suit teams doing something more complex than one-way sending.
  • Strong European infrastructure options for teams with data residency requirements.
  • Detailed event data, provided your plan retains it long enough to be useful.
Trade-offs
  • Log retention on the entry tier can be as short as a single day. Debugging a delivery problem reported on Friday about a Wednesday send is then impossible.
  • Overage rates are expensive relative to the included volume — being on the wrong tier costs more than the tier upgrade would.
  • Validation and deliverability features are separately priced products, so the headline price is not the whole bill.
  • Deliverability support is thinner than a specialist like Postmark unless you buy into the higher tiers.
Setup

Connecting Mailgun.

01

Add and verify your domain

Add the sending domain in Mailgun and publish the TXT and CNAME records it provides, including the DKIM record and the tracking CNAME. Use a subdomain such as news.yourbrand.com.

02

Choose your region

Mailgun operates separate US and EU infrastructure, and the API endpoints differ. Pick deliberately — moving later means re-verifying domains, and if you have EU data residency obligations this is the step that satisfies them.

03

Create a sending API key

Generate a key scoped to sending rather than full account access.

04

Connect it in SendNectar

Add a provider connection with type mailgun, set its purpose, and submit the key. Credentials go to a dedicated endpoint and are encrypted server-side; the API never returns them.

05

Run the connection test

Validate against real health checks before production mail moves. Then create a sender profile pinned to the verified domain.

06

Check your log retention before you need it

Confirm what your tier retains. If it is one day, either upgrade or make sure SendNectar's own message and event history is your working record — it retains longer than Mailgun's entry tier does.

When Mailgun is the right call

Choose Mailgun when you need more than one-way sending. Inbound routing and parsing — receiving mail, applying rules to it, and posting it to your application — is a genuine differentiator that most providers in this list do not offer at all.

If your product needs to receive email as well as send it, Mailgun and a small number of competitors are the shortlist.

The log retention trap

This is the spec to check before you sign up, and it is the one people discover too late.

Entry-tier log retention can be as short as one day. That sounds inconsequential until a customer reports on Monday that they never received something sent on Friday, and there is simply no record left to look at.

Two ways to handle it: pay for a tier with meaningful retention, or lean on SendNectar’s own message and event history, which keeps the full lifecycle — queued, accepted, delivered, failed — alongside the provider events for substantially longer. The second is often the cheaper answer, but decide deliberately rather than finding out during an incident.

Watch the overage arithmetic

Mailgun’s model is an included volume plus per-thousand overage, and the overage rates are comparatively steep. Sitting 40% above your tier’s included volume frequently costs more than simply moving up a tier.

Check this quarterly. Volume creeps, and the bill creeps faster than the volume.

Notes for multi-brand senders

One verified domain per brand, as with every provider here. Reputation is per domain, so sharing one means the weakest brand sets the ceiling.

Pick your region once, deliberately. Mailgun’s US and EU stacks are separate, and mixing brands across both means two sets of endpoints, two sets of verified domains, and two places to look when something breaks. If any brand has EU data residency obligations, put them all in the EU rather than splitting.

Use Mailgun’s tagging alongside SendNectar’s brand scoping so the two systems agree on which brand you are looking at when you investigate something.

Connect Mailgun.
Keep the delivery bill.
Start free.

Sandbox runs in test mode — wire up the connection and run a connection test before anything reaches a real inbox.