A · leads
Metabase
89.4
50,382 stars · AGPL-3.0
Analytics
Metabase leads by 9.7 · clear
A · leads
89.4
50,382 stars · AGPL-3.0
B
79.7
23,865 stars · license n/a
Metabase versus timescaledb is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Metabase is written mainly in Clojure; timescaledb is written mainly in C. The composite score is 89.4 for Metabase and 79.7 for timescaledb.
Metabase has 50,382 GitHub stars to timescaledb's 23,865, a gap of 26,517 (2.11×). Forks are 7,016 for Metabase and 1,188 for timescaledb. On the log scale used inside this pair, adoption is 100 versus 93, and the fork community is 100 versus 80.
Push history: Metabase was last pushed on 17 November 2026 (0 days ago), and timescaledb was last pushed on 17 November 2026 (0 days ago). Open issues stand at 4,696 for Metabase (0.093 per star) and 476 for timescaledb (0.020 per star). Issue-health scores are 52 and 84; activity scores are 100 and 100.
Metabase is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. timescaledb is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. License scores in this pair are 52 for Metabase and 30 for timescaledb. This is a procurement signal, not legal advice.
Only Metabase is marked self-hostable here (50,382 stars, deploy score 100). timescaledb is not (23,865 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: Metabase is freemium, timescaledb is unpriced in this catalog.
The lead is split. Metabase is furthest ahead on self-hosting (100 to 35), while timescaledb is furthest ahead on issue health (84 to 52). Choose the dimension a rollout cannot compromise on.
Metabase finishes ahead at 89.4 against timescaledb at 79.7, a 9.7 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 | Metabase | timescaledb |
|---|---|---|
| GitHub stars | 50,382 | 23,865 |
| Forks | 7,016 | 1,188 |
| Open issues | 4,696 | 476 |
| Adoption | 100 | 93 |
| Activity | 100 | 100 |
| Community | 100 | 80 |
| Issue health | 52 | 84 |
| License | 52 | 30 |
| Self-hosting | 100 | 35 |
| Composite | 89.4 | 79.7 |
Metabase is a business-intelligence tool that lets teams ask questions of a SQL database without writing a report from scratch. It is commonly self-hosted next to the warehouse it reads.
A time-series database for high-performance real-time analytics packaged as a Postgres extension
Metabase has more GitHub stars: 50,382 versus 23,865 for timescaledb. The gap is 26,517 stars.
Both were last pushed on 17 November 2026.
Only Metabase is marked self-hostable. timescaledb is not.
Metabase is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. timescaledb is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Metabase scores 89.4 and timescaledb scores 79.7. This page calls that a clear lead for Metabase.