A · leads
langfuse
88.6
37,546 stars · license n/a
Analytics
langfuse leads by 17.4 · decisive
A · leads
88.6
37,546 stars · license n/a
B
71.2
2,020 stars · license n/a
langfuse versus nao 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 71.2 for nao.
langfuse has 37,546 GitHub stars to nao's 2,020, a gap of 35,526 (18.59×). Forks are 4,243 for langfuse and 305 for nao. On the log scale used inside this pair, adoption is 100 versus 72, and the fork community is 100 versus 68.
Push history: langfuse was last pushed on 17 November 2026 (0 days ago), and nao was last pushed on 17 November 2026 (0 days ago). Open issues stand at 1,173 for langfuse (0.031 per star) and 381 for nao (0.189 per star). Issue-health scores are 70 and 34; 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. nao 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 30 for langfuse and 30 for nao. This is a procurement signal, not legal advice.
In Analytics, both langfuse (37,546 stars) and nao (2,020 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, nao is unpriced in this catalog.
langfuse is ahead on every scored dimension that is not level. Level dimensions: recent activity, license flexibility, self-hosting. The widest gap is issue health at 36 points (70 vs 34), and the tightest is self-hosting at 0 points (100 vs 100).
langfuse finishes ahead at 88.6 against nao at 71.2, a 17.4 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 | langfuse | nao |
|---|---|---|
| GitHub stars | 37,546 | 2,020 |
| Forks | 4,243 | 305 |
| Open issues | 1,173 | 381 |
| Adoption | 100 | 72 |
| Activity | 100 | 100 |
| Community | 100 | 68 |
| Issue health | 70 | 34 |
| License | 30 | 30 |
| Self-hosting | 100 | 100 |
| Composite | 88.6 | 71.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.
👾 nao is the #1 open source agentic BI. (1) Create context with nao-core cli, (2) deploy nao chat interface for everyone
langfuse has more GitHub stars: 37,546 versus 2,020 for nao. The gap is 35,526 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both langfuse and nao 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. nao 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 nao scores 71.2. This page calls that a decisive lead for langfuse.