Fulcrum
Fulcrum ships MCP server and AI Toolkit to let AI assistants build and query field data forms
A side-by-side editorial comparison of Metabase and dbt Core — release velocity, themes, recent moves, and the top alternatives to consider.
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.
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.
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.
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.
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.
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.
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.
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.
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 Metabase or dbt Core.
Fulcrum ships MCP server and AI Toolkit to let AI assistants build and query field data forms
Holistics builds AI governance and docs-as-analytics in parallel, shipping both weekly
OpenHouse breaks ground on Iceberg views while tightening storage lifecycle and authorization
Lightdash is cutting its dbt dependency and building AI-powered authoring into every layer of its BI stack.
Keboola's Kai AI assistant hits GA, completing the pivot from data platform to AI-native pipeline orchestration layer.
Omni's Apps reach general availability, completing its embedded analytics platform pitch.
See all Metabase alternatives → · See all dbt Core alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. dbt Core is currently shipping more aggressively (velocity 6.3 vs 2.5), 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. dbt Core is currently shipping more aggressively (velocity 6.3 vs 2.5), 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.
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.
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.