The PaaS for
confidential apps.
Enclava is a deployment platform that runs your containers inside trusted execution environments (TEEs) on AMD SEV-SNP. You bring an image — we handle attestation, encrypted storage, sealed secrets, TLS, domains, and the gnarly orchestration underneath.The same workflow you have on a normal cloud, but the cloud can't see your data.
The CLI & managed cloud
Install enclava, point it at a container image, and your app is running in a hardware TEE with TLS, attested release, and encrypted volumes — in one command.
$ curl -fsSL https://raw.githubusercontent.com/enclava-labs/cap/main/scripts/install.sh | bash$ enclava deploy myapp ghcr.io/me/app:latest▸ live at https://myapp.enclava.dev
The deploy engine
The orchestration layer that makes confidential deploys work — manifest generation, attestation, encrypted storage, ingress — is open-source. Run it on your own SEV-SNP hardware, brand it, resell it. Every confidential cloud needs this layer; you don't have to build it.
- Bring your own hardwareRun on AMD SEV-SNP-capable clusters (Intel TDX planned).
- White-labelYour brand, your control plane, our engine underneath.
- Open sourceAudit it, fork it, contribute back.
Everything underneath,
handled for you.
Declarative deploys
Describe your app in one file: image, resources, volumes, domain. Push from your laptop or your CI. Same workflow whether you're shipping a web app, a database, or a background worker.
Sealed secrets
Secrets are encrypted on your machine and unsealed only inside the running TEE. They never sit in plaintext in our control plane, our database, or our logs.
Encrypted persistent volumes
Stateful workloads — databases, caches, queues — keep their data on disk, encrypted with keys only the TEE can derive. Restart, scale, migrate; the data stays sealed.
Built-in TLS & domains
Custom domains, ACME certificates, ingress — all handled. TLS terminates inside the TEE so your traffic is never decrypted on shared infrastructure.
Verifiable releases
Every deploy emits a public attestation pinning the exact image running inside the TEE (AMD SEV-SNP). Customers, auditors, or you can verify it without trusting us.
Network isolation
Pod-to-pod policies, internal-only services, egress controls. Workloads are isolated by default; you opt in to what crosses the boundary.