Skip to content
DevUtils Online

Analytics

fathom vs langfuse

langfuse leads by 12.5 · clear

A

fathom

76.1

8,035 stars · MIT

B · leads

langfuse

88.6

37,546 stars · license n/a

fathom versus langfuse is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. fathom is written mainly in Go; langfuse is written mainly in TypeScript. The composite score is 76.1 for fathom and 88.6 for langfuse.

langfuse has 37,546 GitHub stars to fathom's 8,035, a gap of 29,511 (4.67×). Forks are 388 for fathom and 4,243 for langfuse. On the log scale used inside this pair, adoption is 85 versus 100, and the fork community is 71 versus 100.

Push history: fathom was last pushed on 18 March 2026 (244 days ago), and langfuse was last pushed on 17 November 2026 (0 days ago). Open issues stand at 5 for fathom (0.001 per star) and 1,173 for langfuse (0.031 per star). Issue-health scores are 96 and 70; activity scores are 36 and 100.

fathom is listed as MIT, 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. 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 96 for fathom and 30 for langfuse. This is a procurement signal, not legal advice.

In Analytics, both fathom (8,035 stars) and langfuse (37,546 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: fathom is open source, langfuse is unpriced in this catalog.

The lead is split. fathom is furthest ahead on license flexibility (96 to 30), while langfuse is furthest ahead on recent activity (100 to 36). Choose the dimension a rollout cannot compromise on.

langfuse finishes ahead at 88.6 against fathom at 76.1, a 12.5 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.

fathom versus langfuse metrics
Signal fathom langfuse
GitHub stars 8,035 37,546
Forks 388 4,243
Open issues 5 1,173
Adoption 85 100
Activity 36 100
Community 71 100
Issue health 96 70
License 96 30
Self-hosting 100 100
Composite 76.1 88.6

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, fathom or langfuse?

langfuse has more GitHub stars: 37,546 versus 8,035 for fathom. The gap is 29,511 stars.

Which was updated more recently, fathom or langfuse?

langfuse was pushed more recently: 17 November 2026 versus 18 March 2026 for fathom. That is 244 days apart.

Can I self-host both fathom and langfuse?

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

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

fathom is listed as MIT, 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. 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.

Who wins the fathom vs langfuse score?

langfuse scores 88.6 and fathom scores 76.1. This page calls that a clear lead for langfuse.

Related comparisons