← Back to home
Comparison · Analytics

Countly vs Umami

A side-by-side editorial comparison of Countly and Umami — release velocity, themes, recent moves, and the top alternatives to consider.

Shared themes:self-hosted

Countly vs Umami: at a glance

FeatureCountlyUmami
SectorAnalyticsAnalytics
Velocity score5.00.0
Sparks · 30d00
Top themesproduct-analytics, self-hosted, security-patches, api tokensweb analytics, session replay, dashboards, security patches
Last editorial update1d ago3mo ago
WebsiteVisit →Visit →

What is Countly?

Countly 25.03.58 tightens API tokens, sessions and login lockouts in one security patch.

Countly 25.03.58 is a security-heavy patch for the 25.03 line. App-restricted tokens must now declare their permissions, password changes and member lockouts revoke tokens, single-use tokens and reset links work once even under concurrency, and login failures count per account regardless of username casing. It also tightens access to dashboards, dbviewer and exports, and fixes file migration, remote-config targeting and star-rating widgets.

Read the full Countly trajectory →

What is Umami?

Umami spent late 2025 patching Next.js CVEs, then shipped Boards and Session Replay in v3.1.0.

The window splits sharply. Four of six releases are December 2025 patches across the v2 and v3 lines, all responding to the same Next.js and React security advisories plus Docker build breakage — several shipped within days of each other because the first fix updated Next.js without the affected React versions. Then v3.1.0 in April 2026 delivered custom dashboards as Boards, Session Replay, Web Vitals performance tracking, a redesigned share page, and a large batch of fixes.

Read the full Umami trajectory →

Countly vs Umami: editorial side-by-side

C
Countly
ANALYTICS
5.0

Countly 25.03.58 tightens API tokens, sessions and login lockouts in one security patch.

◆ Current state

Countly 25.03.58 is a security-heavy patch for the 25.03 line. App-restricted tokens must now declare their permissions, password changes and member lockouts revoke tokens, single-use tokens and reset links work once even under concurrency, and login failures count per account regardless of username casing. It also tightens access to dashboards, dbviewer and exports, and fixes file migration, remote-config targeting and star-rating widgets.

◆ Where it's heading

The 25.03 LTS line keeps absorbing security work at a fast clip: an upstream Node CVE, certificate distrust, and now a sweep of Countly's own token and permission model. Feature work stays in enterprise licensing and journeys, while LTS releases mostly harden what exists.

◆ Prediction

Expect a matching 24.05 backport of the token and permission fixes. Token owners may also need migration guidance, since existing app-restricted tokens without permissions are now limited to their owner's rights.

Umami logo
Umami
ANALYTICS
0.0

Umami spent late 2025 patching Next.js CVEs, then shipped Boards and Session Replay in v3.1.0.

◆ Current state

The window splits sharply. Four of six releases are December 2025 patches across the v2 and v3 lines, all responding to the same Next.js and React security advisories plus Docker build breakage — several shipped within days of each other because the first fix updated Next.js without the affected React versions. Then v3.1.0 in April 2026 delivered custom dashboards as Boards, Session Replay, Web Vitals performance tracking, a redesigned share page, and a large batch of fixes.

◆ Where it's heading

The security cluster is a framework dependency showing its cost — an analytics tool inheriting its release schedule from Next.js advisories. v3.1.0 is where product work resumes, and its content is telling: Session Replay and Web Vitals move Umami past pageview counting into behaviour and performance, which is the territory occupied by heavier commercial analytics rather than the lightweight privacy-first tools it grew up alongside.

◆ Prediction

Expect the next releases to build on Boards and Session Replay rather than return to the counting core, since both are new surfaces that arrived with a single release and no follow-up yet.

Alternatives to Countly and Umami

Other Analytics products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Countly or Umami.

See all Countly alternatives → · See all Umami alternatives →

Recent activity from Countly and Umami

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 1d agoCountlyCountly 25.03.58: token scoping, revocation and access fixes
  2. 3d agoCountlyCountly 25.03.57-LTS distrusts emSign roots, fixes A/B setup
  3. 6d agoCountlyCountly 25.03.56-LTS: Node CVE patch, licence overdue banner
  4. 17d agoCountlyCountly 25.03.55: throttled active-user refresh, explicit DB names
  5. 29d agoCountly24.05.54: data-manager merge and logging fixes
  6. 1mo agoCountly25.03.54: License v2 entitlements and journey charts
  7. 6mo agoUmamiv3.1.0: Boards, Session Replay and Web Vitals ⚡
  8. 10mo agoUmamiv3.0.3: Next.js security patch
  9. 10mo agoUmamiv2.20.2: Next.js security patch for the v2 line
  10. 10mo agoUmamiv2.20.1: React version fix and Docker build repairs
  11. 10mo agoUmamiv2.20.0: Next.js CVE fix for the v2 line
  12. 10mo agoUmamiv3.0.2: Next.js RSC vulnerability patch and UI fixes

Frequently asked questions

What is the difference between Countly and Umami?

Both compete on the same themes — self-hosted — within Analytics. Countly is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is Countly better than Umami?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Countly is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.

What are the best alternatives to Countly?

Top Countly alternatives in Analytics are ranked by recent ship velocity. Browse the "Countly alternatives" section above for the current picks, or visit /alternatives/countly-server for the full list with editorial commentary on each.

What are the best alternatives to Umami?

Top Umami alternatives in Analytics are ranked by recent ship velocity. Browse the "Umami alternatives" section above for the current picks, or visit /alternatives/umami for the full list with editorial commentary on each.