A
dremio-oss
62.7
1,500 stars · Apache-2.0
Analytics
Metabase leads by 26.7 · decisive
A
62.7
1,500 stars · Apache-2.0
B · leads
89.4
50,382 stars · AGPL-3.0
dremio-oss versus Metabase is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. dremio-oss is written mainly in Java; Metabase is written mainly in Clojure. The composite score is 62.7 for dremio-oss and 89.4 for Metabase.
Metabase has 50,382 GitHub stars to dremio-oss's 1,500, a gap of 48,882 (33.59×). Forks are 474 for dremio-oss and 7,016 for Metabase. On the log scale used inside this pair, adoption is 68 versus 100, and the fork community is 70 versus 100.
Push history: dremio-oss was last pushed on 26 September 2025 (417 days ago), and Metabase was last pushed on 17 November 2026 (0 days ago). Open issues stand at 56 for dremio-oss (0.037 per star) and 4,696 for Metabase (0.093 per star). Issue-health scores are 70 and 52; activity scores are 16 and 100.
dremio-oss 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. 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 dremio-oss and 52 for Metabase. This is a procurement signal, not legal advice.
In Analytics, both dremio-oss (1,500 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: dremio-oss is open source, Metabase is freemium.
The lead is split. dremio-oss is furthest ahead on license flexibility (96 to 52), while Metabase is furthest ahead on recent activity (100 to 16). Choose the dimension a rollout cannot compromise on.
Metabase finishes ahead at 89.4 against dremio-oss at 62.7, a 26.7 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 | dremio-oss | Metabase |
|---|---|---|
| GitHub stars | 1,500 | 50,382 |
| Forks | 474 | 7,016 |
| Open issues | 56 | 4,696 |
| Adoption | 68 | 100 |
| Activity | 16 | 100 |
| Community | 70 | 100 |
| Issue health | 70 | 52 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 62.7 | 89.4 |
Dremio - the missing link in modern data
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 1,500 for dremio-oss. The gap is 48,882 stars.
Metabase was pushed more recently: 17 November 2026 versus 26 September 2025 for dremio-oss. That is 417 days apart.
Yes. This catalog marks both dremio-oss and Metabase as self-hostable. Confirm each project's deploy docs before you plan a migration.
dremio-oss 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. 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 dremio-oss scores 62.7. This page calls that a decisive lead for Metabase.