OpenMetadata
OpenMetadata 2.0.8 widens Hex, Sigma and BigQuery coverage while 2.1 waits in release candidates.
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:self-hosted
Countly vs OpenReplay: at a glance
What is Countly?
Countly 25.03.59 defaults to Node 26, supports MongoDB 9 and tightens app scoping.
Countly 25.03.59 on November 13 is a large LTS patch. Clean installs and Docker images move to Node.js 26 and MongoDB 9.0, with older versions still working, and arm64 Docker images arrive. Security fixes tighten which apps a scoped token or member can reach across exports, dashboards, alerts and data tools, and wrong two-factor codes now count toward lockout.
What is OpenReplay?
OpenReplay's feed is Helm chart bumps behind its asset-cacher deny list.
OpenReplay's entries since November 4 are automated backup tags on the 1.26 and 1.27 lines that only increment Helm chart versions for chalice, assist-api and assist-stats. The last functional change remains the November 3 ASSETS_DENY_HOSTS option, which lets self-hosters block hosts the asset cacher may fetch, alongside a fix for EE 1.26 images that crashed on start.
Countly vs OpenReplay: editorial side-by-side
Countly
5.0ANALYTICS
Countly 25.03.59 defaults to Node 26, supports MongoDB 9 and tightens app scoping.
◆ Current state
Countly 25.03.59 on November 13 is a large LTS patch. Clean installs and Docker images move to Node.js 26 and MongoDB 9.0, with older versions still working, and arm64 Docker images arrive. Security fixes tighten which apps a scoped token or member can reach across exports, dashboards, alerts and data tools, and wrong two-factor codes now count toward lockout.
◆ Where it's heading
Countly is still mostly hardening access control, carrying the token-scoping work from 25.03.58 into every plugin that reads or changes app data. At the same time it keeps the self-hosted stack on current runtimes.
◆ Prediction
Expect a 24.05 patch that backports these scoping fixes, as 24.05.55 did after 25.03.58.
OpenReplay
5.0ANALYTICS
OpenReplay's feed is Helm chart bumps behind its asset-cacher deny list.
◆ Current state
OpenReplay's entries since November 4 are automated backup tags on the 1.26 and 1.27 lines that only increment Helm chart versions for chalice, assist-api and assist-stats. The last functional change remains the November 3 ASSETS_DENY_HOSTS option, which lets self-hosters block hosts the asset cacher may fetch, alongside a fix for EE 1.26 images that crashed on start.
◆ Where it's heading
The project is in a maintenance stretch, backporting fixes across 1.25 to 1.27 and repackaging charts. Nothing in recent entries points to new user-facing features.
◆ Prediction
Unclear from these entries; more chart-bump backup tags are likely until a 1.27.x release with notes appears.
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.
Dovetail
Dovetail lets admins choose which connectors members can plug into the workspace.
Dagster
Dagster drops Python 3.10 and lets agents run schedules and sensors through MCP.
OpenHouse
OpenHouse adds time-zone-aware retention and per-database table caps.
Kubecost
Kubecost cuts three 3.3.2 release candidates in two days, still without notes.
RStudio
RStudio opens the 2026.11 train with another NOTICE file update.
See all Countly alternatives → · See all OpenReplay alternatives →
Recent activity from Countly and OpenReplay
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 17h agoCountlyCountly 25.03.59: Node 26, MongoDB 9, app scoping fixes
- 4d agoOpenReplayOpenReplay backup tag: sourcemap reader chart bump
- 4d agoOpenReplayOpenReplay backup tag: sourcemap reader chart bump
- 4d agoOpenReplayOpenReplay 1.27.0 backup tag bumps sourcemap reader chart
- 7d agoOpenReplayOpenReplay 1.27 backup tag: chalice chart version bump
- 9d agoOpenReplayOpenReplay 1.27 backup tag: assist-stats chart bump
- 9d agoOpenReplayOpenReplay 1.27 backup tag: assist-api chart bump
- 14d agoCountlyCountly 24.05.55: token rules backported, Node 22 move
- 17d agoCountlyCountly 25.03.58: token scoping, revocation and access fixes
- 19d agoCountlyCountly 25.03.57-LTS distrusts emSign roots, fixes A/B setup
- 21d agoCountlyCountly 25.03.56-LTS: Node CVE patch, licence overdue banner
- 1mo agoCountlyCountly 25.03.55: throttled active-user refresh, explicit DB names
Frequently asked questions
What is the difference between Countly and OpenReplay?
Both compete on the same themes — 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.