A
langfuse
88.3
37,546 stars · license n/a
Analytics
PostHog leads by 6.2 · narrow
A
88.3
37,546 stars · license n/a
B · leads
94.5
40,849 stars · MIT
langfuse versus PostHog 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; PostHog is written mainly in Python. The composite score is 88.3 for langfuse and 94.5 for PostHog.
PostHog has 40,849 GitHub stars to langfuse's 37,546, a gap of 3,303 (1.09×). Forks are 4,243 for langfuse and 3,696 for PostHog. On the log scale used inside this pair, adoption is 99 versus 100, and the fork community is 100 versus 98.
Push history: langfuse was last pushed on 17 November 2026 (0 days ago), and PostHog was last pushed on 17 November 2026 (0 days ago). Open issues stand at 1,173 for langfuse (0.031 per star) and 4,463 for PostHog (0.109 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. PostHog 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. License scores in this pair are 30 for langfuse and 96 for PostHog. This is a procurement signal, not legal advice.
In Analytics, both langfuse (37,546 stars) and PostHog (40,849 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, PostHog is freemium.
The lead is split. langfuse is furthest ahead on issue health (70 to 52), while PostHog is furthest ahead on license flexibility (96 to 30). Choose the dimension a rollout cannot compromise on.
PostHog finishes ahead at 94.5 against langfuse at 88.3, a 6.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 | PostHog |
|---|---|---|
| GitHub stars | 37,546 | 40,849 |
| Forks | 4,243 | 3,696 |
| Open issues | 1,173 | 4,463 |
| Adoption | 99 | 100 |
| Activity | 100 | 100 |
| Community | 100 | 98 |
| Issue health | 70 | 52 |
| License | 30 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 88.3 | 94.5 |
🪢 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.
PostHog is a product-analytics suite: events, funnels, session replay, and feature flags. The core is open source and most teams choose between self-hosting and PostHog Cloud.
PostHog has more GitHub stars: 40,849 versus 37,546 for langfuse. The gap is 3,303 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both langfuse and PostHog 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. PostHog 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
PostHog scores 94.5 and langfuse scores 88.3. This page calls that a narrow lead for PostHog.