Skip to main content
Cockroach Continuum Cloud supports a Bring Your Own Cloud (BYOC) deployment model, where a Mission Critical cluster is hosted in your own cloud account rather than in an account managed by Cockroach Labs. This model allows you to take more control of security and take advantage of existing cloud service credits or discounts.

BYOC in a Continuum Cloud organization

BYOC is available on request for Continuum Cloud organizations that are billed by invoice. To enable BYOC for your organization, contact your Cockroach Labs account team. A BYOC cluster is fully managed by Cockroach Labs in the same way as a cluster in a Cockroach Labs account. It has the same feature set, including physical cluster replication and changefeeds, and the same availability SLA as a Mission Critical cluster in a Cockroach Labs account.
Host clusters and virtual clusters (Cluster Virtualization) are in preview and are not covered by the availability SLA.
In a Continuum Cloud organization, BYOC works as follows:
  • BYOC clusters use the Mission Critical edition with provisioned storage. The Standard edition and usage-based storage are not available on BYOC.
  • You choose BYOC per cluster when you create the cluster: after choosing the Mission Critical edition, choose Bring Your Own Cloud as the deployment option and select the cloud account that you prepared. On the Clusters page, a BYOC cluster’s edition is shown as Mission Critical (BYOC).
  • An organization can run BYOC clusters and clusters in Cockroach Labs accounts side by side. Each cluster is billed at its applicable rate, and credits are shared across the organization. An organization can also be restricted so that only BYOC clusters can be created in it.
  • Cluster virtualization on a BYOC cluster is in preview on AWS and GCP and is enabled on request. Refer to Work with Virtual Clusters.

Shared responsibility model for BYOC

In any Continuum Cloud deployment, responsibility for a successful and healthy deployment is split between you and Cockroach Labs. In a BYOC deployment, all of the cluster infrastructure except the control plane lives in an account under your control, which means that you incur additional responsibilities under the shared model. The following table describes the split of responsibilities between you and Cockroach Labs in the shared responsibility model for BYOC:

Next steps

To learn how the control plane interacts with a BYOC deployment and what data leaves your cloud account, refer to CockroachDB BYOC Architecture and Data Flow. To learn about data and account security as well as the shared responsibility model in a BYOC deployment, refer to Security and Compliance in BYOC. CockroachDB supports BYOC deployments in Amazon Web Services, Microsoft Azure, and Google Cloud Platform. To prepare your cloud account for a BYOC deployment, refer to the corresponding deployment guide: Once your cloud account is prepared for a BYOC deployment, cluster configuration and management is identical to a Mission Critical cluster in a Cockroach Labs account. To learn more about Mission Critical cluster planning and management, refer to the following guides: For answers to common questions about BYOC deployments, refer to the Continuum Cloud BYOC FAQ.