Graphite
Graphite's answer to its own CVE backlog is a pre-release nobody calls official.
Comparison · Analytics
NetObserv vs OpenCTI
A side-by-side editorial comparison of NetObserv and OpenCTI — release velocity, themes, recent moves, and the top alternatives to consider.
NetObserv vs OpenCTI: at a glance
What is NetObserv?
NetObserv is layering TLS visibility and health alerting on top of its eBPF flow pipeline.
NetObserv ships roughly monthly as a coordinated bundle — operator, eBPF agent, flowlogs-pipeline and console plugin move together in each release. The functional work over these six releases splits three ways: a TLS visibility feature that arrived as a knob in 1.11.3 and has been extended with metrics and alerts since, a Network Health layer built on Prometheus recording rules rather than alerts alone, and steady hardening of the agent-to-pipeline path (mTLS, hot-reload filters, packet translation and sampling fixes). Prometheus is now on by default.
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.
NetObserv vs OpenCTI: editorial side-by-side
NetObserv
2.5ANALYTICS
NetObserv is layering TLS visibility and health alerting on top of its eBPF flow pipeline.
◆ Current state
NetObserv ships roughly monthly as a coordinated bundle — operator, eBPF agent, flowlogs-pipeline and console plugin move together in each release. The functional work over these six releases splits three ways: a TLS visibility feature that arrived as a knob in 1.11.3 and has been extended with metrics and alerts since, a Network Health layer built on Prometheus recording rules rather than alerts alone, and steady hardening of the agent-to-pipeline path (mTLS, hot-reload filters, packet translation and sampling fixes). Prometheus is now on by default.
◆ Where it's heading
The project is moving from flow collection toward opinionated health signalling — recording rules, runbook links in alerts, ingress 5xx and latency templates, health metadata driving console plugin config. That is the shape of a tool trying to answer 'is the network healthy' rather than only 'what traffic occurred'. In parallel, supply-chain and workflow security is getting real attention: SBOM generation and artifact signing, SHA-pinned GitHub Actions, pwn-request workflow checks and a pprof exposure fix all landed in the last two releases. The operator was also renamed from network-observability-operator to netobserv-operator.
◆ Prediction
Expect the TLS thread to keep extending — the sequence so far is fields, then metrics, then alerts, so dashboards and health rules built on TLS data are the natural next step. Continued investment in the Network Health rule set is the other safe bet, since it is where the last three releases have concentrated their non-dependency commits.
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.
Alternatives to NetObserv and OpenCTI
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 NetObserv or OpenCTI.
Cortex
Cortex is betting on Parquet block storage and graduating years of experimental features.
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 NetObserv alternatives → · See all OpenCTI alternatives →
Recent activity from NetObserv and OpenCTI
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 ⚡
- 19d agoNetObserv1.12.0 adds TLS alerting, flp-informers and signed releases
- 23d agoOpenCTIBug fixes and dependency updates
- 24d agoOpenCTIConnectors relabelled by support tier, plus custom view expansion
- 1mo agoNetObserv1.11.5 adds TLS metrics, Kafka compression and drop events
- 4mo agoNetObservTLS tracking arrives as a feature knob with new TLS fields ⚡
- 5mo agoNetObserv1.11.2 adds a pause control and TLS/mTLS hardening
- 5mo agoNetObserv1.11.1 is documentation, Snyk config and dependency updates
- 6mo agoNetObserv1.11.0 builds out Network Health rules and hot-reload filters
Frequently asked questions
What is the difference between NetObserv and OpenCTI?
They serve adjacent needs but don't currently overlap on shipped themes. OpenCTI is currently shipping more aggressively (velocity 6.3 vs 2.5), 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 NetObserv better than OpenCTI?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. OpenCTI is currently shipping more aggressively (velocity 6.3 vs 2.5), 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 NetObserv?
Top NetObserv alternatives in Analytics are ranked by recent ship velocity. Browse the "NetObserv alternatives" section above for the current picks, or visit /alternatives/netobserv for the full list with editorial commentary on each.
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.