Skip to main content
Exostruction
Back to overview
Juljan Blischke4 min read

ExoSeal: Credentials That Can Only Be Read Once

ExoSeal is our open-source tool for credentials that can be read exactly once: end-to-end encrypted, self-hostable, licensed under AGPL-3.0.

ProductsExoSeal
ExoSeal: Credentials That Can Only Be Read Once

ExoSeal is our new open-source tool for sending passwords, tokens and other credentials so that they can be read exactly once. Encryption happens in your browser, and the application stores neither plaintext nor key. Whoever opens the link first reads the secret, and afterwards it is gone. We run our own instance at exoseal.de. For your team, you set ExoSeal up on your own server with your own login, see self-hosting. You can find more on the ExoSeal product page.

Why we built ExoSeal

Credentials end up in chats and mailboxes, and often stay there forever. Anyone who later gains access to a chat history or a mailbox finds them. When we build web applications for clients, we need credentials from them, and that is exactly what we use ExoSeal for ourselves. We wanted a solution that feels as simple as a link and still leaves no trace.

A secret that can only be read once cannot stay behind in a chat history.

How it works

The key sits in the part of the link after the #. Browsers never send that part to a server. This is how sending works:

  1. You enter the text, and your browser encrypts it with a random key.
  2. The application stores only the ciphertext.
  3. You send the link, which contains the address, the ID and the key.
  4. The recipient opens the link. One database statement returns the ciphertext and deletes it in the same step.
  5. The recipient's browser decrypts it with the key from the link.

Opening a link is a POST, not a GET. That is why link preview bots in chat tools do not use the secret up. For encryption, ExoSeal uses AES-GCM, ECDH P-256 and PBKDF2 in the browser.

Sometimes you do not want to send something, you want to collect it. With the request link, you send a customer a link with a question. The customer answers in their browser, with no account and no software. Only you can decrypt the answer, with a passphrase that never leaves your device. You read the answer once. If you forget the passphrase, the answer cannot be recovered. That is the flip side of this level of security.

When ExoSeal makes sense

Typical cases are an API key for a service provider, an initial password for a new account or the login for a hosting panel. In all of these, the secret should reach exactly one recipient and then stop existing. A short expiry also limits how long an unopened link stays valid at all. Once a link has done its job, it is worthless: anyone who finds it in a history later sees nothing. It remains good practice to change passwords after the handover where possible. ExoSeal does not replace a password manager, it is the safe way for the moment of handover.

What the application stores and what it does not

TopicWhat ExoSeal does
PlaintextNot stored, encryption runs in the browser
KeyNot stored, it only exists in the link after the #
IP addressesThe application stores none
RecipientsThe application does not know them
ReadingOne atomic database statement deletes the secret as it is returned

On top of that come rate limits per user and per visitor, quotas, origin checks, a strict Content Security Policy and a report button on every link. What ExoSeal protects and what it does not is written down honestly in the threat model.

Self-hosting

Every company runs its own ExoSeal instance, with its own login and its own allowlist. Our instance at exoseal.de is meant for our own use. ExoSeal runs with Docker and Docker Compose. You need a server, a domain with HTTPS and an OpenID Connect provider with PKCE, for example Google Workspace, Microsoft Entra or Keycloak. The allowlist decides who may create links. Recipients need no account. The backend runs on .NET 10 and the frontend on Next.js, with PostgreSQL and Valkey alongside. Ready-made images exist for amd64 and arm64, and the instructions are in the GitHub repository.

The license is AGPL-3.0: anyone who runs a modified version as a public service must offer the source code. The name and the logo are not covered by the license.

Good to know

The imprint, privacy policy and terms pages in the app are templates written for German law and have not been reviewed by a lawyer. Read them and have them checked for your situation before you go live.

The name

Exo comes from Exostruction, and Seal is the seal that can only be broken once.

Want ExoSeal set up for your team, or do you have questions? Get in touch.

Share

Author of this article

JB

Juljan Blischke

Co-Founder & Engineering

Certified application developer. Has been building web applications, APIs and internal tools for years.

This article is for general information only and does not replace individual legal, tax, or business advice. Prices, timelines, and assessments are non-binding estimates provided without guarantee.