A
aptabase
75.1
1,874 stars · AGPL-3.0
Analytics
Umami leads by 24.0 · decisive
A
75.1
1,874 stars · AGPL-3.0
B · leads
99.1
40,194 stars · MIT
aptabase versus Umami is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. aptabase is written mainly in C#; Umami is written mainly in TypeScript. The composite score is 75.1 for aptabase and 99.1 for Umami.
Umami has 40,194 GitHub stars to aptabase's 1,874, a gap of 38,320 (21.45×). Forks are 143 for aptabase and 8,567 for Umami. On the log scale used inside this pair, adoption is 71 versus 100, and the fork community is 55 versus 100.
Push history: aptabase was last pushed on 15 November 2026 (2 days ago), and Umami was last pushed on 17 November 2026 (0 days ago). Open issues stand at 61 for aptabase (0.033 per star) and 136 for Umami (0.003 per star). Issue-health scores are 70 and 96; activity scores are 100 and 100.
aptabase is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. 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 52 for aptabase and 96 for Umami. This is a procurement signal, not legal advice.
In Analytics, both aptabase (1,874 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: aptabase is open source, Umami is open source.
Umami is ahead on every scored dimension that is not level. Level dimensions: recent activity, 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 99.1 against aptabase at 75.1, a 24.0 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 | aptabase | Umami |
|---|---|---|
| GitHub stars | 1,874 | 40,194 |
| Forks | 143 | 8,567 |
| Open issues | 61 | 136 |
| Adoption | 71 | 100 |
| Activity | 100 | 100 |
| Community | 55 | 100 |
| Issue health | 70 | 96 |
| License | 52 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 75.1 | 99.1 |
✨ Open Source, Privacy-First and Simple Analytics for Mobile, Desktop and Web Apps
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,874 for aptabase. The gap is 38,320 stars.
Umami was pushed more recently: 17 November 2026 versus 15 November 2026 for aptabase. That is 2 days apart.
Yes. This catalog marks both aptabase and Umami as self-hostable. Confirm each project's deploy docs before you plan a migration.
aptabase is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. 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 aptabase scores 75.1. This page calls that a decisive lead for Umami.