Seal files to your silicon.
Encryption that binds files to the machine that sealed them, with custody split across a t-of-n quorum. Sealed files are cryptographically useless anywhere else — and no single party, including the operator, can open them alone.
Sealed to the silicon that sealed it
Tiered binding walks Intel TDX / AMD SEV-SNP → TPM2 → machine fingerprint on the CPU path, plus NVIDIA GPU attestation. The key derives from the hardware measurement, so a copied file is noise on any other machine.
Governed by a t-of-n quorum
Custody is split across independent parties. A quorum must cooperate to open a file, and no single holder — including the operator — can unseal alone. Any party can revoke.
Recovery shards by default
Every seal writes a k-of-n recovery set, so a dead device no longer means dead data — without handing any one party a copy of the key.
Built-in remote GPU
Rent an attested H100 on demand, seal on it, and terminate. The host operator sees ciphertext and an attestation handshake, never your files.
Conditional release as a service.
The same sealing, as a REST API: data that opens only when conditions are met — a sequential time-lock matures, or a t-of-n quorum approves. Keys are bound to the serving hardware's attested tier, and every access, including every refusal, lands in a hash-chained, tamper-evident log.
- POST /v1/seal: fragment, encrypt, time-lock or quorum-lock
- Hardware-bound by default: unseal refuses below the attested-hardware floor and reports its binding tier on every response
- Sealed-bid auctions, embargoes, wills, and dead-man switches — release that math enforces, not policy
- Hash-chained audit trail — every refusal is a first-class, signed event
Built on the seven-layer SCSA core. See the platform →