> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cockroachlabs.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Continuum Cloud BYOC Overview

Cockroach Continuum Cloud supports a [Bring Your Own Cloud (BYOC) deployment model](https://www.cockroachlabs.com/product/cloud/bring-your-own-cloud/), 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](https://docs.cockroachlabs.com/docs/continuum/physical-cluster-replication.md) and [changefeeds](https://docs.cockroachlabs.com/docs/continuum/changefeed-sinks.md), and the same [availability SLA](https://docs.cockroachlabs.com/docs/continuum/editions-and-add-ons.md#editions) as a Mission Critical cluster in a Cockroach Labs account.

> [!NOTE]
>
> Host clusters and virtual clusters ([Cluster Virtualization](https://docs.cockroachlabs.com/docs/continuum/virtualization-overview.md)) are in [preview](https://docs.cockroachlabs.com/docs/continuum/feature-availability.md) and are not covered by the availability SLA.

In a Continuum Cloud organization, BYOC works as follows:

* BYOC clusters use the [Mission Critical edition](https://docs.cockroachlabs.com/docs/continuum/editions-and-add-ons.md#editions) with provisioned storage. The Standard edition and [usage-based storage](https://docs.cockroachlabs.com/docs/continuum/plenum-overview.md) are not available on BYOC.
* You choose BYOC per cluster when you [create the cluster](https://docs.cockroachlabs.com/docs/continuum/create-a-cluster.md): 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](https://docs.cockroachlabs.com/docs/continuum/virtualization-overview.md) on a BYOC cluster is in [preview](https://docs.cockroachlabs.com/docs/continuum/feature-availability.md) on AWS and GCP and is enabled on request. Refer to [Work with Virtual Clusters](https://docs.cockroachlabs.com/docs/continuum/virtual-clusters.md).

## Shared responsibility model for BYOC

In any Continuum Cloud deployment, responsibility for a successful and healthy deployment is [split between you and Cockroach Labs](https://docs.cockroachlabs.com/docs/cockroachcloud/production-checklist.md). 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:

| Area | Cockroach Labs responsibility | Customer responsibility |
| :-: | :-: | :-: |
| Uptime | Meet the [availability commitment](https://docs.cockroachlabs.com/docs/continuum/byoc-security.md#availability-commitment) for the CockroachDB cluster. Host clusters and virtual clusters are in [preview](https://docs.cockroachlabs.com/docs/continuum/feature-availability.md) and are not covered by the availability SLA | Ensure that clusters remain accessible to CRL via cross-account IAM as documented in the corresponding [deployment guide](#next-steps) |
| Deployments | Automate cluster provisioning and scaling, provide hardware best practices | Provision new cloud service accounts and grant IAM permissions for Cockroach Labs to create and manage clusters |
| Upgrades | Provide automatic minor/patch upgrades and major upgrade automation via Terraform, APIs, or the Cloud Console | Initiate [major version upgrades](https://docs.cockroachlabs.com/docs/cockroachcloud/upgrade-cockroach-version.md), [set maintenance windows](https://docs.cockroachlabs.com/docs/cockroachcloud/advanced-cluster-management.md#set-a-maintenance-window) if applicable |
| Workload | Troubleshoot problems as they pertain to cluster availability | [Size clusters](https://docs.cockroachlabs.com/docs/cockroachcloud/advanced-cluster-management.md#scale-your-cluster) to manage workload requirements, [tune performance](https://docs.cockroachlabs.com/docs/stable/performance-recipes.md), and adjust schema designs with support from Cockroach Labs |
| Backups | Initialize a default backup schedule and write to customer-owned Cloud storage, ensure backup jobs run successfully | Configure a backup schedule as needed to meet RPO/RTO requirements |
| Support | Reactively and proactively identify and resolve availability-impacting incidents | Ensure sufficient hardware is made available to prevent scaling issues, including negotiating cloud resource quotas and availability with your cloud service provider. Maintain appropriate IAM permissions at all times |
| Billing | Meter vCPUs consumed and charge for vCPU consumption at the per-minute level, at the BYOC rate on the Continuum rate card (refer to [Editions and Add-Ons](https://docs.cockroachlabs.com/docs/continuum/editions-and-add-ons.md#billing-and-metering)) | Negotiate with cloud service provider, manage infrastructure spend and discounts. Cloud resources for the cluster are provisioned in your cloud account and billed directly by your cloud provider, including any discounts or commitments you have in place |

## 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](https://docs.cockroachlabs.com/docs/continuum/byoc-architecture.md). 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](https://docs.cockroachlabs.com/docs/continuum/byoc-security.md).

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:

* [Prepare a Continuum Cloud BYOC Deployment in Amazon Web Services](https://docs.cockroachlabs.com/docs/continuum/byoc-aws-deployment.md)
* [Prepare a Continuum Cloud BYOC Deployment in Azure](https://docs.cockroachlabs.com/docs/continuum/byoc-azure-deployment.md)
* [Prepare a Continuum Cloud BYOC Deployment in Google Cloud Platform](https://docs.cockroachlabs.com/docs/continuum/byoc-gcp-deployment.md)

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:

* [Create a Cluster](https://docs.cockroachlabs.com/docs/continuum/create-a-cluster.md)
* [Plan a CockroachDB Advanced Cluster](https://docs.cockroachlabs.com/docs/cockroachcloud/plan-your-cluster-advanced.md)
* [Manage a cluster using the Cloud API](https://docs.cockroachlabs.com/docs/continuum/cloud-api.md)
* [Prepare a deployment for production](https://docs.cockroachlabs.com/docs/cockroachcloud/production-checklist.md)

For answers to common questions about BYOC deployments, refer to the [Continuum Cloud BYOC FAQ](https://docs.cockroachlabs.com/docs/continuum/byoc-faq.md).
