SuprSend vs Mailgun: multi-channel notifications vs email

Mailgun is an email delivery service, and SuprSend sends email through it. Mailgun gives developers an API and an SMTP relay for sending from their own code. SuprSend is the notification infrastructure above it, where engineering, product and growth run transactional, product and engagement messages on nine channels.

Send the email through Mailgun and run everything around it

Mailgun delivers the email. The SuprSend workflow decides whether a message should go, on which channel, when, and to whom, then hands the email step to Mailgun and moves to a backup provider if Mailgun does not confirm delivery. The right message reaches the right user at the right time on the right channel, with none of that logic in your application code.

One workflow reaches every channel

One send step covers email, SMS, WhatsApp, mobile push, web push, the in-app inbox, Slack, Teams and webhooks. Adding a channel is a step in the workflow, on the same user record and log. Mailgun sends email; SMS, push and chat need other vendors and your own code.

Every kind of message runs from one system

SuprSend unifies transactional, product and customer engagement messages in one system. A password reset, a comment notification and a win-back campaign share the same users, preferences and logs. Mailgun sends whatever your code hands it and has no send button, so every campaign is a script.

Each customer account is its own tenant

Each tenant carries its own branding, template version, channel defaults and inbox feed, with sub-tenants nesting five levels deep, and can send from its own domain and provider. Mailgun subaccounts separate domains, IPs and keys; content and defaults per customer are logic you write.

Users choose channels per category, admins set the defaults

Per category, a user picks channels and a digest schedule, a tenant admin sets the defaults above them, and every send checks those choices first. A hosted page and embeddable components ship with it. Mailgun unsubscribes an address per domain, tag or mailing list, with no categories.

Digests, timezone holds and failover in every workflow

Ten comments become one digest. A message waits for morning in the user’s timezone. If Mailgun does not confirm delivery, the workflow moves to a backup provider or another channel. Mailgun sends each message when asked or at a set time, so batching and fallback are code on your server.

Logs that say why a message did not arrive

Each message keeps its workflow run, rendered content, the provider’s error and the reason a send was blocked, searchable by user for 30 to 90 days. Mailgun logs events per message for one to 30 days by plan, and never sees the decision made before the send.

On its own, Mailgun covers email by API and SMTP, sending domains and dedicated IPs, suppressions, stored templates, inbound routing and delivery logs, with deliverability tools on Optimize. It does not know your users beyond an address, send on any other channel, hold a preference per category, or wait, batch or branch.

Build notifications in the dashboard, in your own agent, or in your codebase

A product manager changes a workflow in the dashboard. A developer commits the same workflow as a file and ships it through a pull request. A marketer asks Claude to build a list and send a campaign. All three are working on the same workflows, templates and logs, so nobody waits on a ticket.

The built-in agent builds, edits and debugs notifications from a description; product and growth ship without a ticket.

Connect the MCP to Claude, ChatGPT or any client and operate templates, workflows, tenants and preferences from there.

CLI and API keep workflows versioned, diffable and reviewed in pull requests; coding agents make bulk changes.

One SuprSend customer runs its marketing email end to end from Claude Code, with nobody in the dashboard.

Mailgun is built from code. Developers send through the REST API, the SMTP relay or SDKs in six languages, and the Mailgun MCP server, which runs on your machine, lets Claude, Cursor or Windsurf send email, manage templates, lists and suppressions, and read delivery stats. The dashboard manages domains, templates and suppressions and has no send button, so a campaign is a script.

Short answer

If this is you	Choose
Your product sends email only, from your own server, and your team is content writing the queue, the retries and the opt-out checks	Mailgun
Your team’s work is inbox placement, IP reputation and list hygiene	Mailgun
One trigger has to reach the user by email, push, SMS, WhatsApp or an in-app inbox	SuprSend
Messages need delays, digests, branches, or a push when the email goes unopened	SuprSend
Users should choose which notifications they get and on which channel	SuprSend
Each customer account needs its own branding, sending domain and defaults	SuprSend
Product and growth should change email content and logic without a deploy or a ticket	SuprSend
A marketing team wants its campaigns and the transactional messages in the same dashboard	SuprSend
You want agents to build, send and manage your notifications from Claude, ChatGPT, Claude Code, Cursor or Slack	SuprSend
Mailgun is already wired in and you are now writing the preference table, the digest job and the retry queue	Both

At a glance

	SuprSend	Mailgun
Best when	Notifications span channels and teams, with logic and preferences around each send	Email is the only channel and your server owns the logic
Who uses it	Engineers, product, growth, and agents over MCP	Engineers through the API; deliverability and ops teams in the dashboard
Messages covered	Transactional, product and customer engagement, in one system	Any email your code sends
Layer	Decides channel, timing, content and recipient; sends through providers	Delivers email by API and SMTP
Built and changed from	Dashboard agent, your own agent over MCP, CLI and API	Server code, template builder, local MCP server
Channels	Email, SMS, WhatsApp, mobile push, web push, Slack, Teams, in-app inbox, webhook	Email, sending and receiving
Recipient model	User profile with every channel address and any JSON properties	Email address; mailing list members with variables
Workflow logic	Delay, digest, branch, routing, timezone, throttle, failover	None; written in your code
Preferences	Per category and channel, digest schedule, tenant defaults	Unsubscribe per domain, tag or mailing list
Multi-tenancy	Nested tenants with own branding, templates, defaults, providers	Subaccounts with own domains, IPs and keys
Templates	Editors for nine channels, versions, translation files	Email templates, 40 versions each, 100 per account
Campaigns	Broadcast to a list from the dashboard, API or an agent	No send button; batch sends by API
Delivery data	Per-user message log with errors and block reasons	Per-message event log and reports by tag and domain
Deliverability tooling	Your provider’s	Dedicated IPs, warm-up; inbox placement and monitoring on Optimize
AI	Agents build workflows, write copy, send, and read the log	MCP server sends email and manages templates, lists, suppressions
Hosting	SuprSend cloud on every plan; your VPC, on-prem or BYOC on Enterprise	Mailgun cloud only, in US or EU regions
Pricing model	Per notification per channel; 10,000 free, Essentials $100 per month	Per email; 100 a day free, Basic $15 per month
Implementation	Days: Mailgun key as vendor, SDK, workflows in the dashboard	A day for a first send; weeks for the code around it
G2	4.8, 129 reviews	4.2, 321 reviews

What each actually is

Mailgun

Mailgun is Sinch’s email delivery service. It accepts a message from your code through a REST API or an SMTP relay, sends it from your verified domain on shared or dedicated IPs, and records what happened in an event log. Beside it sit Optimize for inbox placement and reputation, Validate for address checks, and Inspect for previews.

Mailgun is one of the email providers SuprSend sends through, and it bills per email with a free tier of 100 a day. What surrounds delivery is yours to build: the decision to send, the timing, every other channel, and preferences finer than an unsubscribe.

SuprSend

SuprSend is notification infrastructure for products where more than one team works on notifications. An event or an API call starts a workflow, and the workflow decides the channel, the timing, the content and the recipients. Engineers integrate once; product and growth build and change workflows, templates, lists and broadcasts from the dashboard or through an agent.

SuprSend delivers no email on its own. It sends the email step through your Mailgun account with your API key and domain, reads Mailgun’s delivery webhooks into its log, and can fall back to a second provider. Push, SMS, WhatsApp, an in-app inbox, Slack and Teams run through the same workflows.

Where they overlap

Email by APIBoth send from your verified domain. Under SuprSend the delivery is Mailgun’s own.

Stored templates with versionsMailgun keeps Handlebars email templates with up to 40 versions each. SuprSend keeps versioned Handlebars templates for every channel.

Lists and bulk sendsMailgun has mailing lists and batch sends with recipient variables. SuprSend builds lists from rules, warehouse SQL, CSV, the API or a CDP.

Sending in the recipient’s timezoneMailgun’s time zone optimization places a send by click data. SuprSend holds a workflow step to the user’s timezone.

Agent access over MCPBoth publish an MCP server that runs locally and works in Claude, Cursor and Windsurf.

Where Mailgun alone is enough

Price per email100 emails a day free; Basic $15 for 10,000, Foundation $35 for 50,000 and Scale $90 for 100,000 a month, with overage from $1.10 per 1,000 on Scale.

Deliverability toolingDedicated IPs and IP pools with automated warm-up, and on Optimize, inbox placement tests plus blocklist and spam trap monitoring.

Receiving emailInbound routes match incoming mail, then forward it, post it to your endpoint or store it.

An SMTP relayAny app or server that speaks SMTP can send through Mailgun with no code change.

Send time optimization and validationScale picks each recipient’s likeliest hour to open; Validate checks addresses before you send.

Ruby and PHP SDKsMailgun ships SDKs for Go, Node.js, PHP, Java, Ruby and Python, and a GitHub Actions integration.

An email-only productOne channel, logic your server already owns, and nothing beyond an unsubscribe to honour: an orchestration layer adds a bill and little else yet.

When you need SuprSend on top

The decision to send, out of your codeWho hears about what lives in a workflow product can change. With Mailgun alone the queue, the worker and the rules sit in your application, changed through a ticket.

Retries and duplicate protection before the handoffThe trigger takes an idempotency key, so a worker that dies mid-call or an event that fires twice sends once.

Content per language and per customer from one templateTranslation files and tenant variants render one template many ways. Mailgun stores 100 templates per account, and your code picks one.

Answers per workflow and per customerThe log filters by user, workflow, tenant and status for 90 days on paid plans. With Mailgun alone those numbers need its webhooks ingested and stored.

Campaigns without a scriptA marketer picks a list and sends a broadcast from the dashboard or through an agent, now or on a schedule.

More ways to triggerA product event, an API call, a schedule, a broadcast to a list, or a Segment event can each start the same workflow.

Environments and a test modeDevelopment, staging and production are on every plan, and test mode blocks real delivery. Mailgun’s test mode accepts the message and bills it.

A choice of where it runsSuprSend cloud on every plan; your VPC, on-prem or BYOC on Enterprise, with the full product and vendor support.

Who works in it

Mailgun

Engineers send through the REST API, the SMTP relay or an SDK, and own the queue, the timing, the opt-out checks and every other channel. Deliverability and operations staff work in the dashboard on domains, IPs, suppressions, templates and reports. Nobody sends a campaign from it.

Agents connect to the local Mailgun MCP server from Claude, Cursor or Windsurf and send email, manage templates, lists and suppressions, and read delivery stats.

SuprSend

Engineers integrate once through the API, a backend SDK in Python, Node, Java or Go, the CLI and MCP, and keep workflows and templates in the repo. Product and growth build workflows, lists, content and broadcasts in the dashboard, or have the built-in agent build them, with versions to roll back and a test mode.

Agents connect over MCP from Claude, ChatGPT, Claude Code or Cursor and create users, set preferences, write templates, trigger a notification, run a broadcast and read the delivery log.

Feature by feature

From both products, documentation sites and pricing pages, September 2026. Plan names mark the lowest plan that includes a feature.

How notifications are built and changed

In SuprSend a notification is a workflow and a set of templates, each with an API and a file form behind the dashboard, so it can be edited by a person, scripted, versioned and staged. In Mailgun the template is the only stored object. When to send, to whom and what else happens is code in your application.

Capability	SuprSend	Mailgun
Visual workflow builder	YES	NOSend logic is code on your server
Send a campaign from the dashboard	YESBroadcast to a list on any channel	NOThe dashboard has no send button
Templates managed by API	YESWorkflows and templates	YES, BUTTemplate API on Foundation
CLI push and pull of assets	YESWorkflows, templates, schemas, events, categories, translation files	NO
Version history and rollback	YESEvery workflow and template	PARTIALTemplates only, 40 versions each
Promotion from staging to production	YESBy CLI, from CI	NOTemplates are recreated per domain or copied to account level
MCP server for agents	YESOperates users, tenants, preferences, workflows and templates	YESLocal server; sends email and manages templates, lists, suppressions, webhooks
Headless UI components	YESInbox, preference centre, template editor	NO

Teams and scope

SuprSend is worked in by engineers, product and growth, with separate environments and a test mode between them and real users. Mailgun is worked in by engineers and the people who look after deliverability; marketing sends go through code or another tool.

Capability	SuprSend	Mailgun
Who builds send logic	Engineers, product and growth, in the dashboard, by CLI or through an agent	Engineers, in application code
Who sends campaigns	Product, growth and marketing, from the dashboard, the API or an agent	Engineers, by batch API call or script
Transactional notifications	YESEvery channel	YES, BUTEmail only
Customer engagement campaigns	YESEvery plan, every channel	PARTIALBatch email by API to a mailing list
One system across both	YESSame workflows, preferences and logs	PARTIALSame domain and log; the logic for each lives in your code
Environments	YESDevelopment, staging and production on every plan	PARTIALSandbox domain, or a separate domain or subaccount per environment
Test mode that blocks real delivery	YESIn development and staging, not billed	YES, BUTTest-mode messages are billed
Team members	Unlimited on every plan	One on Free and Basic; unlimited from Foundation

Data model and tenancy

SuprSend starts from a user: one profile holds every channel address, every device and any properties, and tenants sit above users. Mailgun starts from an email address. Mailing list members carry variables, and subaccounts split domains, IPs and keys, but a customer’s content and defaults live in your code.

Capability	SuprSend	Mailgun
User profile	YESOne user, every channel address, any JSON properties	NORecipients are addresses; users live in your database
Several addresses and devices per user	YES	NO
Lists	Rules on properties and events, warehouse SQL, CSV, API, CDP sync	Mailing lists by API or dashboard, members with JSON variables
Non-user recipients	YES, BUTObjects with their own channels and subscribers; Business	NO
Tenants	YES, BUTNested five levels; Business add-on, Enterprise	PARTIALSubaccounts with own domains, IPs and keys; usage rolls up to the primary
Per-tenant branding and templates	YES, BUTBusiness add-on, Enterprise	PARTIALAccount-level templates copied into subaccounts
Per-tenant channel and category defaults	YES, BUTBusiness add-on, Enterprise	NO
Per-tenant sending domain and provider	YES, BUTBusiness add-on, Enterprise	YESA domain or subaccount per customer

Customer engagement and marketing

Mailgun sends bulk email when your code calls it with a mailing list or a batch of recipients. SuprSend broadcasts to a list on any channel through the workflow engine. A marketing team working in the SuprSend dashboard also runs the event-driven transactional messages, such as password resets, invoices and alerts, from the same workflows, lists and logs as its campaigns.

Capability	SuprSend	Mailgun
How a list is built	Segmentation rules, scheduled warehouse SQL, CSV, API, Segment, Mixpanel, Amplitude	Members added by API or in the dashboard
List refreshes on its own	YES, BUTDynamic lists: add-on on Essentials and Business, Enterprise	NO
User properties	Any number per user, any JSON value, no schema to declare	JSON variables per mailing list member
Campaign channels	All nine, one or several per send	Email
Scheduling	One-time, scheduled, recurring; recipient’s timezone from Essentials	Delivery time up to 7 days out on plans with 7 days of storage; time zone optimization
Campaign runs through a workflow	YESCan batch, route across channels and respect preferences	NOA batch send is one message to many addresses
Transactional messages from the same dashboard	YES	NONeither kind is sent from the dashboard
Send time optimization	NO	YES, BUTSTO on Scale
Campaign analytics	YESDelivered, seen and clicked per broadcast	YESReports by tag and domain

Channels

Mailgun is an email service that sends and receives. SuprSend covers nine channels from one workflow and uses Mailgun, or another provider, for email.

Capability	SuprSend	Mailgun
Email	YESThrough Mailgun, SendGrid, SES, Postmark, Resend and others	YES
Receive inbound email	NO	YESRoutes forward, post or store incoming mail
SMS and WhatsApp	YESThrough your providers or the WhatsApp Cloud API	NO
Mobile and web push	YESDirect to FCM, APNs and browsers	NO
In-app inbox	YESEvery plan; SuprSend branding on Free	NO
Slack and MS Teams	YES	NO
Webhook	YES	NO
Fallback to another channel	YESSmart channel routing stops once the user engages	NO
Fallback to another email provider	YES, BUTEssentials	NO

Email delivery

The delivery is Mailgun’s in both setups, so domains, IPs and reputation are the same. Mailgun gives direct control of the sending infrastructure. SuprSend decides which provider and which settings each category of email uses.

Capability	SuprSend	Mailgun
Custom sending domains	Your Mailgun domains, set per vendor or per tenant	1 on Free and Basic; 1,000 from Foundation
Dedicated IPs	Your provider’s	From 50,000 a month; one included at 100,000; $59 per extra IP
SMTP relay	NOAPI and SDKs	YES
Separate provider per kind of email	YESSystem, transactional and promotional can each use their own vendor	PARTIALA domain or IP pool per stream, chosen in your code
Bounce and complaint suppression	PARTIALFailures logged per user; suppression stays in the provider	YESBounces, unsubscribes and complaints blocked automatically
Email validation	NO	YES, BUTAdd-on; 5,000 included on Scale
Inbox placement and reputation monitoring	NO	YES, BUTOptimize, a separate subscription
Open and click tracking	YESRead from Mailgun’s webhooks	YES
Data region	US by default; other regions on Enterprise	US or EU, chosen per domain

Workflows

A workflow is the logic between a trigger and a send: wait, batch, branch, pick a channel, stop. SuprSend has it as a product. Mailgun sends each message when your code asks, or at a set time, so every row below is code you write and host.

Capability	SuprSend	Mailgun
Multi-step workflows	YES	NO
Delay and wait for an event	YES	PARTIALA delivery time on one message; no wait for an event
Batching and digest	YES, BUTBusiness	NO
Branches and conditions	YESEvery plan	NO
Send in the recipient’s timezone	YES, BUTEssentials	YESTime zone optimization, from click data; sends at once when there is none
Throttle per user	YES, BUTEssentials	NO
Fetch from an API, call a webhook	YES, BUTEssentials	NO
Cancel a run in flight	YESBy run, recipient or workflow	PARTIALScheduled messages can be deleted from the queue

Templates and content

Both keep email content outside your code in Handlebars templates with versions. SuprSend’s templates cover every channel and carry translation files and tenant variants. Mailgun’s cover email, and a second language is an if block inside the template.

Capability	SuprSend	Mailgun
Content stored outside code	YES	YES, BUTFoundation
Editor per channel	YESAll nine channels	PARTIALEmail template builder
Variables and conditional content	YESHandlebars	YESHandlebars with if, unless, each, with and equal
Template limit	No published cap	100 per account or domain, 40 versions each
Translations	YES, BUTIn the template on Essentials; translation files on Business	PARTIALLanguage blocks inside one template
Version history and rollback	YES	YES
Variants by tenant	YES, BUTMulti-tenant add-on, Enterprise	PARTIALCopies per subaccount
Test send from the editor	YES	YES

Preferences

A preference is a user’s standing choice about what they hear and where. SuprSend stores it per category and channel and checks it before every send. Mailgun keeps an unsubscribe list per domain, and links that unsubscribe from a tag or a mailing list.

Capability	SuprSend	Mailgun
Preferences per category	YES, BUTBusiness	PARTIALUnsubscribe from a tag or a mailing list
Preferences per channel	YES, BUTBusiness	NOOne channel
Digest schedule chosen by the user	YES, BUTBusiness	NO
Tenant admin defaults above the user	YES, BUTMulti-tenant add-on, Enterprise	NO
Hosted page and embeddable components	YES, BUTBusiness	PARTIALUnsubscribe link and footer; no preference page
Opt-out checked on every send	YESBlocked sends are logged and not billed	YESUnsubscribed addresses are dropped for that domain, tag or list
Opt-outs shared across channels	YES	NO

Analytics and logs

Both keep a per-message log. SuprSend’s starts at the workflow, so it shows why a message was or was not sent and what the provider said. Mailgun’s starts when it receives the message and covers delivery, opens, clicks, bounces and complaints.

Capability	SuprSend	Mailgun
Per-message log	YESSearchable by user, workflow, tenant and status	YESEvent log searchable by recipient, tag, domain and event
Rendered content	YES	YES, BUTStored message kept one day on Foundation, up to 7 days on Scale
Reason a send was blocked	YESOpt-out, missing channel, failed condition	YESSuppression reason on dropped messages
Log retention	30 days Free, 90 days paid	1 day Free and Basic, 5 Foundation, 30 Scale
Reports by	Workflow, template, channel, tenant	Tag, domain, provider, device, country
Delivery across channels in one view	YES	NOEmail only
Export	Warehouse sync on Business; Datadog, New Relic on Enterprise	Webhooks; Datadog and Splunk integrations

Developer experience

Both are API-first. Mailgun’s strength is a plain send API, SMTP and six SDKs next to your own backend. SuprSend’s is everything around the send being an asset you can pull into the repo, type-check and promote.

Capability	SuprSend	Mailgun
Backend SDKs	Python, Node, Java, Go	Go, Node.js, PHP, Java, Ruby, Python
Frontend SDKs	JS, React, React Native, Flutter, iOS, Android	None; email needs no client SDK
REST API with OpenAPI spec	YES	YES
Payload validated against a schema	YESJSON schema per event	NO
TypeScript types from schemas	YESBy CLI	NO
Idempotency key	YES	NODeduplication is yours
GitHub Actions integration	NO	YES
Status page	YES	YES

AI, by what it can do

Mailgun’s AI work sits in its MCP server, which lets your own agent send email and manage the account, and in send time optimization. SuprSend’s agents build and run the notifications themselves.

Capability	SuprSend	Mailgun
Build a workflow from a description	YESSuprSend agent, in the dashboard or Slack	NO
Draft copy per channel	YES	NO
Trace why a send failed	YES	PARTIALYour agent reads bounce classification over MCP
Send a notification from a coding agent	YESOver MCP	YESEmail, over the MCP server
Manage templates, lists and opt-outs from an agent	YESPlus users, tenants, preferences and workflows	YESTemplates, mailing lists, suppressions, webhooks; no deletes
Agent inside the product or Slack	YES	NO
SDK for your own agents	YESOpenAI, LangChain, Vercel AI	NO

Security, compliance, support

Mailgun is a larger email vendor under Sinch, with SAML on Scale and a choice of US or EU region. SuprSend has SOC 2 Type II, a named support path and a choice of where it runs.

Capability	SuprSend	Mailgun
Two-factor sign-in	On every plan	On every plan
Single sign-on	Google and GitHub on every plan; SAML on Enterprise	SAML on Scale
Roles and permissions	RBAC on Enterprise	Five user roles and role-based API keys
Certifications	SOC 2 Type II, GDPR; HIPAA BAA on Enterprise	ISO, CSA and GDPR badges on mailgun.com; detail in the Sinch trust portal
Hosting	SuprSend cloud on every plan; your VPC, on-prem or BYOC on Enterprise, full product, supported	Mailgun cloud only, in US or EU regions
Support	Slack community and chat on every plan; email on paid plans; phone and a named CSM on Enterprise	Tickets on every plan; chat and phone on Scale
Uptime	99.9%; SLA on Enterprise	Guaranteed uptime SLA listed on its plan table

Pricing and implementation

Mailgun bills per email, with 100 a day free and paid plans from $15 a month. SuprSend bills per notification per channel, counts a digest as one, and does not bill sends blocked by an opt-out. With both, you pay two vendors: SuprSend for the workflow and Mailgun for delivery.

At 100,000 emails a month, Mailgun Scale is $90. The same emails through SuprSend Essentials cost $200 ($100 for the first 50,000, then 50 blocks of 1,000 at $2), and Mailgun still delivers them for its $90, so the total is $290. The cost on the Mailgun-only side is the engineering time for the queue, preferences, digests, retries and every other channel. Compare on your own event-to-notification ratio; SuprSend’s pricing page and Mailgun’s have the detail.

Capability	SuprSend	Mailgun
Billing unit	Notification per user per channel; digest counts as one	Email sent
Free	10,000 notifications a month; all channels; unlimited members	100 emails a day; one user; 1 day of logs
Entry paid	Essentials $100 per month; 50,000; $2 per extra 1,000	Basic $15 per month; 10,000; $1.80 per extra 1,000
Next tier	Business $250 per month; adds digest, preferences, objects	Foundation $35 for 50,000; Scale $90 for 100,000
Enterprise	Custom; volume discounts; monthly-tracked-user option	Custom, with deliverability services
Other costs	Your email, SMS and WhatsApp providers	Dedicated IPs $59 each; Optimize; validations
Time to first notification	Same day; Mailgun API key added as the email vendor	Same day for a first send; the queue and send logic follow

Putting SuprSend on top of Mailgun

Nothing leaves Mailgun. Your account, domains, IPs and suppressions stay where they are, and SuprSend becomes the caller. Email keeps going out from the same domain throughout, so the move can go one notification at a time.

Mailgun	SuprSend	Moves how
Account and private API key	Email vendor	Add key, domain and region; account stays
Sending domain	From address on the vendor or tenant	No DNS change
Delivery webhooks	SuprSend webhook URL	Add it for delivered, opens, clicks, complaints, failures
Send call in server code	Workflow trigger	One event or API call per product action
Template	Template with versions	Recreate in the email editor
Template variables	Event and user properties	Same Handlebars names
Mailing list	List	Export members; import by CSV or API
Unsubscribe list	User preferences	Import opt-outs; keep Mailgun suppression on
Tag	Category	Map tags to preference categories
Subaccount	Tenant	One tenant per customer, with its own vendor
Event log and reports	Stay in Mailgun; SuprSend logs beside them	No change

Inventory every place your code calls Mailgun, every template, every mailing list and every tag.

Set up SuprSend development and staging, add your Mailgun key as the email vendor, add the webhook URL, and add a second provider for fallback if you want one.

Import users with their email addresses and properties, your lists, and existing opt-outs.

Rebuild the critical notifications as workflows first: security alerts, receipts, password resets. Run them in test mode.

Switch those triggers from the Mailgun send call to a SuprSend event, one at a time, and compare the two logs for a week.

Move the rest, then add what Mailgun alone could not do: a second channel, a digest, preferences, the inbox.

Enterprise customers get migration support and a scoped plan; on other plans the Slack community and docs are the path.

FAQ

Is SuprSend a Mailgun competitor?

No. Mailgun delivers email, and SuprSend sends email through it. The two overlap on stored templates, lists and bulk sends.

The real choice is between writing the code around Mailgun yourself (the decision to send, timing, preferences, other channels, per-customer content) and using SuprSend for it.

Can SuprSend use Mailgun?

Yes. You add your Mailgun private API key, webhook signing key, domain and region as an email vendor in SuprSend, and SuprSend sends from your domain with your credentials. Your Mailgun account, IPs, suppressions and reports stay yours.

Should I use Mailgun directly or through SuprSend?

SuprSend

SuprSend, with Mailgun delivering, suits a product that also sends push, SMS or in-app messages, needs delays, digests or preferences, or wants product and growth to change notifications themselves.

Mailgun

Mailgun directly suits a product where email is the only channel, the send logic already lives on your server, and nobody outside engineering needs to change a notification.

Is SuprSend cheaper than Mailgun?

No. Using SuprSend adds a bill: Mailgun bills per email from $15 a month, and SuprSend bills per notification per channel, with 10,000 a month free and Essentials at $100 a month for 50,000. The saving is the engineering time you would spend building around Mailgun.

Does Mailgun do multi-tenancy?

SuprSend

SuprSend tenants carry their own branding, template versions, channel defaults, sending domain and inbox feed, nest five levels deep and can route through their own providers, as a Business add-on or on Enterprise.

Mailgun

Mailgun has subaccounts, each with its own domains, IPs, API keys and users, with usage rolled into the primary account. Per-customer templates are copies, and per-customer defaults are logic in your own code.

Where does each run, and can I self-host SuprSend?

SuprSend

SuprSend runs as SuprSend cloud on every plan. On Enterprise it also runs in your VPC, on-prem or as bring-your-own-cloud, with the full product and vendor support; see the self-hosting page.

Mailgun

Mailgun runs on its own cloud only, in a US or an EU region chosen per domain.

SuprSend vs Mailgun