A Nisdos project

Email that lives in your cloud, not ours.

Your domain, unlimited addresses, encrypted at rest — and the mail itself is written straight into storage you control: your S3, your R2, your WebDAV server, even a GitHub repo. We route, verify and encrypt. You own the data.

Get early access See what you get
mx — inbound delivery
← MAIL FROM:<news@sender.com>
  spf=pass dkim=pass dmarc=pass
→ route  hello@yourdomain.com
→ encrypt  age(X25519) + zstd
→ PUT  s3://your-bucket/blobs/9f2c…e1
← 250 OK — stored in your storage,
        not on our disks

Your mail, in storage you already trust

Most providers store your mail on their infrastructure and ask you to trust them. We flip it: point a mailbox or a whole domain at storage you control, and that's where every message lives — content‑addressed, compressed, encrypted.

  • Amazon S3
  • Cloudflare R2
  • DigitalOcean Spaces
  • Backblaze B2
  • Wasabi
  • Storj
  • Scaleway
  • MinIO
  • Nextcloud
  • ownCloud
  • Synology
  • a GitHub repo

…or any other S3‑ or WebDAV‑compatible service — SwissDisk, Hetzner, Google Cloud, and more.

Data residency by construction: pick the bucket, pick the region, satisfy the mandate. Leaving? Your mail is already in your account.

Privacy, stated honestly

Encryption is a per‑mailbox choice, and we only claim what each tier actually delivers.

None

optional

Plaintext at rest, for maximum convenience and compatibility. Your call — some mailboxes just don't need more.

Server custody

default today

Encrypted at rest with per‑mailbox keys your storage provider never sees — your bucket holds only ciphertext, and even the credentials to it are sealed in our database. We hold the keys to operate your mailbox; we say so plainly.

Device custody

in beta

Keys generated in your browser and never sent anywhere. Enrolling erases our copy of the mailbox key — from that moment, not even we can read your stored mail. Webmail today; IMAP bridge and key recovery are on the way.

Sovereignty you can actually specify

“Where does my mail live?” is really three questions — and most providers answer none of them. We let you answer all three, then arrange storage to match.

Region

Where the bytes physically sit

Pick the datacenter country — Germany, Switzerland, the US, Singapore, or your own rack. Data residency is satisfied by construction, not by a promise in a policy page.

Jurisdiction

Whose laws can reach it

Region isn't jurisdiction. A US‑owned provider's EU region can still be compelled under the CLOUD Act. Choose storage held by a company incorporated where you want the law to stop.

Operator

Who holds the infrastructure

Down to the operating company: EU‑owned, Swiss‑owned, state‑owned, or a bucket in an account only you hold the keys to.

Have a residency or jurisdiction mandate? Tell us the requirement — we'll design the storage around it.

Talk to us about requirements
Unlimiteddomains
Unlimitedusers & aliases
Unlimitedstorage — because it's yours

Fair‑use terms apply.

What you get

No upsells, no per‑seat surprises. The core product is the product.

01

Your domain, done right

We take care of DNS records (MX, SPF, DMARC, DKIM). We verify them live for your mail. We monitor your domain reputation.

02

Bring your own storage

Link any S3/WebDAV/GitHub‑compatible storage or repo, per domain or per mailbox. Your provider, your region, your quota.

03

Encrypted at rest

Every message is compressed and encrypted with a per‑mailbox key before it touches storage. You have an option to transfer keys custody to yourself.

04

Webmail that respects you

HTML mail runs sandboxed behind three independent layers. Remote images are off until you opt in, tracking links are flagged, and your browser never talks to a sender's servers.

05

Search like you think

Full‑text search with the operators you already know — from:, has:attachment, newer:7d, in:anywhere — plus keyboard‑first navigation and labels that work like folders.

06

Built to never lose mail

The receiving edge is stateless: it confirms delivery only after your mailbox has the message. If anything is down, the sender's own queue retries — standard SMTP, no silent drops.

Early access

We're onboarding developers, prosumers and small technical teams now. Bring a domain — and, if you like, a bucket. Early users set the roadmap.

Sign up