A
maestro
83.5
3,852 stars · Apache-2.0
Analytics
Umami leads by 15.6 · decisive
A
83.5
3,852 stars · Apache-2.0
B · leads
99.1
40,194 stars · MIT
maestro versus Umami is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. maestro is written mainly in Java; Umami is written mainly in TypeScript. The composite score is 83.5 for maestro and 99.1 for Umami.
Umami has 40,194 GitHub stars to maestro's 3,852, a gap of 36,342 (10.43×). Forks are 311 for maestro and 8,567 for Umami. On the log scale used inside this pair, adoption is 78 versus 100, and the fork community is 63 versus 100.
Push history: maestro was last pushed on 06 November 2026 (10 days ago), and Umami was last pushed on 17 November 2026 (0 days ago). Open issues stand at 37 for maestro (0.010 per star) and 136 for Umami (0.003 per star). Issue-health scores are 84 and 96; activity scores are 92 and 100.
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. Umami 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 96 for maestro and 96 for Umami. This is a procurement signal, not legal advice.
In Analytics, both maestro (3,852 stars) and Umami (40,194 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: maestro is open source, Umami is open source.
Umami is ahead on every scored dimension that is not level. Level dimensions: license flexibility, self-hosting. The widest gap is fork community at 37 points (63 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).
Umami finishes ahead at 99.1 against maestro at 83.5, a 15.6 point decisive 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 | maestro | Umami |
|---|---|---|
| GitHub stars | 3,852 | 40,194 |
| Forks | 311 | 8,567 |
| Open issues | 37 | 136 |
| Adoption | 78 | 100 |
| Activity | 92 | 100 |
| Community | 63 | 100 |
| Issue health | 84 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 83.5 | 99.1 |
Maestro: Netflix’s Workflow Orchestrator
Umami is a small web analytics product with a simple dashboard over page and event data. It is MIT-licensed and is usually chosen when a team wants a short self-hosted setup.
Umami has more GitHub stars: 40,194 versus 3,852 for maestro. The gap is 36,342 stars.
Umami was pushed more recently: 17 November 2026 versus 06 November 2026 for maestro. That is 10 days apart.
Yes. This catalog marks both maestro and Umami as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. Umami 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.
Umami scores 99.1 and maestro scores 83.5. This page calls that a decisive lead for Umami.