Email and newsletters decision

Proton Mail Plus

A competent engineer can implement a useful encrypted webmail workflow (send/receive, basic encryption, domain support) using existing open-source mail stacks, but reproducing Proton’s scale, audits, ecosystem, and brand is impractical; keep paying for those enterprise-level benefits.

Visit website
Subscription$4.99/month
Initial build80 hours
Monthly upkeep8 hours + $0
Evidence2/3 runs agree

Open-source builds that already do this

Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need — the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship.

What a replacement has to do

  • Provide end-to-end encrypted email accounts (send/receive) with web UI, support for custom domains, storage and search, and basic spam/filtering.

What it still won’t have

  • Proton’s global scale and infrastructure (100M+ users)
  • Brand trust and enterprise audits/certifications
  • Bundled ecosystem (VPN, Drive, Pass, Lumo AI) and native mobile/desktop apps
  • Independent security audits and long-term transparency/reporting

What remains hard

  • Infrastructure at scaleTrusted by over 100 million users and organizations
  • Brand trustOur transparency, open-source software, and rigorous encryption have earned Proton millions of users — and the recommendation of the United Nations.
Read the build prompt

First-year cost

Keep paying

Paying ischeaper in year one.

On cash alone, building overtakes the subscription at 2 seats.

Paid seatsseats

Money you would actually spend

Keep paying

Subscription price × seats × 12

Build it

AI build APIs + hosting

Time you would spend

What you would spend

What we assumed

The verdict above measures whether you could build it. This one is only about money.

Runnable build prompt

Not run yet
Build a minimal, self-hosted encrypted webmail service using PostgreSQL, Redis, Postfix (or Mailu), Dovecot (IMAP), and a Node.js + React webmail UI. Core features in scope: account signup/login with 2FA, send/receive via SMTP/IMAP, client-side or zero-access message encryption storage (AES per-message with server-stored encrypted keys), inbox/folders/labels, attachments (S3-compatible storage), custom domain MX setup and DNS verification, and basic spam filtering (SpamAssassin). Out of scope: mobile apps, large-scale multi-region infra, proprietary AI features, enterprise compliance certifications. Require TLS everywhere, automated backups, monitoring (Prometheus/Grafana), error handling, and unit/integration tests for auth, mail flow, and storage encryption.
How we checked5 sources · 2/3 runs agreed · evidence score 57

How the score was reached

  • Partly verdict base52
  • An open-source build was found+5
  • 5 cited sources+3
  • Hard moats found in the evidence-3
  • Evidence score57

The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time — so the same evidence always produces the same number.

How scoring works →

Cited sources · 5

Every page the run actually retrieved.

Integrity checks

What held up, and what did not.

! Price not confirmed on the page — this pricing page renders its price in the browser! 2 of 3 runs agreed; the verdict is the majority✓ Citations limited to fetched pages! 2 moats quoted from the page