A
countly-server
76.2
5,931 stars · license n/a
Analytics
Metabase leads by 13.2 · clear
A
76.2
5,931 stars · license n/a
B · leads
89.4
50,382 stars · AGPL-3.0
countly-server versus Metabase 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; Metabase is written mainly in Clojure. The composite score is 76.2 for countly-server and 89.4 for Metabase.
Metabase has 50,382 GitHub stars to countly-server's 5,931, a gap of 44,451 (8.49×). Forks are 984 for countly-server and 7,016 for Metabase. On the log scale used inside this pair, adoption is 80 versus 100, and the fork community is 78 versus 100.
Push history: countly-server was last pushed on 17 November 2026 (0 days ago), and Metabase was last pushed on 17 November 2026 (0 days ago). Open issues stand at 2 for countly-server (0.000 per star) and 4,696 for Metabase (0.093 per star). Issue-health scores are 96 and 52; 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. Metabase 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. License scores in this pair are 30 for countly-server and 52 for Metabase. This is a procurement signal, not legal advice.
Only Metabase is marked self-hostable here (50,382 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, Metabase is freemium.
The lead is split. countly-server is furthest ahead on issue health (96 to 52), while Metabase is furthest ahead on self-hosting (100 to 35). Choose the dimension a rollout cannot compromise on.
Metabase finishes ahead at 89.4 against countly-server at 76.2, a 13.2 point clear 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 | Metabase |
|---|---|---|
| GitHub stars | 5,931 | 50,382 |
| Forks | 984 | 7,016 |
| Open issues | 2 | 4,696 |
| Adoption | 80 | 100 |
| Activity | 100 | 100 |
| Community | 78 | 100 |
| Issue health | 96 | 52 |
| License | 30 | 52 |
| Self-hosting | 35 | 100 |
| Composite | 76.2 | 89.4 |
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.
Metabase is a business-intelligence tool that lets teams ask questions of a SQL database without writing a report from scratch. It is commonly self-hosted next to the warehouse it reads.
Metabase has more GitHub stars: 50,382 versus 5,931 for countly-server. The gap is 44,451 stars.
Both were last pushed on 17 November 2026.
Only Metabase 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. Metabase 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Metabase scores 89.4 and countly-server scores 76.2. This page calls that a clear lead for Metabase.