A
evidence
87.4
7,122 stars · MIT
Analytics
Metabase leads by 2.0 · narrow
A
87.4
7,122 stars · MIT
B · leads
89.4
50,382 stars · AGPL-3.0
evidence versus Metabase is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. evidence is written mainly in TypeScript; Metabase is written mainly in Clojure. The composite score is 87.4 for evidence and 89.4 for Metabase.
Metabase has 50,382 GitHub stars to evidence's 7,122, a gap of 43,260 (7.07×). Forks are 447 for evidence and 7,016 for Metabase. On the log scale used inside this pair, adoption is 82 versus 100, and the fork community is 69 versus 100.
Push history: evidence 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 39 for evidence (0.005 per star) and 4,696 for Metabase (0.093 per star). Issue-health scores are 84 and 52; activity scores are 100 and 100.
evidence 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 evidence and 52 for Metabase. This is a procurement signal, not legal advice.
In Analytics, both evidence (7,122 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: evidence is open source, Metabase is freemium.
The lead is split. evidence is furthest ahead on license flexibility (96 to 52), while Metabase is furthest ahead on fork community (100 to 69). Choose the dimension a rollout cannot compromise on.
Metabase finishes ahead at 89.4 against evidence at 87.4, a 2.0 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 | evidence | Metabase |
|---|---|---|
| GitHub stars | 7,122 | 50,382 |
| Forks | 447 | 7,016 |
| Open issues | 39 | 4,696 |
| Adoption | 82 | 100 |
| Activity | 100 | 100 |
| Community | 69 | 100 |
| Issue health | 84 | 52 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 87.4 | 89.4 |
Business intelligence as code: build fast, interactive data visualizations in SQL and markdown
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 7,122 for evidence. The gap is 43,260 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both evidence and Metabase as self-hostable. Confirm each project's deploy docs before you plan a migration.
evidence 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 evidence scores 87.4. This page calls that a narrow lead for Metabase.