Self-Hosted Email Marketing Software: What You Need to Know
The honest guide to self-hosted email marketing software and platforms — the three layers you run yourself, the open-source applications for each, the deliverability work you can't outsource, and when it's worth it versus a SaaS.
On this page · 8 sections
Overview
Self-hosted email marketing software means running the email marketing application — the platform that manages your lists, campaigns, and sending — on infrastructure you control, instead of renting an all-in-one SaaS like Mailchimp. The appeal is ownership and cost — near-cost sending at volume, your data on your servers, no per-contact pricing. The catch is that you take on the work a SaaS hides: deliverability, maintenance, and stitching the pieces together. Here's an honest map of which self-hosted email marketing platform fits and what you're actually signing up for.
The three layers you run yourself
Self-hosted email splits into three jobs. The sending layer actually delivers mail — usually an open-source app like useSend relaying through Amazon SES, because you should not run your own SMTP server (IP reputation is a full-time job). The list/campaign layer manages subscribers and sends newsletters — Listmonk, Mautic, or SendPortal. The workflow layer (a shared reply inbox, AI drafts, analytics) is the part open-source tools mostly don't cover.
The crucial honesty: "self-hosted" almost never means running the mail server itself. You self-host the application and relay delivery through SES (or similar), so you own the app and data while a provider handles IP reputation. See email marketing with your own server for why that distinction matters.
- Sending layer: useSend/SES (don't run your own SMTP)
- List + campaign layer: Listmonk, Mautic, SendPortal
- Workflow layer: reply inbox, drafts, analytics (mostly DIY)
- "Self-hosted" = host the app, relay delivery through a provider
The work you can't outsource — and when it's worth it
Whatever tool you pick, deliverability stays your job: SPF, DKIM, DMARC, domain warmup, bounce/complaint handling, and suppression. Plus updates, backups, and monitoring. A SaaS bundles all of that into its price; self-hosting trades that money for your time and attention.
It's worth it when you already run infrastructure (a VPS, Coolify, Railway), send enough volume that per-contact SaaS pricing hurts, or specifically want to own your data. It's not worth it for a non-technical team that just wants campaigns to work. A middle path: self-host the sending layer for cost and ownership, and use a focused workflow layer like Mailbase (BYO useSend at €5/mo) instead of building the inbox and campaign tooling yourself. Compare honestly in self-hosted vs SaaS email.
- Non-negotiable: SPF/DKIM/DMARC, warmup, bounces, suppression
- Plus updates, backups, monitoring — the SaaS "hidden" price
- Worth it: you run infra, send volume, or want data ownership
- Middle path: self-host sending, buy the workflow layer
Common mistakes
- Assuming “self-hosted” means plug-and-play — DNS and SES work remain.
- Forgetting the SES sandbox exit and SNS bounce/complaint wiring.
- Self-hosting the app but expecting it to fix IP reputation for you.
- Skipping the workflow layer and stitching five tools together by hand.
Sources and further reading
Official docs for current setup details, pricing, and API behavior — verify specifics there, since they change.
Related guides
More on self-hosted email marketing software and the surrounding self-hosted email workflow: