Storage backed by object store
- Virtually unlimited storage
- No need to manually shard data
- Significantly lower price point for storing data, especially data that is accessed less frequently
Compute
- Automatic scaling and idling: No need to size up front, and no need to over-provision for peak use
- Automatic idling and resume: No need to have unused compute running while no one is using it
- Secure and HA by default
Administration
- Setup, monitoring, backups, and billing are performed for you.
- Cost controls are enabled by default, and can be adjusted by you through the Cloud console.
Service isolation
Network isolation
All services are isolated at the network layer.Compute isolation
All services are deployed in separate pods in their respective Kubernetes spaces, with network level isolation.Storage isolation
All services use a separate subpath of a shared bucket (AWS, GCP) or storage container (Azure). For AWS, access to storage is controlled via AWS IAM, and each IAM role is unique per service. For the Enterprise service, CMEK can be enabled to provide advanced data isolation at rest. CMEK is only supported for AWS services at this time. For GCP and Azure, services have object storage isolation (all services have their own buckets or storage container).Compute-compute separation
Compute-compute separation lets you create multiple compute node groups, each with their own service URL, that all use the same shared object storage. This allows for compute isolation of different use cases such as reads from writes, that share the same data. It also leads to more efficient resource utilization by allowing for independent scaling of the compute groups as needed.On-Demand Compute
On-Demand Compute temporarily assigns workers from a ClickHouse-managed pool to supported workloads through your existing ClickHouse Cloud service. Your service authenticates and coordinates the query, while assigned workers perform the bulk of eligible scan, join, and aggregation work outside the service’s compute. The pool is shared across ClickHouse Cloud services, but each worker serves only one service at a time. During the private preview, On-Demand Compute supports eligibleSELECT queries only. Availability is best effort, performance varies, and ClickHouse Cloud SLOs and SLAs do not apply.
Private Preview terms of service