Know what runs on a server

No more black boxes. Verifiable compute platform with cryptographic proof, portability, and minimal complexity.

ProblemAn enclave without verifiability is still a black box. Attestation reports a hash, not whether it matches your source. You cannot confirm what the enclave is running.

ProblemTrusting one type of hardware creates a single point of failure. All companies, including hardware manufacturers, are susceptible to a wide range of attacks.

Remove single points of failure

Reproducible stack down to the kernel

Create enclave images based on a full-source bootstrapped and fully deterministic toolchain to allow full reproduction of software.

This allows one to inspect the code used to build an image, hash it, and compare it to the hashes provided by the TEE attestation.

Learn more

Multi-hardware, multi-cloud resilience

Leverage a diverse set of TEE hardware for isolation and attestations to mitigate single points of failure.

Then leverage seamless multi-cloud workload deployments for never before seen levels of resilience. We distribute risk at the network level, why not on the hardware level?

Learn more

Fast, verifiable deployments

Replace months of custom infrastructure and security engineering with one unified workflow that runs in minutes. Deploying to a TEE has never been this fast.

$ caution init
Initializing the app...
$ git push caution main
$ caution verify
Attestation verification PASSED
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 capture the build environment and lock it for reproducible enclave builds.

$ 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

One workflow, any TEE

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

Use cases

How teams use Caution

Explore common workloads teams deploy with verifiable builds and cryptographic proof.

Frequently asked questions

Caution is a verifiable compute platform that adds an extra layer of integrity guarantees on top of AWS Nitro Enclaves. It cryptographically links the code running inside an enclave back to the reviewed source code, build, and configuration that produced it.

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.

An AWS account, a containerized application, and an alpha access code—you can request one at info@caution.co. The quick start guide walks through everything step by step.

Caution offers self-hosted, managed on-premises, and fully managed deployment options. See the pricing page for full details and comparison.

Early access is intended for evaluation and proof-of-concept deployments, not production workloads. During alpha, breaking changes may occur as we iterate on the platform. That said, you can deploy real code and experience the full verifiable compute workflow.

Reach out to us at info@caution.co to request an alpha code, then register at alpha.caution.co on desktop.

Get started for free

Try Caution for free. Self-host, or join early access for managed on‑premises and fully managed services to get verifiable compute running in minutes.