A
langfuse
88.4
37,546 stars · license n/a
Analytics
redash leads by 7.3 · clear
A
88.4
37,546 stars · license n/a
B · leads
95.7
28,887 stars · BSD-2-Clause
langfuse versus redash 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.4 for langfuse and 95.7 for redash.
langfuse has 37,546 GitHub stars to redash's 28,887, a gap of 8,659 (1.30×). Forks are 4,243 for langfuse and 4,645 for redash. On the log scale used inside this pair, adoption is 100 versus 98, and the fork community is 99 versus 100.
Push history: langfuse was last pushed on 17 November 2026 (0 days ago), and redash was last pushed on 14 November 2026 (3 days ago). Open issues stand at 1,173 for langfuse (0.031 per star) and 780 for redash (0.027 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. redash is listed as BSD-2-Clause, 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 redash. This is a procurement signal, not legal advice.
In Analytics, both langfuse (37,546 stars) and redash (28,887 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, redash is open source.
The lead is split. langfuse is furthest ahead on adoption (100 to 98), while redash is furthest ahead on license flexibility (96 to 30). Choose the dimension a rollout cannot compromise on.
redash finishes ahead at 95.7 against langfuse at 88.4, a 7.3 point clear 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 | redash |
|---|---|---|
| GitHub stars | 37,546 | 28,887 |
| Forks | 4,243 | 4,645 |
| Open issues | 1,173 | 780 |
| Adoption | 100 | 98 |
| Activity | 100 | 100 |
| Community | 99 | 100 |
| Issue health | 70 | 70 |
| License | 30 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 88.4 | 95.7 |
🪢 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.
Make Your Company Data Driven. Connect to any data source, easily visualize, dashboard and share your data.
langfuse has more GitHub stars: 37,546 versus 28,887 for redash. The gap is 8,659 stars.
langfuse was pushed more recently: 17 November 2026 versus 14 November 2026 for redash. That is 3 days apart.
Yes. This catalog marks both langfuse and redash 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. redash is listed as BSD-2-Clause, 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.
redash scores 95.7 and langfuse scores 88.4. This page calls that a clear lead for redash.