A · leads
langfuse
88.6
37,546 stars · license n/a
Analytics
langfuse leads by 4.2 · narrow
A · leads
88.6
37,546 stars · license n/a
B
84.4
3,852 stars · Apache-2.0
langfuse versus maestro 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; maestro is written mainly in Java. The composite score is 88.6 for langfuse and 84.4 for maestro.
langfuse has 37,546 GitHub stars to maestro's 3,852, a gap of 33,694 (9.75×). Forks are 4,243 for langfuse and 311 for maestro. On the log scale used inside this pair, adoption is 100 versus 78, and the fork community is 100 versus 69.
Push history: langfuse was last pushed on 17 November 2026 (0 days ago), and maestro was last pushed on 06 November 2026 (10 days ago). Open issues stand at 1,173 for langfuse (0.031 per star) and 37 for maestro (0.010 per star). Issue-health scores are 70 and 84; 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. maestro is listed as Apache-2.0, 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 maestro. This is a procurement signal, not legal advice.
In Analytics, both langfuse (37,546 stars) and maestro (3,852 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, maestro is open source.
The lead is split. langfuse is furthest ahead on fork community (100 to 69), while maestro is furthest ahead on license flexibility (96 to 30). Choose the dimension a rollout cannot compromise on.
langfuse finishes ahead at 88.6 against maestro at 84.4, a 4.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 | maestro |
|---|---|---|
| GitHub stars | 37,546 | 3,852 |
| Forks | 4,243 | 311 |
| Open issues | 1,173 | 37 |
| Adoption | 100 | 78 |
| Activity | 100 | 92 |
| Community | 100 | 69 |
| Issue health | 70 | 84 |
| License | 30 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 88.6 | 84.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.
Maestro: Netflix’s Workflow Orchestrator
langfuse has more GitHub stars: 37,546 versus 3,852 for maestro. The gap is 33,694 stars.
langfuse was pushed more recently: 17 November 2026 versus 06 November 2026 for maestro. That is 10 days apart.
Yes. This catalog marks both langfuse and maestro 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. maestro is listed as Apache-2.0, 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.
langfuse scores 88.6 and maestro scores 84.4. This page calls that a narrow lead for langfuse.