Caution is backed by Y Combinator. Learn more.

Secure hosting

Take entire classes of attacks off the table. Deploy sensitive software in minutes with a familiar Git workflow, on your infrastructureinfra or ours.Take entire classes of attacks off the table. Deploy in minutes with a familiar Git workflow, on your infra or ours.

Trusted by

Protect workloads. Verify what runs.

Encrypt data in use

Protect sensitive data during computation inside trusted execution environments (TEEs).

Detect deployment tampering

Verify production matches reviewed source and build inputs through reproducible builds.

Deploy in minutes

Deploy to confidential computing in minutes with Git, without building your own platform.

How it works

Deploy in minutes

From source to a verifiable enclave in minutes. Watch this video for a full platform walkthrough.

1

Initialize

Run caution init to create a Procfile and other data required for the application.

$ caution init
Initializing the app...
2

Deploy

Push with git push caution main. Caution builds a reproducible enclave image and provisions the TEE.

$ git push caution main
Building enclave image...
Deployed to enclave
3

Verify

Run caution verify to rebuild the image, compare hashes, and confirm exactly what the enclave is running.

$ caution verify
Collecting source code...
Rebuilding image...
Comparing hashes...
Attestation verification PASSED

Verify the layers confidential compute leaves opaque

Regular cloud

Trust the operator. Production stays a black box.

Confidential compute

Trust the hardware. The software stack still stays opaque.

  • Application
  • Runtime
  • OS / Kernel
  • Hardware / TEE
  • Compiler / Toolchain

Verifiable compute

Don't trust. Verify every layer yourself, down to the compiler.

  • Application
  • Runtime
  • OS / Kernel
  • Compiler / Toolchain
Use cases

How teams use Caution

For sensitive workloads where integrity failures would be costly—from custody and signing to confidential AI.

One workflow for secure enclaves

Caution runs across AWS Nitro today, with Intel TDX, AMD SEV-SNP, and TPM 2.0 attestations coming in 2026.

FAQs

Frequently asked questions

Caution is a verifiable compute platform that adds an extra layer of integrity guarantees on top of confidential compute. It cryptographically links the code running inside an enclave back to the reviewed source code, build inputs, and configuration that produced the enclave image, so anyone can verify what is running in production.

Caution currently supports deployments on AWS Nitro Enclaves, with additional attestation backends in active development.

No. Caution builds on top of AWS Nitro Enclaves, not instead of them. Nitro provides hardware-level isolation and attestation. Caution extends those guarantees by linking enclave measurements back to auditable source code and reproducible builds.

Book 20 minutes with one of our engineers. We’ll discuss your goals, answer technical questions, and help you get ready to deploy with Caution.

Caution offers bring-your-own-compute and fully managed deployment options. Because Caution is open source, teams can also self-host it if they want to operate deployments independently.

Compare the options in the deployment models reference.

Deploy confidential compute in minutes. Prove exactly what is running in production, from source code to live enclave.