A
Matomo
86.9
22,032 stars · GPL-3.0
Analytics
Metabase leads by 2.5 · narrow
A
86.9
22,032 stars · GPL-3.0
B · leads
89.4
50,382 stars · AGPL-3.0
Matomo versus Metabase is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Matomo is written mainly in PHP; Metabase is written mainly in Clojure. The composite score is 86.9 for Matomo and 89.4 for Metabase.
Metabase has 50,382 GitHub stars to Matomo's 22,032, a gap of 28,350 (2.29×). Forks are 2,938 for Matomo and 7,016 for Metabase. On the log scale used inside this pair, adoption is 92 versus 100, and the fork community is 90 versus 100.
Push history: Matomo was last pushed on 17 November 2026 (0 days ago), and Metabase was last pushed on 17 November 2026 (0 days ago). Open issues stand at 2,563 for Matomo (0.116 per star) and 4,696 for Metabase (0.093 per star). Issue-health scores are 52 and 52; activity scores are 100 and 100.
Matomo 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. 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 64 for Matomo and 52 for Metabase. This is a procurement signal, not legal advice.
In Analytics, both Matomo (22,032 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: Matomo is open source, Metabase is freemium.
The lead is split. Matomo is furthest ahead on license flexibility (64 to 52), while Metabase is furthest ahead on fork community (100 to 90). Choose the dimension a rollout cannot compromise on.
Metabase finishes ahead at 89.4 against Matomo at 86.9, a 2.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 | Matomo | Metabase |
|---|---|---|
| GitHub stars | 22,032 | 50,382 |
| Forks | 2,938 | 7,016 |
| Open issues | 2,563 | 4,696 |
| Adoption | 92 | 100 |
| Activity | 100 | 100 |
| Community | 90 | 100 |
| Issue health | 52 | 52 |
| License | 64 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 86.9 | 89.4 |
Matomo is a web analytics platform built as a privacy-oriented alternative to Google Analytics. It has a long plugin history and is designed to run on your own server.
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 22,032 for Matomo. The gap is 28,350 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both Matomo and Metabase as self-hostable. Confirm each project's deploy docs before you plan a migration.
Matomo 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. 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 Matomo scores 86.9. This page calls that a narrow lead for Metabase.