Tuta Mail Cost Per User: Encrypted Email Pricing

Tuta Mail cost per user is among the lowest in encrypted email, and that is exactly why the pricing page is the wrong thing to budget against. Tuta bills per seat per month, with a cheaper yearly rate, and the seat is genuinely inexpensive.

But the encryption model that keeps it cheap also rules out IMAP. Every tool in your stack that reaches a mailbox over IMAP stops working the day you switch, and the work those tools were doing moves onto a person.

This page counts both halves. Tier contents and rates change, so confirm current figures on Tuta's own pricing page before you commit a budget.

The short answer: what a Tuta seat actually costs#

Tuta sells two families of plans. Personal is a free tier plus two paid tiers, Revolutionary and Legend. Business is three per-user tiers — Essential for freelancers, Advanced for teams, Unlimited for larger businesses — billed per user per month, with a yearly payment option that lowers the effective rate.

Multiply the per-user figure by headcount and by twelve and you have the invoice. Tuta charges no surcharge for a custom domain; domain support is gated by tier instead, and you pay a registrar separately for the name itself. What the invoice omits is the cost of running an email workflow without standard protocol access.

Tuta storage limits by plan, as of August 2026#

Storage is allocated per seat and is not pooled across a team, so a five-person business buys five separate quotas rather than one shared pot. Business tiers add an administration console — multiple admin roles, password and second-factor resets, sign-in-as-user, centralised billing — plus shared mailboxes, calendar sharing, a GDPR data processing agreement and a stated 99.95% SLA. Advanced and Unlimited add email templates; on the personal side, Legend adds priority email support with a one-business-day target.

Criteria that actually matter when you count cost per user#

Seat price is one input of seven. A comparison that stops there tells you Tuta is cheap — true — and leaves you to find the rest in month two.

• Seat price times headcount times twelve — the only number most comparisons show.
• Protocol access: can the tools you already run reach the mailbox themselves?
• Migration in: how mail gets from your current provider into the new one, and who does it.
• Migration out: whether you can leave without a manual copy job.
• Search behaviour: whether finding an old thread is instant or needs per-device setup.
• Storage headroom per seat, since quotas here are not shared.
• Admin overhead: provisioning, domain setup, and who resets a lost second factor.

Does Tuta support IMAP? No — and that is the biggest line item#

Tuta's position is explicit and consistent: supporting IMAP would mean sending decrypted mail to your device and storing it there unencrypted, which contradicts the promise that data stays end-to-end encrypted on your own hardware. So Tuta ships its own web, desktop and mobile apps with an encrypted local cache instead.

That is a coherent engineering decision, not an oversight. It is also a hard boundary. Tuta publishes no IMAP, POP3, SMTP, CalDAV or CardDAV endpoints for third-party clients, and no bridge application that exposes a local IMAP endpoint on your machine. IMAP is specified in RFC 9051 and is what nearly every mailbox-adjacent tool implements, so when a provider does not speak it there is no configuration that gets you there.

• Desktop clients you may already use: Outlook, Apple Mail, Thunderbird, eM Client, Mimestream.
• CRM email logging that connects over IMAP to attach threads to records.
• Help-desk and shared-inbox products that ingest a mailbox over IMAP.
• Third-party backup, archiving and e-discovery connectors.
• AI triage and drafting layers that sit on an existing mailbox — including ours.
• Anything scripted with an IMAP client library, from a nightly export to an internal notifier.

Scoring table: where the price is real and where it is a transfer#

Worked example: a five-person agency#

Take a five-person agency on a bundled suite, moving to a Tuta business tier. The invoice is simple: five seats, one tier, twelve months, at whatever rate Tuta lists that day. Against a bundled suite seat it will look like a clear saving.

Now count what the invoice omits. Migration is five separate jobs: export from the old provider, then import .eml or .mbox files through the Tuta desktop app on each machine, one mailbox at a time. Large archives make that an afternoon each.

The agency logs client threads to a CRM over IMAP. That integration ends. The replacement is a BCC address or manual logging — a few minutes a day, per person, every working day, which is not a rounding error against a cheap seat. Search adds its own tax: each person indexes their own mailbox on each device.

One item goes the other way, and it is worth saying: shared mailboxes are included on Tuta's business tiers, so a team inbox needs no third-party product bolted on. That is a real saving, and a page that only wanted to sell you something else would leave it out.

Is the Tuta free plan usable for work?#

No, on two independent grounds. The practical one: the free tier gives 1 GB of storage, no aliases, no custom domain and a single calendar. A business mailbox on your own domain is not achievable on it at all.

The contractual one is firmer. Tuta's terms state that free versions are for private customers only and that business use requires a paid version (section 4.6), and that each person may hold only one free account (section 4.7). This is not a grey area you can quietly live in.

Why is encrypted email cheaper per user than Google Workspace?#

Because you are buying one product rather than a suite. Google Workspace and Microsoft 365 bundle documents, spreadsheets, video meetings, shared drives, device management and compliance tooling into the seat. Tuta sells an encrypted mailbox with a calendar and contacts, and that is the whole scope.

A second reason is worth naming. A provider that cannot read mailbox contents cannot derive advertising or model-training value from them, so the subscription is the entire business model. That usually pushes prices up, not down — Tuta keeps the number low by keeping scope narrow. The seat-price comparison is therefore a category error: the honest version is mailbox against mailbox, plus a line for whatever you now buy to handle documents and calls.

Red flags to check before you commit#

1. 1

   Inventory your IMAP dependencies first

   List everything that touches a mailbox: CRM, help desk, backup, archiving, mail merge, scripts. Each one is dropped, replaced or done by hand after the switch. If the list is empty, Tuta's low seat price is the whole story.

2. 2

   Confirm the import path on the tier you are buying

   Import runs in the Tuta desktop app rather than the web client, and Tuta has gated import capability by plan. Check on Tuta's own page which tier includes it before you assume your migration path exists at the price you budgeted.

3. 3

   Ask how you get out, before you get in

   Export is manual, from the desktop client to .eml or .mbox. There is no IMAP sync to point at a second provider, so any future migration is a copy job with a cutover, not a gradual overlap.

4. 4

   Check storage headroom per person, not per team

   Quotas are per seat and not pooled. One archivist can need a higher tier than the other four, and you cannot lend them capacity.

5. 5

   Match the encryption to your real threat model

   Tuta encrypts contents including subject lines, but sender and recipient addresses and dates stay readable so mail can be routed. If your concern is who corresponded with whom, no mailbox provider solves that.

6. 6

   Date your quote

   Plan names, storage limits and per-user rates in this category change more than once a year. Record the date you checked and re-check at renewal.

What we'd pick and why (honest)#

Buy Tuta if your hard requirement is that the provider cannot read your mailbox — including subject lines — at the lowest credible per-seat price, and your stack has no IMAP dependency you are unwilling to drop. On that requirement Tuta is the best-value answer we know of, and nothing here is an argument against it. A solo consultant or a small team whose email tooling is simply email will pay almost no workflow tax and get real cryptographic guarantees for the money.

Do not buy Tuta if your mail is wired into other systems, if a specific desktop client is part of how your team works, or if anyone needs to reach the mailbox programmatically. Those are not preferences you talk yourself out of after the migration.

Here is where we sit, and it is not flattering to us. AI Emaily connects to Gmail, Outlook and standard IMAP mailboxes. It cannot connect to Tuta at all, because Tuta publishes no IMAP endpoint. If you choose Tuta you are also choosing not to use us, and we would rather write that plainly than imply otherwise. We build AI Emaily, which is why saying so matters.

The distinction worth drawing is between two requirements that sound identical. If the requirement is that the provider is cryptographically unable to read the mail, Tuta wins and you can stop reading. If it is that nobody trains a model on your mail and you keep control of what gets sent, that is a different problem — the one we built for. AI Emaily does not train on user mail; drafting works from a Personal Context brain and per-client profiles you set yourself, every send goes through approval, and every agent action carries undo and an audit entry, on the mailbox you already have. Our packaging, for symmetry: a 7-day free trial on Pro and Autopilot, card required, nothing charged if you cancel before day seven. There is no permanent free tier.