Fulcrum
Fulcrum launches MCP + AI Toolkit in Labs, giving AI assistants the ability to build and query Fulcrum forms directly.
A side-by-side editorial comparison of dbt Core and DuckDB — release velocity, themes, recent moves, and the top alternatives to consider.
dbt Core 2.0 is in release candidate, replacing its Python parser with a Rust-based Fusion engine
dbt Core is in a major version transition. The 2.0.0 RC series, now at rc.2, introduces the Fusion parser—a Rust-based replacement for the Python compilation engine—alongside first-party ClickHouse support via the ADBC driver, a new Exasol adapter, and expanded Databricks and Snowflake capabilities. The 1.x line continues to receive maintenance fixes in parallel.
Six releases, all patches — this window shows DuckDB's maintenance machine, not its roadmap
Every entry in this window is a bugfix release, and two release lines are being maintained side by side: 1.5.5, 1.5.4, 1.5.3, 1.5.2 and 1.5.1 on the current branch, with 1.4.5 shipped the same day as 1.5.4 for users still on the older line. The content is backports, race-condition fixes, extension and build plumbing, and in 1.5.5 a backport of out-of-bounds security fixes. Feature releases sit outside this window, so what is visible is the patch cadence rather than the direction.
dbt Core is in a major version transition. The 2.0.0 RC series, now at rc.2, introduces the Fusion parser—a Rust-based replacement for the Python compilation engine—alongside first-party ClickHouse support via the ADBC driver, a new Exasol adapter, and expanded Databricks and Snowflake capabilities. The 1.x line continues to receive maintenance fixes in parallel.
The architectural story is Fusion: a faster, more correct compilation engine that enables stricter manifest validation, better cross-adapter consistency, and eventual binary distribution for non-Python environments. ClickHouse and Exasol add two new adapters in a single release cycle, suggesting dbt Labs is broadening the platform list as the 2.0 engine makes cross-adapter work cheaper.
The 2.0 GA release is close—the RC cycle is stabilizing. After GA, the Fusion engine will likely unlock new features that were hard to build on the Python parser, including faster parse times and richer lint rules.
Every entry in this window is a bugfix release, and two release lines are being maintained side by side: 1.5.5, 1.5.4, 1.5.3, 1.5.2 and 1.5.1 on the current branch, with 1.4.5 shipped the same day as 1.5.4 for users still on the older line. The content is backports, race-condition fixes, extension and build plumbing, and in 1.5.5 a backport of out-of-bounds security fixes. Feature releases sit outside this window, so what is visible is the patch cadence rather than the direction.
The pattern is a project treating its previous minor as a supported branch rather than abandoning it — same-day 1.4.5 and 1.5.4 releases, with fixes explicitly backported from the newer line. Patch spacing has tightened over the window, from roughly two months between 1.5.1 and 1.5.2 to about five weeks between 1.5.4 and 1.5.5. Each release also points at an announcement blog post, so the substantive narrative lives off the feed.
The visible entries only support a continuation of the same pattern: further patch releases on both the 1.5 and 1.4 lines, with fixes backported between them. Nothing in this window signals what the next feature release contains.
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 DuckDB.
Fulcrum launches MCP + AI Toolkit in Labs, giving AI assistants the ability to build and query Fulcrum forms directly.
Holistics is weaving AI governance and proactive alerting into its analytics semantic layer.
Keboola's Kai AI assistant hits GA, completing the pivot from data platform to AI-native pipeline orchestration layer.
Omni's Apps reach general availability, completing its embedded analytics platform pitch.
Lightdash ships AI-generated custom chart types — describe what you want, get a reusable chart type for your whole project.
OpenCTI ships FIPS-validated base images and a new vulnerability data model, targeting enterprise and government deployments.
See all dbt Core alternatives → · See all DuckDB 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 6.3 vs 2.5), 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. dbt Core is currently shipping more aggressively (velocity 6.3 vs 2.5), 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 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 DuckDB alternatives in Analytics are ranked by recent ship velocity. Browse the "DuckDB alternatives" section above for the current picks, or visit /alternatives/duckdb for the full list with editorial commentary on each.