Skip to content
DevUtils Online

Analytics

langfuse vs lmnr

langfuse leads by 4.4 · narrow

A · leads

langfuse

88.6

37,546 stars · license n/a

B

lmnr

84.2

3,501 stars · Apache-2.0

langfuse versus lmnr is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Both projects are written mainly in TypeScript. The composite score is 88.6 for langfuse and 84.2 for lmnr.

langfuse has 37,546 GitHub stars to lmnr's 3,501, a gap of 34,045 (10.72×). Forks are 4,243 for langfuse and 263 for lmnr. On the log scale used inside this pair, adoption is 100 versus 78, and the fork community is 100 versus 67.

Push history: langfuse was last pushed on 17 November 2026 (0 days ago), and lmnr was last pushed on 17 November 2026 (0 days ago). Open issues stand at 1,173 for langfuse (0.031 per star) and 173 for lmnr (0.049 per star). Issue-health scores are 70 and 70; 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. lmnr 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. License scores in this pair are 30 for langfuse and 96 for lmnr. This is a procurement signal, not legal advice.

In Analytics, both langfuse (37,546 stars) and lmnr (3,501 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, lmnr is open source.

The lead is split. langfuse is furthest ahead on fork community (100 to 67), while lmnr is furthest ahead on license flexibility (96 to 30). Choose the dimension a rollout cannot compromise on.

langfuse finishes ahead at 88.6 against lmnr at 84.2, a 4.4 point narrow margin under the published weights.

Scores are computed inside this pair only. Method and weights.

Where they separate

The numbers

Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.

langfuse versus lmnr metrics
Signal langfuse lmnr
GitHub stars 37,546 3,501
Forks 4,243 263
Open issues 1,173 173
Adoption 100 78
Activity 100 100
Community 100 67
Issue health 70 70
License 30 96
Self-hosting 100 100
Composite 88.6 84.2

langfuse

🪢 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.

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, langfuse or lmnr?

langfuse has more GitHub stars: 37,546 versus 3,501 for lmnr. The gap is 34,045 stars.

Which was updated more recently, langfuse or lmnr?

Both were last pushed on 17 November 2026.

Can I self-host both langfuse and lmnr?

Yes. This catalog marks both langfuse and lmnr as self-hostable. Confirm each project's deploy docs before you plan a migration.

Which license is easier to embed in a commercial product, langfuse or lmnr?

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. lmnr 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.

Who wins the langfuse vs lmnr score?

langfuse scores 88.6 and lmnr scores 84.2. This page calls that a narrow lead for langfuse.

Related comparisons