A
timescaledb
82.8
23,865 stars · license n/a
Analytics
trino leads by 8.2 · clear
A
82.8
23,865 stars · license n/a
B · leads
91.0
13,520 stars · Apache-2.0
timescaledb versus trino is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. timescaledb is written mainly in C; trino is written mainly in Java. The composite score is 82.8 for timescaledb and 91.0 for trino.
timescaledb has 23,865 GitHub stars to trino's 13,520, a gap of 10,345 (1.77×). Forks are 1,188 for timescaledb and 3,880 for trino. On the log scale used inside this pair, adoption is 100 versus 94, and the fork community is 86 versus 100.
Push history: timescaledb was last pushed on 17 November 2026 (0 days ago), and trino was last pushed on 17 November 2026 (0 days ago). Open issues stand at 476 for timescaledb (0.020 per star) and 2,758 for trino (0.204 per star). Issue-health scores are 84 and 34; activity scores are 100 and 100.
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. trino 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. License scores in this pair are 30 for timescaledb and 96 for trino. This is a procurement signal, not legal advice.
Only trino is marked self-hostable here (13,520 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: timescaledb is unpriced in this catalog, trino is open source.
The lead is split. timescaledb is furthest ahead on issue health (84 to 34), while trino is furthest ahead on license flexibility (96 to 30). Choose the dimension a rollout cannot compromise on.
trino finishes ahead at 91.0 against timescaledb at 82.8, a 8.2 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 | timescaledb | trino |
|---|---|---|
| GitHub stars | 23,865 | 13,520 |
| Forks | 1,188 | 3,880 |
| Open issues | 476 | 2,758 |
| Adoption | 100 | 94 |
| Activity | 100 | 100 |
| Community | 86 | 100 |
| Issue health | 84 | 34 |
| License | 30 | 96 |
| Self-hosting | 35 | 100 |
| Composite | 82.8 | 91.0 |
A time-series database for high-performance real-time analytics packaged as a Postgres extension
Official repository of Trino, the distributed SQL query engine for big data, formerly known as PrestoSQL (https://trino.io)
timescaledb has more GitHub stars: 23,865 versus 13,520 for trino. The gap is 10,345 stars.
Both were last pushed on 17 November 2026.
Only trino is marked self-hostable. timescaledb is not.
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. trino 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.
trino scores 91.0 and timescaledb scores 82.8. This page calls that a clear lead for trino.