Skip to content
DevUtils Online

Analytics

langfuse vs rotki

langfuse leads by 9.1 · clear

A · leads

langfuse

88.6

37,546 stars · license n/a

B

rotki

79.5

4,093 stars · AGPL-3.0

langfuse versus rotki 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; rotki is written mainly in Python. The composite score is 88.6 for langfuse and 79.5 for rotki.

langfuse has 37,546 GitHub stars to rotki's 4,093, a gap of 33,453 (9.17×). Forks are 4,243 for langfuse and 791 for rotki. On the log scale used inside this pair, adoption is 100 versus 79, and the fork community is 100 versus 80.

Push history: langfuse was last pushed on 17 November 2026 (0 days ago), and rotki was last pushed on 17 November 2026 (0 days ago). Open issues stand at 1,173 for langfuse (0.031 per star) and 353 for rotki (0.086 per star). Issue-health scores are 70 and 52; 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. rotki is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. License scores in this pair are 30 for langfuse and 52 for rotki. This is a procurement signal, not legal advice.

In Analytics, both langfuse (37,546 stars) and rotki (4,093 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, rotki is open source.

The lead is split. langfuse is furthest ahead on adoption (100 to 79), while rotki is furthest ahead on license flexibility (52 to 30). Choose the dimension a rollout cannot compromise on.

langfuse finishes ahead at 88.6 against rotki at 79.5, a 9.1 point clear margin under the published weights.

Scores are computed inside this pair only. Method and weights.

Where they separate

The numbers

Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.

langfuse versus rotki metrics
Signal langfuse rotki
GitHub stars 37,546 4,093
Forks 4,243 791
Open issues 1,173 353
Adoption 100 79
Activity 100 100
Community 100 80
Issue health 70 52
License 30 52
Self-hosting 100 100
Composite 88.6 79.5

langfuse

🪢 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.

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, langfuse or rotki?

langfuse has more GitHub stars: 37,546 versus 4,093 for rotki. The gap is 33,453 stars.

Which was updated more recently, langfuse or rotki?

Both were last pushed on 17 November 2026.

Can I self-host both langfuse and rotki?

Yes. This catalog marks both langfuse and rotki as self-hostable. Confirm each project's deploy docs before you plan a migration.

Which license is easier to embed in a commercial product, langfuse or rotki?

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. rotki is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. Read both grants before you embed either codebase in a hosted product. This is not legal advice.

Who wins the langfuse vs rotki score?

langfuse scores 88.6 and rotki scores 79.5. This page calls that a clear lead for langfuse.

Related comparisons