A
eventql
45.7
1,176 stars · license n/a
Analytics
langfuse leads by 41.1 · decisive
A
45.7
1,176 stars · license n/a
B · leads
86.8
37,546 stars · license n/a
eventql versus langfuse is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. eventql is written mainly in C++; langfuse is written mainly in TypeScript. The composite score is 45.7 for eventql and 86.8 for langfuse.
langfuse has 37,546 GitHub stars to eventql's 1,176, a gap of 36,370 (31.93×). Forks are 104 for eventql and 4,243 for langfuse. On the log scale used inside this pair, adoption is 67 versus 100, and the fork community is 56 versus 100.
Push history: eventql was last pushed on 06 May 2017 (3487 days ago), and langfuse was last pushed on 17 November 2026 (5 days ago). Open issues stand at 113 for eventql (0.096 per star) and 1,173 for langfuse (0.031 per star). Issue-health scores are 52 and 70; activity scores are 16 and 92.
eventql 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. 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. License scores in this pair are 30 for eventql and 30 for langfuse. This is a procurement signal, not legal advice.
Only langfuse is marked self-hostable here (37,546 stars, deploy score 100). eventql is not (1,176 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: eventql is unpriced in this catalog, langfuse is unpriced in this catalog.
langfuse is ahead on every scored dimension that is not level. Level dimensions: license flexibility. The widest gap is recent activity at 76 points (16 vs 92), and the tightest is license flexibility at 0 points (30 vs 30).
langfuse finishes ahead at 86.8 against eventql at 45.7, a 41.1 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 | eventql | langfuse |
|---|---|---|
| GitHub stars | 1,176 | 37,546 |
| Forks | 104 | 4,243 |
| Open issues | 113 | 1,173 |
| Adoption | 67 | 100 |
| Activity | 16 | 92 |
| Community | 56 | 100 |
| Issue health | 52 | 70 |
| License | 30 | 30 |
| Self-hosting | 35 | 100 |
| Composite | 45.7 | 86.8 |
Distributed "massively parallel" SQL query engine
🪢 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.
langfuse has more GitHub stars: 37,546 versus 1,176 for eventql. The gap is 36,370 stars.
langfuse was pushed more recently: 17 November 2026 versus 06 May 2017 for eventql. That is 3482 days apart.
Only langfuse is marked self-hostable. eventql is not.
eventql 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. 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
langfuse scores 86.8 and eventql scores 45.7. This page calls that a decisive lead for langfuse.