A
bruin
80.5
1,813 stars · Apache-2.0
Analytics
langfuse leads by 8.1 · clear
A
80.5
1,813 stars · Apache-2.0
B · leads
88.6
37,546 stars · license n/a
bruin versus langfuse is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. bruin is written mainly in Go; langfuse is written mainly in TypeScript. The composite score is 80.5 for bruin and 88.6 for langfuse.
langfuse has 37,546 GitHub stars to bruin's 1,813, a gap of 35,733 (20.71×). Forks are 101 for bruin and 4,243 for langfuse. On the log scale used inside this pair, adoption is 71 versus 100, and the fork community is 55 versus 100.
Push history: bruin 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 69 for bruin (0.038 per star) and 1,173 for langfuse (0.031 per star). Issue-health scores are 70 and 70; activity scores are 100 and 100.
bruin 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 bruin and 30 for langfuse. This is a procurement signal, not legal advice.
In Analytics, both bruin (1,813 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: bruin is open source, langfuse is unpriced in this catalog.
The lead is split. bruin is furthest ahead on license flexibility (96 to 30), while langfuse is furthest ahead on fork community (100 to 55). Choose the dimension a rollout cannot compromise on.
langfuse finishes ahead at 88.6 against bruin at 80.5, a 8.1 point clear 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 | bruin | langfuse |
|---|---|---|
| GitHub stars | 1,813 | 37,546 |
| Forks | 101 | 4,243 |
| Open issues | 69 | 1,173 |
| Adoption | 71 | 100 |
| Activity | 100 | 100 |
| Community | 55 | 100 |
| Issue health | 70 | 70 |
| License | 96 | 30 |
| Self-hosting | 100 | 100 |
| Composite | 80.5 | 88.6 |
Build data pipelines with SQL and Python, ingest data from different sources, add quality checks, and build end-to-end flows.
🪢 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,813 for bruin. The gap is 35,733 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both bruin and langfuse as self-hostable. Confirm each project's deploy docs before you plan a migration.
bruin 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 bruin scores 80.5. This page calls that a clear lead for langfuse.