Graphite
Graphite's answer to its own CVE backlog is a pre-release nobody calls official.
Comparison · Analytics
OpenCTI vs Cortex
A side-by-side editorial comparison of OpenCTI and Cortex — release velocity, themes, recent moves, and the top alternatives to consider.
OpenCTI vs Cortex: at a glance
What is OpenCTI?
OpenCTI is turning its connector catalog into a marketplace with a support tier attached.
OpenCTI ships on a roughly weekly cadence, and the last six releases mix steady platform work — saved searches, dashboard filters, workflow governance — with a consistent push on how connectors are discovered and supported. The catalog became a faceted marketplace in late July, connectors are now labelled as supported by Filigran or by the community, and several releases wire the platform into Filigran's XTM Hub. The notes themselves are dense PR lists with no narrative, so the direction has to be read off what keeps recurring.
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.
OpenCTI vs Cortex: editorial side-by-side
OpenCTI
6.3ANALYTICS
OpenCTI is turning its connector catalog into a marketplace with a support tier attached.
◆ Current state
OpenCTI ships on a roughly weekly cadence, and the last six releases mix steady platform work — saved searches, dashboard filters, workflow governance — with a consistent push on how connectors are discovered and supported. The catalog became a faceted marketplace in late July, connectors are now labelled as supported by Filigran or by the community, and several releases wire the platform into Filigran's XTM Hub. The notes themselves are dense PR lists with no narrative, so the direction has to be read off what keeps recurring.
◆ Where it's heading
The recurring thread is commercial structure around an open-source core. Enterprise Edition gating on workflow restrictions, a catalog that distinguishes vendor-supported connectors from community ones, and repeated XTM Hub integration all point the same way: the platform stays open while the ecosystem and its support tiers become the thing being sold. Underneath that, the workflow subsystem keeps maturing through draft approval, auto-save, reset and restore, which suggests adoption by teams that need review gates before intelligence is published.
◆ Prediction
Expect more of the catalog to organize around the supported-versus-community distinction, and the draft approval workflow to pick up the permission and audit controls that the recent RBAC and audit-log work is laying groundwork for.
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 OpenCTI 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 OpenCTI 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 OpenCTI alternatives → · See all Cortex alternatives →
Recent activity from OpenCTI and Cortex
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 2d agoOpenCTIShareable saved searches and reusable dashboard filters
- 5d agoOpenCTIStoppable data-sanity runs; fix for merges hanging on dense graphs
- 10d agoOpenCTIRelease draft approval workflow and a reworked integrations experience
- 18d agoOpenCTIConnector catalog becomes a faceted marketplace ⚡
- 23d agoOpenCTIBug fixes and dependency updates
- 24d agoOpenCTIConnectors relabelled by support tier, plus custom view expansion
- 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 OpenCTI and Cortex?
They serve adjacent needs but don't currently overlap on shipped themes. OpenCTI 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 OpenCTI better than Cortex?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. OpenCTI 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 OpenCTI?
Top OpenCTI alternatives in Analytics are ranked by recent ship velocity. Browse the "OpenCTI alternatives" section above for the current picks, or visit /alternatives/opencti 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.