Google is one of the few clouds where "confidential GPU" means what it says: Intel TDX on the CPU, NVIDIA Confidential Computing on an H100, generally available. That makes an honest comparison possible. Same architecture on both sides, Intel TDX plus NVIDIA Confidential Computing; different operator, different GPUs in confidential mode, different billing, and a different answer to "can I check this myself".
Google’s supported configurations table lists Confidential VM with GPUs on two machine series, both generally available on 12 September 2026. A3 High runs Intel Sapphire Rapids with Intel TDX and attaches NVIDIA H100 80GB GPUs, in three zones: europe-west4-c, us-central1-a and us-east5-a; these instances do not support reservations. G4 runs AMD EPYC Turin with AMD SEV and attaches NVIDIA RTX PRO 6000 GPUs, across many more zones. Google documents NVIDIA Confidential Computing together with Intel TDX on A3 High, and its own attestation service for Confidential VMs. No confidential H200 or B200 configuration appears in the table.
We could not verify a confidential-specific H100 price on a primary Google page, so this comparison does not print one; Google publishes per-GPU and per-machine rates by zone on its GPU pricing page and in its calculator.
| Criterion | VoltageGPU | Google Cloud A3 High |
|---|---|---|
| CPU trusted execution environment | Intel TDX trust domain on every tier | Intel TDX on Intel Sapphire Rapids (A3 High); AMD SEV on AMD EPYC Turin for the G4 series |
| GPUs in confidential mode | Single-GPU H200 VM; 8x H100 and 8x H200 nodes; RTX 6000B VM; H100, H200 and B200 containers | NVIDIA H100 80GB on A3 High; NVIDIA RTX PRO 6000 on G4 |
| NVIDIA Confidential Computing | CC State ON on the single-GPU H200 VM (NVIDIA attestation verified by us on 4 Sept 2026). 8-GPU nodes run NVIDIA Protected PCIe mode: all eight H100 attested on 10 Sept 2026, NVSwitch not attested, 8x H200 not yet run. RTX 6000B VM: GPU CC off. Containers: no tenant-side GPU attestation. | NVIDIA Confidential Computing with Intel TDX on A3 High (Google documentation) |
| Attestation root | Intel SGX Root CA (DCAP) for the TDX quote, NVIDIA NRAS for the GPU report | Intel-rooted TDX evidence plus NVIDIA GPU attestation; Google also offers its own attestation service |
| Tenant-side verification | Yes, from inside your VM: /dev/tdx_guest and configfs TSM, your own report_data and nonce, offline DCAP check, NVIDIA report on your nonce. voltage-verify (open source) binds both proofs to a workload manifest. | Documented by Google for Confidential VM; we have not run it on A3 High ourselves |
| H100 | $5.00/hr container; $6.95/hr single-GPU VM (attestation not yet verified on that VM) | Per-GPU H100 rate on Google's GPU pricing page, region dependent; not reproduced here because we could not verify a confidential-specific figure |
| H200 | $8.08/hr single-GPU VM (both proofs verified); $6.58/hr container; 8x H200 VM $64.62/hr | No confidential H200 configuration listed (A3 High and G4 only) |
| Regions and zones | EU jurisdiction; hardware from the sub-processors listed on the Trust Center | A3 High Confidential VM zones: europe-west4-c, us-central1-a, us-east5-a |
| Operator and jurisdiction | EU (French company, EU law); sub-processors listed on /trust/subprocessors | US company; EU zone available (europe-west4-c) under Standard Contractual Clauses |
| Billing | One hour prepaid at deploy, then per second; the unused remainder is refunded when you stop | Per-second within the hourly meter; the VM bills while allocated |
| Deployment time | About two and a half minutes to an SSH prompt, self-service since 7 September 2026 | Minutes per VM once GPU quota is granted; A3 High Confidential VMs do not support reservations |
| Compliance paperwork | GDPR Art. 28 DPA; HIPAA technical safeguards by architecture, no BAA yet (planned after SOC 2 Type I); SOC 2 not yet held | Google signs HIPAA BAAs and holds SOC 2 and ISO certifications at the platform level |
Sources, Google: Google, Confidential VM supported configurations · Google, GPUs on Compute Engine · Google, GPU pricing. VoltageGPU: the two proofs, with the raw outputs, live prices on /pricing.
Yes. On 12 September 2026 Google's supported configurations table lists Confidential VM with GPUs on two machine series, both generally available: A3 High (Intel Sapphire Rapids with Intel TDX, NVIDIA H100 80GB) in europe-west4-c, us-central1-a and us-east5-a, and G4 (AMD EPYC Turin with AMD SEV, NVIDIA RTX PRO 6000). A3 High Confidential VMs do not support reservations. No confidential H200 or B200 configuration is listed.
On the silicon, largely yes: Intel TDX on the CPU and NVIDIA Confidential Computing on a Hopper GPU, with attestation rooted at Intel and NVIDIA rather than at the cloud. The differences are the operator (Google LLC, US, versus VOLTAGE EI, France), the GPUs in confidential mode (H100 at Google; H200 single-GPU VM at VoltageGPU, with 8x H100 attested per GPU), billing (VM meter versus one hour prepaid then per second with refund), and the evidence: VoltageGPU publishes the quotes and NVIDIA tokens it generated as a tenant, plus an open-source verifier.
When your data, identity, networking and compliance paperwork already live in GCP, when you need a signed BAA or SOC 2 report from your GPU provider today, or when a Google zone is a hard requirement. VoltageGPU has no BAA yet and no SOC 2 report; it says so on its Trust Center.
Google documents Confidential VM attestation for its customers; we have not run it on A3 High ourselves and do not describe it beyond Google's page. On VoltageGPU the procedure is published with the real outputs: /dev/tdx_guest and configfs TSM in your VM, your own report_data, offline DCAP verification, NVIDIA report on your nonce, and voltage-verify to bind both to a workload manifest.
The verification procedure is public and vendor-neutral. Deploy a Confidential VM here, generate both proofs on your own nonce, and compare with what your Google zone gives you.