A · leads
Metabase
89.4
50,382 stars · AGPL-3.0
Analytics
Metabase leads by 5.5 · narrow
A · leads
89.4
50,382 stars · AGPL-3.0
B
83.9
6,640 stars · GPL-3.0
Metabase versus Tautulli 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; Tautulli is written mainly in Python. The composite score is 89.4 for Metabase and 83.9 for Tautulli.
Metabase has 50,382 GitHub stars to Tautulli's 6,640, a gap of 43,742 (7.59×). Forks are 7,016 for Metabase and 640 for Tautulli. On the log scale used inside this pair, adoption is 100 versus 81, and the fork community is 100 versus 73.
Push history: Metabase was last pushed on 17 November 2026 (0 days ago), and Tautulli was last pushed on 17 November 2026 (0 days ago). Open issues stand at 4,696 for Metabase (0.093 per star) and 117 for Tautulli (0.018 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. Tautulli is listed as GPL-3.0, which this catalog treats as a strong copyleft grant. Distributing a modified binary typically means offering the corresponding source of that program. License scores in this pair are 52 for Metabase and 64 for Tautulli. This is a procurement signal, not legal advice.
In Analytics, both Metabase (50,382 stars) and Tautulli (6,640 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, Tautulli is open source.
The lead is split. Metabase is furthest ahead on fork community (100 to 73), while Tautulli is furthest ahead on issue health (84 to 52). Choose the dimension a rollout cannot compromise on.
Metabase finishes ahead at 89.4 against Tautulli at 83.9, a 5.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 | Tautulli |
|---|---|---|
| GitHub stars | 50,382 | 6,640 |
| Forks | 7,016 | 640 |
| Open issues | 4,696 | 117 |
| Adoption | 100 | 81 |
| Activity | 100 | 100 |
| Community | 100 | 73 |
| Issue health | 52 | 84 |
| License | 52 | 64 |
| Self-hosting | 100 | 100 |
| Composite | 89.4 | 83.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.
A Python based monitoring and tracking tool for Plex Media Server.
Metabase has more GitHub stars: 50,382 versus 6,640 for Tautulli. The gap is 43,742 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both Metabase and Tautulli 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. Tautulli is listed as GPL-3.0, which this catalog treats as a strong copyleft grant. Distributing a modified binary typically means offering the corresponding source of that program. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Metabase scores 89.4 and Tautulli scores 83.9. This page calls that a narrow lead for Metabase.