A
amplify-cli
80.8
2,875 stars · Apache-2.0
Analytics
Umami leads by 18.3 · decisive
A
80.8
2,875 stars · Apache-2.0
B · leads
99.1
40,194 stars · MIT
amplify-cli versus Umami 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 80.8 for amplify-cli and 99.1 for Umami.
Umami has 40,194 GitHub stars to amplify-cli's 2,875, a gap of 37,319 (13.98×). Forks are 826 for amplify-cli and 8,567 for Umami. On the log scale used inside this pair, adoption is 75 versus 100, and the fork community is 74 versus 100.
Push history: amplify-cli was last pushed on 16 November 2026 (1 day ago), and Umami was last pushed on 17 November 2026 (0 days ago). Open issues stand at 882 for amplify-cli (0.307 per star) and 136 for Umami (0.003 per star). Issue-health scores are 34 and 96; activity scores are 100 and 100.
amplify-cli 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 amplify-cli and 96 for Umami. This is a procurement signal, not legal advice.
In Analytics, both amplify-cli (2,875 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: amplify-cli is open source, Umami is open source.
Umami is ahead on every scored dimension that is not level. Level dimensions: recent activity, license flexibility, self-hosting. The widest gap is issue health at 62 points (34 vs 96), and the tightest is self-hosting at 0 points (100 vs 100).
Umami finishes ahead at 99.1 against amplify-cli at 80.8, a 18.3 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 | amplify-cli | Umami |
|---|---|---|
| GitHub stars | 2,875 | 40,194 |
| Forks | 826 | 8,567 |
| Open issues | 882 | 136 |
| Adoption | 75 | 100 |
| Activity | 100 | 100 |
| Community | 74 | 100 |
| Issue health | 34 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 80.8 | 99.1 |
The AWS Amplify CLI is a toolchain for simplifying serverless web and mobile development.
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 2,875 for amplify-cli. The gap is 37,319 stars.
Umami was pushed more recently: 17 November 2026 versus 16 November 2026 for amplify-cli. That is 1 days apart.
Yes. This catalog marks both amplify-cli and Umami as self-hostable. Confirm each project's deploy docs before you plan a migration.
amplify-cli 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 amplify-cli scores 80.8. This page calls that a decisive lead for Umami.