A · leads
ClickHouse
92.9
50,970 stars · Apache-2.0
Databases
ClickHouse leads by 3.9 · narrow
A · leads
92.9
50,970 stars · Apache-2.0
B
89.0
13,448 stars · BSD-3-Clause
ClickHouse versus pgcli 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++; pgcli is written mainly in Python. The composite score is 92.9 for ClickHouse and 89.0 for pgcli.
ClickHouse has 50,970 GitHub stars to pgcli's 13,448, a gap of 37,522 (3.79×). Forks are 9,275 for ClickHouse and 619 for pgcli. On the log scale used inside this pair, adoption is 100 versus 88, and the fork community is 100 versus 70.
Push history: ClickHouse was last pushed on 17 November 2026 (0 days ago), and pgcli was last pushed on 04 November 2026 (12 days ago). Open issues stand at 9,191 for ClickHouse (0.180 per star) and 56 for pgcli (0.004 per star). Issue-health scores are 34 and 96; activity scores are 100 and 92.
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. pgcli is listed as BSD-3-Clause, 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. License scores in this pair are 96 for ClickHouse and 96 for pgcli. This is a procurement signal, not legal advice.
In Databases, both ClickHouse (50,970 stars) and pgcli (13,448 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, pgcli is open source.
The lead is split. ClickHouse is furthest ahead on fork community (100 to 70), while pgcli is furthest ahead on issue health (96 to 34). Choose the dimension a rollout cannot compromise on.
ClickHouse finishes ahead at 92.9 against pgcli at 89.0, a 3.9 point narrow 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 | pgcli |
|---|---|---|
| GitHub stars | 50,970 | 13,448 |
| Forks | 9,275 | 619 |
| Open issues | 9,191 | 56 |
| Adoption | 100 | 88 |
| Activity | 100 | 92 |
| Community | 100 | 70 |
| Issue health | 34 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 92.9 | 89.0 |
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.
Postgres CLI with autocompletion and syntax highlighting
ClickHouse has more GitHub stars: 50,970 versus 13,448 for pgcli. The gap is 37,522 stars.
ClickHouse was pushed more recently: 17 November 2026 versus 04 November 2026 for pgcli. That is 12 days apart.
Yes. This catalog marks both ClickHouse and pgcli 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. pgcli is listed as BSD-3-Clause, 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 pgcli scores 89.0. This page calls that a narrow lead for ClickHouse.