A · level
dbt
89.0
14,183 stars · Apache-2.0
Analytics
Too close to call · 89.0 to 88.6
A · level
89.0
14,183 stars · Apache-2.0
B · level
88.6
37,546 stars · license n/a
dbt versus langfuse 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; langfuse is written mainly in TypeScript. The composite score is 89.0 for dbt and 88.6 for langfuse.
langfuse has 37,546 GitHub stars to dbt's 14,183, a gap of 23,363 (2.65×). Forks are 2,679 for dbt and 4,243 for langfuse. On the log scale used inside this pair, adoption is 91 versus 100, and the fork community is 94 versus 100.
Push history: dbt was last pushed on 17 November 2026 (0 days ago), and langfuse was last pushed on 17 November 2026 (0 days ago). Open issues stand at 1,915 for dbt (0.135 per star) and 1,173 for langfuse (0.031 per star). Issue-health scores are 34 and 70; 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. langfuse is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. License scores in this pair are 96 for dbt and 30 for langfuse. This is a procurement signal, not legal advice.
In Analytics, both dbt (14,183 stars) and langfuse (37,546 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, langfuse is unpriced in this catalog.
The lead is split. dbt is furthest ahead on license flexibility (96 to 30), while langfuse is furthest ahead on issue health (70 to 34). Choose the dimension a rollout cannot compromise on.
Composite score: dbt 89.0, langfuse 88.6. The margin is under one point, so this page calls a tie. Use the dimension breakdown rather than the headline number.
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 | langfuse |
|---|---|---|
| GitHub stars | 14,183 | 37,546 |
| Forks | 2,679 | 4,243 |
| Open issues | 1,915 | 1,173 |
| Adoption | 91 | 100 |
| Activity | 100 | 100 |
| Community | 94 | 100 |
| Issue health | 34 | 70 |
| License | 96 | 30 |
| Self-hosting | 100 | 100 |
| Composite | 89.0 | 88.6 |
dbt enables data analysts and engineers to transform their data using the same practices that software engineers use to build applications.
🪢 Open source AI engineering platform: AI Gateway, agent observability, evals, and prompt/skill management, built on OpenTelemetry. One open platform for every AI call and every agent. Self-host or use Langfuse Cloud.
langfuse has more GitHub stars: 37,546 versus 14,183 for dbt. The gap is 23,363 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both dbt and langfuse 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. langfuse is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Neither tool clears a one-point margin. dbt scores 89.0 and langfuse scores 88.6.