ClickHouse Cloud Deployment Options

Though click house is an open source database, we are also in a fortunate position of having a very good, fully managed cloud service. This isn't the case for a lot of other databases, such as snowflake or redshift, which are purely cloud only.

There are four options to choose from, each with a different balance of cost, control, compliance, and operational overhead.

This article walks through what each option is, and the strengths and weaknesses of each.

The Four Deployment Options

ClickHouse Open Source - Self-Managed

• The free, open-source distribution.
• Deployed on your own infrastructure or cloud account. You pay the cloud provider directly for servers and supporting services.
• Your team are responsible for installation, configuration, scaling, upgrades, backups, monitoring, and high availability.
• Community support is available through GitHub, Slack, and forums. Commercial support is available from third parties and, in some cases, from ClickHouse Inc.

ClickHouse Cloud - Fully Managed

• Built on the open-source distribution with a small set of proprietary features added (such as SharedMergeTree and ClickPipes).
• Fully managed by ClickHouse Inc, who run the infrastructure and store the data in their own cloud accounts.
• Available on AWS, Azure, and GCP, with multiple regions on each.
• ClickHouse Inc handles provisioning, scaling, compute/storage separation, upgrades, backups, monitoring, and security patching.
• Pay-as-you-go pricing with elastic autoscaling and automatic idling. No cluster management, and the bill tracks actual usage rather than peak capacity.
• Support comes from ClickHouse Inc under SLA.

Bring Your Own Cloud - Partially Managed

• A hybrid model. ClickHouse Inc runs the control plane while the data plane runs inside your own cloud account.
• The data plane covers Kubernetes, EC2 worker nodes, S3 storage, Keeper, load balancing, IAM roles, and supporting services, all administered in your account.
• Data and backups stay in your cloud account, which addresses data residency, sovereignty, and compliance concerns.
• You pay the cloud provider directly for the underlying servers and supporting infrastructure, plus a separate consumption-based fee to ClickHouse Inc for the BYOC service.
• The BYOC control plane hosted in ClickHouse account handles scaling, upgrades, monitoring, and backups.
• It is the middle ground between the simplicity of Cloud and the control of self-managed.
• Well suited to regulated industries that want managed operations without handing over their data plane.
• Support comes from ClickHouse Inc under SLA.

ClickHouse Private - Self Managed

• A commercial package built from the proprietary Cloud version and operator.
• Aimed at large enterprises that need full control over dedicated infrastructure while still benefiting from Cloud features such as compute/storage separation.
• Typically chosen when Cloud or BYOC cannot be used due to isolation, air-gap, supplier-risk, or specific infrastructure constraints.
• Carries a heavier setup and operational overhead than BYOC.
• Support comes from ClickHouse Inc under SLA.

Strengths and Weaknesses

ClickHouse Open Source - Self-Managed

Strengths

• No licence or subscription fees. You only pay for servers and infrastructure.
• Simpler compliance. Every component and all data stays inside your environment.
• Maximum control over configuration, networking, hardware, and tuning.
• Can run in air-gapped or highly restricted environments.

Weaknesses

• Complex to run at scale. Multiple shards and replicas, Keeper coordination, and careful replication topology all need to be managed.
• Needs in-house or external expertise for sharding, rebalancing, upgrades, schema migrations, and failure recovery.
• You have responsibility for backups, DR, observability, security hardening, and capacity planning.
• ClickHouse releases often. Stable builds ship monthly and LTS builds twice a year with a year of support. Self-managing means you assess, test, and apply each one.
• Third-party support can help with diagnostics, operational advice, and upgrade planning, but those vendors do not control the ClickHouse codebase. They cannot prioritise upstream fixes, accelerate product tickets, or issue official security patches.
• Higher operational risk. Failed upgrades, replication divergence, Keeper quorum loss, missed outages, security misconfiguration, and key-person dependency all sit with your team.

ClickHouse Cloud - Fully Managed

Strengths

• Zero cluster management. ClickHouse Inc handles provisioning, scaling, replication, backups, and upgrades.
• Storage and compute are separated, enabling elastic autoscaling.
• Idle compute can spin down, so the bill tracks actual usage rather than peak capacity.
• First-party support and SLAs from the team that builds ClickHouse.
• Fast time to value. A production-ready cluster is available in minutes.
• Lower operational risk. ClickHouse Inc runs the service on a simpler shared-storage architecture, with managed patching, compliance controls, and no key-person dependency.
• Despite the subscription cost, TCO can be comparable or lower thanks to autoscaling and reduced staffing.
• Access to Cloud-exclusive features that are not available in Open Source or BYOC. These include ClickPipes, the SQL console, the ClickHouse AI Assistant, autoscaling, and customer-managed encryption keys. Roadmap items such as distributed cache and stateless workers will also land here first.

Weaknesses

• Subscription costs can exceed raw infrastructure costs for steady, predictable workloads. Cloud is typically better economically when there are bursty variable workloads.
• Data sits in ClickHouse Inc's cloud accounts, which may conflict with data residency or compliance rules.

Bring Your Own Cloud - Partially Managed

Strengths

• ClickHouse handles upgrades, monitoring, scaling, backups, and lifecycle management through the control plane.
• Data and backups stay inside your cloud account, meeting compliance, sovereignty, and audit requirements.
• Removes most of the operational burden of running a distributed cluster.
• Lower operational risk than Open Source. BYOC runs on the same Cloud architecture, including SharedMergeTree and separation of compute and storage, with failure modes handled by ClickHouse Inc rather than your team.
• A useful middle ground for regulated industries that cannot use shared SaaS but still want ClickHouse support and managed-service features.

Weaknesses

• More expensive than Cloud due to the dedicated footprint and isolation.
• Requires giving the ClickHouse control plane scoped access into your cloud account, which adds a security review.
• You still own the VPC, networking, IAM guardrails, and general cloud-account hygiene.
• Subscription fees to both the cloud provider for infrastructure and ClickHouse for software license.

Total Cost of Ownership

This section estimates the cost of each deployment option, building a total cost of ownership for self-managed Open Source, ClickHouse Cloud, and BYOC.

TCO is not just a matter of comparing license costs. A realistic comparison (see ClickHouse Cloud vs Open Source TCO) also needs to account for several factors that often shift the case towards managed offerings. For instance:

• Self-managed ClickHouse requires ongoing investment in provisioning, sharding and replica configuration, backups, monitoring, version upgrades, OS patching, network changes, and compliance coordination. These costs accumulate in enterprise environments and are routinely under-counted in business cases.
• Self-managed clusters typically run overprovisioned 24x7x365 to handle short bursts of demand. ClickHouse Cloud autoscales compute up and down, and to zero, automatically. You therefore pay for capacity actually used rather than peak capacity that might be needed.
• Replicating Cloud's elastic behaviour on self-managed ClickHouse is not free. It needs orchestration, capacity planning automation, and safe scale-in of stateful nodes, none of which is trivial on a shared-nothing cluster.
• Cloud and BYOC include integrated monitoring, alerting, audit, and managed backup scheduling. Self-managed deployments require you to select, deploy, and integrate equivalents such as Prometheus and Grafana, log pipelines, and backup orchestration.
• Downtime, security or compliance breaches, key-person dependency, and data-loss scenarios all carry real expected cost. Managed offerings reduce these risks, in part through certifications such as PCI and this risk reduction has a value.

Open source ClickHouse is free to licence, but the managed offerings become attractive once operational labour, tooling, and risk are included. With that framing in mind, the rest of this section describes the cost model for each option.

Cost Model For Each Deployment Option

To begin the analysis, the main cost lines under each deployment model are as follows:

ClickHouse Open Source - Self-Managed

• Licence - no licence or subscription fee for the ClickHouse software itself.
• Infrastructure - you pay your cloud provider directly for the servers you provision, plus block and object storage, network egress, and backup storage. There is no ClickHouse fee on top, but you own the full cloud bill.
• Operational labour - you own the operational work. Upgrades, monitoring, backups, incident response, capacity planning, security hardening, and failure recovery. This could require specialist skills and ClickHouse expertise.
• Tooling - you provide the supporting platform tooling. Monitoring, observability, alerting, log management, and backup orchestration.
• Support and commercial terms - community support is available, and third-party support can be purchased.
• Capacity planning - costs are predictable for steady workloads, but you have to size for peak demand. Over-provisioning is common because self-managed clusters cannot easily scale down stateful capacity.

ClickHouse Cloud - Fully Managed

• Licence - the managed service is billed by ClickHouse Inc on a consumption basis. On the Enterprise plan, compute is charged at ~$0.40 per 8 GiB compute unit hour (US East, list price).
• Infrastructure - cloud provider infrastructure is bundled into the ClickHouse Cloud invoice. You do not separately provision EC2, EKS, storage, routers, or Keeper for the database.
• Operational labour - ClickHouse Inc operates the database platform. You still need platform governance, access management, usage review, cost monitoring, and integration with internal controls.
• Tooling - monitoring, alerting, backups, upgrades, scaling, and managed-service operations are included.
• Support and commercial terms - support comes from ClickHouse Inc under the relevant SLA. Commercial terms may include committed-use discounts, upfront payment options, enterprise terms, bundled support, and Marketplace procurement.
• Capacity planning - compute is billed by the number of units, replicas, and hours consumed. Autoscaling and idling reduce the bill when load drops, so the cost tracks actual usage more closely than self-managed.

Bring Your Own Cloud - Partially Managed

• Licence - there is no separate software licence. You pay ClickHouse Inc a BYOC managed-service fee in addition to the cloud infrastructure you pay for directly.
• Infrastructure - you pay your cloud provider directly for the servers and data-plane services running inside your VPC. EC2 worker nodes, EKS, EBS, S3, load balancing, NAT, logging, networking, and related services. ClickHouse does not resell or mark up that cloud capacity.
• Operational labour - ClickHouse Inc operates the database lifecycle, but you still own the cloud account boundary, VPC, IAM guardrails, connectivity, and cloud-account hygiene.
• Tooling - managed database tooling (monitoring, alerting, backups, upgrades, scaling, Keeper, and router operations) is provided through the BYOC service. You still run your normal cloud governance and observability around the account.
• Support and commercial terms - support comes from ClickHouse Inc under the relevant SLA.
• Capacity planning - BYOC keeps the same managed scaling benefits as Cloud, but you see two bills. Cloud infrastructure directly from the cloud provider, and the BYOC managed-service fee from ClickHouse Inc.

Closing Thoughts

When you properly account for manpower costs, tooling, and the operational risk that sits on the team running the cluster, ClickHouse Cloud tends to come out close to cost neutral against self-managed Open Source. That is particularly true for spiky and variable workloads, where autoscaling and idling mean you pay for what you actually use rather than for peak capacity that sits idle most of the time.

If you can use ClickHouse Cloud, I would generally recommend that you do. You get the managed service, the SLA-backed support, the Cloud-exclusive features, and a bill that tracks real usage, without having to build and staff a team to run ClickHouse yourselves. BYOC and Private are then the right fallbacks when data residency, compliance, or isolation requirements mean that Cloud is not an option.