ClickHouse’s core database engine is open-source under the Apache-2.0 license, allowing unlimited free self-hosted usage, while optional cloud and support services are paid.
Yes. The ClickHouse server, client, and official drivers are released under the permissive Apache-2.0 license. You may download, modify, and distribute the software without paying license fees or sharing proprietary code.
You only pay for infrastructure—VMs, disks, and network traffic. The software itself remains free. Running on commodity hardware or low-cost cloud instances keeps total cost of ownership minimal.
ClickHouse Cloud, enterprise support contracts, and managed Kubernetes operators incur recurring fees. These subscriptions cover SLA guarantees, monitoring, backups, and expert help, not the database bits.
You can prototype locally with the open-source build, then migrate to ClickHouse Cloud for production. No code changes are required; both variants share identical SQL syntax and storage formats.
Install the public APT repo, then sudo apt-get install clickhouse-server clickhouse-client
. After service start, connect with clickhouse-client
and run SQL like any other RDBMS.
All core features—columnar storage, vectorized execution, compression codecs, joins, window functions, and materialized views—are part of the open-source codebase and cost nothing to use.
SELECT customer_id,
sum(total_amount) AS lifetime_value
FROM Orders
GROUP BY customer_id
ORDER BY lifetime_value DESC
LIMIT 10;
The query runs locally or in the free tier exactly as it does in paid hosting.
Mount data on inexpensive object storage (e.g., S3, MinIO) and scale stateless ClickHouse nodes horizontally. This architecture maximises performance while keeping infra costs low.
No. The Apache-2.0 license permits free commercial use, redistribution, and modification.
Yes. A time-limited trial with credits lets you test managed ClickHouse at no cost. After credits expire, standard pay-as-you-go pricing begins.
Absolutely. Backup your data with CLICKHOUSE-backup
or INSERT INTO ... SELECT *
, then restore into a cloud cluster using the same table schemas.