- ClickHouse Server for traditional client/server deployments
- ClickHouse Cloud for fully managed database operations
- ClickHouse CLI for local development and cloud management
- clickhouse-local for command-line data processing
- chDB for embedding ClickHouse directly in applications
ClickHouse Server
ClickHouse Server represents the traditional client/server architecture and is ideal for production deployments. This deployment mode provides the full OLAP database capabilities with high throughput and low latency queries that ClickHouse is known for.
When it comes to deployment flexibility, ClickHouse Server can be installed on your local machine for development or testing, deployed to major cloud providers like AWS, GCP, or Azure for cloud-based operations, or set up on your own on-premises hardware. For larger scale operations, it can be configured as a distributed cluster to handle increased load and provide high availability. This deployment mode is the go-to choice for production environments where reliability, performance, and full feature access are crucial.
ClickHouse Cloud
ClickHouse Cloud is a fully managed version of ClickHouse that removes the operational overhead of running your own deployment. While it maintains all the core capabilities of ClickHouse Server, it enhances the experience with additional features designed to streamline development and operations.
ClickHouse CLI
The ClickHouse CLI (clickhousectl, alias chctl) is a command-line tool for local ClickHouse and Postgres development and for ClickHouse Cloud management. It installs ClickHouse versions, launches and manages local servers, and runs queries.
For local development, clickhousectl installs any ClickHouse version and runs named servers. Connect with clickhousectl local client, which runs that version’s clickhouse-client. Each server keeps its data in the project’s .clickhouse/ directory, so you can run multiple isolated environments side by side. With Docker running, clickhousectl local postgres starts local Postgres servers the same way.
clickhousectl also manages ClickHouse Cloud resources: services, scaling, backups, Managed Postgres, ClickPipes, Managed ClickStack, API keys, and organizations. Browser login (clickhousectl cloud auth login) is read-only; creating or changing resources needs an API key.
clickhouse-local
clickhouse-local is a powerful command-line tool that provides the complete functionality of ClickHouse in a standalone executable. It’s essentially the same database as ClickHouse Server, but packaged in a way that lets you harness all of ClickHouse’s capabilities directly from the command line without running a server instance.
chDB
chDB is ClickHouse embedded as an in-process database engine, with Python being the primary implementation, though it’s also available for Go, Rust, NodeJS, and Bun. This deployment option brings ClickHouse’s powerful OLAP capabilities directly into your application’s process, eliminating the need for a separate database installation.