Graphite
Graphite's answer to its own CVE backlog is a pre-release nobody calls official.
Comparison · Analytics
Cortex vs MotherDuck
A side-by-side editorial comparison of Cortex and MotherDuck — release velocity, themes, recent moves, and the top alternatives to consider.
Cortex vs MotherDuck: 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 MotherDuck?
MotherDuck is building the governance layer its agent-native pipelines already needed.
The weekly cadence is split between two tracks. One is agent surface: Flights (Python pipelines drivable from SQL, UI, or any MCP client) went from Preview to all plans in six weeks, and Guides now let an organization hand agents its metric definitions and join rules so every session writes SQL against the same semantics. The other is enterprise readiness: RBAC with scoped privileges, Sydney and Tokyo regions, Iceberg read/write against Cloudflare R2 and Databricks, a Postgres wire endpoint that BI tools and dbt Cloud connect to natively.
Cortex vs MotherDuck: 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.
MotherDuck
6.3ANALYTICS
MotherDuck is building the governance layer its agent-native pipelines already needed.
◆ Current state
The weekly cadence is split between two tracks. One is agent surface: Flights (Python pipelines drivable from SQL, UI, or any MCP client) went from Preview to all plans in six weeks, and Guides now let an organization hand agents its metric definitions and join rules so every session writes SQL against the same semantics. The other is enterprise readiness: RBAC with scoped privileges, Sydney and Tokyo regions, Iceberg read/write against Cloudflare R2 and Databricks, a Postgres wire endpoint that BI tools and dbt Cloud connect to natively.
◆ Where it's heading
The order is deliberate — ship the agent capability, then the controls that make it deployable. Flights arrived in Preview, reached every plan, gained per-run config overrides and runtime caps, and now Admins get org-wide visibility while edit and delete stay with the creator. Guides is the same move applied to correctness: rather than better prompting, MotherDuck is making organizational context a stored, shareable object agents read automatically. Regional expansion and Iceberg catalog interop suggest the target is a warehouse that sits inside someone else's data estate rather than replacing it.
◆ Prediction
Expect Guides to leave Preview with permissions attached, and the Admin visibility model to extend from viewing Flights to governing them — scheduling limits, ownership transfer, or approval before a Flight runs against production data.
Alternatives to Cortex and MotherDuck
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 MotherDuck.
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 Cortex alternatives → · See all MotherDuck alternatives →
Recent activity from Cortex and MotherDuck
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 4d agoMotherDuckDuckDB 1.5.5, APAC Flights, and org-wide Flight visibility for Admins
- 11d agoMotherDuckGuides: org context agents read automatically through MCP ⚡
- 17d agoMotherDuckRBAC, Cloudflare R2 Iceberg catalog, and Flight runtime limits
- 24d agoMotherDuckMotherDuck opens Sydney and Tokyo; Flights reach the Lite plan
- 1mo agoMotherDuckDatabricks Iceberg writes, Flights on every plan, Dive statuses
- 1mo agoMotherDuckServer-side Iceberg attach and native dbt Cloud connectivity
- 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 MotherDuck?
They serve adjacent needs but don't currently overlap on shipped themes. MotherDuck is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 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 MotherDuck?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. MotherDuck is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 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 MotherDuck?
Top MotherDuck alternatives in Analytics are ranked by recent ship velocity. Browse the "MotherDuck alternatives" section above for the current picks, or visit /alternatives/motherduck for the full list with editorial commentary on each.