Countly Community Edition

Real time mobile and web analytics, crash reporting and push notifications platform.

Thriving · 90
90/100
Thriving

High commit volume, frequent releases and growing activity.

Maintenance 36/40
Releases 25/25
Community 14/20
Momentum 15/15

Commit activity more than 89% of tracked projects; popularity more than 69%. How this is calculated.

Commits, last 11 months

2025-12: 76 commits 2026-01: 162 commits 2026-02: 105 commits 2026-03: 177 commits 2026-04: 135 commits 2026-05: 189 commits 2026-06: 430 commits 2026-07: 166 commits 2026-08: 412 commits 2026-09: 162 commits 2026-10: 431 commits
2025-12 2445 total 2026-10
Stars5.9k
Latest release25.03.59 · 13 Nov 2026
Repo updated19 Nov 2026
LicenceAGPL-3.0
Built withNodejs, Docker

Is Countly Community Edition actively maintained?

Countly Community Edition is under active development: 2445 commits landed over the last 11 months, averaging roughly 335 commits a month in the most recent quarter.

The most recent tagged release, 25.03.59, shipped within the last month — a current, installable version exists today.

Of the 32 projects we track in Analytics, Countly Community Edition ranks #4 by health score — in the top quarter of its category.

What Countly Community Edition actually does

Countly Community Edition is a self-hosted analytics platform designed to track user interactions across mobile and web applications. It also includes built-in tools for monitoring application crashes and dispatching push notifications. Built using Node.js, it provides an alternative to third-party cloud analytics services by keeping your data on your own infrastructure.

Best fit: Teams that need to collect mobile and web telemetry data internally for compliance or privacy reasons, and want a unified dashboard for analytics and crash reports.

Worth knowing: The software is licensed under the AGPL-3.0, which imposes strict copyleft requirements if you modify the code or offer it as a service to external users. Operating a real-time event ingestion platform also demands careful capacity planning for storage and database resources as event volume scales.

Deployment notes

Because the application runs via Docker and Node.js, you will typically need to configure persistent volumes for data storage and place the container behind a reverse proxy to handle TLS termination. You should also ensure adequate memory allocation for the Node.js runtime and its associated database backend.


Countly Community Edition as a replacement for


Alternatives to Countly Community Edition

Projects in the same categories, ordered by health score.