OpenMetadata
OpenMetadata 2.0.8 widens Hex, Sigma and BigQuery coverage while 2.1 waits in release candidates.
A side-by-side editorial comparison of Cortex and Kubecost — 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.
Kubecost cuts three 3.3.2 release candidates in two days, still without notes.
Kubecost opened the 3.3.2 patch line on November 11 and tagged rc.1 through rc.3 by November 13. Each is an automated in-code version bump with no described changes, as with every tag since October, when the 3.3.1 and 3.2.5 candidates went out the same way.
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.
Kubecost opened the 3.3.2 patch line on November 11 and tagged rc.1 through rc.3 by November 13. Each is an automated in-code version bump with no described changes, as with every tag since October, when the 3.3.1 and 3.2.5 candidates went out the same way.
The quick run of candidates suggests 3.3.2 is close to a final tag. The public tags still say nothing about what the patch fixes.
Expect a 3.3.2 final tag within days; what it changes will not be visible from these release notes.
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 Kubecost.
OpenMetadata 2.0.8 widens Hex, Sigma and BigQuery coverage while 2.1 waits in release candidates.
Dovetail lets admins choose which connectors members can plug into the workspace.
Dagster drops Python 3.10 and lets agents run schedules and sensors through MCP.
OpenHouse adds time-zone-aware retention and per-database table caps.
Countly 25.03.59 defaults to Node 26, supports MongoDB 9 and tightens app scoping.
RStudio opens the 2026.11 train with another NOTICE file update.
See all Cortex alternatives → · See all Kubecost alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Kubecost 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. Kubecost 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 Kubecost alternatives in Analytics are ranked by recent ship velocity. Browse the "Kubecost alternatives" section above for the current picks, or visit /alternatives/kubecost for the full list with editorial commentary on each.