ROOT
ROOT 6.42 rebuilds its Python interface on cppjit and moves Cling to LLVM 22.
Comparison · Analytics
Cortex vs Countly
A side-by-side editorial comparison of Cortex and Countly — release velocity, themes, recent moves, and the top alternatives to consider.
Cortex vs Countly: at a glance
What is Cortex?
Cortex 1.22 is on its fourth candidate, with sharded Parquet and years of deprecated flags removed.
Cortex 1.22.0 has been in release candidates since 12 September, reaching rc.3 on 6 October, and GitHub shows no final yet. The candidate adds sharded Parquet conversion and querying, resource-based query eviction that cancels the heaviest query when CPU or heap crosses a threshold, OCI Object Storage as a backend, and an active-series tracker per tenant. It also removes long-deprecated flags and config fields, some of which now stop Cortex from starting if left in place.
What is Countly?
Countly's two LTS lines now get the same security fixes within a week of each other.
Countly ships security patches on two LTS lines, 25.03 and 24.05. In late October 25.03.56 moved the Docker images to Node.js 24.22.1 for a Brotli CVE and brought Python 3.12.15 to the A/B testing stack; 25.03.58 tightened tokens: app-restricted tokens must state their permissions, password changes revoke a member's tokens, and single-use tokens hold under concurrent requests. 24.05.55 then brought those same fixes to the older line, including the isolated-vm sandbox for custom hook code that 25.03 adopted in August.
Cortex vs Countly: editorial side-by-side
Cortex
2.5ANALYTICS
Cortex 1.22 is on its fourth candidate, with sharded Parquet and years of deprecated flags removed.
◆ Current state
Cortex 1.22.0 has been in release candidates since 12 September, reaching rc.3 on 6 October, and GitHub shows no final yet. The candidate adds sharded Parquet conversion and querying, resource-based query eviction that cancels the heaviest query when CPU or heap crosses a threshold, OCI Object Storage as a backend, and an active-series tracker per tenant. It also removes long-deprecated flags and config fields, some of which now stop Cortex from starting if left in place.
◆ Where it's heading
The storage arc toward Parquet continues: after 1.21 made Parquet a Store Gateway query mode, 1.22 shards files that exceed column limits. A second arc is protecting shared clusters from heavy tenants, through query eviction, resource-based throttling and concurrent data-byte limits on store gateways. The cleanup is the maturity arc from 1.21 carried further: no-op flags that were tolerated for releases now fail at startup.
◆ Prediction
1.22.0 final should follow rc.3, which added only two fixes. Operators should expect upgrade failures from leftover deprecated flags, and the release notes tell them to grep runtime configs before upgrading.
Countly
5.0ANALYTICS
Countly's two LTS lines now get the same security fixes within a week of each other.
◆ Current state
Countly ships security patches on two LTS lines, 25.03 and 24.05. In late October 25.03.56 moved the Docker images to Node.js 24.22.1 for a Brotli CVE and brought Python 3.12.15 to the A/B testing stack; 25.03.58 tightened tokens: app-restricted tokens must state their permissions, password changes revoke a member's tokens, and single-use tokens hold under concurrent requests. 24.05.55 then brought those same fixes to the older line, including the isolated-vm sandbox for custom hook code that 25.03 adopted in August.
◆ Where it's heading
The work is about access control and supply chain, not new analytics features. Tokens, sessions and login counting are being tightened release by release, and the 24.05 line is being pulled up to the 25.03 runtime (Node.js 22 for custom code, Python 3.12 with CmdStanPy for A/B testing) instead of being left on older stacks. Feature work shows up only in small items such as explicitly named databases and a licence payment-overdue banner.
◆ Prediction
Expect more paired patches as token and session hardening continues on both lines. The entries don't say how long 24.05 will keep receiving backports.
Alternatives to Cortex and Countly
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 Cortex or Countly.
Rho
Rho's feed jumped from 0.4.0 to 0.5.2, and the only note is about its release pipeline.
NetObserv
NetObserv hit 2.0 without breaking changes, then started renaming its metrics.
OpenMetadata
OpenMetadata reaches 2.1 rc1 after a month of repairing 2.0's connectors.
Stitch
Stitch keeps patching connectors one replication bug at a time.
Datawrapper
Datawrapper's October is touch tooltips, keyboard focus and small chart repairs.
See all Cortex alternatives → · See all Countly alternatives →
Recent activity from Cortex and Countly
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 2d agoCountlyCountly Version 24.05.55
- 5d agoCountlyCountly Version 25.03.58
- 7d agoCountlyCountly Version 25.03.57-LTS
- 9d agoCountlyCountly Version 25.03.56-LTS
- 20d agoCountlyCountly Version 25.03.55
- 26d agoCortex1.22 candidate 4 fixes tenant-deletion cleanup on GCS and Azure
- 1mo agoCountlyCountly Version 24.05.54
- 1mo agoCortex1.22 candidate 3 fixes the ingestion-delay histogram
- 1mo agoCortex1.22 candidate 2 adds three bug fixes
- 1mo agoCortex1.22 candidate: sharded Parquet, query eviction, OCI storage
- 5mo agoCortex1.21.1 candidate hardens gossip, ingestion and status pages
- 6mo agoCortex1.21.0-rc.1 fixes memberlist, tenant federation and a memory leak
Frequently asked questions
What is the difference between Cortex and Countly?
They serve adjacent needs but don't currently overlap on shipped themes. Countly is currently shipping more aggressively (velocity 5.0 vs 2.5), 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 Cortex better than Countly?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Countly is currently shipping more aggressively (velocity 5.0 vs 2.5), 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 Cortex?
Top Cortex alternatives in Analytics are ranked by recent ship velocity. Browse the "Cortex alternatives" section above for the current picks, or visit /alternatives/cortex-metrics for the full list with editorial commentary on each.
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 for the full list with editorial commentary on each.