Skip to content
DevUtils Online

Analytics

amplify-js vs Umami

Umami leads by 11.1 · clear

B · leads

Umami

99.1

40,194 stars · MIT

amplify-js 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 88.0 for amplify-js and 99.1 for Umami.

Umami has 40,194 GitHub stars to amplify-js's 9,556, a gap of 30,638 (4.21×). Forks are 2,171 for amplify-js and 8,567 for Umami. On the log scale used inside this pair, adoption is 86 versus 100, and the fork community is 85 versus 100.

Push history: amplify-js 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 518 for amplify-js (0.054 per star) and 136 for Umami (0.003 per star). Issue-health scores are 52 and 96; activity scores are 100 and 100.

amplify-js 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-js and 96 for Umami. This is a procurement signal, not legal advice.

In Analytics, both amplify-js (9,556 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-js 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 44 points (52 vs 96), and the tightest is self-hosting at 0 points (100 vs 100).

Umami finishes ahead at 99.1 against amplify-js at 88.0, a 11.1 point clear margin under the published weights.

Scores are computed inside this pair only. Method and weights.

Where they separate

The numbers

Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.

amplify-js versus Umami metrics
Signal amplify-js Umami
GitHub stars 9,556 40,194
Forks 2,171 8,567
Open issues 518 136
Adoption 86 100
Activity 100 100
Community 85 100
Issue health 52 96
License 96 96
Self-hosting 100 100
Composite 88.0 99.1

Umami

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.

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, amplify-js or Umami?

Umami has more GitHub stars: 40,194 versus 9,556 for amplify-js. The gap is 30,638 stars.

Which was updated more recently, amplify-js or Umami?

Umami was pushed more recently: 17 November 2026 versus 16 November 2026 for amplify-js. That is 1 days apart.

Can I self-host both amplify-js and Umami?

Yes. This catalog marks both amplify-js and Umami as self-hostable. Confirm each project's deploy docs before you plan a migration.

Which license is easier to embed in a commercial product, amplify-js or Umami?

amplify-js 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.

Who wins the amplify-js vs Umami score?

Umami scores 99.1 and amplify-js scores 88.0. This page calls that a clear lead for Umami.

Related comparisons