Skip to content
DevUtils Online

Analytics

ahoy vs Umami

Umami leads by 16.6 · decisive

A

ahoy

82.5

4,482 stars · MIT

B · leads

Umami

99.1

40,194 stars · MIT

ahoy versus Umami is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. ahoy is written mainly in Ruby; Umami is written mainly in TypeScript. The composite score is 82.5 for ahoy and 99.1 for Umami.

Umami has 40,194 GitHub stars to ahoy's 4,482, a gap of 35,712 (8.97×). Forks are 385 for ahoy and 8,567 for Umami. On the log scale used inside this pair, adoption is 79 versus 100, and the fork community is 66 versus 100.

Push history: ahoy was last pushed on 22 October 2026 (26 days ago), and Umami was last pushed on 17 November 2026 (0 days ago). Open issues stand at 8 for ahoy (0.002 per star) and 136 for Umami (0.003 per star). Issue-health scores are 96 and 96; activity scores are 78 and 100.

Both ahoy 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 ahoy (4,482 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: ahoy is open source, Umami is open source.

Umami is ahead on every scored dimension that is not level. Level dimensions: issue health, license flexibility, self-hosting. The widest gap is fork community at 34 points (66 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).

Umami finishes ahead at 99.1 against ahoy at 82.5, a 16.6 point decisive 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.

ahoy versus Umami metrics
Signal ahoy Umami
GitHub stars 4,482 40,194
Forks 385 8,567
Open issues 8 136
Adoption 79 100
Activity 78 100
Community 66 100
Issue health 96 96
License 96 96
Self-hosting 100 100
Composite 82.5 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, ahoy or Umami?

Umami has more GitHub stars: 40,194 versus 4,482 for ahoy. The gap is 35,712 stars.

Which was updated more recently, ahoy or Umami?

Umami was pushed more recently: 17 November 2026 versus 22 October 2026 for ahoy. That is 26 days apart.

Can I self-host both ahoy and Umami?

Yes. This catalog marks both ahoy 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, ahoy or Umami?

ahoy 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.

Who wins the ahoy vs Umami score?

Umami scores 99.1 and ahoy scores 82.5. This page calls that a decisive lead for Umami.

Related comparisons