OpenMetadata
MCP servers became first-class governed assets in 1.13.0 — and 2.0 is now in release candidate.
Comparison · Analytics
Mage vs dbt Core
A side-by-side editorial comparison of Mage and dbt Core — release velocity, themes, recent moves, and the top alternatives to consider.
Mage vs dbt Core: at a glance
What is Mage?
Feature releases every two months in 2024; one bugfix release in the last twelve.
The release cadence has collapsed. Through 2024 Mage shipped roughly every two months with substantial features each time — memory management rework, dynamic blocks, new sources and destinations, Python 3.11 and 3.12 support. 2025 produced two releases. The most recent entry, 0.9.79 in January 2026, contains no feature section at all: it is dependency pinning, SQLAlchemy 2.0 compatibility, character escaping during code interpolation, and log file handle cleanup. Nothing has followed it in the six months since.
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.
Mage vs dbt Core: editorial side-by-side
Mage
0.0ANALYTICS
Feature releases every two months in 2024; one bugfix release in the last twelve.
◆ Current state
The release cadence has collapsed. Through 2024 Mage shipped roughly every two months with substantial features each time — memory management rework, dynamic blocks, new sources and destinations, Python 3.11 and 3.12 support. 2025 produced two releases. The most recent entry, 0.9.79 in January 2026, contains no feature section at all: it is dependency pinning, SQLAlchemy 2.0 compatibility, character escaping during code interpolation, and log file handle cleanup. Nothing has followed it in the six months since.
◆ Where it's heading
The arc runs from expanding the product to keeping it compiling. The 2024 releases added capability — a canvas rework, multi-project support, streaming sinks, Kubernetes job parameters. The 2025 releases shifted toward integrations and CVE response, including a batch of path traversal fixes carrying assigned identifiers. The last release is entirely defensive, including vendoring croniter into the repository and locking scikit-learn to stop upstream changes from breaking builds. That is the profile of a codebase being kept viable rather than developed.
◆ Prediction
The entries give no basis for predicting the next release — a six-month gap after a dependency-only patch is the only signal available, and nothing here indicates whether the line is paused or finished.
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 Mage 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 Mage or dbt Core.
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
Lightdash
Lightdash is making the whole instance — dashboards, roles, agents — checkable into git
See all Mage alternatives → · See all dbt Core alternatives →
Recent activity from Mage and dbt Core
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 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
- 22d agodbt Core1.12.0 release candidate 2
- 25d agodbt Core1.12.0 release candidate 1
- 26d agodbt CoreFusion gains read-write Iceberg REST catalogs and catalogs.yml v2 ⚡
- 6mo agoMageDependency pinning and SQLAlchemy 2.0 compatibility fixes
- 11mo agoMagePath traversal CVE fixes and cancellation callbacks
- 1y agoMageTeradata, Doris and Airtable connectors, rotatable API tokens
- 1y agoMageAirtable destination and Python 3.11 and 3.12 support
- 1y agoMageGoogle Cloud Storage source and Airtable integration
- 1y agoMageMemory management rework and dynamic blocks 2.0
Frequently asked questions
What is the difference between Mage and dbt Core?
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.
Is Mage better than dbt Core?
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.
What are the best alternatives to Mage?
Top Mage alternatives in Analytics are ranked by recent ship velocity. Browse the "Mage alternatives" section above for the current picks, or visit /alternatives/mage-ai 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.