A
countly-server
76.5
5,931 stars · license n/a
Analytics
Umami leads by 22.6 · decisive
A
76.5
5,931 stars · license n/a
B · leads
99.1
40,194 stars · MIT
countly-server versus Umami is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. countly-server is written mainly in JavaScript; Umami is written mainly in TypeScript. The composite score is 76.5 for countly-server and 99.1 for Umami.
Umami has 40,194 GitHub stars to countly-server's 5,931, a gap of 34,263 (6.78×). Forks are 984 for countly-server and 8,567 for Umami. On the log scale used inside this pair, adoption is 82 versus 100, and the fork community is 76 versus 100.
Push history: countly-server was last pushed on 17 November 2026 (0 days ago), and Umami was last pushed on 17 November 2026 (0 days ago). Open issues stand at 2 for countly-server (0.000 per star) and 136 for Umami (0.003 per star). Issue-health scores are 96 and 96; activity scores are 100 and 100.
countly-server is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. 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 30 for countly-server and 96 for Umami. This is a procurement signal, not legal advice.
Only Umami is marked self-hostable here (40,194 stars, deploy score 100). countly-server is not (5,931 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: countly-server is unpriced in this catalog, Umami is open source.
Umami is ahead on every scored dimension that is not level. Level dimensions: recent activity, issue health. The widest gap is license flexibility at 66 points (30 vs 96), and the tightest is issue health at 0 points (96 vs 96).
Umami finishes ahead at 99.1 against countly-server at 76.5, a 22.6 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 | countly-server | Umami |
|---|---|---|
| GitHub stars | 5,931 | 40,194 |
| Forks | 984 | 8,567 |
| Open issues | 2 | 136 |
| Adoption | 82 | 100 |
| Activity | 100 | 100 |
| Community | 76 | 100 |
| Issue health | 96 | 96 |
| License | 30 | 96 |
| Self-hosting | 35 | 100 |
| Composite | 76.5 | 99.1 |
Countly is a privacy-first, AI-powered analytics and engagement platform for understanding and optimizing customer journeys across digital applications, from desktop and mobile to IoT and connected environments.
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 5,931 for countly-server. The gap is 34,263 stars.
Both were last pushed on 17 November 2026.
Only Umami is marked self-hostable. countly-server is not.
countly-server is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. 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 countly-server scores 76.5. This page calls that a decisive lead for Umami.