A
langfuse
88.6
37,546 stars · license n/a
Analytics
partytown leads by 1.8 · narrow
A
88.6
37,546 stars · license n/a
B · leads
90.4
13,817 stars · MIT
langfuse versus partytown 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 90.4 for partytown.
langfuse has 37,546 GitHub stars to partytown's 13,817, a gap of 23,729 (2.72×). Forks are 4,243 for langfuse and 460 for partytown. On the log scale used inside this pair, adoption is 100 versus 90, and the fork community is 100 versus 73.
Push history: langfuse was last pushed on 17 November 2026 (0 days ago), and partytown was last pushed on 09 November 2026 (8 days ago). Open issues stand at 1,173 for langfuse (0.031 per star) and 1 for partytown (0.000 per star). Issue-health scores are 70 and 96; activity scores are 100 and 92.
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. partytown 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 partytown. This is a procurement signal, not legal advice.
In Analytics, both langfuse (37,546 stars) and partytown (13,817 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, partytown is open source.
The lead is split. langfuse is furthest ahead on fork community (100 to 73), while partytown is furthest ahead on license flexibility (96 to 30). Choose the dimension a rollout cannot compromise on.
partytown finishes ahead at 90.4 against langfuse at 88.6, a 1.8 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 | partytown |
|---|---|---|
| GitHub stars | 37,546 | 13,817 |
| Forks | 4,243 | 460 |
| Open issues | 1,173 | 1 |
| Adoption | 100 | 90 |
| Activity | 100 | 92 |
| Community | 100 | 73 |
| Issue health | 70 | 96 |
| License | 30 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 88.6 | 90.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.
Relocate resource intensive third-party scripts off of the main thread and into a web worker. 🎉
langfuse has more GitHub stars: 37,546 versus 13,817 for partytown. The gap is 23,729 stars.
langfuse was pushed more recently: 17 November 2026 versus 09 November 2026 for partytown. That is 8 days apart.
Yes. This catalog marks both langfuse and partytown 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. partytown 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.
partytown scores 90.4 and langfuse scores 88.6. This page calls that a narrow lead for partytown.