A
auto_ml
60.9
1,651 stars · MIT
Analytics
Umami leads by 38.2 · decisive
A
60.9
1,651 stars · MIT
B · leads
99.1
40,194 stars · MIT
auto_ml versus Umami is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. auto_ml is written mainly in Python; Umami is written mainly in TypeScript. The composite score is 60.9 for auto_ml and 99.1 for Umami.
Umami has 40,194 GitHub stars to auto_ml's 1,651, a gap of 38,543 (24.35×). Forks are 304 for auto_ml and 8,567 for Umami. On the log scale used inside this pair, adoption is 70 versus 100, and the fork community is 63 versus 100.
Push history: auto_ml was last pushed on 10 February 2021 (2106 days ago), and Umami was last pushed on 17 November 2026 (0 days ago). Open issues stand at 187 for auto_ml (0.113 per star) and 136 for Umami (0.003 per star). Issue-health scores are 52 and 96; activity scores are 16 and 100.
Both auto_ml and Umami are listed as MIT. 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. The license score is therefore level at 96 versus 96, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.
In Analytics, both auto_ml (1,651 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: auto_ml 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 recent activity at 84 points (16 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).
Umami finishes ahead at 99.1 against auto_ml at 60.9, a 38.2 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 | auto_ml | Umami |
|---|---|---|
| GitHub stars | 1,651 | 40,194 |
| Forks | 304 | 8,567 |
| Open issues | 187 | 136 |
| Adoption | 70 | 100 |
| Activity | 16 | 100 |
| Community | 63 | 100 |
| Issue health | 52 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 60.9 | 99.1 |
[UNMAINTAINED] Automated machine learning for analytics & production
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 1,651 for auto_ml. The gap is 38,543 stars.
Umami was pushed more recently: 17 November 2026 versus 10 February 2021 for auto_ml. That is 2106 days apart.
Yes. This catalog marks both auto_ml and Umami as self-hostable. Confirm each project's deploy docs before you plan a migration.
auto_ml 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. 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 auto_ml scores 60.9. This page calls that a decisive lead for Umami.