countly-server

Countly/countly-server

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.

Ship status

Still shipping

Pushed in the last 30 days.

Last push
20 Nov 2026
today
Ship score
73/100
How it is calculated →
Stars, last 7 weeks
no history yet
No weekly sample has been taken for this repository yet.

Shipping: pushed in the last 30 days · slowed: quiet for 31–120 days · silent: no push in over 120 days.

Repository facts

Stars
5.9K
Forks
985
Open issues
7
Watchers
208
Primary language
JavaScript
License
Other
Created
28 May 2012
Owner
Countly · Organization

Open issues are the issues and pull requests GitHub reports as open; watchers are the accounts subscribed to the repository. License unknown — GitHub’s own license field, not legal advice. 85 startups in the directory ship primarily in JavaScript.

Topics

#ai#analytics#coppa#crash-analytics#customer-engagement#dashboard#data-ownership#data-privacy#digital-analytics#feature-flags#gdpr#hipaa#insights#mobile-analytics#push-notifications#remote-configuration#tracking#user-feedback#user-journeys#web-analytics

How Jev classified this project

Classified as an open-source startup by Jev, TypeSafe’s classifier, on 19 Nov 2026 — os_startup 100%, self-hostable 84%, hosted offering 89%. The classifier reads only the repository’s name, description and homepage; it can be wrong, and a probability under 0.5 puts a listing in the review queue rather than out of the directory.

Joined the directory 19 Nov 2026, found by the weekly discovery job at confidence 1.00. Answered by jev-1.14.0. How the classification works →

Add the status badge to your README

OSSEAN ship status: shipping — last push 20 Nov 2026This is the badge for Countly/countly-server, as served from the URL below.
[![OSSEAN: shipping](https://ossean.com/badge/Countly/countly-server.svg)](https://ossean.com/Countly/countly-server)

Updates daily, from the last push GitHub saw.

The badge links to this profile, even after a GitHub rename. GitHub caches README images, so the badge can take a little longer to update there.