The Three States of Data
Every piece of data exists in one of three states. Two of them are well-protected by modern encryption. The third is the gap that confidential computing closes.
Without protection for data in use, anyone with access to the physical server, or the hypervisor running it, can potentially read the contents of memory. This includes the cloud provider, their staff, and anyone who compromises the host system.
Confidential computing closes this gap by encrypting data while it is being processed, using hardware built into the CPU itself.
What Is a Hardware Enclave?
A hardware enclave is a protected region of memory that the CPU isolates from everything else on the machine. The architecture is designed so that the operating system, hypervisor, and cloud operator do not have technical means to read it in plaintext. Only code running inside the enclave can access the data.
Intel calls these Trust Domains (TDX). AMD calls them Secure Encrypted Virtualization (SEV). The concept is the same: hardware-enforced isolation at the CPU level.
This is not a software sandbox or a container. It is physical isolation enforced by the silicon itself. The CPU generates and manages encryption keys that no software, including the operating system, can access.
Intel TDX Explained
Intel Trust Domain Extensions (TDX) is Intel's implementation of confidential computing. It creates Trust Domains, virtual machines where all memory is encrypted by the CPU using AES-256. The host operating system and hypervisor are completely removed from the trust boundary.
- AES-256 memory encryption, every byte of the Trust Domain's memory is encrypted with a unique key that only the CPU holds
- Hardware-enforced isolation, the host OS and hypervisor are removed from the trust boundary entirely
- Integrity protection, the CPU detects if enclave memory has been tampered with and halts execution
- Production-ready, shipped in 4th Gen Xeon Scalable (Sapphire Rapids) and used by Microsoft Azure, Google Cloud, and Oracle Cloud
TDX is not experimental. It shipped in 4th Gen Xeon Scalable processors (Sapphire Rapids) and is used in production by Microsoft Azure, Google Cloud, and Oracle Cloud for their confidential VM offerings.
NVIDIA Confidential Computing
Protecting the CPU is only half the equation for AI workloads. The GPU is where the actual computation happens: training, inference, and data processing. NVIDIA Confidential Computing extends the sealed boundary to the GPU.
- trust-domain GPU isolation, encrypts the bus between CPU and GPU so data cannot be intercepted in transit between processors
- GPU memory encryption, data stored in GPU HBM (high bandwidth memory) is encrypted at the hardware level
- Supported hardware, H100, H200 (Hopper architecture) and B200 (Blackwell architecture)
Combined with Intel TDX, this creates an end-to-end sealed pipeline: data is encrypted in CPU memory, encrypted in transit between CPU and GPU, and encrypted in GPU memory. At no point during the entire AI workflow is data exposed in plaintext to the infrastructure operator.
This matters because AI workloads process the most sensitive data an organization has: contracts, medical records, financial models, proprietary research. Without GPU-level confidential computing, that data would be exposed every time it moves to the GPU for processing.
How Attestation Works
Trust is not enough. You need verification. Remote attestation is the mechanism that lets you prove, cryptographically, that a hardware enclave is genuine and has not been tampered with.
Before sending any data, you can ask the CPU: “Is this enclave genuine and untampered?” The process works like this:
- The CPU generates a cryptographic measurement of the enclave's state, its code, configuration, and security properties
- This measurement is signed using hardware keys embedded by Intel at manufacturing time, keys that cannot be extracted or forged
- You (or your software) verify this signed report against Intel's public attestation service
- If verification passes, you know the enclave is genuine, running the expected code, and has not been modified
Intel, AMD, and NVIDIA all support remote attestation for their confidential computing implementations. It is the foundation of zero-trust cloud computing: verify everything, trust nothing.
Who Uses Confidential Computing
Confidential computing is not a niche technology. It is deployed in production by the largest cloud providers and adopted by regulated industries worldwide.
VoltageGPU is one of the first platforms to offer confidential GPU compute specifically for AI workloads, with Intel TDX sealed NVIDIA GPUs available per-second at a fraction of hyperscaler pricing.
Intel Confidential Computing on GPUs in 2026: Who Actually Ships It
The phrase "Intel confidential computing" covers two things in 2026: Intel TDX on the CPU, which every major cloud sells, and TDX paired with NVIDIA Confidential Computing on a GPU, which only a few do. Checked against vendor documentation on 12 September 2026:
Google Cloud runs Intel TDX with NVIDIA H100 on its A3 High Confidential VMs (generally available, three zones). Microsoft Azure sells Intel TDX confidential VMs without GPUs; its confidential GPU series, NCC H100 v5, pairs an H100 with AMD SEV-SNP instead. AWS Nitro Enclaves isolate CPU and memory only, with no GPU inside the enclave. VoltageGPU runs Intel TDX on every tier, with NVIDIA Confidential Computing verified on its single-GPU H200 VM and, per GPU, on its 8x H100 node.
The practical test is not the logo but the proof: can you, the tenant, generate the Intel TDX quote and the NVIDIA GPU report yourself, on values you chose, and verify them offline? Where that is documented with real outputs, the claim is checkable; where it is not, it is marketing.
Four clouds compared on the same criteria, with sources · How to verify a confidential GPU yourself · voltage-verify, the open-source verifier