Zero knowledge
Encryption and decryption happen in the browser (AES-GCM, ECDH P-256, PBKDF2). The server stores no plaintext, no key, no IP address and no recipient.
// PRODUCT: EXOSEAL
Passwords and tokens end up in chats and mailboxes, where they stay forever. ExoSeal makes a secret travel exactly once: encrypted in the browser, sent as a link, read by the first person to open it, then gone for good.

// WHAT IT DOES
Encryption and decryption happen in the browser (AES-GCM, ECDH P-256, PBKDF2). The server stores no plaintext, no key, no IP address and no recipient.
A single database statement returns the secret and deletes it in the same step. Link previews from Slack, Teams or Outlook cannot use it up, because reading is a POST behind a button.
Send a customer a link with a question. They answer in the browser, without an account or any software. Only you can decrypt the reply, with a passphrase that never leaves your device.
Sign in through any OpenID Connect provider with PKCE, limited to the domains or addresses you allow. Opening a link needs no account.
Rate limits per user and per visitor, quotas, origin checks, a strict CSP and a report button on every link.
.NET 10 backend, Next.js frontend, PostgreSQL and Valkey, all in Docker. Few moving parts that you can actually understand.
// HOW IT WORKS
Browsers never send the part of a link after the # to a server. That is exactly where the key lives.
What an ExoSeal link looks like
exoseal.de/s/7Hq2xVbN#kT9mW3pLr8Zq…
What the server sees
exoseal.de/s/7Hq2xVbN (ID)
Stays in the browser, never sent
#kT9mW3pLr8Zq… (key)
Your browser encrypts the secret with a random key and sends only the ciphertext to the server.
The link is the address, an ID and the key behind the #. You send it through the channel of your choice.
The recipient opens the link, their browser fetches the ciphertext, the server deletes it in the same step and the browser decrypts locally.
// REQUEST LINK
Collect credentials from customers without asking them to install or register anything. The customer sees your question and a field for the reply. You read it once, in your own browser, after entering your passphrase.
// WHAT IT LOOKS LIKE




// LIMITS
A security tool should state its own limits. The long version is in the threat model.
// RUN IT YOURSELF
Every organisation runs its own instance with its own login and allowlist. You need a server with Docker, a domain with HTTPS and an OpenID Connect provider such as Google Workspace, Microsoft Entra, Keycloak or Zoho. Ready-made images exist for amd64 and arm64.
License: GNU AGPL-3.0. If you run a modified version as a public service, you must offer the source of your version. The name and logo are not covered by the license.
Setup guide on GitHub// QUESTIONS
// QUESTIONS?
Write to us if you want to use ExoSeal or something is unclear. We reply within one business day.