Countly Review (2026)

Countly is the only tool in this directory built mobile-first. Started in June 2012, incorporated as NIS Ltd in London early 2013 — predates virtually every other tool here by several years. 11+ official platform SDKs (iOS, Android, React Native, Flutter, Unity, Windows, C++, Node, Java, Dart, Web), tvOS / watchOS / macOS via the iOS umbrella.

AI Agent "Cee" — natural-language analytics concierge that builds cohorts and funnels from plain English. Plus AI-powered analytics generates reports, dashboards, and recommendations (countly.com/feature/ai-agent-cee). Two genuine AI capabilities, marked NEW on the Analyze section.

ISO 27001 + SOC 2 certified — third tool in this directory with formal third-party security attestations after Matomo Cloud and Piwik PRO. Serves enterprise mobile/IoT customers where audit-trail compliance is non-negotiable.

The product surface goes far beyond pageviews: event-based product analytics, funnels, cohorts, retention reports, per-user timelines, heatmaps, in-app messaging, push notifications (mobile), surveys, feature flags / remote config, A/B content testing, and crash reporting.

Countly's web SDK is the largest tracker among open-source peers — ~36 KB gzipped (~132 KB raw min) vs Plausible's 1 KB or Umami's 2 KB. It bundles content-testing, heatmaps, form analytics, error tracking, and scroll/click tracking in one file. For Core Web Vitals on slow connections this dents performance noticeably. Only Piwik PRO at ~86 KB is heavier in the directory.

The AGPL-3.0 license has a Section 7 modification that prohibits removing Countly's branding from any deployed UI — a real consideration for white-label SaaS plans. Pure-AGPL peers (Plausible, Rybbit, Swetrix, OpenPanel) don't have this restriction.

Pricing transparency is the worst in the directory's certified-tools cohort. Flex starts at $40/month MAU-based, but the exact per-MAU price curve and feature-by-add-on breakdown require expanding the calculator on /pricing or contacting sales. Compare to Matomo Cloud's published €29/mo entry with full ladder.

Sub-processor disclosure is minimal — the cloud provider behind Flex private-cloud, email/support tooling, and payment processor are NOT disclosed on public pages. Plausible publishes 8 sub-processors; Piwik PRO publishes 15+. Countly's DPA exists but doesn't list specific sub-processors publicly.

DNT browser-signal honoring not advertised. Default identity model uses cookies + localStorage; Anonymous mode is configurable but a deliberate downgrade.

Best for: mobile-app-heavy organizations that want one analytics platform across native (iOS/Android/Flutter/RN/Unity), desktop (Windows/.NET), and web. Strong fit for app studios, gaming companies, IoT/embedded teams (C++ SDK), regulated industries that need ISO 27001 + SOC 2 attestations.

Real value at Flex paid ($40+/mo) or Enterprise tier: That's where you unlock private-cloud regional pinning, full feature set (push, A/B, heatmaps), and ISO 27001 + SOC 2 evidence. Lite (free self-host) gives you analytics + funnels but gates push, content testing, and some engagement features.

Not for: sub-5KB-tracker requirements (look at Plausible, Pirsch, GoatCounter, Rybbit, OpenPanel); pure web analytics where Matomo or Piwik PRO fit better; teams that need transparent published pricing across all tiers; DNT-honoring requirements (only Fathom does in this directory); white-label rebrand use cases (Section 7 brand-protection clause prohibits Countly-logo removal).

Cloud Flex: sign up at count.ly, choose region for private-cloud deployment (vendor doesn't publish underlying provider). Drop one snippet for web tracking; integrate one of 11+ SDKs for native apps.

Web SDK: standard Countly snippet — Countly.q.push(['init', { app_key: '...', url: 'https://...' }]) then Countly.q.push(['track_pageview']). ~36 KB gzipped on first paint.

iOS / Swift: add Countly Cocoapod or SPM package. Countly.sharedInstance().startWithConfig(config). Crash reporting is automatic.

Android / Kotlin: Gradle dependency on ly.count.android.sdk. Init in Application.onCreate().

Self-host (Lite): clone github.com/Countly/countly-server, deploy via Helm chart (countly/helm) or Docker — MongoDB-backed. AGPL-3.0 + Section 7 brand-clause means you cannot remove Countly's logo from source or UI.

From GA4 (web): Countly's web SDK supports event-based tracking similar to GA4 (custom events, custom segments, goals). Migration is fresh-tag — drop the GA4 snippet, install Countly snippet, redefine events using Countly's Countly.q.push(['add_event', {...}]) API. Funnels are recreated in Countly's UI.

From Firebase Analytics (mobile): Countly's mobile SDKs are deeper than Firebase's — crash reporting, push notifications, A/B testing, surveys all bundled. Migration: replace Firebase SDK with Countly SDK in your app, port event names + properties (Countly accepts arbitrary key-value maps).

From Mixpanel (product analytics): Countly's funnel/cohort/retention model maps closely to Mixpanel. Identity layer differs (Countly uses configurable device_id; Mixpanel uses identify()). Plan to re-implement user-identity bindings.

For ISO 27001 / SOC 2 procurement: request the audit reports under NDA from your account executive after signing the DPA at /dpa.