A · level
langfuse
88.6
37,546 stars · license n/a
Analytics
Too close to call · 88.6 to 89.5
A · level
88.6
37,546 stars · license n/a
B · level
89.5
13,520 stars · Apache-2.0
langfuse versus trino 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; trino is written mainly in Java. The composite score is 88.6 for langfuse and 89.5 for trino.
langfuse has 37,546 GitHub stars to trino's 13,520, a gap of 24,026 (2.78×). Forks are 4,243 for langfuse and 3,880 for trino. On the log scale used inside this pair, adoption is 100 versus 90, and the fork community is 100 versus 99.
Push history: langfuse was last pushed on 17 November 2026 (0 days ago), and trino was last pushed on 17 November 2026 (0 days ago). Open issues stand at 1,173 for langfuse (0.031 per star) and 2,758 for trino (0.204 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. trino 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 trino. This is a procurement signal, not legal advice.
In Analytics, both langfuse (37,546 stars) and trino (13,520 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, trino is open source.
The lead is split. langfuse is furthest ahead on issue health (70 to 34), while trino is furthest ahead on license flexibility (96 to 30). Choose the dimension a rollout cannot compromise on.
Composite score: langfuse 88.6, trino 89.5. The margin is under one point, so this page calls a tie. Use the dimension breakdown rather than the headline number.
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 | trino |
|---|---|---|
| GitHub stars | 37,546 | 13,520 |
| Forks | 4,243 | 3,880 |
| Open issues | 1,173 | 2,758 |
| Adoption | 100 | 90 |
| Activity | 100 | 100 |
| Community | 100 | 99 |
| Issue health | 70 | 34 |
| License | 30 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 88.6 | 89.5 |
🪢 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.
Official repository of Trino, the distributed SQL query engine for big data, formerly known as PrestoSQL (https://trino.io)
langfuse has more GitHub stars: 37,546 versus 13,520 for trino. The gap is 24,026 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both langfuse and trino 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. trino 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.
Neither tool clears a one-point margin. langfuse scores 88.6 and trino scores 89.5.