Graphite
Graphite's answer to its own CVE backlog is a pre-release nobody calls official.
Comparison · Analytics
Polars vs Cortex
A side-by-side editorial comparison of Polars and Cortex — release velocity, themes, recent moves, and the top alternatives to consider.
Polars vs Cortex: at a glance
What is Polars?
A deprecation sweep and hive-partition join rewrites, shipped on two trains at once.
Polars releases Python and Rust builds in lockstep, with each Rust tag naming the Python version its DSL matches. The recent work is concentrated in two places: query-plan performance — len() pushdown into concat and union inputs, pre-partitioning on hive-partitioned joins, split multiplexers scanning in-memory DataFrames — and cloud IO, where an adaptive HTTP rate-limiter and a global DNS cache landed. Correctness fixes reach into unsoundness in rayon block_on and undefined behaviour on empty chunks.
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.
Polars vs Cortex: editorial side-by-side
Polars
5.0ANALYTICS
A deprecation sweep and hive-partition join rewrites, shipped on two trains at once.
◆ Current state
Polars releases Python and Rust builds in lockstep, with each Rust tag naming the Python version its DSL matches. The recent work is concentrated in two places: query-plan performance — len() pushdown into concat and union inputs, pre-partitioning on hive-partitioned joins, split multiplexers scanning in-memory DataFrames — and cloud IO, where an adaptive HTTP rate-limiter and a global DNS cache landed. Correctness fixes reach into unsoundness in rayon block_on and undefined behaviour on empty chunks.
◆ Where it's heading
The 1.43.0 release carried seven deprecations at once — numeric-to-categorical casts, casts from non-nested dtypes into lists, bitwise ops between integers and booleans, LazyFrame.profile, unnamed list.to_struct calls — and 1.43.2 added more. That density of deprecation in minor releases is how a project narrows its type semantics before a major. Alongside it, Iceberg and Delta support keeps taking fixes, which is where the lakehouse-format work is showing up.
◆ Prediction
Expect the deprecation cycle to keep tightening casting and categorical semantics, with performance work staying focused on hive-partitioned and cloud-hosted data where the query planner has the most left to exploit.
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.
Alternatives to Polars and Cortex
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 Polars or Cortex.
NetObserv
NetObserv is layering TLS visibility and health alerting on top of its eBPF flow pipeline.
Apache Storm
Storm 3.0 finishes removing the Clojure it was built in, and moves to a Java 21 baseline.
Apache StreamPark
Five release candidates in two years, none of them stable, and none since October 2025.
Apache HertzBeat
A monitoring project whose public release feed skips the release that mattered.
Axiom
Axiom is rebuilding observability so an AI agent, not a human, can be the first user.
See all Polars alternatives → · See all Cortex alternatives →
Recent activity from Polars and Cortex
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 3d agoPolarsRust 0.55.2 adds an adaptive HTTP rate-limiter for cloud IO
- 4d agoPolarsRust 0.55.1 rewrites joins on hive-partitioned data
- 8d agoPolarsPython 1.43.2 deprecates Categorical-to-integer casts
- 13d agoPolarsPython 1.43.1 allows callback sinks on cloud targets
- 19d agoPolarsPython 1.43.0 lands seven deprecations in one release
- 1mo agoPolarsPython 1.42.1 samples multi-file parquet metadata resolution
- 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 Polars and Cortex?
They serve adjacent needs but don't currently overlap on shipped themes. Polars is currently shipping more aggressively (velocity 5.0 vs 0.0), 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 Polars better than Cortex?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Polars is currently shipping more aggressively (velocity 5.0 vs 0.0), 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 Polars?
Top Polars alternatives in Analytics are ranked by recent ship velocity. Browse the "Polars alternatives" section above for the current picks, or visit /alternatives/polars for the full list with editorial commentary on each.
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.