A
langfuse
88.6
37,546 stars · license n/a
Analytics
uPlot leads by 1.6 · narrow
A
88.6
37,546 stars · license n/a
B · leads
90.2
10,650 stars · MIT
langfuse versus uPlot is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. langfuse is written mainly in TypeScript; uPlot is written mainly in JavaScript. The composite score is 88.6 for langfuse and 90.2 for uPlot.
langfuse has 37,546 GitHub stars to uPlot's 10,650, a gap of 26,896 (3.53×). Forks are 4,243 for langfuse and 472 for uPlot. On the log scale used inside this pair, adoption is 100 versus 88, and the fork community is 100 versus 74.
Push history: langfuse was last pushed on 17 November 2026 (0 days ago), and uPlot was last pushed on 17 November 2026 (0 days ago). Open issues stand at 1,173 for langfuse (0.031 per star) and 132 for uPlot (0.012 per star). Issue-health scores are 70 and 84; activity scores are 100 and 100.
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. uPlot is listed as MIT, 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. License scores in this pair are 30 for langfuse and 96 for uPlot. This is a procurement signal, not legal advice.
In Analytics, both langfuse (37,546 stars) and uPlot (10,650 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: langfuse is unpriced in this catalog, uPlot is open source.
The lead is split. langfuse is furthest ahead on fork community (100 to 74), while uPlot is furthest ahead on license flexibility (96 to 30). Choose the dimension a rollout cannot compromise on.
uPlot finishes ahead at 90.2 against langfuse at 88.6, a 1.6 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 | langfuse | uPlot |
|---|---|---|
| GitHub stars | 37,546 | 10,650 |
| Forks | 4,243 | 472 |
| Open issues | 1,173 | 132 |
| Adoption | 100 | 88 |
| Activity | 100 | 100 |
| Community | 100 | 74 |
| Issue health | 70 | 84 |
| License | 30 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 88.6 | 90.2 |
🪢 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.
📈 A small, fast chart for time series, lines, areas, ohlc & bars
langfuse has more GitHub stars: 37,546 versus 10,650 for uPlot. The gap is 26,896 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both langfuse and uPlot as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. uPlot is listed as MIT, 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
uPlot scores 90.2 and langfuse scores 88.6. This page calls that a narrow lead for uPlot.