← Back to home
Comparison · Analytics

Countly vs OpenReplay

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

Shared themes:product-analyticsself-hosted

Countly vs OpenReplay: at a glance

FeatureCountlyOpenReplay
SectorAnalyticsAnalytics
Velocity score5.05.0
Sparks · 30d00
Top themesproduct-analytics, self-hosted, security-patches, api tokenssession-replay, product-analytics, self-hosted, helm
Last editorial update9h ago14h 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 OpenReplay?

OpenReplay moves assist and sourcemap services to Node 26; still no feature notes.

OpenReplay's recent releases are automated v1.26 and v1.27 backup tags. The newest batch moves the assist and sourcemap-reader services to Node 26 LTS with dependency upgrades, published as four separate tags; the rest are Helm chart version bumps. None describes a user-facing change.

Read the full OpenReplay trajectory →

Countly vs OpenReplay: 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.

O
OpenReplay
ANALYTICS
5.0

OpenReplay moves assist and sourcemap services to Node 26; still no feature notes.

◆ Current state

OpenReplay's recent releases are automated v1.26 and v1.27 backup tags. The newest batch moves the assist and sourcemap-reader services to Node 26 LTS with dependency upgrades, published as four separate tags; the rest are Helm chart version bumps. None describes a user-facing change.

◆ Where it's heading

The public release feed is mostly packaging and runtime maintenance, now applied to both the 1.26 and 1.27 lines. The Node 26 move shows backend upkeep continues, but there is no visible move toward a 1.28 release.

◆ Prediction

The entries don't show what's next; a tagged 1.27 or 1.28 release with real notes would be the first signal.

Alternatives to Countly and OpenReplay

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 OpenReplay.

See all Countly alternatives → · See all OpenReplay alternatives →

Recent activity from Countly and OpenReplay

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

  1. 11h agoCountlyCountly 25.03.58: token scoping, revocation and access fixes
  2. 17h agoOpenReplayNode 26 LTS move backported to the 1.22 line
  3. 20h agoOpenReplayNode 26 LTS move backported to the 1.25 line
  4. 1d agoOpenReplayAssist and sourcemap reader move to Node 26 LTS (1.26)
  5. 1d agoOpenReplayNode 26 LTS move for assist services (1.26, repeat tag)
  6. 1d agoOpenReplayNode 26 LTS move for assist services (1.27, repeat tag)
  7. 1d agoOpenReplayAssist and sourcemap reader move to Node 26 LTS (1.27)
  8. 1d agoCountlyCountly 25.03.57-LTS distrusts emSign roots, fixes A/B setup
  9. 4d agoCountlyCountly 25.03.56-LTS: Node CVE patch, licence overdue banner
  10. 15d agoCountlyCountly 25.03.55: throttled active-user refresh, explicit DB names
  11. 27d agoCountly24.05.54: data-manager merge and logging fixes
  12. 1mo agoCountly25.03.54: License v2 entitlements and journey charts

Frequently asked questions

What is the difference between Countly and OpenReplay?

Both compete on the same themes — product-analytics, self-hosted — within Analytics. Countly and OpenReplay are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is Countly better than OpenReplay?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Countly and OpenReplay are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). 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 OpenReplay?

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