Seal it. Send it. Own it.

File and secret transfer you can verify. For people and AI agents, anywhere.

How it works.

DROP

Drag any files or a folder into the seal. No sign-up and no account.

ENCRYPT

AES-256-GCM encryption runs in your browser. The server never sees plaintext.

SHARE

Get a self-destructing link with expiry, passwords, and download limits.

For AI agents.

The same seals, for the agents you work with: large files and keys move between people and agents encrypted on the sending device, no key is pasted into the chat, and the SEAL server reads none of it.

AGENT TO PERSON

An agent seals a large file for you and it arrives in your SEAL inbox; before you connect one, the link goes to your clipboard. It opens in any browser, with no account.

PERSON TO AGENT

An agent asks for a key or a folder. You answer on a seal.net page that opens in your browser, and it gets a file path, not the value.

AGENT TO AGENT

A link sealed to another agent’s address opens only for that agent. A leaked copy is useless to anyone else.

One seal. Every platform.

Cute name. Unbreakable math.

One-line install for people, scripts and agents with a terminal: macOS, Linux, headless servers and CI.

curl -fsSL https://seal.net/install.sh | sh

Auto-detects OS / arch • verifies sha256

SEAL CLI
RUST
Rust core: key operations as a WASM file, loaded on demand
AES-256-GCM
File bytes through WebCrypto
X-WING
X25519 + ML-KEM-768 for addressed links
SHA-256
The digest of a file’s header
ED25519
Signatures

Math, not promises.

CLIENT-SIDE ENCRYPTION

Files are encrypted with AES-256-GCM in your browser before upload. The server stores only ciphertext.

ACCESS RULES

A password, an NDA signed before the first byte, one download or a set lifetime. Revoke at any moment and the ciphertext is deleted.

SIGNED ACCESS LOG

Every open and download is logged with its time and country, and each entry is signed by the SEAL server. Export the log as JSONL.