A
lago
87.1
10,891 stars · AGPL-3.0
Analytics
langfuse leads by 1.5 · narrow
A
87.1
10,891 stars · AGPL-3.0
B · leads
88.6
37,546 stars · license n/a
lago versus langfuse is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. lago is written mainly in Go; langfuse is written mainly in TypeScript. The composite score is 87.1 for lago and 88.6 for langfuse.
langfuse has 37,546 GitHub stars to lago's 10,891, a gap of 26,655 (3.45×). Forks are 798 for lago and 4,243 for langfuse. On the log scale used inside this pair, adoption is 88 versus 100, and the fork community is 80 versus 100.
Push history: lago 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 17 for lago (0.002 per star) and 1,173 for langfuse (0.031 per star). Issue-health scores are 96 and 70; activity scores are 100 and 100.
lago 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. 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 52 for lago and 30 for langfuse. This is a procurement signal, not legal advice.
In Analytics, both lago (10,891 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: lago is open source, langfuse is unpriced in this catalog.
The lead is split. lago is furthest ahead on issue health (96 to 70), while langfuse is furthest ahead on fork community (100 to 80). Choose the dimension a rollout cannot compromise on.
langfuse finishes ahead at 88.6 against lago at 87.1, a 1.5 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 | lago | langfuse |
|---|---|---|
| GitHub stars | 10,891 | 37,546 |
| Forks | 798 | 4,243 |
| Open issues | 17 | 1,173 |
| Adoption | 88 | 100 |
| Activity | 100 | 100 |
| Community | 80 | 100 |
| Issue health | 96 | 70 |
| License | 52 | 30 |
| Self-hosting | 100 | 100 |
| Composite | 87.1 | 88.6 |
Open Source Metering and Usage Based Billing API ⭐️ Consumption tracking, Subscription management, Pricing iterations, Payment orchestration & Revenue analytics
🪢 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 10,891 for lago. The gap is 26,655 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both lago and langfuse as self-hostable. Confirm each project's deploy docs before you plan a migration.
lago 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. 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 lago scores 87.1. This page calls that a narrow lead for langfuse.