A
Metabase
89.4
50,382 stars · AGPL-3.0
Analytics
redash leads by 4.7 · narrow
A
89.4
50,382 stars · AGPL-3.0
B · leads
94.1
28,887 stars · BSD-2-Clause
Metabase versus redash 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; redash is written mainly in TypeScript. The composite score is 89.4 for Metabase and 94.1 for redash.
Metabase has 50,382 GitHub stars to redash's 28,887, a gap of 21,495 (1.74×). Forks are 7,016 for Metabase and 4,645 for redash. On the log scale used inside this pair, adoption is 100 versus 95, and the fork community is 100 versus 95.
Push history: Metabase was last pushed on 17 November 2026 (0 days ago), and redash was last pushed on 14 November 2026 (3 days ago). Open issues stand at 4,696 for Metabase (0.093 per star) and 780 for redash (0.027 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. redash is listed as BSD-2-Clause, 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 redash. This is a procurement signal, not legal advice.
In Analytics, both Metabase (50,382 stars) and redash (28,887 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, redash is open source.
The lead is split. Metabase is furthest ahead on adoption (100 to 95), while redash is furthest ahead on license flexibility (96 to 52). Choose the dimension a rollout cannot compromise on.
redash finishes ahead at 94.1 against Metabase at 89.4, a 4.7 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 | Metabase | redash |
|---|---|---|
| GitHub stars | 50,382 | 28,887 |
| Forks | 7,016 | 4,645 |
| Open issues | 4,696 | 780 |
| Adoption | 100 | 95 |
| Activity | 100 | 100 |
| Community | 100 | 95 |
| Issue health | 52 | 70 |
| License | 52 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 89.4 | 94.1 |
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.
Make Your Company Data Driven. Connect to any data source, easily visualize, dashboard and share your data.
Metabase has more GitHub stars: 50,382 versus 28,887 for redash. The gap is 21,495 stars.
Metabase was pushed more recently: 17 November 2026 versus 14 November 2026 for redash. That is 3 days apart.
Yes. This catalog marks both Metabase and redash 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. redash is listed as BSD-2-Clause, 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.
redash scores 94.1 and Metabase scores 89.4. This page calls that a narrow lead for redash.