SEAL SDK

Three lines of code to E2EE file sharing.

Browser and Node.js ≥ 20. No account. No API key.

npm install sealnet

Or one SRI-pinned script tag, served from seal.net only

Interlocking machined brass blocks

Your app. Our math.

Users hand your product their files; what your product does next decides whether a breach is an incident or a headline. With sealnet the file is encrypted inside your app (browser or Node) before a single byte leaves it. SEAL stores ciphertext, your user gets an expiring capability link, and the decryption key travels only inside the link your app hands out: SEAL never receives it.

The whole access-rule surface is one call: ttl, otp, nda, singleUse, maxOpens, geoAllowlist, message. Progress callbacks cover encrypting, uploading and verifying; typed SealError codes carry enough detail that a failed send is never orphaned, so you can always retry or revoke.

Client-side E2EE

Encryption before upload; SEAL only ever stores ciphertext.

Full rule surface

ttl, otp, nda, singleUse, maxOpens, geoAllowlist: one options object.

SRI script tag

No bundler? One integrity-pinned tag, served from seal.net only.

send() and you are done.

  1. Install

    npm install sealnet for bundled apps, or the standalone script tag with a pinned SHA-384 digest for a plain page.

  2. seal.send({ file, ttl })

    Accepts File, Blob, ArrayBuffer or Uint8Array. Encrypts, uploads, verifies, then returns shareUrl, ownerUrl and ownerToken.

  3. Hand over the link

    The recipient opens shareUrl on seal.net. You keep ownerUrl for management and ownerToken for programmatic revocation.

open() reads a received link into a stream or onto disk, and request() asks a person for a file or a secret: the same SDK, no separate tier.

Questions, answered.

Who is this for?
Product teams whose users upload documents that carry consequences: legal tech, health tech, fintech, HR. Three lines of code and your app stops being the weakest link in the chain.
Do I need an API key?
No. Capability comes from tokens the SDK generates client-side; there is no account and nothing to rotate.
Does it work server-side?
Yes. Node.js 20+ with the same API; pass a Buffer or Uint8Array instead of a File.
What if the upload fails midway?
The thrown SealError carries sealId and ownerToken when the seal already exists remotely, so you can retry or revoke. Nothing is orphaned.
npm install sealnet

Or one SRI-pinned script tag, served from seal.net only

Read the documentation

One seal. Every platform.