A · level
trino
92.9
13,520 stars · Apache-2.0
Analytics
Too close to call · 92.9 to 93.5
A · level
92.9
13,520 stars · Apache-2.0
B · level
93.5
10,650 stars · MIT
trino versus uPlot is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. trino is written mainly in Java; uPlot is written mainly in JavaScript. The composite score is 92.9 for trino and 93.5 for uPlot.
trino has 13,520 GitHub stars to uPlot's 10,650, a gap of 2,870 (1.27×). Forks are 3,880 for trino and 472 for uPlot. On the log scale used inside this pair, adoption is 100 versus 98, and the fork community is 100 versus 74.
Push history: trino was last pushed on 17 November 2026 (0 days ago), and uPlot was last pushed on 17 November 2026 (0 days ago). Open issues stand at 2,758 for trino (0.204 per star) and 132 for uPlot (0.012 per star). Issue-health scores are 34 and 84; activity scores are 100 and 100.
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. uPlot is listed as MIT, 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 trino and 96 for uPlot. This is a procurement signal, not legal advice.
In Analytics, both trino (13,520 stars) and uPlot (10,650 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: trino is open source, uPlot is open source.
The lead is split. trino is furthest ahead on fork community (100 to 74), while uPlot is furthest ahead on issue health (84 to 34). Choose the dimension a rollout cannot compromise on.
Composite score: trino 92.9, uPlot 93.5. The margin is under one point, so this page calls a tie. Use the dimension breakdown rather than the headline number.
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 | trino | uPlot |
|---|---|---|
| GitHub stars | 13,520 | 10,650 |
| Forks | 3,880 | 472 |
| Open issues | 2,758 | 132 |
| Adoption | 100 | 98 |
| Activity | 100 | 100 |
| Community | 100 | 74 |
| Issue health | 34 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 92.9 | 93.5 |
Official repository of Trino, the distributed SQL query engine for big data, formerly known as PrestoSQL (https://trino.io)
📈 A small, fast chart for time series, lines, areas, ohlc & bars
trino has more GitHub stars: 13,520 versus 10,650 for uPlot. The gap is 2,870 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both trino and uPlot as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. uPlot is listed as MIT, 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.
Neither tool clears a one-point margin. trino scores 92.9 and uPlot scores 93.5.