A
analytics
69.3
2,671 stars · MIT
Analytics
langfuse leads by 19.3 · decisive
A
69.3
2,671 stars · MIT
B · leads
88.6
37,546 stars · license n/a
analytics versus langfuse is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. analytics is written mainly in JavaScript; langfuse is written mainly in TypeScript. The composite score is 69.3 for analytics and 88.6 for langfuse.
langfuse has 37,546 GitHub stars to analytics's 2,671, a gap of 34,875 (14.06×). Forks are 266 for analytics and 4,243 for langfuse. On the log scale used inside this pair, adoption is 75 versus 100, and the fork community is 67 versus 100.
Push history: analytics was last pushed on 27 June 2026 (142 days ago), and langfuse was last pushed on 17 November 2026 (0 days ago). Open issues stand at 116 for analytics (0.043 per star) and 1,173 for langfuse (0.031 per star). Issue-health scores are 70 and 70; activity scores are 36 and 100.
analytics 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. 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 analytics and 30 for langfuse. This is a procurement signal, not legal advice.
In Analytics, both analytics (2,671 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: analytics is open source, langfuse is unpriced in this catalog.
The lead is split. analytics is furthest ahead on license flexibility (96 to 30), while langfuse is furthest ahead on recent activity (100 to 36). Choose the dimension a rollout cannot compromise on.
langfuse finishes ahead at 88.6 against analytics at 69.3, a 19.3 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 | analytics | langfuse |
|---|---|---|
| GitHub stars | 2,671 | 37,546 |
| Forks | 266 | 4,243 |
| Open issues | 116 | 1,173 |
| Adoption | 75 | 100 |
| Activity | 36 | 100 |
| Community | 67 | 100 |
| Issue health | 70 | 70 |
| License | 96 | 30 |
| Self-hosting | 100 | 100 |
| Composite | 69.3 | 88.6 |
Lightweight analytics abstraction layer for tracking page views, custom events, & identifying visitors
🪢 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 2,671 for analytics. The gap is 34,875 stars.
langfuse was pushed more recently: 17 November 2026 versus 27 June 2026 for analytics. That is 142 days apart.
Yes. This catalog marks both analytics and langfuse as self-hostable. Confirm each project's deploy docs before you plan a migration.
analytics 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. 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 analytics scores 69.3. This page calls that a decisive lead for langfuse.