A · leads
Metabase
89.4
50,382 stars · AGPL-3.0
Analytics
Metabase leads by 8.7 · clear
A · leads
89.4
50,382 stars · AGPL-3.0
B
80.7
3,734 stars · MIT
Metabase versus player 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; player is written mainly in TypeScript. The composite score is 89.4 for Metabase and 80.7 for player.
Metabase has 50,382 GitHub stars to player's 3,734, a gap of 46,648 (13.49×). Forks are 7,016 for Metabase and 231 for player. On the log scale used inside this pair, adoption is 100 versus 76, and the fork community is 100 versus 62.
Push history: Metabase was last pushed on 17 November 2026 (0 days ago), and player was last pushed on 07 October 2026 (40 days ago). Open issues stand at 4,696 for Metabase (0.093 per star) and 1 for player (0.000 per star). Issue-health scores are 52 and 96; activity scores are 100 and 78.
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. player 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 player. This is a procurement signal, not legal advice.
In Analytics, both Metabase (50,382 stars) and player (3,734 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, player is open source.
The lead is split. Metabase is furthest ahead on fork community (100 to 62), while player is furthest ahead on issue health (96 to 52). Choose the dimension a rollout cannot compromise on.
Metabase finishes ahead at 89.4 against player at 80.7, a 8.7 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 | Metabase | player |
|---|---|---|
| GitHub stars | 50,382 | 3,734 |
| Forks | 7,016 | 231 |
| Open issues | 4,696 | 1 |
| Adoption | 100 | 76 |
| Activity | 100 | 78 |
| Community | 100 | 62 |
| Issue health | 52 | 96 |
| License | 52 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 89.4 | 80.7 |
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.
Deprecated in favour of Video.js 10; security fixes only until January 2028. UI components and hooks for building video and audio players on the web.
Metabase has more GitHub stars: 50,382 versus 3,734 for player. The gap is 46,648 stars.
Metabase was pushed more recently: 17 November 2026 versus 07 October 2026 for player. That is 40 days apart.
Yes. This catalog marks both Metabase and player 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. player 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 player scores 80.7. This page calls that a clear lead for Metabase.