A
countly-server
78.2
5,931 stars · license n/a
Analytics
redash leads by 18.3 · decisive
A
78.2
5,931 stars · license n/a
B · leads
96.5
28,887 stars · BSD-2-Clause
countly-server versus redash 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; redash is written mainly in TypeScript. The composite score is 78.2 for countly-server and 96.5 for redash.
redash has 28,887 GitHub stars to countly-server's 5,931, a gap of 22,956 (4.87×). Forks are 984 for countly-server and 4,645 for redash. On the log scale used inside this pair, adoption is 85 versus 100, and the fork community is 82 versus 100.
Push history: countly-server was last pushed on 17 November 2026 (0 days ago), and redash was last pushed on 14 November 2026 (3 days ago). Open issues stand at 2 for countly-server (0.000 per star) and 780 for redash (0.027 per star). Issue-health scores are 96 and 70; 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. redash is listed as BSD-2-Clause, 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 redash. This is a procurement signal, not legal advice.
Only redash is marked self-hostable here (28,887 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, redash is open source.
The lead is split. countly-server is furthest ahead on issue health (96 to 70), while redash is furthest ahead on license flexibility (96 to 30). Choose the dimension a rollout cannot compromise on.
redash finishes ahead at 96.5 against countly-server at 78.2, a 18.3 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 | redash |
|---|---|---|
| GitHub stars | 5,931 | 28,887 |
| Forks | 984 | 4,645 |
| Open issues | 2 | 780 |
| Adoption | 85 | 100 |
| Activity | 100 | 100 |
| Community | 82 | 100 |
| Issue health | 96 | 70 |
| License | 30 | 96 |
| Self-hosting | 35 | 100 |
| Composite | 78.2 | 96.5 |
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.
Make Your Company Data Driven. Connect to any data source, easily visualize, dashboard and share your data.
redash has more GitHub stars: 28,887 versus 5,931 for countly-server. The gap is 22,956 stars.
countly-server was pushed more recently: 17 November 2026 versus 14 November 2026 for redash. That is 3 days apart.
Only redash 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. redash is listed as BSD-2-Clause, 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.
redash scores 96.5 and countly-server scores 78.2. This page calls that a decisive lead for redash.