Omni
Omni ships weekly, and almost every week the headline item is an AI feature.
A side-by-side editorial comparison of OpenCTI and Whatagraph — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | OpenCTI | Whatagraph |
|---|---|---|
| Sector | Analytics | Analytics |
| Velocity score | 6.3 | 5.0 |
| Sparks · 30d | 0 | 0 |
| Top themes | threat-intelligence, stix, data-model, ingestion | agency reporting, client portals, integrations, data storage |
| Last editorial update | 16h ago | 4d ago |
| Website | Visit → | — |
OpenCTI spends a release unblocking queues and hardening upserts
7.260817.0 is a fix release. The most consequential item is malformed STIX messages nacking forever and blocking worker queues indefinitely — a stall in the ingestion path rather than a display bug. Alongside it: upsert clearing an existing createdBy when incoming confidence is higher, draft upserts crashing on existing attack patterns, OTP handling in the stream middleware, and case template relation authorization. Score fields were added to threat actor groups, intrusion sets and malware.
Whatagraph is turning a report from a document you send into a place clients come back to.
Whatagraph has been working on the parts of agency reporting that break under volume rather than on new analysis capability. Stored data removes live API calls from render time, connection failover keeps widgets alive when one teammate's token expires, and the Basis rebuild traded live loading for stored data to fix slow widgets and mismatched spend figures. Alongside that runs a steady stream of presentation control — automatic conditional formatting, per-metric decimal places, chosen comparison colors, consolidated theme settings.
7.260817.0 is a fix release. The most consequential item is malformed STIX messages nacking forever and blocking worker queues indefinitely — a stall in the ingestion path rather than a display bug. Alongside it: upsert clearing an existing createdBy when incoming confidence is higher, draft upserts crashing on existing attack patterns, OTP handling in the stream middleware, and case template relation authorization. Score fields were added to threat actor groups, intrusion sets and malware.
The platform's feature energy went into the connector catalog and integrations rework in July, and the releases since have been consolidating: mass operations on relation times, shareable saved searches, and now a pass over ingestion robustness. Adding score to more entity types continues the slow enrichment of the data model that runs underneath the feature work.
Given score arriving on three entity types in one release, expect it to keep spreading across the data model, and the queue-blocking class of bug to draw more worker-side hardening.
Whatagraph has been working on the parts of agency reporting that break under volume rather than on new analysis capability. Stored data removes live API calls from render time, connection failover keeps widgets alive when one teammate's token expires, and the Basis rebuild traded live loading for stored data to fix slow widgets and mismatched spend figures. Alongside that runs a steady stream of presentation control — automatic conditional formatting, per-metric decimal places, chosen comparison colors, consolidated theme settings.
The through-line is reliability and reader experience at agency scale, where one account runs hundreds or thousands of sources across several people. Report shortcuts extend that from inside a single report to the relationships between reports, letting a heavy report be split into a hub and supporting detail rather than one long scroll or five unlabeled links. Integration work continues to be additive and specific — Ahrefs Rank Tracker, WhatConverts, Snowflake, bol. — chosen to fill named reporting gaps rather than to broaden a catalog.
Expect the portal framing to get more structure — navigation, landing behavior or access controls on the entry-point report — since a hub built from a link widget will run into the limits of being just another report.
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 Whatagraph.
Omni ships weekly, and almost every week the headline item is an AI feature.
silx settles into maintenance a release after its PySide6 migration
Plotly is turning its cloud into a metered compute platform with an enterprise on-ramp.
aniread stops asking you to know which tracker wrote the file
Rho's release machinery finally produced a stable build — and it shipped no new product.
Usermaven closed the loop: data comes in from anywhere, and now it goes back out.
See all OpenCTI alternatives → · See all Whatagraph alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. OpenCTI is currently shipping more aggressively (velocity 6.3 vs 5.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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. OpenCTI is currently shipping more aggressively (velocity 6.3 vs 5.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.
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.
Top Whatagraph alternatives in Analytics are ranked by recent ship velocity. Browse the "Whatagraph alternatives" section above for the current picks, or visit /alternatives/whatagraph for the full list with editorial commentary on each.