Skip to content
DevUtils Online

Analytics

goatcounter vs langfuse

langfuse leads by 23.4 · decisive

B · leads

langfuse

88.6

37,546 stars · license n/a

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

langfuse has 37,546 GitHub stars to goatcounter's 6,171, a gap of 31,375 (6.08×). Forks are 288 for goatcounter and 4,243 for langfuse. On the log scale used inside this pair, adoption is 83 versus 100, and the fork community is 68 versus 100.

Push history: goatcounter was last pushed on 27 September 2026 (50 days ago), and langfuse was last pushed on 17 November 2026 (0 days ago). Open issues stand at 60 for goatcounter (0.010 per star) and 1,173 for langfuse (0.031 per star). Issue-health scores are 84 and 70; activity scores are 58 and 100.

goatcounter 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 goatcounter 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). goatcounter is not (6,171 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: goatcounter is unpriced in this catalog, langfuse is unpriced in this catalog.

The lead is split. goatcounter is furthest ahead on issue health (84 to 70), while langfuse is furthest ahead on self-hosting (100 to 35). Choose the dimension a rollout cannot compromise on.

langfuse finishes ahead at 88.6 against goatcounter at 65.2, a 23.4 point decisive 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.

goatcounter versus langfuse metrics
Signal goatcounter langfuse
GitHub stars 6,171 37,546
Forks 288 4,243
Open issues 60 1,173
Adoption 83 100
Activity 58 100
Community 68 100
Issue health 84 70
License 30 30
Self-hosting 35 100
Composite 65.2 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, goatcounter or langfuse?

langfuse has more GitHub stars: 37,546 versus 6,171 for goatcounter. The gap is 31,375 stars.

Which was updated more recently, goatcounter or langfuse?

langfuse was pushed more recently: 17 November 2026 versus 27 September 2026 for goatcounter. That is 50 days apart.

Can I self-host both goatcounter and langfuse?

Only langfuse is marked self-hostable. goatcounter is not.

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

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

Who wins the goatcounter vs langfuse score?

langfuse scores 88.6 and goatcounter scores 65.2. This page calls that a decisive lead for langfuse.

Related comparisons