A · leads
langfuse
88.6
37,546 stars · license n/a
Analytics
langfuse leads by 5.2 · narrow
A · leads
88.6
37,546 stars · license n/a
B
83.4
3,123 stars · Apache-2.0
langfuse versus tianji is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Both projects are written mainly in TypeScript. The composite score is 88.6 for langfuse and 83.4 for tianji.
langfuse has 37,546 GitHub stars to tianji's 3,123, a gap of 34,423 (12.02×). Forks are 4,243 for langfuse and 200 for tianji. On the log scale used inside this pair, adoption is 100 versus 76, and the fork community is 100 versus 64.
Push history: langfuse was last pushed on 17 November 2026 (0 days ago), and tianji was last pushed on 16 November 2026 (1 day ago). Open issues stand at 1,173 for langfuse (0.031 per star) and 145 for tianji (0.046 per star). Issue-health scores are 70 and 70; 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. tianji 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 tianji. This is a procurement signal, not legal advice.
In Analytics, both langfuse (37,546 stars) and tianji (3,123 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, tianji is open source.
The lead is split. langfuse is furthest ahead on fork community (100 to 64), while tianji is furthest ahead on license flexibility (96 to 30). Choose the dimension a rollout cannot compromise on.
langfuse finishes ahead at 88.6 against tianji at 83.4, a 5.2 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 | tianji |
|---|---|---|
| GitHub stars | 37,546 | 3,123 |
| Forks | 4,243 | 200 |
| Open issues | 1,173 | 145 |
| Adoption | 100 | 76 |
| Activity | 100 | 100 |
| Community | 100 | 64 |
| Issue health | 70 | 70 |
| License | 30 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 88.6 | 83.4 |
🪢 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.
Tianji: Insight into everything, Website Analytics + Uptime Monitor + Server Status. not only another GA alternatives
langfuse has more GitHub stars: 37,546 versus 3,123 for tianji. The gap is 34,423 stars.
langfuse was pushed more recently: 17 November 2026 versus 16 November 2026 for tianji. That is 1 days apart.
Yes. This catalog marks both langfuse and tianji 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. tianji 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 tianji scores 83.4. This page calls that a narrow lead for langfuse.