Glances
Glances 4.5.9 closes out the 4.x line as a 5.0 beta opens for testing.
A side-by-side editorial comparison of Cortex and OpenReplay — release velocity, themes, recent moves, and the top alternatives to consider.
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.
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.
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.
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.
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.
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.
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.
Unclear from these entries; more chart-bump backup tags are likely until a 1.27.x release with notes appears.
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 OpenReplay.
Glances 4.5.9 closes out the 4.x line as a 5.0 beta opens for testing.
Calibre MCP lets your coding agent read RUM and Lighthouse data, then fix the slow code
Dovetail opens its docs to Claude and ChatGPT as co-authors.
SkyWalking 11.1 builds service maps from OpenTelemetry traces, no SkyWalking agent required.
Tinybird shrinks its Local image by a third after a run of observability updates.
OpenHouse tightens view authorization and moves its optimizer schema to Flyway.
See all Cortex alternatives → · See all OpenReplay alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. OpenReplay 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. OpenReplay 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.
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.
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.