Fulcrum
Fulcrum is consolidating on Esri, with Google Maps gone September 1
Comparison · Analytics
dbt Core vs Whatagraph
A side-by-side editorial comparison of dbt Core and Whatagraph — release velocity, themes, recent moves, and the top alternatives to consider.
dbt Core vs Whatagraph: at a glance
| Feature | dbt Core | Whatagraph |
|---|---|---|
| Sector | Analytics | Analytics |
| Velocity score | 7.5 | 5.0 |
| Sparks · 30d | 2 | 0 |
| Top themes | dbt-fusion, rust-rewrite, static-analysis, semantic-layer | marketing-reporting, agencies, integrations, data-storage |
| Last editorial update | 1d ago | 12d ago |
| Website | Visit → | — |
What is dbt Core?
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.
What is Whatagraph?
Marketing reporting quietly rebuilding itself around stored data instead of live API calls.
Whatagraph builds client reports for marketing agencies by pulling from dozens of ad, analytics, and call-tracking sources. The recent releases split into two groups. One keeps widening the source catalog — Snowflake as a warehouse source, WhatConverts lead data, and Ahrefs Rank Tracker as a keyword-level integration separate from the existing domain-level Ahrefs. The other attacks reliability: a Data Storage destination that pre-syncs data so widgets stop waiting on live APIs, the Basis integration rebuilt on that model, and automatic failover when the team member whose account owns a source loses access.
dbt Core vs Whatagraph: editorial side-by-side
dbt Core
7.5ANALYTICS
The Rust rewrite crosses from alpha to beta, and it can now bind SQL without touching the warehouse.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
Whatagraph
5.0ANALYTICS
Marketing reporting quietly rebuilding itself around stored data instead of live API calls.
◆ Current state
Whatagraph builds client reports for marketing agencies by pulling from dozens of ad, analytics, and call-tracking sources. The recent releases split into two groups. One keeps widening the source catalog — Snowflake as a warehouse source, WhatConverts lead data, and Ahrefs Rank Tracker as a keyword-level integration separate from the existing domain-level Ahrefs. The other attacks reliability: a Data Storage destination that pre-syncs data so widgets stop waiting on live APIs, the Basis integration rebuilt on that model, and automatic failover when the team member whose account owns a source loses access.
◆ Where it's heading
The reporting layer is being made boring in the good sense. Live-API reports break in ways an agency cannot explain to a client — a token expires, someone leaves, a widget goes blank mid-presentation — and the last few months answer each of those failure modes directly: store the data, align spend figures with the vendor's own billing totals, and silently switch to a colleague's credentials when one account stops working. The presentation work is following the same instinct, replacing per-metric threshold rules with automatic shading and consolidating scattered style settings into themes. Less configuration to maintain, fewer ways for a report to be wrong in front of a client.
◆ Prediction
Credential failover currently rescues a source when someone else on the team happens to have access; the gap it exposes is agency-owned connections that do not depend on an individual at all, which is where this thread points next.
Alternatives to dbt Core and Whatagraph
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 Whatagraph.
Omni
Omni ships weekly, and almost every week the headline item is an AI feature
OpenDataDiscovery
Four ODD Platform releases in two weeks, and not one of them changes the product
Apache Baremaps
Baremaps got geoparquet and hillshading, then went quiet for eighteen months in incubation
Deequ
Deequ ships GitHub tags whose release notes are one commit message long
Marquez
Marquez spent 2024 turning a lineage store into a UI, then stopped releasing
See all dbt Core alternatives → · See all Whatagraph alternatives →
Recent activity from dbt Core and Whatagraph
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agodbt Coredbt Fusion 2.0 reaches first beta with catalog-free SQL binding ⚡
- 12d agoWhatagraphOne broken connection won't break your reports
- 13d agoWhatagraphClearer charts and tables, and a faster way to find the right template
- 18d agoWhatagraphTrack your keywords against competitors with Ahrefs Rank Tracker
- 22d agodbt Corev2.0.0-alpha.5
- 26d agodbt Coredbt-core v1.12.0 ⚡
- 28d agodbt Coredbt-core v1.12.0rc3
- 1mo agoWhatagraphBasis rebuilt: faster data, cleaner numbers, per-client sources
- 1mo agodbt Coredbt-core v1.12.0rc2
- 1mo agodbt Coredbt-core v1.12.0rc1
- 1mo agoWhatagraphThemes settings, simplified
- 2mo agoWhatagraphWhatConverts data available on Whatagraph
Frequently asked questions
What is the difference between dbt Core and Whatagraph?
They serve adjacent needs but don't currently overlap on shipped themes. dbt Core is currently shipping more aggressively (velocity 7.5 vs 5.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.
Is dbt Core better than Whatagraph?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. dbt Core is currently shipping more aggressively (velocity 7.5 vs 5.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.
What are the best alternatives to dbt Core?
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.
What are the best alternatives to Whatagraph?
Top Whatagraph alternatives in Analytics are ranked by recent ship velocity. Browse the "Whatagraph alternatives" section above for the current picks, or visit /alternatives/whatagraph for the full list with editorial commentary on each.