A
dbt
90.5
14,183 stars · Apache-2.0
Analytics
Plausible leads by 2.8 · narrow
A
90.5
14,183 stars · Apache-2.0
B · leads
93.3
29,871 stars · AGPL-3.0
dbt versus Plausible 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; Plausible is written mainly in Elixir. The composite score is 90.5 for dbt and 93.3 for Plausible.
Plausible has 29,871 GitHub stars to dbt's 14,183, a gap of 15,688 (2.11×). Forks are 2,679 for dbt and 1,940 for Plausible. On the log scale used inside this pair, adoption is 93 versus 100, and the fork community is 100 versus 96.
Push history: dbt was last pushed on 17 November 2026 (0 days ago), and Plausible was last pushed on 17 November 2026 (0 days ago). Open issues stand at 1,915 for dbt (0.135 per star) and 58 for Plausible (0.002 per star). Issue-health scores are 34 and 96; 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. Plausible 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 Plausible. This is a procurement signal, not legal advice.
In Analytics, both dbt (14,183 stars) and Plausible (29,871 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, Plausible is freemium.
The lead is split. dbt is furthest ahead on license flexibility (96 to 52), while Plausible is furthest ahead on issue health (96 to 34). Choose the dimension a rollout cannot compromise on.
Plausible finishes ahead at 93.3 against dbt at 90.5, a 2.8 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 | Plausible |
|---|---|---|
| GitHub stars | 14,183 | 29,871 |
| Forks | 2,679 | 1,940 |
| Open issues | 1,915 | 58 |
| Adoption | 93 | 100 |
| Activity | 100 | 100 |
| Community | 100 | 96 |
| Issue health | 34 | 96 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 90.5 | 93.3 |
dbt enables data analysts and engineers to transform their data using the same practices that software engineers use to build applications.
Plausible is a lightweight, cookie-less web analytics tool. The community edition can be self-hosted; the company also sells a managed service.
Plausible has more GitHub stars: 29,871 versus 14,183 for dbt. The gap is 15,688 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both dbt and Plausible 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. Plausible 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.
Plausible scores 93.3 and dbt scores 90.5. This page calls that a narrow lead for Plausible.