A
dremio-oss
64.0
1,500 stars · Apache-2.0
Analytics
langfuse leads by 24.6 · decisive
A
64.0
1,500 stars · Apache-2.0
B · leads
88.6
37,546 stars · license n/a
dremio-oss versus langfuse 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; langfuse is written mainly in TypeScript. The composite score is 64.0 for dremio-oss and 88.6 for langfuse.
langfuse has 37,546 GitHub stars to dremio-oss's 1,500, a gap of 36,046 (25.03×). Forks are 474 for dremio-oss and 4,243 for langfuse. On the log scale used inside this pair, adoption is 69 versus 100, and the fork community is 74 versus 100.
Push history: dremio-oss was last pushed on 26 September 2025 (417 days ago), and langfuse was last pushed on 17 November 2026 (0 days ago). Open issues stand at 56 for dremio-oss (0.037 per star) and 1,173 for langfuse (0.031 per star). Issue-health scores are 70 and 70; 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. 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 dremio-oss and 30 for langfuse. This is a procurement signal, not legal advice.
In Analytics, both dremio-oss (1,500 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: dremio-oss is open source, langfuse is unpriced in this catalog.
The lead is split. dremio-oss is furthest ahead on license flexibility (96 to 30), while langfuse is furthest ahead on recent activity (100 to 16). Choose the dimension a rollout cannot compromise on.
langfuse finishes ahead at 88.6 against dremio-oss at 64.0, a 24.6 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 | langfuse |
|---|---|---|
| GitHub stars | 1,500 | 37,546 |
| Forks | 474 | 4,243 |
| Open issues | 56 | 1,173 |
| Adoption | 69 | 100 |
| Activity | 16 | 100 |
| Community | 74 | 100 |
| Issue health | 70 | 70 |
| License | 96 | 30 |
| Self-hosting | 100 | 100 |
| Composite | 64.0 | 88.6 |
Dremio - the missing link in modern data
🪢 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 1,500 for dremio-oss. The gap is 36,046 stars.
langfuse 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 langfuse 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. 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.
langfuse scores 88.6 and dremio-oss scores 64.0. This page calls that a decisive lead for langfuse.