Skip to content

Deployment models

Compare Caution’s deployment options to choose the setup that fits your infrastructure ownership and operational control needs.

At a glance

Caution runs on AWS Nitro Enclaves and supports multiple deployment options depending on how much infrastructure ownership and operational control you want.

Use fully managed for the fastest path to production on Caution-managed infrastructure, or bring your own cloud when workloads and data must stay in your AWS account. If you want to operate the platform yourself, self-host using the Caution source code on Codeberg.

Model Hosted in Caution manages You manage
Fully managed Caution-managed infrastructure Infrastructure, enclave lifecycle, and public ingress Application code and deployment configuration
Bring your own cloud Your AWS account Builds, enclave lifecycle, and deployment orchestration in your AWS account AWS account, billing, network boundaries, and data residency
Self-host Your own environment Nothing Platform operations, infrastructure, and deployments

Fully managed

Fully managed is for teams that want Caution to host and operate deployments end-to-end. Your application runs on Caution-managed infrastructure, while you keep control of your code and deployment configuration.

Bring your own cloud

Bring your own cloud is for teams that want Caution to manage verifiable deployments in their own AWS account. Your data and workloads stay in your environment while Caution manages the enclave lifecycle within that boundary.

Self-host

Caution is fully open source, and you can self-host the platform if you want to operate deployments independently instead of using a Caution-managed path.

  • Start here if you need full platform control or want to run the system yourself.
  • Self-hosting is not part of the guided quickstart flow today.
  • See the Caution source code on Codeberg to explore the platform.

Which should you choose?

Use this decision flow if you want the shortest path to a recommendation:

flowchart LR
    A[Do workloads and data need to stay in your own AWS account?]
    A -->|Yes| B[Bring your own cloud]
    A -->|No| C[Do you want to operate the platform yourself?]
    C -->|Yes| D[Self-host]
    C -->|No| E[Fully managed]

Choose fully managed if:

  • You want to get started quickly without infrastructure setup
  • You do not have specific data residency requirements
  • You prefer Caution to handle operational concerns

Choose bring your own cloud if:

  • You want data and workloads to stay in your own AWS account
  • You need control over AWS billing and account boundaries
  • You want Caution to manage enclave operations without hosting the deployment environment
  • You have network or compliance requirements tied to customer-owned infrastructure

Choose self-host if:

  • You want to operate the platform independently
  • You want to manage your own infrastructure and platform operations
  • You do not need a guided Caution-managed setup path