SEAL CLI

seal send file.pdf, done.

One-line install. Works on macOS, Linux, headless servers and CI.

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

Auto-detects OS / arch • verifies sha256

Solid brass industrial toggle switch

Built for pipelines, not just people.

Some files leave machines no human is sitting at: build artifacts, database dumps, incident logs. The SEAL CLI is a single static binary with deterministic exit codes and parseable output, so it drops into CI pipelines, cron jobs and headless boxes, encrypts locally with the SEAL Rust core into the format every SEAL client shares (the web, the SDK and the extension encrypt with WebCrypto), and prints share + manage links you can pipe anywhere.

Access rules are flags on the send command (TTL, password, single-use, max opens, geo allowlist, NDA), so the sealing policy lives in your script, reviewed and versioned like the rest of it.

Scriptable

Deterministic exit codes, parseable output, isolated state via SEAL_CONFIG_DIR.

Rules inline

Every access rule is a flag. No dashboard round-trip.

Rust core

AES-256-GCM, X25519 and ML-KEM-768 in one memory-safe static binary.

Install, send, own.

  1. Install in one line

    The installer detects OS and architecture and verifies the binary’s SHA-256 checksum before it touches your PATH.

  2. seal keygen, once

    Creates your local identity and prints its address and eight words: senders seal files to that address.

  3. seal send <file> --ttl 1d

    Encrypts locally, uploads ciphertext, prints the share link, the manage link and a QR.

  4. Manage from anywhere

    The same seal is visible in every client: revoke from the web, append from Telegram, list from another machine with seal import.

Full command set: send, receive, request, inbox, pair, run, doctor, list, status, files, append, share mint/list/revoke, import, keygen, revoke. Every command takes --json.

Questions, answered.

Who is this for?
Engineers and operators moving files no pipeline should leak: build artifacts, database dumps, incident logs, client deliverables. One binary, deterministic exit codes, sealed output.
Which platforms?
macOS and Linux, x86-64 and arm64, including fully headless environments and CI runners.
How do I keep CI state isolated?
Point SEAL_CONFIG_DIR at a job-scoped directory, and identity and seal history stay inside the job.
Is the install verifiable?
install.sh pins and verifies the binary’s SHA-256 before installing; the script itself is served only from seal.net.
curl -fsSL https://seal.net/install.sh | sh

Auto-detects OS / arch • verifies sha256

Read the documentation

One seal. Every platform.