Sealed
For the data no one may see. Not even the operator.
Sealed keeps data unreadable while a model runs on it, and issues a receipt that proves the run happened that way. Available for inference today.
What it changes
Three states of data. Sealed closes the third.
At rest
Encrypted on disk. Every cloud does this, and so does Triple X Cloud.
In transit
Encrypted on the wire between your services and your users. Standard here too.
In use
Where data is normally readable by whoever runs the machine. Sealed keeps it unreadable there as well, including to the operator.
How a Sealed run works
Four steps, one receipt.
The enclave proves itself.
Before any data arrives, the machine attests what code it is running.
The key is released to it.
Only to a machine whose attestation matches. Nowhere else.
The model runs inside.
Your prompt, your data and the answer stay unreadable outside the enclave.
A receipt is written.
What ran, where, and that it was sealed. Hand it to an auditor, not a promise. Receipt issued
Who it is for
When a contract or a regulator says no one may read it.
Governments
Records a ministry may not let an operator read.
Defense and industrial
A digital twin or controlled data that may be opened only inside machines you name.
AI and agent teams
Prompts, outputs and training data no vendor should see, and a per-action receipt for governed agents.
Merchants and fintech
Card and payment data processed without a human able to read it.
Honest limits
What Sealed is, and what it is not.
Is Sealed available for everything?
Today it is available for inference: a model running on your data. Sealed for other workloads is arranged with an engineer, not from the console.
Does Sealed replace the trust tiers?
No. Tiers decide where work runs and who may operate the capacity. Sealed decides whether anyone can read the data while it runs. Use both.
Is Sealed a certification?
No. It is a hardware boundary plus a receipt. The attestations and the patent filings behind it are described on request; nine USPTO filings are pending, not granted.
Who can see what?
You see your data. The platform sees that a run happened, how large it was and what it cost. No cloud operator or engineer can read the data in use.
Get started
Run the first Sealed workload with us.
A short call sets the model, the data and the pass mark.
- 01
Join the waitlist.
Tell us what you want to run and where. No credit card.
TakesTwo minutes
- 02
Launch a machine or a cluster.
From the console, the API or the CLI.
Takes2 to 5 minutes
- 03
Bring your own servers.
Triple X sets up your private cloud on them.
WhoTriple X
We never ask for your root credentials, API keys or bank details by email.
What to ask any provider
Questions for anyone who says the word confidential.
Ask each one, and ask for the document that answers it.
| Ask | Triple X Cloud | Where to verify |
|---|---|---|
| Is data unreadable while in use? | Yes, on AMD SEV-SNP hardware | Attestation report for your run |
| Can the operator read it? | No; it sees size, existence and cost | Security page access table |
| Does the machine prove its code first? | Yes, attestation before the key is released | Receipt for the run |
| Is there a record per run? | A receipt is issued for every Sealed run | Receipt list in your console |
| What workloads qualify today? | Inference; others arranged with an engineer | This page, pilot agreement |
| Is it a certification? | No; a hardware boundary plus a receipt | Limits section on this page |
| What does it cost? | On quote; GPU rates are not published | Written quote from Triple X |
Questions
What buyers ask before they sign.
In the order they come up. Every answer ends with where to check it.
10 answers
All questionsWhat does Sealed protect that normal encryption does not?
The third state. Every cloud encrypts data at rest and in transit. Sealed keeps data unreadable while in use, on AMD SEV-SNP hardware, so the machine running the model cannot expose your prompt, your data or the answer. A receipt is issued for every Sealed run.
Proofthe three states of data and the four steps described on this page, and the attestation report for your run.
What can I run Sealed today?
Inference: a model running on your data. Other workloads are arranged with an engineer, not from the console. Tell Triple X the model, the data and the pass mark, and the first run is set up on a short call.
Proofthe availability note on this page and the scope written into your pilot agreement.
What does a Sealed run cost?
On quote. Sealed runs on GPU capacity, and GPU rates are not on the published rate card. The quote names the capacity, its operator and the hourly rate before you sign. Storage and transfer around the run use the published rates.
Proofa written quote from Triple X, and the published storage and transfer rates, August 1, 2026.[1]
What does it cost to stop?
Nothing beyond outbound transfer from $0.01 per GB. There is no exit fee and no minimum term. Your receipts stay yours after you leave, so the audit record does not depend on staying a customer.
Proofthe no-minimum-term rule in the published pricing and the no-exit-fee clause in your contract.[1]
Who can see my data during a run?
You. Data stays unreadable while in use, on AMD SEV-SNP hardware, so the operator of the machine and the platform underneath cannot read it. They see that a run happened, how large it was and what it cost. A receipt is issued for every Sealed run.
Proofthe access table on the Security page and the receipt for each run in your console.
Where does a Sealed run happen?
On AMD SEV-SNP hardware in the region you pick, on hosted GPU capacity or on machines you name. The operator of any quoted GPU capacity is named before signature. Data stays unreadable while in use on whichever machine attests.
Proofthe operator named in your quote and the machine identity recorded in each receipt.
What is in the receipt?
What ran, where it ran, and that the enclave attested before the key was released. A receipt is issued for every Sealed run. Hand it to an auditor as a record, not a promise. The attestation format is described on request.
Proofa sample receipt from Triple X and the receipt list in your console.
What happens if the machine fails attestation?
The key is not released and the run does not start. Data stays unreadable while in use because no data arrives on hardware that did not attest. Your work is scheduled again on AMD SEV-SNP hardware that does attest, under your placement policy.
Proofstep two of the Sealed run on this page and the failover rules on the Reliability page.
Is Sealed a certification?
No. It is a hardware boundary plus a receipt. Nine USPTO filings are pending, not granted. The platform's SOC 2 Type II attestation covers the control environment, not Sealed itself. Ask for the attestation details in writing.
Proofthe limits section on this page and the SOC 2 Type II report under NDA.[2]
What do I need from my side?
A model, the data it runs on, and a pass mark you set before the first run. If a regulator or contract names the machines, bring that list. Data stays unreadable while in use; you still own the keys and the retention rules around it.
Proofthe pilot scope agreed on the first call and written into your pilot agreement.
No questions under this term yet. Ask Triple X.