tidyr
tidyr replaced separate() with a family that says what it does.
A side-by-side editorial comparison of dowhy and OpenCTI — release velocity, themes, recent moves, and the top alternatives to consider.
DoWhy adds one estimation method a year and keeps its identification edge.
DoWhy is at v0.14, which added a doubly robust estimator and Python 3.13 support. The releases before it followed the same shape: v0.13 brought the Generalized Adjustment Criterion for identification, v0.12 added time-series effect estimation and a rank-based anomaly scorer. Between the feature releases sit patch versions handling pandas and CUDA breakage.
OpenCTI is rebuilding its connector layer into a marketplace and wiring the platform to XTM Hub
OpenCTI ships on a roughly weekly date-stamped cadence, and the last six releases divide cleanly: the connector catalog was redesigned into a faceted marketplace, then the surrounding integrations experience was reworked around it, then the platform gained two-way connection with Filigran's XTM Hub. Alongside that, saved searches and saved filters became shareable and reusable across dashboards. The most recent releases are weighted toward fixes rather than new surface.
DoWhy is at v0.14, which added a doubly robust estimator and Python 3.13 support. The releases before it followed the same shape: v0.13 brought the Generalized Adjustment Criterion for identification, v0.12 added time-series effect estimation and a rank-based anomaly scorer. Between the feature releases sit patch versions handling pandas and CUDA breakage.
Two threads run through the window. The identification side — DoWhy's differentiator against libraries that only estimate — keeps gaining criteria, from frontdoor with multiple variables through the Generalized Adjustment Criterion. The GCM side grows separately with missing-data handling, classifier selection logic and calibration work. The two halves are converging on a single API rather than staying separate entry points.
Given the pace of one estimator or criterion per release and the experimental flags still on missing-data support in GCM, the next release most likely promotes existing experimental features rather than opening a new estimation family.
OpenCTI ships on a roughly weekly date-stamped cadence, and the last six releases divide cleanly: the connector catalog was redesigned into a faceted marketplace, then the surrounding integrations experience was reworked around it, then the platform gained two-way connection with Filigran's XTM Hub. Alongside that, saved searches and saved filters became shareable and reusable across dashboards. The most recent releases are weighted toward fixes rather than new surface.
The centre of gravity is moving from OpenCTI as a self-contained platform to OpenCTI as a client of Filigran's wider ecosystem — connectors sourced from a catalog with support tiers, custom views deployed from XTM Hub, an MCP server exposed through XTM One. The workflow engine is maturing in parallel, picking up draft approval, transition restrictions and full reset. Telemetry coverage expanded significantly in the same period, which is what makes the catalog's adoption measurable.
Expect more of the platform's configuration surface — dashboards, playbooks, mappers — to become distributable through XTM Hub the way custom views and connectors already are. The workflow approval features suggest governance controls are the next area to fill in.
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 dowhy or OpenCTI.
tidyr replaced separate() with a family that says what it does.
modeltime built conformal intervals in, then went quiet on features.
performance keeps adding ways to check a model you have already fitted.
CmdStanPy is clearing deprecations ahead of a 2.0 it keeps announcing.
OpenHouse is hardening the seams where table policies and jobs quietly fail.
silx 3.0 moved its default Qt binding to PySide6 — a migration for everyone embedding it.
See all dowhy alternatives → · See all OpenCTI 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 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.
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.
Top dowhy alternatives in Analytics are ranked by recent ship velocity. Browse the "dowhy alternatives" section above for the current picks, or visit /alternatives/dowhy for the full list with editorial commentary on each.
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.