ThingsBoard
An IoT platform whose release notes have become a CVE ledger
Comparison · Analytics
Cortex vs ROOT
A side-by-side editorial comparison of Cortex and ROOT — release velocity, themes, recent moves, and the top alternatives to consider.
Cortex vs ROOT: at a glance
What is Cortex?
Cortex is betting on Parquet block storage and graduating years of experimental features.
Cortex publishes its release notes as release candidates, and the two majors visible here tell a consistent story. 1.20 introduced Parquet-based block storage, Prometheus Remote Write 2.0, a resource-based limiter for ingesters and store-gateways, and regex tenant resolution, all experimental. 1.21 then made Parquet a Store Gateway query mode, graduated the Ruler API, Alertmanager API and sharding, tenant federation, FIFO/Redis cache and memcached service discovery out of experimental, and enabled the bucket index by default. The 1.21.1 candidate is almost entirely security hardening.
What is ROOT?
ROOT is shipping the pieces of its long-promised v7 inside the v6 release line
ROOT maintains an unusual number of parallel branches — patches for 6.26, 6.28, 6.30, 6.32, 6.36 and 6.38 all landed within weeks of each other in June 2026 — because CERN experiments pin to versions for years at a time. The 6.40 LTS released in May is where the actual work is: an opt-out from automatic object registration, experimental multithreaded histograms, a new RFile interface, an libcurl-based HTTP I/O layer with S3 support, and a rebuilt ML data loader. June's patch wave is the routine consequence, closing out the 6.26 and 6.38 series while fixing the first regressions in 6.40.
Cortex vs ROOT: editorial side-by-side
Cortex
0.0ANALYTICS
Cortex is betting on Parquet block storage and graduating years of experimental features.
◆ Current state
Cortex publishes its release notes as release candidates, and the two majors visible here tell a consistent story. 1.20 introduced Parquet-based block storage, Prometheus Remote Write 2.0, a resource-based limiter for ingesters and store-gateways, and regex tenant resolution, all experimental. 1.21 then made Parquet a Store Gateway query mode, graduated the Ruler API, Alertmanager API and sharding, tenant federation, FIFO/Redis cache and memcached service discovery out of experimental, and enabled the bucket index by default. The 1.21.1 candidate is almost entirely security hardening.
◆ Where it's heading
Two arcs run in parallel. The storage arc is moving Cortex off pure TSDB blocks toward Parquet, first as a converter and format, then as a queryable Store Gateway mode — the same columnar direction the rest of the observability market has taken for long-retention data. The maturity arc is a deliberate clearing of the experimental backlog, with six subsystems graduating in one release and their flags renamed to drop the experimental prefix. Layered on both is a distinct hardening push: the latest candidate bounds gossip connections, caps decompressed request bodies, adds HMAC stream authentication and validates tenant IDs against the authenticated caller.
◆ Prediction
Expect Parquet to keep progressing from experimental toward default, following the path the bucket index just completed. The security work in 1.21.1 reads like a systematic pass over untrusted input paths rather than a response to a single report, so more of the same in the ingestion and gossip layers is likely.
ROOT
0.0ANALYTICS
ROOT is shipping the pieces of its long-promised v7 inside the v6 release line
◆ Current state
ROOT maintains an unusual number of parallel branches — patches for 6.26, 6.28, 6.30, 6.32, 6.36 and 6.38 all landed within weeks of each other in June 2026 — because CERN experiments pin to versions for years at a time. The 6.40 LTS released in May is where the actual work is: an opt-out from automatic object registration, experimental multithreaded histograms, a new RFile interface, an libcurl-based HTTP I/O layer with S3 support, and a rebuilt ML data loader. June's patch wave is the routine consequence, closing out the 6.26 and 6.38 series while fixing the first regressions in 6.40.
◆ Where it's heading
The ROOT 7 redesign is arriving piecemeal under ROOT::Experimental rather than as a version bump: RNTuple replacing TTree, RDataFrame replacing TTree::Draw, RFile replacing TFile, and now the ability to switch off the global-directory ownership model that has defined ROOT's ergonomics for decades. The team is easing migration with documentation rather than deprecation — 6.40 ships a TTree::Draw-to-RDataFrame translation guide instead of a removal notice. Build weight is being cut in the same pass, with bundled builtin packages reduced roughly fourfold in favour of system libraries.
◆ Prediction
Expect further 6.40.x patches through the year as experiments migrate onto the LTS, concentrated in RNTuple and the new histogram paths where the code is youngest. The experimental namespace is the thing to watch: features that stabilize there are the clearest available signal of what a ROOT 7 would actually contain.
Alternatives to Cortex and ROOT
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 ROOT.
Apache Drill
A SQL-on-anything engine shipping rarely, but each release widens what it can reach
Apache Superset
Superset's tracked feed is a Helm chart tag stream with no notes attached.
ApexCharts
Three releases in three weeks moved ApexCharts from free library to gated open-core.
Graphite
Graphite's answer to its own CVE backlog is a pre-release nobody calls official.
NetObserv
NetObserv is layering TLS visibility and health alerting on top of its eBPF flow pipeline.
Recent activity from Cortex and ROOT
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agoROOTROOT 6.32.24 patches the 6.32 maintenance branch
- 1mo agoROOTROOT 6.30.12 patches the 6.30 maintenance branch
- 1mo agoROOTROOT 6.28.16 patches the 6.28 maintenance branch
- 1mo agoROOTROOT 6.38.06 closes the 6.38 series, adds Python 3.15 support
- 2mo agoROOTROOT 6.40.02 fixes RNTuple model extension and SOFIE padding
- 2mo agoROOTROOT 6.26.20 is the final patch for the 6.26 series
- 2mo agoCortex1.21.1 candidate hardens gossip, ingestion and status pages
- 3mo agoCortex1.21.0-rc.1 fixes memberlist, tenant federation and a memory leak
- 4mo agoCortexParquet becomes a Store Gateway mode as six features graduate ⚡
- 9mo agoCortex1.20.0-rc.1 fixes metric name validation and a compactor race
- 9mo agoCortexCortex 1.20 introduces Parquet storage and Remote Write 2.0 ⚡
Frequently asked questions
What is the difference between Cortex and ROOT?
They serve adjacent needs but don't currently overlap on shipped themes. Cortex and ROOT are shipping at a similar cadence (velocity 0.0 vs 0.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 Cortex better than ROOT?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Cortex and ROOT are shipping at a similar cadence (velocity 0.0 vs 0.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 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 ROOT?
Top ROOT alternatives in Analytics are ranked by recent ship velocity. Browse the "ROOT alternatives" section above for the current picks, or visit /alternatives/cern-root for the full list with editorial commentary on each.