Confidential VM
Better Security.
Less complexity.
Run Docker in a confidential VM.
Deploy existing containers into hardware-backed TEEs. Keep AI secrets private, and prove what ran.
What is TEE hardware creates an isolated runtime for your workload. the CPU or GPU runs code inside a measured boundary. that measurement covers firmware, runtime, image, and configuration. Private memory keeps operators, hosts, and cloud admins out. secrets stay in encrypted memory while apps keep running. operators can schedule the workload without reading it. attestation proof Phala turns TEE hardware into a developer primitive. proof can leave the cloud and travel with the output. verify hardware, firmware, image, and runtime before trusting the result.
01
privacy
TEE memory keeps secrets away from hosts and operators.
02
verified runtime
Attestation binds hardware, OS, VM, image, and app config.
03
public proof
Agents can attach an inspectable proof to the output.
Secure hardware paths
One runtime for CPU and GPU TEEs.
Use the same Docker deployment path for agent services, private APIs, inference workers, and GPU jobs. Phala handles the secure hardware layer and exposes proof for verification.
hardware proof rail
CPU, GPU, and runtime state stay on one verifiable path.
Intel TDXConfidential VM memory and CPU execution.
NVIDIA GPU TEEPrivate inference and GPU memory isolation.
Phala attestationProof binds hardware, image, compose, and result.CloudApplication
endpoint
app id
compose hash
Global infrastructure
Phala Cloud Worldwide Network
Distributed CVM and GPU capacity across multiple continents for low-latency confidential compute.
vCPUs
2680
17 allowed nodes
GPU devices
64
8 teepods
named regions
◎5
22 node rows
Nodes (17)
Easy to use
Vibe-code a CVM
A developer or coding agent can generate a compose file, deploy it to a CVM, seal secrets, and fetch attestation without learning TEE provisioning.
marvin@Mac ~/ai-agent % claude code
Claude Code
Opus 4.7 · xhigh effort · Phala CLI installed
docker-compose.yml
generated 01
Bring your compose file
Use the Docker Compose file you already ship with: images, ports, volumes, private registries, and multi-service apps.
Read docs
02
Seal secrets before upload
Encrypted secrets are encrypted locally before they are sent to Phala Cloud. Only the CVM TEE can decrypt them at boot.
Read docs
03
Return proof for users and agents
Attestation proves genuine TEE hardware, expected runtime state, and the exact app configuration that ran.
Read docs
What Phala handles for the CVM path.
The point is not to make teams assemble TEE primitives by hand. Phala turns private runtime, proof, deployment, and operations into one product surface.
Private runtime memory
TEE hardware protects workload memory from the host, operator, and cloud layer.
Existing Docker workflow
Bring Docker Compose, ports, volumes, environment variables, and private registries.
Encrypted secrets
Secrets are encrypted client-side and decrypted only by the CVM TEE at boot.
Attestation proof
Verify the hardware quote, runtime measurements, and compose hash.
Cloud operations
Public HTTPS endpoints, logs, updates, lifecycle controls, SDKs, and Terraform.
CPU and GPU TEEs
One confidentiality story for agent services, APIs, inference workers, and GPU jobs.
Works with the apps and infra you already run
24 integrations
GitHub
Docker
Kubernetes
OpenAI
Anthropic
Hugging Face
TensorFlow
PyTorch
LangChain
Jupyter
Databricks
Supabase
MongoDB
AWS
GCP
NVIDIA
Intel
Ethereum
Solana
Coinbase
Vercel
Next.jsPhala Cloud
dstackQuick Win Confidential VM
Phala Cloud
Managed CVM capacity, deployment workflow, endpoints, logs, updates, and attestation surfaced through one cloud dashboard.
Control Plane
Self-hosted dstack-cloud
Run the control plane on AWS, GCP, or bring-your-own hardware when the boundary, rack, or region must stay under your operation.
FAQ
Common questions
Everything you need to know about Confidential VM
What's the difference between Intel TDX and NVIDIA GPU TEE?
Intel TDX provides VM-level CPU isolation while NVIDIA GPU TEE offers hardware-secured GPU memory and compute for AI workloads.
Do I need to modify my Docker containers for TEE deployment?
No modifications needed. Your existing containers work as-is with automatic TEE security applied at infrastructure level.
How do I verify my application is running in genuine TEE?
Use attestation endpoints to get cryptographic reports signed by Intel/NVIDIA hardware proving TEE genuineness and code integrity.
What's the performance impact of memory encryption?
CPU workloads see 2-5% overhead, GPU AI/ML workloads see 5-7% overhead while maintaining hardware acceleration.
Can Phala operators access my running containers?
No. TEE hardware prevents any external access including from operators, cloud providers, or system administrators.
How does environment variable encryption work?
Variables are encrypted with TEE public keys during deployment. Only your running TEE instance can decrypt them.
What compliance standards does this meet?
SOC 2 Type I certified and HIPAA compliant, with ISO 27001 in progress. Supports GDPR and FedRAMP requirements with hardware-backed security guarantees and audit trails.
How do I debug applications running in TEE?
Standard debugging tools work through encrypted channels. Remote debugging, logging, and profiling maintain security.