A · leads
langfuse
88.6
37,546 stars · license n/a
Analytics
langfuse leads by 6.7 · narrow
A · leads
88.6
37,546 stars · license n/a
B
81.9
2,389 stars · Apache-2.0
langfuse versus quary 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; quary is written mainly in Rust. The composite score is 88.6 for langfuse and 81.9 for quary.
langfuse has 37,546 GitHub stars to quary's 2,389, a gap of 35,157 (15.72×). Forks are 4,243 for langfuse and 58 for quary. On the log scale used inside this pair, adoption is 100 versus 74, and the fork community is 100 versus 49.
Push history: langfuse was last pushed on 17 November 2026 (0 days ago), and quary was last pushed on 16 November 2026 (1 day ago). Open issues stand at 1,173 for langfuse (0.031 per star) and 45 for quary (0.019 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. quary 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 quary. This is a procurement signal, not legal advice.
In Analytics, both langfuse (37,546 stars) and quary (2,389 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, quary is open source.
The lead is split. langfuse is furthest ahead on fork community (100 to 49), while quary is furthest ahead on license flexibility (96 to 30). Choose the dimension a rollout cannot compromise on.
langfuse finishes ahead at 88.6 against quary at 81.9, a 6.7 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 | quary |
|---|---|---|
| GitHub stars | 37,546 | 2,389 |
| Forks | 4,243 | 58 |
| Open issues | 1,173 | 45 |
| Adoption | 100 | 74 |
| Activity | 100 | 100 |
| Community | 100 | 49 |
| Issue health | 70 | 84 |
| License | 30 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 88.6 | 81.9 |
🪢 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.
Open-source BI for engineers
langfuse has more GitHub stars: 37,546 versus 2,389 for quary. The gap is 35,157 stars.
langfuse was pushed more recently: 17 November 2026 versus 16 November 2026 for quary. That is 1 days apart.
Yes. This catalog marks both langfuse and quary 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. quary 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 quary scores 81.9. This page calls that a narrow lead for langfuse.