A · leads
Metabase
87.7
50,382 stars · AGPL-3.0
Analytics
Metabase leads by 26.2 · decisive
A · leads
87.7
50,382 stars · AGPL-3.0
B
61.5
1,286 stars · MIT
Metabase versus sniffly 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; sniffly is written mainly in Python. The composite score is 87.7 for Metabase and 61.5 for sniffly.
Metabase has 50,382 GitHub stars to sniffly's 1,286, a gap of 49,096 (39.18×). Forks are 7,016 for Metabase and 118 for sniffly. On the log scale used inside this pair, adoption is 100 versus 66, and the fork community is 100 versus 54.
Push history: Metabase was last pushed on 17 November 2026 (5 days ago), and sniffly was last pushed on 08 August 2025 (471 days ago). Open issues stand at 4,696 for Metabase (0.093 per star) and 13 for sniffly (0.010 per star). Issue-health scores are 52 and 84; activity scores are 92 and 16.
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. sniffly 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 sniffly. This is a procurement signal, not legal advice.
In Analytics, both Metabase (50,382 stars) and sniffly (1,286 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, sniffly is open source.
The lead is split. Metabase is furthest ahead on recent activity (92 to 16), while sniffly is furthest ahead on license flexibility (96 to 52). Choose the dimension a rollout cannot compromise on.
Metabase finishes ahead at 87.7 against sniffly at 61.5, a 26.2 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 | Metabase | sniffly |
|---|---|---|
| GitHub stars | 50,382 | 1,286 |
| Forks | 7,016 | 118 |
| Open issues | 4,696 | 13 |
| Adoption | 100 | 66 |
| Activity | 92 | 16 |
| Community | 100 | 54 |
| Issue health | 52 | 84 |
| License | 52 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 87.7 | 61.5 |
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.
Claude Code dashboard with usage stats, error analysis, and sharable feature
Metabase has more GitHub stars: 50,382 versus 1,286 for sniffly. The gap is 49,096 stars.
Metabase was pushed more recently: 17 November 2026 versus 08 August 2025 for sniffly. That is 466 days apart.
Yes. This catalog marks both Metabase and sniffly 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. sniffly 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 87.7 and sniffly scores 61.5. This page calls that a decisive lead for Metabase.