← Back to home
Comparison · Analytics

dbt Core vs Metabase

A side-by-side editorial comparison of dbt Core and Metabase — release velocity, themes, recent moves, and the top alternatives to consider.

dbt Core vs Metabase: at a glance

Featuredbt CoreMetabase
SectorAnalyticsAnalytics
Velocity score7.52.5
Sparks · 30d10
Top themesmajor-release, oss-fork, agent-skills, databricksmcp server, agentic analytics, open source ai, semantic layer
Last editorial update2d ago4mo ago
WebsiteVisit →Visit →

What is dbt Core?

dbt 2.0 ships — proprietary binary forks from dbt-oss as AI agent skills land

dbt just shipped its 2.0.0 GA release, formally splitting the codebase into a proprietary 'dbt' binary (the Fusion engine) and 'dbt-oss'. The 2.0 release adds AI agent skill installs from packages, native Databricks metric view materializations, and a new ClickHouse ADBC driver. Post-2.0 dev builds (dev.41) are already extending Lake Compute with Databricks Unity Catalog read access.

Read the full dbt Core trajectory →

What is Metabase?

Metabase open-sourced its AI stack and shipped an MCP server — analytics is going agentic.

Metabase's recent two releases have been the most directionally significant in years. Metabase 60 (March) open-sourced the company's AI tools, shipped an official Metabase MCP server, put Metabot inside Slack, added bring-your-own-model, plus a metrics explorer and split multi-series charts. Metabase 59 (February) introduced Data Studio — an analyst workbench with a semantic layer — and pushed AI SQL generation into the open-source edition. Earlier 55–58 work focused on Documents, embedded analytics, dark mode, and governance.

Read the full Metabase trajectory →

dbt Core vs Metabase: editorial side-by-side

D
dbt Core
ANALYTICS
7.5

dbt 2.0 ships — proprietary binary forks from dbt-oss as AI agent skills land

◆ Current state

dbt just shipped its 2.0.0 GA release, formally splitting the codebase into a proprietary 'dbt' binary (the Fusion engine) and 'dbt-oss'. The 2.0 release adds AI agent skill installs from packages, native Databricks metric view materializations, and a new ClickHouse ADBC driver. Post-2.0 dev builds (dev.41) are already extending Lake Compute with Databricks Unity Catalog read access.

◆ Where it's heading

The proprietary/OSS fork is the defining structural move: dbt (proprietary) will accumulate AI-adjacent features — agent skills, Lake Compute, Databricks-specific materializations — while dbt-oss serves the backward-compat install base. The agent skills system (SKILL.md packages) is early but establishes a plugin surface for AI workflow definitions inside dbt runs. Expect the Databricks surface to keep widening as Lake Compute moves toward write support.

◆ Prediction

Next likely move: agent skills expand from installation-only to execution, and Lake Compute adds write paths or more Unity Catalog capabilities. The ClickHouse ADBC driver work may also get a GA tag soon given the volume of RC iterations.

Metabase logo
Metabase
ANALYTICS
2.5

Metabase open-sourced its AI stack and shipped an MCP server — analytics is going agentic.

◆ Current state

Metabase's recent two releases have been the most directionally significant in years. Metabase 60 (March) open-sourced the company's AI tools, shipped an official Metabase MCP server, put Metabot inside Slack, added bring-your-own-model, plus a metrics explorer and split multi-series charts. Metabase 59 (February) introduced Data Studio — an analyst workbench with a semantic layer — and pushed AI SQL generation into the open-source edition. Earlier 55–58 work focused on Documents, embedded analytics, dark mode, and governance.

◆ Where it's heading

The arc through 55→60 traces a clear pivot: Metabase is repositioning the BI tool around an AI-native semantic layer that any agent can call. Open-sourcing AI tooling and shipping an MCP server are sequential bets that the value is moving from 'humans clicking dashboards' to 'agents and LLMs querying business data through a governed semantic layer.' Pairing that with Slack-native Metabot and BYO model targets distribution (chat) and enterprise procurement (your model, your governance) at the same time.

◆ Prediction

Expect rapid third-party MCP integrations to follow the official server release, and AI tooling currently in OSS to become the wedge for self-hosted adoption. The next likely moves are deeper Data Studio integration with the AI generation path, and pricing tiers that bundle agentic-query usage rather than seat counts.

Alternatives to dbt Core and Metabase

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 Metabase.

See all dbt Core alternatives → · See all Metabase alternatives →

Recent activity from dbt Core and Metabase

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 2d agodbt CoreLake Compute gains Databricks Unity Catalog read access
  2. 9d agodbt Coredbt v2.0.0 ⚡
  3. 10d agodbt Coredbt v1.12.5
  4. 10d agodbt CoreInternal test-PyPI build (2.0.2)
  5. 15d agodbt Corev2.0.0-rc.2
  6. 16d agodbt CoreClickHouse ADBC driver dev build (2.0.0-dev.39)
  7. 5mo agoMetabaseScraping artifact: cookie consent page, not a release
  8. 5mo agoMetabaseDuplicate index capture of Metabase 60 changelog page
  9. 5mo agoMetabaseScraping artifact: changelog index page, not a release
  10. 5mo agoMetabaseMetabase 60 ⚡
  11. 5mo agoMetabaseScraping artifact: newsletter signup module, not a release
  12. 6mo agoMetabaseMetabase 59 ⚡

Frequently asked questions

What is the difference between dbt Core and Metabase?

They serve adjacent needs but don't currently overlap on shipped themes. dbt Core is currently shipping more aggressively (velocity 7.5 vs 2.5), with 1 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 Metabase?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. dbt Core is currently shipping more aggressively (velocity 7.5 vs 2.5), with 1 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 Metabase?

Top Metabase alternatives in Analytics are ranked by recent ship velocity. Browse the "Metabase alternatives" section above for the current picks, or visit /alternatives/metabase for the full list with editorial commentary on each.