A · leads
langfuse
88.6
37,546 stars · license n/a
Analytics
langfuse leads by 18.9 · decisive
A · leads
88.6
37,546 stars · license n/a
B
69.7
3,436 stars · Apache-2.0
langfuse versus roapi is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. langfuse is written mainly in TypeScript; roapi is written mainly in Rust. The composite score is 88.6 for langfuse and 69.7 for roapi.
langfuse has 37,546 GitHub stars to roapi's 3,436, a gap of 34,110 (10.93×). Forks are 4,243 for langfuse and 212 for roapi. On the log scale used inside this pair, adoption is 100 versus 77, and the fork community is 100 versus 64.
Push history: langfuse was last pushed on 17 November 2026 (0 days ago), and roapi was last pushed on 25 March 2026 (237 days ago). Open issues stand at 1,173 for langfuse (0.031 per star) and 83 for roapi (0.024 per star). Issue-health scores are 70 and 70; activity scores are 100 and 36.
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. roapi 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 roapi. This is a procurement signal, not legal advice.
In Analytics, both langfuse (37,546 stars) and roapi (3,436 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, roapi is open source.
The lead is split. langfuse is furthest ahead on recent activity (100 to 36), while roapi is furthest ahead on license flexibility (96 to 30). Choose the dimension a rollout cannot compromise on.
langfuse finishes ahead at 88.6 against roapi at 69.7, a 18.9 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 | roapi |
|---|---|---|
| GitHub stars | 37,546 | 3,436 |
| Forks | 4,243 | 212 |
| Open issues | 1,173 | 83 |
| Adoption | 100 | 77 |
| Activity | 100 | 36 |
| Community | 100 | 64 |
| Issue health | 70 | 70 |
| License | 30 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 88.6 | 69.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.
Create full-fledged APIs for slowly moving datasets without writing a single line of code.
langfuse has more GitHub stars: 37,546 versus 3,436 for roapi. The gap is 34,110 stars.
langfuse was pushed more recently: 17 November 2026 versus 25 March 2026 for roapi. That is 237 days apart.
Yes. This catalog marks both langfuse and roapi 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. roapi 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.
langfuse scores 88.6 and roapi scores 69.7. This page calls that a decisive lead for langfuse.