Best Privacy-First Email for Developers in 2026: Proton vs Infomaniak

Some links on this page are affiliate links: if you sign up through them, this site earns a commission at no extra cost to you. Prices and recommendations are not affected.

Every side project ends up needing two different things from email, and most guides only talk about one of them.

The first is a human mailbox: you@yourdomain.dev, read on a laptop and a phone, kept away from an advertising company. The second is an outbound SMTP endpoint: the thing your app authenticates against at three in the morning to send a password reset. These are not the same job, the same traffic pattern, or the same failure mode, and the moment you treat them as one you get a project whose signups silently stop working.

This is a comparison of the two privacy-first providers that are genuinely worth running a domain on in 2026, with the prices as they are billed today, the DNS records you will actually paste, and an honest line about where each one stops.

The short version

Rates checked 25 October 2026; the CHF conversion uses 1 CHF = €1.0838 from 23 October 2026. Proton publishes USD on the plan pages and converts at checkout.

What “privacy-first” actually buys you

Be precise about the threat you are paying to remove, because the two providers remove different ones.

Proton encrypts mail end to end between Proton users, and at rest with zero-access encryption for everything else. The practical consequence is the one people forget: the provider cannot read your inbox, and neither can anything you plug into it. There is no plain IMAP, because there is nothing on the server to hand over in plaintext. That is the feature. It is also the limitation.

Infomaniak does not do end-to-end encryption. It does ordinary, well-run, European-hosted mail with encryption in transit and at rest, no ad profiling, and a company that sells hosting rather than attention. For most side projects that is the real alternative to a free Gmail account, and it speaks every protocol your tooling already knows.

If your mail must be unreadable to the provider, that decision is already made for you. If what you want is to stop being the product, Infomaniak is cheaper, faster to set up, and far less likely to fight your tools.

Developer reality check: the Bridge

This is the single thing that decides the choice for most people writing code, so it goes before the price table in your head.

Proton has no IMAP server you can connect to. To use Thunderbird, Apple Mail, mutt, neomutt, aerc, or anything else that speaks the protocol, you run Proton Bridge: a local daemon that holds your keys, exposes 127.0.0.1 IMAP and SMTP, and decrypts on your machine. It works well and it has a headless mode. But it is a process that has to be running, on a machine that has to be unlocked, which means:

• Mail on a headless server through Proton means running the Bridge on that server and trusting it with the keys.
• A phone uses the Proton app, not your preferred client. There is no way around this.
• If the Bridge is not running, your client is simply offline.

Infomaniak gives you mail.infomaniak.com on 993 and 465, and your client connects. That is the whole paragraph.

Sending from your application

Both providers can send mail for an app. Neither should be your transactional mail provider. Those statements are compatible, and the distinction is where most people get burned.

Proton SMTP submission

Paid plans can generate SMTP submission tokens for custom-domain addresses. The settings:

host:     smtp.protonmail.ch
port:     587
security: STARTTLS
user:     noreply@yourdomain.dev
password: <the generated token>

Three details that are not obvious from the setup screen:

1. The token is shown once, at creation. Put it in your secret store the same minute.
2. Tokens only pair with custom-domain addresses, never with your @proton.me one.
3. Generate one token per client and per address. Revoking then costs you one integration instead of all of them.

A msmtp config, which is all a cron job or a small container needs:

account        proton
host           smtp.protonmail.ch
port           587
tls            on
tls_starttls   on
auth           on
from           noreply@yourdomain.dev
user           noreply@yourdomain.dev
passwordeval   "cat /run/secrets/smtp_token"

account default : proton

The limit nobody documents

Proton’s published limits are 50 emails an hour and 150 a day on free accounts, and for paid accounts “it depends on the reputation of your account”, with up to 100 recipients on a single message. There is no published paid ceiling.

Read that twice before you point a signup flow at it. An undocumented, reputation-shaped limit is fine for a contact form, a backup alert, or a nightly report. It is not a foundation for a product that sends onboarding mail in bursts, because the first time you hit the limit you will learn about it from your users rather than from a dashboard.

The rule worth keeping: your mailbox provider sends mail to you and as you. A transactional provider with a real API, webhooks and a bounce dashboard sends mail to your users. Pay one bill for each. The second bill is usually zero at side-project volume.

The DNS records, in full

Identical in shape for both providers, and the step people skip at the cost of a week in spam folders. Replace the selector and host values with the ones your provider shows.

; MX
yourdomain.dev.          3600  IN  MX   10 mail.provider.example.
; SPF - exactly one TXT record starting with v=spf1
yourdomain.dev.          3600  IN  TXT  "v=spf1 include:_spf.provider.example -all"
; DKIM - copy the public key your provider generates
sel._domainkey.yourdomain.dev. 3600 IN TXT "v=DKIM1; k=rsa; p=MIIBIjANBg..."
; DMARC - start at none, read the reports, then tighten
_dmarc.yourdomain.dev.   3600  IN  TXT  "v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.dev; fo=1"

Four things that cause nearly every delivery problem we have had to debug:

• Two SPF records. Only one TXT record may begin with v=spf1. A second one, usually left behind by an old provider, invalidates both. Merge them.
• -all before you are ready. Start with ~all, confirm in the DMARC reports that everything legitimate passes, then harden to -all.
• p=reject on day one. You will reject your own mail. p=none for two weeks is not timidity, it is the only way to find the sender you forgot about.
• A missing PTR when you send from your own box. Not relevant with either provider here, but it is the reason self-hosted SMTP on a VPS goes to spam. If you are tempted to run your own mail server, read Best VPS for self-hosting in 2026 first and then do it for the mailbox, not for sending.

Cost at the sizes that matter

One person, one domain. Proton Mail Plus at $3.99/month yearly gives one user, custom domain support and SMTP tokens. Infomaniak’s standalone mail service is CHF 2.29 per address per month with unlimited mail storage, or CHF 1.76 per user on kSuite Standard, which bundles two addresses and 50 GB of cloud storage. Infomaniak wins on price; Proton wins if you want the mailbox encrypted against its own operator.

A small team of five. Proton Mail Essentials is $6.99 per user per month on a yearly term, so about $420 a year, with 15 GB per user and up to 3 domains. Infomaniak kSuite Business is CHF 7.33 per user (about €7.94), halved for the first year, and brings 3 TB of cloud storage per user, which is the line item that actually changes the comparison if you were about to pay for storage anyway.

You already pay for a VPN or cloud storage. Proton Unlimited at $9.99/month yearly folds mail, 500 GB, VPN and a password manager into one bill. Against four separate subscriptions it is the cheaper answer, and that bundle, not the mail client, is the honest reason most developers end up on Proton.

What we would pick

For a private mailbox on your own domain where the provider must not be able to read it, take Proton , accept the Bridge, and use the SMTP token only for low-volume machine mail.

For everything else - a team that lives in standard clients, a project that wants cheap mailboxes and storage in one place, a mail setup that should take fifteen minutes and never be thought about again - take Infomaniak .

And whichever you choose, send your product’s mail through a transactional provider. The €2 mailbox and the 10,000-message sending tier are different purchases, and conflating them is the most expensive mistake in this entire article.

Next in this series: the full mail setup on a custom domain, from DNS to a working client, with the DMARC reports read out loud.