A
ahoy_email
72.3
1,194 stars · MIT
Analytics
Umami leads by 25.1 · decisive
A
72.3
1,194 stars · MIT
B · leads
97.4
40,194 stars · MIT
ahoy_email versus Umami is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. ahoy_email is written mainly in Ruby; Umami is written mainly in TypeScript. The composite score is 72.3 for ahoy_email and 97.4 for Umami.
Umami has 40,194 GitHub stars to ahoy_email's 1,194, a gap of 39,000 (33.66×). Forks are 144 for ahoy_email and 8,567 for Umami. On the log scale used inside this pair, adoption is 67 versus 100, and the fork community is 55 versus 100.
Push history: ahoy_email was last pushed on 21 September 2026 (61 days ago), and Umami was last pushed on 17 November 2026 (5 days ago). Open issues stand at 1 for ahoy_email (0.001 per star) and 136 for Umami (0.003 per star). Issue-health scores are 96 and 96; activity scores are 58 and 92.
Both ahoy_email 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_email (1,194 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_email 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 45 points (55 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).
Umami finishes ahead at 97.4 against ahoy_email at 72.3, a 25.1 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 | ahoy_email | Umami |
|---|---|---|
| GitHub stars | 1,194 | 40,194 |
| Forks | 144 | 8,567 |
| Open issues | 1 | 136 |
| Adoption | 67 | 100 |
| Activity | 58 | 92 |
| Community | 55 | 100 |
| Issue health | 96 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 72.3 | 97.4 |
First-party email analytics for Rails
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,194 for ahoy_email. The gap is 39,000 stars.
Umami was pushed more recently: 17 November 2026 versus 21 September 2026 for ahoy_email. That is 56 days apart.
Yes. This catalog marks both ahoy_email and Umami as self-hostable. Confirm each project's deploy docs before you plan a migration.
ahoy_email 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 97.4 and ahoy_email scores 72.3. This page calls that a decisive lead for Umami.