ClickHouse
ClickHouse is an open-source, column-oriented database management system for online analytical processing (OLAP).
Platform availability
Available on 2 of 10 platforms
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
68/100 Good
- Maintained
- 100last commit 14 days ago
- Popular
- 9450,801 GitHub stars
- Easy to install
- 150 install platforms, install notes
- Light to run
- 1016 GB minimum RAM
Availability: links checked today
- GitHub stars
- 50,801
- Open issues
- 8829
- Last commit
- 2026-11-07
- Latest release
- v26.10.2.103-stable
- License
- Apache-2.0
- Activity
- declining
Checked 14 days ago - source: GitHub (ClickHouse/ClickHouse)
Resources & Compatibility
Minimum requirements: 16 GB RAM, 4 CPU core(s), 1024 GB disk.
Checked 40 days ago - source: Docker Hub image tags and published docs
First-install notes
- Install and start ClickHouse server Unpack the downloaded ClickHouse server file, then use sudo (admin command) to run the install script and start the service, the background program that keeps ClickHouse running. Without this, ClickHouse is missing or stopped, so apps can't connect. source
- Quick install (Linux, macOS, FreeBSD) Run the official one-liner curl https://clickhouse.com/ | sh to download and install the ClickHouse server in one step. source
Fetched 40 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
What common self-hosting problems should I investigate first?
ClickHouse troubleshooting points to slow queries, memory errors, connection issues, and configuration problems as common areas to check.
What should I plan for when scaling a self-hosted ClickHouse deployment?
Production scaling depends on choosing sharding and replication options, cluster setup, and distributed execution.
What alerting gap do self-hosters often experience with ClickHouse?
Self-hosted environments can lack reliable alerting, making incidents reactive. They need lightweight operational visibility such as built-in alerts, health checks, threshold monitoring, and notifications.
Answers sourced from clickhouse.com, dev.to, www.reddit.com
Community
- Recommended way to self-host Clickhouse : r/Clickhouse - Reddit (reddit)
- r/selfhosted on Reddit: Deep Dive on ClickHouse Sharding and ... (reddit)
- ClickHouse - Reddit (reddit)
- ClickHouse - Reddit (reddit)
Collected 48 days ago - public community threads