A · leads
Metabase
89.4
50,382 stars · AGPL-3.0
Analytics
Metabase leads by 22.4 · decisive
A · leads
89.4
50,382 stars · AGPL-3.0
B
67.0
1,672 stars · MIT
Metabase versus trench 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; trench is written mainly in TypeScript. The composite score is 89.4 for Metabase and 67.0 for trench.
Metabase has 50,382 GitHub stars to trench's 1,672, a gap of 48,710 (30.13×). Forks are 7,016 for Metabase and 66 for trench. On the log scale used inside this pair, adoption is 100 versus 69, and the fork community is 100 versus 48.
Push history: Metabase was last pushed on 17 November 2026 (0 days ago), and trench was last pushed on 06 April 2026 (224 days ago). Open issues stand at 4,696 for Metabase (0.093 per star) and 3 for trench (0.002 per star). Issue-health scores are 52 and 96; activity scores are 100 and 36.
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. trench 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 52 for Metabase and 96 for trench. This is a procurement signal, not legal advice.
In Analytics, both Metabase (50,382 stars) and trench (1,672 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, trench is open source.
The lead is split. Metabase is furthest ahead on recent activity (100 to 36), while trench is furthest ahead on issue health (96 to 52). Choose the dimension a rollout cannot compromise on.
Metabase finishes ahead at 89.4 against trench at 67.0, a 22.4 point decisive 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 | trench |
|---|---|---|
| GitHub stars | 50,382 | 1,672 |
| Forks | 7,016 | 66 |
| Open issues | 4,696 | 3 |
| Adoption | 100 | 69 |
| Activity | 100 | 36 |
| Community | 100 | 48 |
| Issue health | 52 | 96 |
| License | 52 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 89.4 | 67.0 |
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.
Trench — Open-Source Analytics Infrastructure. A single production-ready Docker image built on ClickHouse, Kafka, and Node.js for tracking events. Easily build product analytics dashboards, LLM RAGs, observability platforms, or any other analytics product.
Metabase has more GitHub stars: 50,382 versus 1,672 for trench. The gap is 48,710 stars.
Metabase was pushed more recently: 17 November 2026 versus 06 April 2026 for trench. That is 224 days apart.
Yes. This catalog marks both Metabase and trench 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. trench 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.
Metabase scores 89.4 and trench scores 67.0. This page calls that a decisive lead for Metabase.