Self-Hosted Email Marketing

Self-hosting email marketing means running the platform that sends your campaigns and stores your subscriber data on infrastructure you control, rather than on a SaaS vendor like Mailchimp or Beehiiv. It changes three things at once: the pricing curve, where the data physically and legally resides, and who owns your sender reputation.

This hub collects the practical guides we maintain on the topic. None of them are pitches. The cheapest broadcast tool is the one whose pricing and trust model fits your list — and that isn’t always Broadcast.

What “self-hosted” actually means

The application runs on a server you rent or own, the database sits on disks you control, and subscriber records never leave that perimeter. You typically still use a third-party SMTP relay or ESP (Amazon SES, Postmark, SendGrid, Resend) for the physical sending — that’s normal; the relay sees the outgoing email, not your subscriber list.

The three things self-hosting changes

1. Pricing curve. SaaS email tools charge by contact count. Self-hosted tools usually charge a flat licence fee plus your infrastructure costs (Hetzner / DigitalOcean / your own server, plus the ESP per-email price). The crossover where self-hosted gets cheaper is somewhere between 10,000 and 25,000 contacts depending on send frequency.

2. Data residency and legal exposure. SaaS ESPs based in the US are subject to the US CLOUD Act regardless of which region they store data in. For European companies, this isn’t theoretical — we cover the regulatory detail in EU data sovereignty for email marketers in 2026 and the German-specific stack in E-Mail-Marketing selbst hosten.

3. Sender reputation portability. On Mailchimp or similar, you share IP pools. If you self-host and use your own ESP, the reputation belongs to your domain and your ESP account — if you change platforms, your warm IPs and DKIM-aligned sender reputation come with you.

The honest catch

Self-hosting moves three problems onto your plate that SaaS handled invisibly:

  • Deliverability operations. Bounce processing, complaint feedback loops, IP warm-up. Most of this is now automated by good platforms + a competent ESP, but you should know it’s happening.
  • Patch cadence. You’re responsible for keeping the platform and the host up to date.
  • Compliance paperwork. Privacy policy, DPA (or AVV for EU), unsubscribe handling, retention windows. SaaS hands you a template; self-hosted means you draft these for your stack.

If your list is under 5,000 and none of the three things in the section above matter to you, SaaS is the correct answer. Don’t self-host for ideological reasons.

Guides in this section

Related pages

If self-hosted is the right answer for you

Broadcast runs on a single Docker container, talks to any SMTP relay or ESP, and is priced as a one-time licence plus your own infrastructure costs. The savings calculator shows the crossover for your list size.