SEAL Documentation

Every client speaks the same wire format, so a seal created anywhere opens everywhere. Pick your surface.

All encryption is client-side (AES-256-GCM); the SEAL backend stores ciphertext only. The link key travels in the URL fragment, or, for a link sealed to an address, wrapped to that address on the server.

Get started

GuidesOne task at a time: a file for one download, a document under NDA, a large file, a key for an agent and more.

For Humans

Web appseal.net itself: creating a seal, access rules, the NDA, the owner page, the access log and its export, revoking, paying for more room.TelegramFull flow as chat commands with @Sealnetbot, plus the Mini App.SlackFiles in a direct message with the bot, /seal commands for the rest.

For AI Agents

MCPGive Claude, Cursor or Cline secure file sharing. The link goes to you, not into the chat.AGENTS.mdLines for your AGENTS.md or CLAUDE.md, so coding agents move files and secrets through SEAL, not the chat.

Developers

CLIOne-line install; send, receive and manage seals from any terminal or CI.SDKnpm install sealnet: E2EE sends from your website or Node.js server.

Reference

HTTP APIThe public send surface behind every client, for anything we do not ship.ProtocolThe formats, links and HTTP flows with test vectors, for anyone writing a client of their own.