A · leads
ClickHouse
92.9
50,970 stars · Apache-2.0
Databases
ClickHouse leads by 11.3 · clear
A · leads
92.9
50,970 stars · Apache-2.0
B
81.6
23,335 stars · Apache-2.0
ClickHouse versus neon is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. ClickHouse is written mainly in C++; neon is written mainly in Rust. The composite score is 92.9 for ClickHouse and 81.6 for neon.
ClickHouse has 50,970 GitHub stars to neon's 23,335, a gap of 27,635 (2.18×). Forks are 9,275 for ClickHouse and 1,139 for neon. On the log scale used inside this pair, adoption is 100 versus 93, and the fork community is 100 versus 77.
Push history: ClickHouse was last pushed on 17 November 2026 (0 days ago), and neon was last pushed on 31 August 2026 (78 days ago). Open issues stand at 9,191 for ClickHouse (0.180 per star) and 589 for neon (0.025 per star). Issue-health scores are 34 and 70; activity scores are 100 and 58.
Both ClickHouse and neon are listed as Apache-2.0. A permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. The license score is therefore level at 96 versus 96, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.
In Databases, both ClickHouse (50,970 stars) and neon (23,335 stars) are marked self-hostable. Deploy scores are 100 and 100. Running either one means you own upgrades, backups, and the license duties that follow a modified copy. Pricing labels on file: ClickHouse is open source, neon is open source.
The lead is split. ClickHouse is furthest ahead on recent activity (100 to 58), while neon is furthest ahead on issue health (70 to 34). Choose the dimension a rollout cannot compromise on.
ClickHouse finishes ahead at 92.9 against neon at 81.6, a 11.3 point clear margin under the published weights.
Scores are computed inside this pair only. Method and weights.
Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.
| Signal | ClickHouse | neon |
|---|---|---|
| GitHub stars | 50,970 | 23,335 |
| Forks | 9,275 | 1,139 |
| Open issues | 9,191 | 589 |
| Adoption | 100 | 93 |
| Activity | 100 | 58 |
| Community | 100 | 77 |
| Issue health | 34 | 70 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 92.9 | 81.6 |
ClickHouse is a columnar OLAP database built for fast analytical queries on large event tables. It is common as the store behind product analytics and observability.
Neon: Serverless Postgres. We separated storage and compute to offer autoscaling, code-like database branching, and scale to zero.
ClickHouse has more GitHub stars: 50,970 versus 23,335 for neon. The gap is 27,635 stars.
ClickHouse was pushed more recently: 17 November 2026 versus 31 August 2026 for neon. That is 78 days apart.
Yes. This catalog marks both ClickHouse and neon as self-hostable. Confirm each project's deploy docs before you plan a migration.
ClickHouse is listed as Apache-2.0, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. neon is listed as Apache-2.0, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
ClickHouse scores 92.9 and neon scores 81.6. This page calls that a clear lead for ClickHouse.