Omni
Omni ships weekly, and almost every week the headline item is an AI feature
A side-by-side editorial comparison of dbt Core and Deequ — release velocity, themes, recent moves, and the top alternatives to consider.
The Rust rewrite crosses from alpha to beta, and it can now bind SQL without touching the warehouse.
dbt is running two release lines at once. The 1.x Python line reached 1.12.0 in July, a GA that removed the experimental dbt login command and the bundled dbt-state plugin outright while adding the v2 semantic layer YAML parsing. The 2.0 Fusion line — the Rust engine — moved through five alphas and reached its first beta on August 10, carrying catalog-free binding, dbt state explain, redundant-test skipping, and a lint rule system that understands node selection.
Deequ ships GitHub tags whose release notes are one commit message long
Deequ is a data quality library for Spark, and it releases per Spark version — tags carry a -spark-3.5 or -spark-4.0 suffix, so the same code line ships more than once. The release notes are whatever the last commit message said, which here means each entry is a single line. Four releases landed in a month between March and April 2026, and only two of them contain any product change: a Range analyzer with DQDL rule support, and a processRowsTyped API for typed outcome access.
dbt is running two release lines at once. The 1.x Python line reached 1.12.0 in July, a GA that removed the experimental dbt login command and the bundled dbt-state plugin outright while adding the v2 semantic layer YAML parsing. The 2.0 Fusion line — the Rust engine — moved through five alphas and reached its first beta on August 10, carrying catalog-free binding, dbt state explain, redundant-test skipping, and a lint rule system that understands node selection.
Fusion is being built to do statically what dbt-core did by asking the warehouse. Catalog-free binding lets SQL bind without introspection, tests get skipped when they are provably redundant, and dbt State speculatively submits nodes while the dependency prefetch is still in flight — all of it trading round-trips for compile-time analysis. Meanwhile 1.x is absorbing the v2 semantic layer YAML piece by piece, which puts metrics and entities into the model graph itself. Adapter breadth keeps widening in parallel, with Databricks service principal auth, Redshift group grants, and ClickHouse materialization configs.
With beta.1 out, the next milestones are further betas hardening the Fusion feature set toward parity, and continued v2 semantic YAML work landing in the 1.x line.
Deequ is a data quality library for Spark, and it releases per Spark version — tags carry a -spark-3.5 or -spark-4.0 suffix, so the same code line ships more than once. The release notes are whatever the last commit message said, which here means each entry is a single line. Four releases landed in a month between March and April 2026, and only two of them contain any product change: a Range analyzer with DQDL rule support, and a processRowsTyped API for typed outcome access.
The visible work points in one direction — making check results programmatically consumable rather than just readable. A typed outcome API and a rule language binding are what you build when Deequ is being called from a pipeline that reacts to the result, not from a notebook where a human reads it. The column-pruning override added alongside the Range analyzer suggests the same attention on the cost side, keeping analyzers from scanning columns they do not reference.
The entries are too thin to support a confident read of what comes next; the only clear pattern is that each change will ship separately against Spark 3.5 and Spark 4.0, so the version skew between those branches will keep widening.
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 dbt Core or Deequ.
Omni ships weekly, and almost every week the headline item is an AI feature
Four ODD Platform releases in two weeks, and not one of them changes the product
Baremaps got geoparquet and hillshading, then went quiet for eighteen months in incubation
Marquez spent 2024 turning a lineage store into a UI, then stopped releasing
Amundsen's last release was a config flag, and the feed has been silent for two years
LinkedIn's Iceberg control plane, shipping one pull request per release.
See all dbt Core alternatives → · See all Deequ alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. dbt Core is currently shipping more aggressively (velocity 7.5 vs 0.0), with 2 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. dbt Core is currently shipping more aggressively (velocity 7.5 vs 0.0), with 2 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 dbt Core alternatives in Analytics are ranked by recent ship velocity. Browse the "dbt Core alternatives" section above for the current picks, or visit /alternatives/dbt-core for the full list with editorial commentary on each.
Top Deequ alternatives in Analytics are ranked by recent ship velocity. Browse the "Deequ alternatives" section above for the current picks, or visit /alternatives/deequ for the full list with editorial commentary on each.