Available nowA confidential GPU that signs what it ran.Run your job inside a confidential VM on a confidential-computing GPU: system memory, GPU memory and the link between them are all encrypted, so the host can’t read it — and the GPU signs an attestation of what ran, so you verify the result rather than trust it.Run a Private jobWhat "Private" meansEncrypted away from the host, then signedYour job runs inside a confidential VM on a GPU in confidential-computing mode. The operator of that machine — us included — cannot read it, and the hardware proves what it did.Encrypted end to endSystem memory is encrypted, the GPU’s own memory is encrypted, and the link between them is encrypted under a session the hardware negotiates. The host cannot read your prompt, your weights, or your output.The GPU signs what ranThe launch is measured and the GPU signs an attestation of the work it did — checked before a single weight or prompt is shipped to it.You verify, not trustThe result is attributable and tamper-evident: yours to verify against the hardware signature rather than take on faith. It’s also the only tier that can carry a whole payload.Turn it on per jobStep 1Choose the Private tierSet the confidentiality field to private on your request — one field moves that job onto confidential hardware.Step 2It runs on a confidential GPUOnly confidential-computing GPUs in attested VMs serve this tier. The attestation is verified before your data is ever shipped.Step 3Check the signatureVerify the hardware’s signed attestation of what ran yourself — proof, not a promise. Available now.Verify, don't trust.The Private tier is available now: confidential end to end, with a hardware signature you check yourself. Create an account and run your first Private job.Get started with Private