Skip to main content
Skip to main content
Edit this page

Overview

Overview​

BYOC (Bring Your Own Cloud) allows you to deploy ClickHouse Cloud on your own cloud infrastructure. This is useful if you have specific requirements or constraints that prevent you from using the ClickHouse Cloud managed service.

If you would like access, please contact us. Refer to our Terms of Service for additional information.

BYOC is currently only supported for AWS. You can join the wait list for GCP and Azure here.

Note

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

Glossary​

  • ClickHouse VPC: The VPC owned by ClickHouse Cloud.
  • Customer BYOC VPC: The VPC, owned by the customer's cloud account, is provisioned and managed by ClickHouse Cloud and dedicated to a ClickHouse Cloud BYOC deployment.
  • Customer VPC Other VPCs owned by the customer cloud account used for applications that need to connect to the Customer BYOC VPC.

Features​

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.
  • Console access for managing service state:
    • Supports operations such as start, stop, and terminate.
    • View services and status.
  • Backup and restore.
  • Manual vertical and horizontal scaling.
  • Idling.
  • Warehouses: Compute-Compute Separation
  • Zero Trust Network via Tailscale.
  • Monitoring:
    • The Cloud console includes built-in health dashboards for monitoring service health.
    • Prometheus scraping for centralized monitoring with Prometheus, Grafana, and Datadog. See the Prometheus documentation for setup instructions.
  • VPC Peering.
  • Integrations: See the full list on this page.
  • Secure S3.
  • AWS PrivateLink.

Planned features (currently unsupported)​

  • AWS KMS aka CMEK (customer-managed encryption keys)
  • ClickPipes for ingest
  • Autoscaling
  • MySQL interface