Fulcrum
Fulcrum ships MCP server and AI Toolkit to let AI assistants build and query field data forms
Comparison · Analytics
Marquez vs dbt Core
A side-by-side editorial comparison of Marquez and dbt Core — release velocity, themes, recent moves, and the top alternatives to consider.
Marquez vs dbt Core: at a glance
What is Marquez?
Marquez spent 2024 turning a lineage store into a UI, then stopped releasing
Marquez is the reference metadata server for OpenLineage, and this window captures a concentrated push on its web interface: a column-lineage page and redesigned lineage graph in 0.45.0, data quality and job status displays in 0.47.0, and a data observability dashboard in 0.50.0 showing event stats over 24-hour and 7-day windows with per-source, per-dataset and per-job views. The API side moved in step — job tagging, dataset schema versions, paging on jobs and dataset versions, job-to-job lineage, richer metrics labels. One contributor accounts for nearly all the web work in these entries. Note that the 0.45 through 0.49 releases were all stamped within three minutes of each other and in reverse version order, so publication timestamps here do not reflect release order.
What is dbt Core?
dbt 2.0 enters final RC with beta Snowflake interactive_table materialization and full ClickHouse MV support.
dbt Core is in the final stretch of the v2.0 release cycle, running RC builds while the 1.x stable branch continues receiving targeted fixes. RC.2 added beta support for Snowflake's interactive_table materialization — covering static and dynamic variants with config-change detection for target_lag, warehouse, and cluster_by — and completed ClickHouse materialized view support via the new ADBC driver. The 1.12.5 and 1.11.15 patch releases address a MetricFlow protocol compliance issue and a package path traversal security fix respectively.
Marquez vs dbt Core: editorial side-by-side
Marquez
0.0ANALYTICS
Marquez spent 2024 turning a lineage store into a UI, then stopped releasing
◆ Current state
Marquez is the reference metadata server for OpenLineage, and this window captures a concentrated push on its web interface: a column-lineage page and redesigned lineage graph in 0.45.0, data quality and job status displays in 0.47.0, and a data observability dashboard in 0.50.0 showing event stats over 24-hour and 7-day windows with per-source, per-dataset and per-job views. The API side moved in step — job tagging, dataset schema versions, paging on jobs and dataset versions, job-to-job lineage, richer metrics labels. One contributor accounts for nearly all the web work in these entries. Note that the 0.45 through 0.49 releases were all stamped within three minutes of each other and in reverse version order, so publication timestamps here do not reflect release order.
◆ Where it's heading
The arc is a backend project growing a front end: lineage data that existed in the API was progressively given pages, panels and paging, and by 0.50.0 the framing had shifted from lineage graph to observability dashboard. Tagging deepened in the same period, moving from dataset tags to field-level tags to job tags. That arc stops abruptly — 0.50.0 in October 2024 is the last entry, with nothing published in the roughly two years since.
◆ Prediction
The entries give no roadmap signal past 0.50.0, and the job-to-job lineage change was explicitly framed as a prompt for a wider parent/child hierarchy discussion that no later release picks up, so that hierarchy work is best read as unfinished rather than planned.
dbt Core
6.3ANALYTICS
dbt 2.0 enters final RC with beta Snowflake interactive_table materialization and full ClickHouse MV support.
◆ Current state
dbt Core is in the final stretch of the v2.0 release cycle, running RC builds while the 1.x stable branch continues receiving targeted fixes. RC.2 added beta support for Snowflake's interactive_table materialization — covering static and dynamic variants with config-change detection for target_lag, warehouse, and cluster_by — and completed ClickHouse materialized view support via the new ADBC driver. The 1.12.5 and 1.11.15 patch releases address a MetricFlow protocol compliance issue and a package path traversal security fix respectively.
◆ Where it's heading
dbt 2.0's final stabilization phase is expanding adapter coverage depth rather than adding new DAG primitives. ClickHouse now has full MV and unit-test support; Snowflake gets interactive table handling with edge-case-level cluster_by comparison fixes that only come from deep validation work. The pattern: make dbt reliably correct on what modern warehouses already ship, rather than shipping new features.
◆ Prediction
The v2.0 stable tag is imminent — RC.2's fixes are narrow and precision-targeted, not broad. Post-2.0 expect a Fusion manifest integration stabilization push, given that 1.12.4 shipped two fixes specifically for Fusion-generated manifests.
Alternatives to Marquez 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 Marquez or dbt Core.
Holistics
Holistics builds AI governance and docs-as-analytics in parallel, shipping both weekly
OpenHouse
OpenHouse breaks ground on Iceberg views while tightening storage lifecycle and authorization
Lightdash
Lightdash is cutting its dbt dependency and building AI-powered authoring into every layer of its BI stack.
Keboola
Keboola's Kai AI assistant hits GA, completing the pivot from data platform to AI-native pipeline orchestration layer.
Omni
Omni's Apps reach general availability, completing its embedded analytics platform pitch.
See all Marquez alternatives → · See all dbt Core alternatives →
Recent activity from Marquez and dbt Core
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 20h agodbt Coredbt 1.12.5: MetricFlow protocol fix and v2 install banner
- 1d agodbt Coredbt 2.0.2 test-PyPI build
- 5d agodbt Coredbt 2.0.0-rc.2: ClickHouse MV support and Snowflake interactive_table beta
- 7d agodbt Coredbt 2.0.0-dev.39 test-PyPI: ClickHouse ADBC driver settings
- 7d agodbt Coredbt 2.0.0-dev.38 test-PyPI: ClickHouse ADBC driver settings
- 7d agodbt Coredbt 2.0.0-dev.37 test-PyPI: ClickHouse ADBC driver settings
- 1y agoMarquezMarquez 0.50.0 adds a data observability dashboard
- 2y agoMarquezMarquez 0.45.0 ships a column lineage page and redesigned graph
- 2y agoMarquezMarquez 0.46.0 cleans up the UI and fixes streaming terminal events
- 2y agoMarquezMarquez 0.47.0 adds data quality and job status views, job tagging
- 2y agoMarquezMarquez 0.49.0 adds job-to-job lineage to the API
- 2y agoMarquezMarquez 0.48.0 adds paging and dataset schema versions
Frequently asked questions
What is the difference between Marquez and dbt Core?
They serve adjacent needs but don't currently overlap on shipped themes. dbt Core is currently shipping more aggressively (velocity 6.3 vs 0.0), 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.
Is Marquez 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 6.3 vs 0.0), 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.
What are the best alternatives to Marquez?
Top Marquez alternatives in Analytics are ranked by recent ship velocity. Browse the "Marquez alternatives" section above for the current picks, or visit /alternatives/marquez 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.