~/email-for-developers providers ↗
← home
ranking

Best self-hosted email

Open-source platforms you can run on your own infrastructure.

criteria

  1. 01

    Postal

    Self-hosted Transactional

    Most mature open-source SMTP-server replacement.

  2. 02

    mailcow

    Self-hosted

    Full Dockerized mail and groupware suite with admin UI, Postfix, Dovecot, Rspamd, and SOGo.

  3. 03

    maddy

    Self-hosted

    Compact all-in-one mail server with SMTP, MX receipt, IMAP, DKIM, SPF, DMARC, DANE, and MTA-STS.

  4. 04

    Plunk

    Self-hosted Marketing

    Unified marketing plus transactional in a single AGPL app.

  5. 05

    Listmonk

    Newsletter Self-hosted

    Single-binary newsletter manager. Bring your own SMTP.

  6. 06

    Cuttlefish

    Self-hosted Transactional

    Self-hosted transactional email dashboard around Postfix with bounce handling and analytics.

  7. 07

    Novu

    Notifications Self-hosted

    Open-source notification infrastructure with email as one channel.

  8. 08

    Ghost

    Newsletter Self-hosted

    Self-hosted publishing with built-in newsletters.

All 8 compared

Every provider in this ranking against the priorities developers picking email infrastructure weigh. Free tier and entry price sit with each pick above.

ProviderDX scoreSDKsIdempotency keysOperating sinceEvent streamBest published rate per 1,000Webhooks
Postal6/10node, ruby, phpNoNot publishedYesTiers not published in comparable formYes
mailcow7/10NoneNoNot publishedYesTiers not published in comparable formNo
maddy6/10NoneNoNot publishedNoTiers not published in comparable formNo
Plunk7/10node, pythonNoNot publishedYesTiers not published in comparable formYes
Listmonk7/10NoneNoNot publishedYesTiers not published in comparable formYes
Cuttlefish6/10NoneNoNot publishedYesTiers not published in comparable formNo
Novu8/10node, python, go, php, java, dotnetYes2021YesTiers not published in comparable formYes
Ghost7/10nodeNo2013NoTiers not published in comparable formYes

If you are developers picking email infrastructure

The question here is which one a backend engineer would rather operate. That means SDK depth in the language already in use, whether a retry can safely be replayed, how much the event log tells you when a customer says the email never arrived, and whether the pricing curve stays sane as volume grows.

The order above is the general editorial ranking. Re-sorted against developer experience, SDK breadth, and idempotency keys, the shortlist for password resets, receipts, and magic links shipped from application code becomes Novu, Postal, and Plunk. That differs from the headline order, which weighs all audiences together.

How rankings are produced →