Confidential GPUs in Intel TDX Virtual Machines
VoltageGPU rents NVIDIA H100, H200 and RTX PRO 6000 Blackwell GPUs inside Intel TDX virtual machines: $6.95 per GPU-hour for an H100, $9.00 for an H200, billed per second with no commitment. Inside the VM you generate the Intel TDX quote and the NVIDIA GPU attestation on your own nonce; our proofs page lists what they cover and what they do not.
New to the technology? Read our plain-language guide to confidential computing , what hardware enclaves are, how Intel TDX works, and why it matters for AI. Need the attestation device exposed directly to you? See the Confidential VM tier.
How it works
Upload your workload
Push your model, container, or notebook to a Confidential VM.
Inside Intel TDX
Your workload launches inside a hardware enclave: encrypted memory, GPU inside the trust domain.
Run your compute
Full GPU access, SSH, web terminal.
Verify attestation
Cryptographic proof your enclave is genuine, verifiable before and during execution.
Security Architecture
Intel TDX Enclaves
Hardware-level isolation: the hypervisor and host OS cannot access enclave memory.
AES Memory Encryption
RAM is cryptographically isolated from the hypervisor and host operating system.
GPU in Confidential Mode
GPU passed through into the Intel TDX trust domain. NVIDIA confidential computing (CC) is ON on the attested single-GPU VMs (H100, H200, RTX PRO 6000 Blackwell). 8-GPU nodes run NVIDIA's Protected PCIe mode: attested on 8x H100 (NVSwitch fabric not verified) and on 8x H200 (4 November 2026, NVSwitch attested only with libnvidia-nscq added in the guest). No Intel TEE-IO or PCIe TDISP.
Your data stays in your VM
Prompts and outputs of the models you run in your VM stay in its encrypted memory; the disk is destroyed with the machine when you release it. Security and billing logs are kept per the schedule at /legal/security.
Publicly Verifiable Attestation
Cryptographic proof the enclave is authentic before your code runs.
Compliance & Certifications
Architected to support strict regulatory requirements.
Where confidential computing runs today
The silicon our VMs run on, and two clouds that sell confidential VMs too. Microsoft Azure and Google Cloud are other providers, not partners; we compare our prices and proofs with theirs, dated and sourced.
Available Hardware
Enterprise GPUs inside Intel TDX confidential VMs.
Where GPU attestation is verified, and where it is not
Intel TDX isolates the virtual machine from the host on every confidential SKU. NVIDIA GPU attestation is a second, separate proof, and we only claim it where we have run it ourselves from inside a tenant VM. This is that list, with dates.
| SKU | Intel TDX enclave | NVIDIA GPU attestation | What we measured |
|---|---|---|---|
| RTX PRO 6000 Blackwell, single GPU VM | Yes | Verified 9 October 2026 | nvidia-smi reads CC State ON with all GPU memory protected; voltage-verify checks the TDX quote up to the Intel root and the NVIDIA tokens on the manifest nonce, offline. Evidence published with checksums. Evidence and checksums. |
| H100, single GPU VM | Yes | Verified 28 October 2026 | nvidia-smi reads CC State ON with all GPU memory protected; voltage-verify checks the TDX quote up to the Intel root and the NVIDIA tokens on the manifest nonce, offline. The earlier capture, on 16 September 2026, was GPU attestation only. Evidence and checksums. |
| H200, single GPU VM | Yes | Verified 4 September 2026 | nvidia-smi reads CC State ON, NVIDIA remote attestation successful with a nonce we chose. Evidence and checksums. |
| H100, 8 GPU node | Yes | Verified 4 November 2026 | Multi-GPU Protected PCIe mode: nvidia-smi reads CC State OFF and Multi-GPU Mode Protected PCIe, which is normal there. All 8 GPUs attested individually by NVIDIA’s remote service, first on 10 September 2026; since 4 November 2026 the TDX quote and NVIDIA tokens are bound to one manifest, verified offline. The NVSwitch is not covered by those tokens. Evidence and checksums. |
| H200, 8 GPU node | Yes | Verified 4 November 2026 | Multi-GPU Protected PCIe mode, like the 8x H100 node: all 8 GPUs attested individually by NVIDIA’s remote service, and the TDX quote and NVIDIA tokens bound to one manifest, verified offline. The NVSwitch is not covered by those tokens. Evidence and checksums. |
| B200, B300 | Yes | Not verified | Listed only when in stock, never available to date; no tenant-side attestation run, so none is claimed. |
| Standard tier | No enclave | None | Ordinary GPUs at lower prices, for work whose data is not sensitive. Never sold as confidential. |
Run the proofs yourself rather than taking this table on trust: the five steps with real outputs, or voltage-verify, our open-source checker. Before you rent, you can also check a quote or a token yourself, field by field, in your browser.
Confidential CPU Servers
AMD EPYC Linux servers for non-GPU workloads: PDF, OCR, embeddings, RAG indexing, Whisper, ETL. AMD SEV-SNP guests: you generate the attestation on your own challenge and check it on your own machine up to the AMD root, with the chain fetched from AMD. Not proven: the measurement is not compared with any reference image; the guest kernel uses VMPCK0, consistent with VMPL 0 (no SVSM), and the report's VMPL field is the level you request.
Start with confidential compute
Deploy a confidential GPU in minutes. $3.80 welcome credit, one hour on an RTX PRO 6000 Blackwell VM, with your first top-up of $10 or more; per-second billing, no subscription.
Ship faster with 30+ ready-made templates (PyTorch, SGLang, ComfyUI, OpenClaw) or follow the 5-minute quick-start guide. Unfamiliar terms? See the confidential computing glossary.