A
dbt
87.4
14,183 stars · Apache-2.0
Analytics
Metabase leads by 2.0 · narrow
A
87.4
14,183 stars · Apache-2.0
B · leads
89.4
50,382 stars · AGPL-3.0
dbt versus Metabase is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. dbt is written mainly in Rust; Metabase is written mainly in Clojure. The composite score is 87.4 for dbt and 89.4 for Metabase.
Metabase has 50,382 GitHub stars to dbt's 14,183, a gap of 36,199 (3.55×). Forks are 2,679 for dbt and 7,016 for Metabase. On the log scale used inside this pair, adoption is 88 versus 100, and the fork community is 89 versus 100.
Push history: dbt 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 1,915 for dbt (0.135 per star) and 4,696 for Metabase (0.093 per star). Issue-health scores are 34 and 52; activity scores are 100 and 100.
dbt 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 dbt and 52 for Metabase. This is a procurement signal, not legal advice.
In Analytics, both dbt (14,183 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: dbt is open source, Metabase is freemium.
The lead is split. dbt is furthest ahead on license flexibility (96 to 52), while Metabase is furthest ahead on issue health (52 to 34). Choose the dimension a rollout cannot compromise on.
Metabase finishes ahead at 89.4 against dbt 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 | dbt | Metabase |
|---|---|---|
| GitHub stars | 14,183 | 50,382 |
| Forks | 2,679 | 7,016 |
| Open issues | 1,915 | 4,696 |
| Adoption | 88 | 100 |
| Activity | 100 | 100 |
| Community | 89 | 100 |
| Issue health | 34 | 52 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 87.4 | 89.4 |
dbt enables data analysts and engineers to transform their data using the same practices that software engineers use to build applications.
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 14,183 for dbt. The gap is 36,199 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both dbt and Metabase as self-hostable. Confirm each project's deploy docs before you plan a migration.
dbt 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 dbt scores 87.4. This page calls that a narrow lead for Metabase.