Self-hosted email marketing (2026)
Self-hosted email marketing means two different things stacked together: the application that writes, segments and schedules campaigns, and the mail server that actually delivers them. Self-host the first — Listmonk, Keila, Plunk and Mautic all do it well and free. Renting the second is almost always the right call, and every major cloud blocks the port you would need anyway.
- The two layers separate cleanly. The campaign app holds your list, your segments and your content, and is worth owning. The sending path is deliverability infrastructure, and owning it buys you reputation problems rather than freedom.
- This is not a preference. AWS, Google Cloud, DigitalOcean, Hetzner and Oracle all restrict outbound port 25 by default — Hetzner blocks 465 as well, and DigitalOcean blocks 465 and 587, with no documented way to ask.
- Every tool here is free and genuinely open source, and every one of them expects you to bring a sending provider. Plunk requires AWS SES outright, which is the layer split stated as a config value.
- Pick by what you send, not by stars: Listmonk for broadcasts, Keila for a polished newsletter with GDPR posture, Plunk if you already send transactional from your app, Mautic when you need real automation.
Search for self-hosted email marketing and you get two categories of software mixed together with no warning. One is the campaign application: it holds subscribers, builds segments, composes messages and schedules sends. The other is the mail server — Postal, Mailu, Mailcow, iRedMail — and none of those projects describe themselves as marketing tools. Postal calls itself a mail delivery platform for websites and web servers; Mailcow calls itself a groupware suite. Conflating the two is how people end up running an MTA they did not want, discovering the deliverability problem only after the first campaign underperforms. This page keeps the layers apart: four applications worth self-hosting, and an honest answer about the sending path underneath them.
We looked at what a two-to-ten person technical team can actually stand up and keep running: a real open-source licence verified in the repository rather than a badge, a project alive enough to trust, and a clear answer to what it does when you outgrow broadcasts. Everything was checked against each project's own repository, docs and release history in the first week of September 2026. We left out tools that are alive but aimed elsewhere — Ghost is a publishing platform whose bulk sending is locked to one provider, OpenEMM is an enterprise on-prem deployment with a distro allowlist — and we left out Mailtrain, which looks maintained in the GitHub API only because a bot pushes branches; its last release was 2021. We build fromHello, so it is listed last and held to the same standard, including where it is not ready.
- 01ListmonkAGPLv3
Best for: Teams who want to send a newsletter or a broadcast to a segment today, and then never think about the tool again.
Strengths- The lightest real option in the category: a single Go binary whose only dependency is Postgres, which means the whole thing is one process and one database to back up.
- Segmentation is raw SQL over subscriber fields and a JSONB attributes column — an advantage rather than a limitation for a technical founder, because you already know the query language.
- Bounce handling is built in rather than bolted on, with POP3 mailbox scanning, a generic webhook endpoint and provider-specific receivers, so your list cleans itself.
Watch-outs- It is a one-way broadcast manager by its own description, with no drip sequences and no journey builder. If you want a welcome series that reacts to behaviour, this is the wrong tool and no plugin fixes that.
- Everything is BYO SMTP. That is the right design, but it means the deliverability work is yours to arrange before the first send, not a feature you switch on.
- 02KeilaAGPLv3
Best for: A polished newsletter operation where European privacy posture is a first-class requirement rather than a checkbox.
Strengths- The best composition story here by some distance: a visual block editor plus Markdown, MJML, HTML and plain text, with reusable templates and content slots.
- Segmentation works two ways — a visual editor and a query language — and can target people by how they interacted with a previous campaign, which is unusual at this weight.
- The broadest sender flexibility in the roundup: bring your own SMTP, SES, Mailgun, Postmark or Sendgrid, and open and click tracking can be switched off entirely.
Watch-outs- Marketing automation is on the roadmap, not in the product. As of the September 2026 release there is no drip or journey builder, so plan around broadcasts and segments.
- It is still pre-1.0 and versioned accordingly. Development is fast and steady rather than risky, but the version number is telling you something real about API stability.
- 03PlunkAGPLv3
Best for: Developer teams already sending transactional email from their product who want marketing on the same rails and in the same codebase.
Strengths- Transactional sends, campaigns and event-triggered automations live in one TypeScript codebase you can actually read, which is a different proposition from a plugin ecosystem.
- A fast, steady release line — five minor versions between May and August 2026 — and a modern API-first shape that fits teams who would rather write code than click through an admin panel.
- It ships an official MCP server, so an agent can drive it — a useful property if you expect to hand parts of this work to software later.
Watch-outs- Self-hosting requires AWS SES specifically; the environment file lists it as required. That is the layer split written as configuration — you self-host the application and rent the sending, whether or not you meant to.
- It is 0.x software. The direction is good and the pace is real, but treat interfaces as moving.
- 04MauticGPLv3
Best for: Teams who have outgrown broadcasts and need branching lifecycle automation on infrastructure they control.
Strengths- The only mature self-hosted option here with a real visual multi-stage campaign builder alongside a contact and company data model.
- Actively invested in rather than merely alive: version 7.2 arrived in September 2026 with substantial campaign-builder work, on a steady release line.
- Free under GPLv3 with no paid core tier, community-governed, and a large plugin ecosystem for the integrations the core does not cover.
Watch-outs- The heaviest operational and learning burden of the four — PHP and Symfony on MySQL, with cron driving campaign steps, so automations run at cron latency rather than instantly.
- It is GPLv3 rather than AGPL, a real licensing difference if you plan to offer a modified version as a service.
- 05
Best for: Small teams that want the open-source platform and an AI growth team to run it — once early access opens.
Strengths- The only option here that pairs the open-source platform with eight AI specialists who set strategy, build journeys, write copy, and run experiments — you approve, edit, or auto-ship.
- A complete platform underneath rather than a chat layer over one: email, SMS, in-app, web push, ad audiences, a 16-node visual journey builder, real-time segments, GDPR consent tracking, and a first-party JS/TS SDK.
- AGPL-licensed and self-hostable on Postgres + Redis, so your customer data stays on your own infrastructure.
Watch-outs- The hosted product and the agents are in early access behind a waitlist — Listmonk, Keila, Plunk and Mautic you can run this afternoon.
- Hosted pricing is announced at general availability; self-hosting the open-source platform is free.
Common questions
Should I run my own mail server for marketing email?
Almost certainly not, and the clearest warning comes from a mail-server project rather than from us: Postal's own documentation tells you not to take running your own email platform lightly. Running an MTA means owning IP reputation, bounce and complaint handling, blocklist monitoring and TLS, none of which is what you set out to do. Self-host the campaign application, and send through a provider that does deliverability for a living.
Can I even send email from a cheap VPS?
Usually not without asking, and sometimes not at all. Outbound port 25 is restricted by default on AWS, Google Cloud, DigitalOcean, Hetzner and Oracle — AWS throttles it, the rest block it outright. AWS lifts the throttle by support request, Google may lift its block on its own risk assessment, and Hetzner blocks 465 too and gates both behind account age and payment history. DigitalOcean blocks 25, 465 and 587 on every Droplet and publishes no unblock path. Assume the port is closed and plan to relay.
What does self-hosting actually get me, then?
The valuable half. Your subscriber list, your segment definitions, your templates and your send history stay in a database you control, under a licence nobody can change on you, with no per-contact meter. What you give up by renting the sending layer is an IP address, which was never the part that made the software yours.
Which of these can do drip sequences?
Mautic and Plunk. Mautic has a full visual campaign builder with branching, and Plunk has event-triggered automations in code. Listmonk is explicitly a one-way broadcast manager, and Keila lists automations as planned rather than shipped, so if a welcome sequence is the requirement, those two are out regardless of how much you like them.
Is self-hosted email cheaper?
The software is free; the sending is not, and the operating time is not. Budget for a relay priced per message, a server, and the hours you will spend on upgrades and bounce hygiene. Self-hosting wins on ownership, control and per-contact economics at scale, not on being free.
What do I need to get right before the first campaign?
Authentication and list hygiene, both of which have their own guides here rather than a paragraph on this page. The short version: publish SPF, DKIM and DMARC before you send anything, warm the domain gradually instead of mailing your whole list on day one, and watch your complaint rate — Google asks bulk senders to stay under 0.10% and treats 0.30% as the line you must never cross.
- 01Listmonk — documentation and segmentation
- 02Keila — features and sending options
- 03Plunk — self-hosting requirements
- 04Mautic — campaign builder
- 05Postal — mail server documentation and FAQ
- 06AWS — port 25 throttling on EC2
- 07DigitalOcean — SMTP ports blocked on Droplets
- 08Google — email sender guidelines
See the platform the team runs.
- Open-source growthOpen-source, self-hostable growth means software you can read, run, and own — and customer data that lives on your infrastructure, not a vendor's. This track covers what that buys you, what it costs, and how it meets GDPR, without the myth that self-hosting alone makes you compliant.Read
- Channels & deliverabilityA customer-engagement platform is the system that reaches your customers across every channel — email, SMS, web push, and in-app — and keeps those messages landing. This track explains the channels, how they work together instead of in silos, and the deliverability and consent rules that decide whether a message is seen at all.Read
- Email deliverability for startupsDeliverability is whether your email reaches the inbox instead of the spam folder or a hard block. Three things drive it: authentication that proves you are who you say, sender reputation built over time, and list hygiene that keeps your audience engaged. Get those right and the inbox follows.Read
- SPF, DKIM, and DMARC explainedSPF, DKIM, and DMARC are three DNS-based email authentication standards: SPF lists which servers may send for your domain, DKIM signs each message so tampering shows, and DMARC ties both to your visible From: domain and tells receivers what to do when they fail. Together they prove a message is really from you.Read
- Self-hosted customer engagementA self-hosted customer-engagement platform runs on infrastructure you control — your own servers, a VPS, or your cloud account — so customer profiles, events, and messages stay in your environment instead of a vendor's multi-tenant cloud. You trade managed convenience for control and ownership.Read
- Own your customer dataOwning your customer data means it lives in a database you control — exportable, auditable, and portable — instead of locked inside a vendor's platform, so a price hike, a sunset feature, or a shutdown can't strand years of customer history behind an export wall.Read
- Braze alternatives (2026)Read the guide
- Best customer engagement platforms for small teams (2026)Read the guide
- Customer.io alternatives (2026)Read the guide
- Dittofeed alternatives (2026)Read the guide
- HubSpot alternatives (2026)Read the guide
- Klaviyo alternatives for SaaS and subscription businesses (2026)Read the guide
- Mautic alternatives (2026)Read the guide
- Best open-source customer engagement platforms (2026)Read the guide
- Best open-source marketing automation tools (2026)Read the guide
Put your growth teamon autopilot.
Early access opens gradually, so the team tunes to real use cases. Small teams with big ambitions go first.
Not ready to share an email? It's open source. Run it yourself today. View on GitHub