Password never sent
Your account password never leaves your browser, not even when you sign up. The server keeps no conventional password hash.
Private beta · zero-knowledge
The whole mail client runs in your browser and talks to your IMAP and SMTP servers over TLS that ends on your device. Our servers only pass the encrypted traffic along and store data encrypted with keys they never have.
Works with any standard IMAP/SMTP provider. Gmail and Outlook are not supported.
AI, on your terms
Connect your own API key for Anthropic Claude or any OpenAI-compatible API, or run a model on your own computer, and ask across every mailbox at once: “Which invoices came in October?”, “Who is still waiting for my reply?”, “Draft an answer to Sarah”. You see every search it runs and every message it opens.
Which invoices came in October?
→ search_mail {"text": "invoice", "since": "2026-10-01"} ← 2 hits m1 Power company · m2 Accounting → read_mail {"id": "m1"} → read_mail {"id": "m2"}
You got 2 invoices in October: from the power company (EUR 48.20, due 31 October) and from accounting (No. 2026-118).
Zero-knowledge by design, not by policy. Everything that needs a key or sees plaintext runs on your device. Our side only relays encrypted traffic and stores encrypted data.
The mail client runs here: it opens the encrypted connection, speaks IMAP and SMTP, shows and searches your mail. Your keys are created and kept here.
Plaintext lives only herePasses encrypted traffic between your browser and your mail server. Mail ports and public servers only. It holds no keys.
Sees ciphertext onlyAny standard IMAP and SMTP server with a password or app password. Gmail and Outlook are not supported. Your mail stays where it is.
UnchangedBuilt on established, widely reviewed cryptography. No home-made algorithms.
Your account password never leaves your browser, not even when you sign up. The server keeps no conventional password hash.
Mailbox logins, settings and your AI key are encrypted in your browser before they are stored. Only your browser can decrypt them.
Keep the vault on one device and the server holds nothing, not even encrypted. The local copy of your mail is encrypted too.
A recovery key is the only way back if you forget your password. Optional two-step verification and remembered devices you can revoke.
TLS or STARTTLS, never a downgrade: if encryption fails, the connection closes before your login is sent. Self-signed certificates need your explicit trust.
Messages are cleaned and shown in a sandbox where scripts cannot run. Remote images and tracking pixels stay blocked until you allow them.
Zero-knowledge covers keys and content, not every piece of metadata. To relay your connections we still see a few things, and we would rather you know exactly which.
imap.example.com:993)All mailboxes in one list, each with its own colour. Replies go out through the mailbox the message came to.
New mail arrives as it lands while the app is open, with notifications when the tab is in the background.
Instant search in the encrypted local copy, and server-side search for the full archive.
Server settings are found from your address; manual host, port and TLS mode when you need them.
Rich text or plain, drafts saved over IMAP, undo send, attachment and missing-subject checks.
Bring-your-own-key AI with search, read and draft tools across every enabled mailbox.
The connection is: encryption runs from your browser all the way to your IMAP/SMTP server, and we only pass it along. Your mail stays at your provider as it always was; inboxhub does not add PGP-style encryption to the messages themselves. What we store (your logins, your settings) is encrypted with keys we never have.
Both push you to OAuth sign-in and restrict password access. inboxhub targets standard IMAP/SMTP with a password or an app password: Fastmail, mailbox.org, Purelymail, Migadu, self-hosted Dovecot and Postfix, and most hosting providers.
Nothing runs. All keys live in your browser, so our servers can neither fetch nor send mail for you. That also means no server-side rules or scheduled sending; use Sieve at your provider for filters.
An attacker would get encrypted data, login records and connection metadata, none of which reveal passwords or mail. The real risk for any web app is modified JavaScript served to you; that is the trust you place in us on each visit.
On our own servers in the European Union. Your mail itself stays with your provider.
Use the recovery key you saved when creating the account. Without it, nobody can decrypt your data, including us; you would connect your mailboxes again to a new account.