OpenCTI is rebuilding its connector layer into a marketplace and wiring the platform to XTM Hub
dowhy alternatives
The best dowhy alternatives in analytics tools, ranked by Sparkpulse's velocity_score.
Updated Aug 12, 2026
Looking for the best alternatives to dowhy? Sparkpulse tracks and ranks 12 alternatives in analytics tools by shipping velocity — how frequently each ships meaningful updates, verified from official changelogs. For reference, dowhy shipped 0 meaningful updates in the last 30 days and carries a velocity score of 0.0 out of 10 in 2026. The alternatives below are ranked the same way, so you're comparing real release momentum, not marketing claims.
About dowhy
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.
Velocity 0.0 · Last update 1h ago
Top 12 alternatives to dowhy
Ranked by recent ship velocity. Tap any card for the full editorial breakdown, or pivot to a head-to-head.
Fulcrum is consolidating on Esri, with Google Maps gone September 1
Omni ships weekly, and almost every week the headline item is an AI feature
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.
Iris ships steadily on a two-a-year cadence, but its feed publishes only pointers.
Julia's distribution library grinds forward one distribution at a time
Quantum chemistry package adding whole method families every release.
OpenMC's random ray solver has gone from new arrival to the centre of every release
TsFile is quietly rebuilding itself as an Arrow-speaking interchange format
tidyr replaced separate() with a family that says what it does.
modeltime built conformal intervals in, then went quiet on features.
dowhy vs alternatives — shipping velocity at a glance
Velocity score (0–10) and meaningful releases shipped in the last 30 days, from official changelogs. Higher = shipping faster.
| Product | Velocity | Sparks · 30d | Focus areas | Latest release |
|---|---|---|---|---|
| dowhy (baseline) | 0.0 | 0 | causal-inferenceeffect-estimationidentification | — |
| OpenCTI | 6.3 | 1 | threat-intelligenceconnector-marketplacextm-hub | Connector catalog is rebuilt as a faceted marketplace |
| Fulcrum | 6.3 | 0 | field-data-collectionesri-arcgisoffline-maps | — |
| Omni | 6.3 | 1 | business-intelligencesemantic-modelai-routines | AI semantic model generation goes generally available in Omni |
| OpenHouse | 5.0 | 0 | icebergdata governancetable policies | — |
| silx | 2.5 | 0 | synchrotronqthdf5 | 3.0.0: PySide6 becomes the default Qt binding, Python 3.10 required |
| iris | 2.5 | 0 | earth sciencerelease cadencepython | — |
| Distributions.jl | 2.5 | 0 | juliastatisticsdistributions | — |
| PySCF | 2.5 | 0 | quantum-chemistryperiodic-systemscoupled-cluster | — |
| OpenMC | 2.5 | 0 | monte-carlo-transportrandom-raydepletion | OpenMC 0.15.0 introduces a random ray transport solver |
| Apache TsFile | 2.5 | 0 | time-seriescolumnar-formatapache-arrow | — |
| tidyr | 0.0 | 0 | tidyversedata-reshapingpivoting | — |
| modeltime | 0.0 | 0 | forecastingconformal-predictiontidymodels | — |
The 12 best dowhy alternatives, in depth
1. OpenCTI · velocity 6.3
OpenCTI is rebuilding its connector layer into a marketplace and wiring the platform to XTM Hub.
Over the last 30 days OpenCTI shipped 1 meaningful update vs dowhy's 0, most recently “Connector catalog is rebuilt as a faceted marketplace”. Its velocity score of 6.3/10 blends that with longer-term release cadence.
Where dowhy leans on causal inference, effect estimation and identification, OpenCTI focuses on threat intelligence, connector marketplace and xtm hub.
Over the last 30 days OpenCTI has been shipping faster than dowhy — a point in its favour if release momentum matters to you.
2. Fulcrum · velocity 6.3
Fulcrum is consolidating on Esri, with Google Maps gone September 1.
Its velocity score of 6.3/10 reflects longer-term release cadence.
Where dowhy leans on causal inference, effect estimation and identification, Fulcrum focuses on field data collection, esri arcgis and offline maps.
Fulcrum and dowhy have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
3. Omni · velocity 6.3
Omni ships weekly, and almost every week the headline item is an AI feature.
Over the last 30 days Omni shipped 1 meaningful update vs dowhy's 0, most recently “AI semantic model generation goes generally available in Omni”. Its velocity score of 6.3/10 blends that with longer-term release cadence.
Where dowhy leans on causal inference, effect estimation and identification, Omni focuses on business intelligence, semantic model and ai routines.
Over the last 30 days Omni has been shipping faster than dowhy — a point in its favour if release momentum matters to you.
4. OpenHouse · velocity 5.0
OpenHouse is hardening the seams where table policies and jobs quietly fail.
Its velocity score of 5.0/10 reflects longer-term release cadence.
Where dowhy leans on causal inference, effect estimation and identification, OpenHouse focuses on iceberg, data governance and table policies.
OpenHouse and dowhy have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
5. silx · velocity 2.5
Silx 3.0 moved its default Qt binding to PySide6 — a migration for everyone embedding it.
Its velocity score of 2.5/10 reflects longer-term release cadence; its most recent meaningful update was “3.0.0: PySide6 becomes the default Qt binding, Python 3.10 required”.
Where dowhy leans on causal inference, effect estimation and identification, silx focuses on synchrotron, qt and hdf5.
silx and dowhy have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
6. iris · velocity 2.5
Iris ships steadily on a two-a-year cadence, but its feed publishes only pointers.
Its velocity score of 2.5/10 reflects longer-term release cadence.
Where dowhy leans on causal inference, effect estimation and identification, iris focuses on earth science, release cadence and python.
iris and dowhy have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
7. Distributions.jl · velocity 2.5
Julia's distribution library grinds forward one distribution at a time.
Its velocity score of 2.5/10 reflects longer-term release cadence.
Where dowhy leans on causal inference, effect estimation and identification, Distributions.jl focuses on julia, statistics and distributions.
Distributions.jl and dowhy have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full Distributions.jl trajectory → · Compare dowhy vs Distributions.jl →
8. PySCF · velocity 2.5
Quantum chemistry package adding whole method families every release.
Its velocity score of 2.5/10 reflects longer-term release cadence.
Where dowhy leans on causal inference, effect estimation and identification, PySCF focuses on quantum chemistry, periodic systems and coupled cluster.
PySCF and dowhy have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
9. OpenMC · velocity 2.5
OpenMC's random ray solver has gone from new arrival to the centre of every release.
Its velocity score of 2.5/10 reflects longer-term release cadence; its most recent meaningful update was “OpenMC 0.15.0 introduces a random ray transport solver”.
Where dowhy leans on causal inference, effect estimation and identification, OpenMC focuses on monte carlo transport, random ray and depletion.
OpenMC and dowhy have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
10. Apache TsFile · velocity 2.5
TsFile is quietly rebuilding itself as an Arrow-speaking interchange format.
Its velocity score of 2.5/10 reflects longer-term release cadence.
Where dowhy leans on causal inference, effect estimation and identification, Apache TsFile focuses on time series, columnar format and apache arrow.
Apache TsFile and dowhy have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full Apache TsFile trajectory → · Compare dowhy vs Apache TsFile →
11. tidyr · velocity 0.0
Tidyr replaced separate() with a family that says what it does.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where dowhy leans on causal inference, effect estimation and identification, tidyr focuses on tidyverse, data reshaping and pivoting.
tidyr and dowhy have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
12. modeltime · velocity 0.0
Modeltime built conformal intervals in, then went quiet on features.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where dowhy leans on causal inference, effect estimation and identification, modeltime focuses on forecasting, conformal prediction and tidymodels.
modeltime and dowhy have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Frequently asked questions
What are the best alternatives to dowhy?
The top dowhy alternatives we currently track in analytics tools are OpenCTI, Fulcrum, Omni, OpenHouse, silx, ranked by recent ship velocity.
How is this list of dowhy alternatives ranked?
Alternatives are ranked by Sparkpulse's velocity_score — release cadence + 30-day spark count + sector-relative ship rate.
Can I compare dowhy directly with one of these alternatives?
Yes — every card has a "Compare with dowhy" link to a side-by-side /compare page.