Fulcrum
Fulcrum is consolidating on Esri, with Google Maps gone September 1
A side-by-side editorial comparison of Chord and dbt Core — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Chord | dbt Core |
|---|---|---|
| Sector | Analytics | Analytics |
| Velocity score | 6.3 | 7.5 |
| Sparks · 30d | 1 | 2 |
| Top themes | cdp, agent-native, audience-building, conversational-analytics | dbt-fusion, rust-rewrite, static-analysis, semantic-layer |
| Last editorial update | 5d ago | 1d ago |
| Website | — | Visit → |
Chord rebuilt Copilot, renamed it, and let it start building the audiences it used to describe
Chord has spent four months rebuilding its assistant and is now finishing the rename. Copilot Next appeared as a limited preview in late June, then gained persistent chat history, shareable conversations, answers grounded in the customer's own business definitions, and background detection of whether feedback was positive or negative. As of this release the Copilot name is retired in favour of Ask Chord.
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.
Chord has spent four months rebuilding its assistant and is now finishing the rename. Copilot Next appeared as a limited preview in late June, then gained persistent chat history, shareable conversations, answers grounded in the customer's own business definitions, and background detection of whether feedback was positive or negative. As of this release the Copilot name is retired in favour of Ask Chord.
The rename is the least interesting part; what changed is what the assistant is allowed to do. Answering questions about data became building audiences from a conversation and naming them, which moves Chord AI out of the reporting layer and into the operational path of the CDP. The grounding in business definitions and the visible sources are the trust scaffolding that had to land first before users would let it write anything.
If audience building was the first write action, activation is the obvious next one — pushing an audience to a destination or scheduling it rather than handing it back for a human to send. These entries do not yet show that step, so it stays a read on direction rather than a certainty.
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.
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 Chord or dbt Core.
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
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
Deequ ships GitHub tags whose release notes are one commit message long
Marquez spent 2024 turning a lineage store into a UI, then stopped releasing
See all Chord alternatives → · See all dbt Core 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 6.3), with 2 editorial sparks in the last 30 days against 1. 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 6.3), with 2 editorial sparks in the last 30 days against 1. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
Top Chord alternatives in Analytics are ranked by recent ship velocity. Browse the "Chord alternatives" section above for the current picks, or visit /alternatives/chord for the full list with editorial commentary on each.
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.