A · leads
langfuse
88.6
37,546 stars · license n/a
Analytics
langfuse leads by 4.6 · narrow
A · leads
88.6
37,546 stars · license n/a
B
84.0
13,157 stars · license n/a
langfuse versus openreplay 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.0 for openreplay.
langfuse has 37,546 GitHub stars to openreplay's 13,157, a gap of 24,389 (2.85×). Forks are 4,243 for langfuse and 891 for openreplay. On the log scale used inside this pair, adoption is 100 versus 90, and the fork community is 100 versus 81.
Push history: langfuse was last pushed on 17 November 2026 (0 days ago), and openreplay was last pushed on 17 November 2026 (0 days ago). Open issues stand at 1,173 for langfuse (0.031 per star) and 193 for openreplay (0.015 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. openreplay 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 openreplay. This is a procurement signal, not legal advice.
In Analytics, both langfuse (37,546 stars) and openreplay (13,157 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, openreplay is unpriced in this catalog.
The lead is split. langfuse is furthest ahead on fork community (100 to 81), while openreplay is furthest ahead on issue health (84 to 70). Choose the dimension a rollout cannot compromise on.
langfuse finishes ahead at 88.6 against openreplay at 84.0, a 4.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 | openreplay |
|---|---|---|
| GitHub stars | 37,546 | 13,157 |
| Forks | 4,243 | 891 |
| Open issues | 1,173 | 193 |
| Adoption | 100 | 90 |
| Activity | 100 | 100 |
| Community | 100 | 81 |
| Issue health | 70 | 84 |
| License | 30 | 30 |
| Self-hosting | 100 | 100 |
| Composite | 88.6 | 84.0 |
🪢 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.
Session replay, cobrowsing and product analytics you can self-host. Best for reproducing issues and iterating on your product.
langfuse has more GitHub stars: 37,546 versus 13,157 for openreplay. The gap is 24,389 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both langfuse and openreplay 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. openreplay 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 openreplay scores 84.0. This page calls that a narrow lead for langfuse.