A · leads
langfuse
88.6
37,546 stars · license n/a
Analytics
langfuse leads by 34.7 · decisive
A · leads
88.6
37,546 stars · license n/a
B
53.9
1,646 stars · license n/a
langfuse versus LocustDB 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; LocustDB is written mainly in Rust. The composite score is 88.6 for langfuse and 53.9 for LocustDB.
langfuse has 37,546 GitHub stars to LocustDB's 1,646, a gap of 35,900 (22.81×). Forks are 4,243 for langfuse and 75 for LocustDB. On the log scale used inside this pair, adoption is 100 versus 70, and the fork community is 100 versus 52.
Push history: langfuse was last pushed on 17 November 2026 (0 days ago), and LocustDB was last pushed on 23 April 2026 (208 days ago). Open issues stand at 1,173 for langfuse (0.031 per star) and 14 for LocustDB (0.009 per star). Issue-health scores are 70 and 84; 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. LocustDB 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 langfuse and 30 for LocustDB. This is a procurement signal, not legal advice.
Only langfuse is marked self-hostable here (37,546 stars, deploy score 100). LocustDB is not (1,646 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: langfuse is unpriced in this catalog, LocustDB is unpriced in this catalog.
The lead is split. langfuse is furthest ahead on self-hosting (100 to 35), while LocustDB is furthest ahead on issue health (84 to 70). Choose the dimension a rollout cannot compromise on.
langfuse finishes ahead at 88.6 against LocustDB at 53.9, a 34.7 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 | LocustDB |
|---|---|---|
| GitHub stars | 37,546 | 1,646 |
| Forks | 4,243 | 75 |
| Open issues | 1,173 | 14 |
| Adoption | 100 | 70 |
| Activity | 100 | 36 |
| Community | 100 | 52 |
| Issue health | 70 | 84 |
| License | 30 | 30 |
| Self-hosting | 100 | 35 |
| Composite | 88.6 | 53.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.
Blazingly fast analytics database that will rapidly devour all of your data.
langfuse has more GitHub stars: 37,546 versus 1,646 for LocustDB. The gap is 35,900 stars.
langfuse was pushed more recently: 17 November 2026 versus 23 April 2026 for LocustDB. That is 208 days apart.
Only langfuse is marked self-hostable. LocustDB is not.
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. LocustDB 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 88.6 and LocustDB scores 53.9. This page calls that a decisive lead for langfuse.