A · leads
Metabase
89.4
50,382 stars · AGPL-3.0
Analytics
Metabase leads by 1.5 · narrow
A · leads
89.4
50,382 stars · AGPL-3.0
B
87.9
13,520 stars · Apache-2.0
Metabase versus trino 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; trino is written mainly in Java. The composite score is 89.4 for Metabase and 87.9 for trino.
Metabase has 50,382 GitHub stars to trino's 13,520, a gap of 36,862 (3.73×). Forks are 7,016 for Metabase and 3,880 for trino. On the log scale used inside this pair, adoption is 100 versus 88, and the fork community is 100 versus 93.
Push history: Metabase 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 4,696 for Metabase (0.093 per star) and 2,758 for trino (0.204 per star). Issue-health scores are 52 and 34; 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. 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 52 for Metabase and 96 for trino. This is a procurement signal, not legal advice.
In Analytics, both Metabase (50,382 stars) and trino (13,520 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: Metabase is freemium, trino is open source.
The lead is split. Metabase is furthest ahead on issue health (52 to 34), while trino is furthest ahead on license flexibility (96 to 52). Choose the dimension a rollout cannot compromise on.
Metabase finishes ahead at 89.4 against trino at 87.9, a 1.5 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 | Metabase | trino |
|---|---|---|
| GitHub stars | 50,382 | 13,520 |
| Forks | 7,016 | 3,880 |
| Open issues | 4,696 | 2,758 |
| Adoption | 100 | 88 |
| Activity | 100 | 100 |
| Community | 100 | 93 |
| Issue health | 52 | 34 |
| License | 52 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 89.4 | 87.9 |
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.
Official repository of Trino, the distributed SQL query engine for big data, formerly known as PrestoSQL (https://trino.io)
Metabase has more GitHub stars: 50,382 versus 13,520 for trino. The gap is 36,862 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both Metabase and trino as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. 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.
Metabase scores 89.4 and trino scores 87.9. This page calls that a narrow lead for Metabase.