A · leads
Metabase
89.4
50,382 stars · AGPL-3.0
Analytics
Metabase leads by 7.7 · clear
A · leads
89.4
50,382 stars · AGPL-3.0
B
81.7
2,454 stars · Apache-2.0
Metabase versus openmeter 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; openmeter is written mainly in Go. The composite score is 89.4 for Metabase and 81.7 for openmeter.
Metabase has 50,382 GitHub stars to openmeter's 2,454, a gap of 47,928 (20.53×). Forks are 7,016 for Metabase and 244 for openmeter. On the log scale used inside this pair, adoption is 100 versus 72, and the fork community is 100 versus 62.
Push history: Metabase was last pushed on 17 November 2026 (0 days ago), and openmeter was last pushed on 17 November 2026 (0 days ago). Open issues stand at 4,696 for Metabase (0.093 per star) and 88 for openmeter (0.036 per star). Issue-health scores are 52 and 70; 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. openmeter is listed as Apache-2.0, 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 openmeter. This is a procurement signal, not legal advice.
In Analytics, both Metabase (50,382 stars) and openmeter (2,454 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, openmeter is open source.
The lead is split. Metabase is furthest ahead on fork community (100 to 62), while openmeter is furthest ahead on license flexibility (96 to 52). Choose the dimension a rollout cannot compromise on.
Metabase finishes ahead at 89.4 against openmeter at 81.7, a 7.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 | openmeter |
|---|---|---|
| GitHub stars | 50,382 | 2,454 |
| Forks | 7,016 | 244 |
| Open issues | 4,696 | 88 |
| Adoption | 100 | 72 |
| Activity | 100 | 100 |
| Community | 100 | 62 |
| Issue health | 52 | 70 |
| License | 52 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 89.4 | 81.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.
Metering and Billing for AI, API and DevOps. Collect and aggregate millions of usage events in real-time and enable usage-based billing.
Metabase has more GitHub stars: 50,382 versus 2,454 for openmeter. The gap is 47,928 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both Metabase and openmeter 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. openmeter is listed as Apache-2.0, 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 openmeter scores 81.7. This page calls that a clear lead for Metabase.