Self-Hosted Broadcast Email: What It Means, What It Costs, and When It’s the Right Call

A self-hosted broadcast email platform is software you install on your own server to send one-to-many email campaigns. The application — subscriber records, segments, templates, the queue — lives on infrastructure you control. The physical sending almost always goes through a third-party SMTP relay (Amazon SES, Postmark, SendGrid, Resend, Mailgun, or your own MTA), because running your own outbound mail server from a cold IP in 2026 is a losing fight against mailbox-provider reputation systems.

So “self-hosted” doesn’t mean “I run my own postfix on a VPS and hope Gmail accepts it.” It means: the application and the data are mine; the sending pipe is rented from someone whose job is keeping IP reputation healthy.

How it differs from SaaS, dedicated SMTP, and BYOE

Self-hosted broadcast platforms typically connect to a dedicated SMTP relay. Broadcast’s “bring your own ESP” model is exactly this: you run the application, you point it at the relay account you already pay (or one you sign up for cheaply), and the cost of large-volume sending decouples from the cost of the platform.

The four things you control when you self-host

Your sending IP and domain reputation. On a self-hosted platform with a transactional ESP, your DKIM is on your domain, your SPF includes your relay, and your sender reputation lives in your ESP account. Change platforms and the reputation comes with you.

Your subscriber data residency. The records sit in your Postgres on your host in whichever country you chose. If your DPO needs to draw a data-flow diagram, the application layer is one box, not a sub-processor list.

Your templates and rendering. No “you’ve reached the limit of your plan” surprise. No proprietary template engine you can’t export. Liquid, MJML, or raw HTML — whatever the platform supports.

Your pricing curve. This is the boring one but it’s where the budget conversation actually lives. A flat licence plus infrastructure plus per-email cost grows much more slowly than per-contact SaaS pricing.

The four things you take on

Be honest about these before deciding.

1. Deliverability operations. Bounce processing (hard vs. soft, when to suspend), complaint feedback loops, IP warm-up if you ever go to a dedicated IP. A modern self-hosted platform automates most of this through the relay; you still need to know it’s happening when something goes wrong.

2. DNS hygiene. SPF that includes your ESP, DKIM on the sending subdomain, DMARC at least at p=quarantine. Tools that help: our free DMARC tester, DMARC record generator, SPF record generator.

3. Patch cadence and uptime. You’re upgrading the platform, the OS, and the database. With Docker-based platforms this is usually a docker compose pull && docker compose up -d once a month plus a yearly OS upgrade. Real, but small.

4. Compliance paperwork. Privacy policy entries for your platform and your relay, DPA / AVV (if EU), retention windows, unsubscribe flow audit. SaaS hands you a template; you draft these for your stack. Worth a one-time hour with a lawyer.

A real infrastructure stack, with numbers

Below is the kind of stack a small-team broadcast operation actually runs in 2026. Numbers are public list prices at time of writing (May 2026); they will drift, but the order of magnitude won’t.

Host. Ubuntu 24.04 LTS on a single VPS. Hetzner CX22 (2 vCPU, 4 GB RAM, 40 GB SSD) sits at €4.59/month including VAT and is enough for tens of thousands of subscribers. Step up to CX32 (€6.95/month) once you’re past ~100k or running heavy analytics.

Application. A single Docker container running the broadcast platform plus Postgres (or a managed Postgres if you prefer separation of concerns).

SMTP relay. Pick one based on volume:

Amazon SES is the cheapest at volume by a wide margin; Postmark has the best deliverability defaults out of the box; Resend has the cleanest API. Broadcast supports all of them, and you can switch between them without reconfiguring subscriber records.

Backups. Daily Postgres dump to S3-compatible object storage. Hetzner Storage Box at €3.81/month for 1 TB is overkill but cheap.

TLS. Automatic via Let’s Encrypt. Broadcast handles this via Thruster on the host; other platforms vary.

What it actually costs, side-by-side

Three list sizes, three columns. Assume one broadcast per week to the whole list.

10,000 subscribers (~40k emails/month)

Plus a one-time licence cost for the platform if it’s not free OSS.

50,000 subscribers (~200k emails/month)

250,000 subscribers (~1M emails/month)

The crossover where self-hosted starts saving money is around 10,000 subscribers if you use SES, and around 25,000 subscribers if you use Postmark. The crossover for the non-monetary benefits (data residency, reputation portability) is wherever those start to matter to your business.

Our savings calculator does this math against your real numbers.

When self-hosted broadcast email is the wrong call

Be honest with yourself. Don’t self-host if:

• Your list is under 5,000 and you don’t have an EU compliance angle. The savings don’t yet cover one hour a month of your time on platform maintenance.
• You don’t have anyone on the team who can SSH into a server. This is not a high bar, but it’s a non-zero bar. If nobody on the team can comfortably read a Docker log, SaaS is the right call.
• You need a drag-and-drop visual editor as table-stakes. Self-hosted platforms are catching up, but Mailchimp and Beehiiv lead here. Broadcast supports rich text, HTML, and Liquid templates; if your team’s primary email author needs a Squarespace-style canvas, you’ll miss it.
• Your data is already nowhere near compliance-sensitive. A US e-commerce store with mostly US customers and no European subscribers genuinely doesn’t need to think about CLOUD Act exposure. Pick the tool that ships product fastest.

How Broadcast handles each of the four operational things

Brief, so we can be specific:

• Deliverability ops. Broadcast tracks bounces and complaints inbound from your ESP, suspends after configurable thresholds, and exposes a “suppressed” segment you can audit. Multi-domain support means you can isolate reputation across products or channels.
• DNS. Automatic DKIM key generation per channel, SPF guidance in-app, DMARC record templates. Combined with our free DMARC tester.
• Patch cadence. Docker image + version checker in-app. docker compose pull && docker compose up -d is the upgrade.
• Compliance. Self-hosted = your data, your jurisdiction. We publish a sample AVV for EU customers and the German DSGVO stack guide is the longer read.

Frequently asked

Do I need to run my own SMTP server to self-host broadcast email?

No, and we recommend against it for production. Use a transactional relay (SES, Postmark, SendGrid, Resend, Mailgun). Your self-hosted platform handles subscribers, segments, templates, and queueing; the relay handles the physical sending and IP reputation.

Can I switch ESPs without re-importing my list?

If your platform supports bring-your-own-ESP cleanly (Broadcast does), yes. You change the relay credentials, re-publish SPF / DKIM for the new ESP, and your subscriber list, segments, and history stay intact.

What hardware do I need?

For lists under ~100k subscribers, a 2 vCPU / 4 GB / 40 GB VPS is sufficient. Bigger lists or higher send frequency want 4 vCPU / 8 GB. Both Hetzner and DigitalOcean offer suitable instances at €5–15/month.

How long does setup take?

For a Docker-based platform like Broadcast, around 30 minutes including DNS propagation. We document the automatic installation flow.

Is self-hosted broadcast email GDPR / DSGVO compliant?

Self-hosting on EU infrastructure removes the structural CLOUD Act issue that affects US-controlled SaaS ESPs. It does not automatically make you compliant — you still need a privacy policy, lawful basis for processing, data retention rules, and a DPA with your relay. See EU data sovereignty for email marketers for the longer read.

Related

• Self-hosted email marketing software — 2026 comparison
• The self-hosted Mailchimp alternative
• Open-source email marketing — what’s actually maintained
• Newsletter broadcast: practical playbook
• Broadcast vs. Mailchimp