A
analytics
68.1
2,671 stars · MIT
Analytics
Metabase leads by 21.3 · decisive
A
68.1
2,671 stars · MIT
B · leads
89.4
50,382 stars · AGPL-3.0
analytics versus Metabase is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. analytics is written mainly in JavaScript; Metabase is written mainly in Clojure. The composite score is 68.1 for analytics and 89.4 for Metabase.
Metabase has 50,382 GitHub stars to analytics's 2,671, a gap of 47,711 (18.86×). Forks are 266 for analytics and 7,016 for Metabase. On the log scale used inside this pair, adoption is 73 versus 100, and the fork community is 63 versus 100.
Push history: analytics was last pushed on 27 June 2026 (142 days ago), and Metabase was last pushed on 17 November 2026 (0 days ago). Open issues stand at 116 for analytics (0.043 per star) and 4,696 for Metabase (0.093 per star). Issue-health scores are 70 and 52; activity scores are 36 and 100.
analytics 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. 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. License scores in this pair are 96 for analytics and 52 for Metabase. This is a procurement signal, not legal advice.
In Analytics, both analytics (2,671 stars) and Metabase (50,382 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: analytics is open source, Metabase is freemium.
The lead is split. analytics is furthest ahead on license flexibility (96 to 52), while Metabase is furthest ahead on recent activity (100 to 36). Choose the dimension a rollout cannot compromise on.
Metabase finishes ahead at 89.4 against analytics at 68.1, a 21.3 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 | analytics | Metabase |
|---|---|---|
| GitHub stars | 2,671 | 50,382 |
| Forks | 266 | 7,016 |
| Open issues | 116 | 4,696 |
| Adoption | 73 | 100 |
| Activity | 36 | 100 |
| Community | 63 | 100 |
| Issue health | 70 | 52 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 68.1 | 89.4 |
Lightweight analytics abstraction layer for tracking page views, custom events, & identifying visitors
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.
Metabase has more GitHub stars: 50,382 versus 2,671 for analytics. The gap is 47,711 stars.
Metabase was pushed more recently: 17 November 2026 versus 27 June 2026 for analytics. That is 142 days apart.
Yes. This catalog marks both analytics and Metabase as self-hostable. Confirm each project's deploy docs before you plan a migration.
analytics 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. 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Metabase scores 89.4 and analytics scores 68.1. This page calls that a decisive lead for Metabase.