A
angle-grinder
68.6
3,769 stars · MIT
Analytics
Metabase leads by 20.8 · decisive
A
68.6
3,769 stars · MIT
B · leads
89.4
50,382 stars · AGPL-3.0
angle-grinder versus Metabase is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. angle-grinder is written mainly in Rust; Metabase is written mainly in Clojure. The composite score is 68.6 for angle-grinder and 89.4 for Metabase.
Metabase has 50,382 GitHub stars to angle-grinder's 3,769, a gap of 46,613 (13.37×). Forks are 76 for angle-grinder and 7,016 for Metabase. On the log scale used inside this pair, adoption is 76 versus 100, and the fork community is 49 versus 100.
Push history: angle-grinder was last pushed on 05 February 2026 (285 days ago), and Metabase was last pushed on 17 November 2026 (0 days ago). Open issues stand at 29 for angle-grinder (0.008 per star) and 4,696 for Metabase (0.093 per star). Issue-health scores are 84 and 52; activity scores are 36 and 100.
angle-grinder 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 angle-grinder and 52 for Metabase. This is a procurement signal, not legal advice.
In Analytics, both angle-grinder (3,769 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: angle-grinder is open source, Metabase is freemium.
The lead is split. angle-grinder 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 angle-grinder at 68.6, a 20.8 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 | angle-grinder | Metabase |
|---|---|---|
| GitHub stars | 3,769 | 50,382 |
| Forks | 76 | 7,016 |
| Open issues | 29 | 4,696 |
| Adoption | 76 | 100 |
| Activity | 36 | 100 |
| Community | 49 | 100 |
| Issue health | 84 | 52 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 68.6 | 89.4 |
Slice and dice logs on the command line
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 3,769 for angle-grinder. The gap is 46,613 stars.
Metabase was pushed more recently: 17 November 2026 versus 05 February 2026 for angle-grinder. That is 285 days apart.
Yes. This catalog marks both angle-grinder and Metabase as self-hostable. Confirm each project's deploy docs before you plan a migration.
angle-grinder 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 angle-grinder scores 68.6. This page calls that a decisive lead for Metabase.