Mage
Feature releases every two months in 2024; one bugfix release in the last twelve.
Comparison · Analytics
Lightdash vs dbt Core
A side-by-side editorial comparison of Lightdash and dbt Core — release velocity, themes, recent moves, and the top alternatives to consider.
Lightdash vs dbt Core: at a glance
| Feature | Lightdash | dbt Core |
|---|---|---|
| Sector | Analytics | Analytics |
| Velocity score | 7.5 | 7.5 |
| Sparks · 30d | 1 | 2 |
| Top themes | bi-as-code, data-apps, ai-agents, governance | data-transformation, lakehouse, iceberg, dual-engine |
| Last editorial update | 16h ago | 3h ago |
| Website | — | Visit → |
What is Lightdash?
Lightdash is making the whole instance — dashboards, roles, agents — checkable into git
Lightdash ships close to daily and the recent run splits cleanly in two. One track is the data-app platform: apps that call third-party HTTP APIs through a server-side proxy that never exposes a secret, a query inspector that links a chart back to the query behind it, and prompt-generated chart types. The other is making the instance declarative — content as code now covers charts, dashboards, spaces, permissions, virtual views, AI agents, automations, and organization-level users, groups and custom roles.
What is dbt Core?
Two engines in one repo: the Python 1.x line tightens while Fusion 2.0 goes lakehouse-catalog native
dbt-core is releasing on two tracks at once. The Python line reached 1.12.0 on 16 July after three release candidates, and it is a tightening release: the experimental `dbt login` command and the bundled dbt-state plugin were removed outright, and flags introduced in 1.9 and 1.10 now default to true. The 2.0.0 alpha track is the Fusion engine, and its work is almost entirely about catalogs — read-write Horizon and Unity access over Iceberg REST via DuckDB, a catalogs.yml v2 covering DuckLake, Iceberg REST and local filesystem, plus catalog_database overrides and Redshift catalog generation through SHOW TABLES and SVV_REDSHIFT_COLUMNS.
Lightdash vs dbt Core: editorial side-by-side
Lightdash
7.5ANALYTICS
Lightdash is making the whole instance — dashboards, roles, agents — checkable into git
◆ Current state
Lightdash ships close to daily and the recent run splits cleanly in two. One track is the data-app platform: apps that call third-party HTTP APIs through a server-side proxy that never exposes a secret, a query inspector that links a chart back to the query behind it, and prompt-generated chart types. The other is making the instance declarative — content as code now covers charts, dashboards, spaces, permissions, virtual views, AI agents, automations, and organization-level users, groups and custom roles.
◆ Where it's heading
Both tracks serve the same reader: a data team that wants BI it can build on and review in a pull request. Merging verified content with AI agents was the tell — humans and agents now draw on one trust layer, and the Lightdash MCP exposes it to outside tools like Claude and Cursor. The surface Lightdash is claiming is the semantic and governance layer, with the visualization layer increasingly something you describe rather than configure.
◆ Prediction
The export side is now complete enough that CI checks on Lightdash content — diffing or validating the exported definitions in a pull request — are the natural next step.
dbt Core
7.5ANALYTICS
Two engines in one repo: the Python 1.x line tightens while Fusion 2.0 goes lakehouse-catalog native
◆ Current state
dbt-core is releasing on two tracks at once. The Python line reached 1.12.0 on 16 July after three release candidates, and it is a tightening release: the experimental `dbt login` command and the bundled dbt-state plugin were removed outright, and flags introduced in 1.9 and 1.10 now default to true. The 2.0.0 alpha track is the Fusion engine, and its work is almost entirely about catalogs — read-write Horizon and Unity access over Iceberg REST via DuckDB, a catalogs.yml v2 covering DuckLake, Iceberg REST and local filesystem, plus catalog_database overrides and Redshift catalog generation through SHOW TABLES and SVV_REDSHIFT_COLUMNS.
◆ Where it's heading
The division of labour between the two tracks is clear from the entries: 1.x is consolidating and removing experiments, while 2.0 is where the new surface area lands. The 2.0 surface is specifically the lakehouse catalog layer — dbt is moving from a tool that writes to a warehouse toward one that binds to open table catalogs directly, with materialization made catalog-aware. Notably 1.12.0rc1 also teaches the Python engine to tolerate Fusion-specific warn_error_options rather than erroring, so the two engines are being made to coexist in the same projects rather than fork.
◆ Prediction
The alphas are still expanding catalog coverage adapter by adapter, so expect further catalog integrations and continued catalogs.yml v2 work before 2.0 leaves alpha. On the Python side, with the deprecated flags now defaulted and the experimental commands removed, 1.12 looks like a stabilization point rather than a base for new features.
Alternatives to Lightdash and dbt Core
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 Lightdash or dbt Core.
OpenMetadata
MCP servers became first-class governed assets in 1.13.0 — and 2.0 is now in release candidate.
TimescaleDB
Every release in this window is columnstore work — compression is where TimescaleDB is spending
Polars
The streaming engine is stable and the API is being narrowed — Polars is clearing ground for a breaking release
DuckDB
Six releases, all patches — this window shows DuckDB's maintenance machine, not its roadmap
Basedash
Basedash turned its AI analyst into an API, then spent two weeks making it auditable
See all Lightdash alternatives → · See all dbt Core alternatives →
Recent activity from Lightdash and dbt Core
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agoLightdash📦 More content as code
- 1d agoLightdashSQL Runner: Big Number
- 5d agoLightdash🎯 Ask for one filter, not every filter
- 12d agodbt CoreFusion alpha 5: Redshift datasharing catalogs and job-specific deferral
- 15d agodbt Coredbt-core 1.12.0 drops `dbt login` and the dbt-state plugin ⚡
- 17d agodbt Core1.12.0 release candidate 3
- 19d agoLightdash🌍 Timezones that just work
- 22d agodbt Core1.12.0 release candidate 2
- 23d agoLightdash🔌 Data apps can now talk to APIs ⚡
- 24d agoLightdash🕵️♀️ Inspect your data app queries
- 25d agodbt Core1.12.0 release candidate 1
- 26d agodbt CoreFusion gains read-write Iceberg REST catalogs and catalogs.yml v2 ⚡
Frequently asked questions
What is the difference between Lightdash and dbt Core?
They serve adjacent needs but don't currently overlap on shipped themes. Lightdash and dbt Core are shipping at a similar cadence (velocity 7.5 vs 7.5, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is Lightdash better than dbt Core?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Lightdash and dbt Core are shipping at a similar cadence (velocity 7.5 vs 7.5, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
What are the best alternatives to Lightdash?
Top Lightdash alternatives in Analytics are ranked by recent ship velocity. Browse the "Lightdash alternatives" section above for the current picks, or visit /alternatives/lightdash for the full list with editorial commentary on each.
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.