Overview

[Edit this page](https://github.com/ClickHouse/clickhouse-docs/blob/main/docs/cloud/guides/infrastructure/01_deployment_options/byoc/01_overview.md)

## Overview[​](#overview "Direct link to Overview")

Bring Your Own Cloud (BYOC) empowers you to deploy ClickHouse services and store your data directly within your own cloud accounts, rather than relying on the default ClickHouse Cloud infrastructure. This approach is particularly well-suited for organizations with stringent security policies or regulatory compliance requirements that demand complete control and sovereignty over their data.

At a high level, BYOC separates the ClickHouse control plane, which runs in the ClickHouse VPC and is managed by ClickHouse Cloud, from the data plane, which runs entirely in your cloud account and contains your ClickHouse clusters, data, and backups. For a detailed view of the components involved and how traffic flows between them, see the [Architecture](/docs/cloud/reference/byoc/architecture) page.

> **If you would like access, please [contact us](https://clickhouse.com/cloud/bring-your-own-cloud).** Refer to our [Terms of Service](https://clickhouse.com/legal/agreements/terms-of-service) for additional information.

Note

BYOC is designed specifically for large-scale deployments, and requires customers to sign a committed contract.

**Supported Cloud Service Providers:**

- AWS (GA)
- GCP (GA)
- Azure (Private Preview). Please join the waitlist [here](https://clickhouse.com/cloud/bring-your-own-cloud) if you're interested.

**Supported Cloud Regions:**
All **public regions** listed in our [supported regions](https://clickhouse.com/docs/cloud/reference/supported-regions) documentation are available for BYOC deployments. Private regions aren't currently supported.

## Features[​](#features "Direct link to Features")

### Supported features[​](#supported-features "Direct link to Supported features")

- **SharedMergeTree**: ClickHouse Cloud and BYOC use the same binary and configuration. Therefore all features from ClickHouse core are supported in BYOC such as SharedMergeTree.
- **Shared Catalog**
- **Console access for managing service state**:
  - Supports operations such as start, stop, and terminate.
  - View services and status.
- **Managed backup and restore**
- **Manual vertical and horizontal scaling.**
- **Auto Idling/Wake up**
- **Warehouses**: Compute-Compute Separation
- **Zero Trust Network via Tailscale.**
- **Monitoring**:
  - Prometheus scraping for centralized monitoring with Prometheus, Grafana, and Datadog. See the [BYOC Observability](/docs/cloud/reference/byoc/observability) for setup instructions.
- **VPC Peering**
- **Secure S3**
- **[AWS PrivateLink](https://aws.amazon.com/privatelink/)**
- **[GCP Private Service Connect](https://docs.cloud.google.com/vpc/docs/private-service-connect)**
- **Integrations**: See the full list on [this page](/docs/integrations).

### Planned features (currently unsupported)[​](#planned-features-currently-unsupported "Direct link to Planned features (currently unsupported)")

The following features have limitations or are not fully supported in Bring Your Own Cloud (BYOC) deployments.

- SQL Console: The standard SQL console is not available for BYOC deployments, but is on our roadmap.
- ClickPipes Support: Currently available in private preview with streaming integrations such as Kafka, Kinesis supported. Additional integrations (CDC, object storage etc.) are on the roadmap.
- Autoscaling: On the roadmap to add to future releases.
- MySQL interface
- AWS KMS aka CMEK (customer-managed encryption keys)
- Advanced Dashboard: The client-only UI that requires your browser to have direct access and be able to connect directly to your ClickHouse server using its endpoint. If your VPC network policies restrict inbound browser access to the ClickHouse endpoint, the advanced dashboard will not function.
- Monitoring Dashboards: Currently, only memory allocation metrics are available in the monitoring dashboard. Support for additional metrics is in progress and expected to be available in a future release.

- [Overview](#overview)- [Features](#features)
    - [Supported features](#supported-features)- [Planned features (currently unsupported)](#planned-features-currently-unsupported)

Was this page helpful?