Semantic layer for defining metrics as code, integrated into dbt. Acquired by dbt Labs and integrated into the dbt Cloud Semantic Layer. License: BSL-1.1 (not OSI-approved). Companion to existing cube and atscale rows.
MetricFlow is the OSS semantic layer for defining metrics as code — BSL-1.1 license. Acquired by dbt Labs and integrated into dbt Cloud Semantic Layer. Pick MetricFlow for dbt-native semantic-layer workloads where metrics-as-code + dbt integration are the value props. License posture (BSL) is the trade-off.
MetricFlow's BSL-1.1 license is the load-bearing trust dimension: not OSI-approved. dbt Cloud Semantic Layer signs BAAs; OSS BSL requires procurement review for SaaS deployments. Technical model (metrics-as-code, semantic graph) is sound; license posture matters more.
Compiled SQL — warehouse-dependent.
Metric query API + dbt SQL.
Warehouse-dependent. Cap rule applied.
Multi-warehouse via dbt connectors.
Semantic graph + dimension consistency + dbt lineage.
Compiled SQL inspection.
Definitions-as-code. 1/6 -> 3.
dbt observability. 1/6 -> 3 lenient.
3/6 -> 3.
Semantic-layer purpose.
5/6 -> 4.
Best suited for
Compliance certifications
BSL not OSI; dbt Cloud signs BAAs.
Use with caution for
Cube for vendor-neutral semantic layer. MetricFlow for dbt-native.
View analysis →AtScale for enterprise semantic layer. MetricFlow for dbt-native.
View analysis →Role: L3 dbt-native semantic layer.
Upstream: dbt model definitions.
Downstream: Metric API + compiled SQL.
Mitigation: Procurement review. Use dbt Cloud for SaaS.
Native dbt integration.
Cube fits better.
This analysis is AI-generated using the INPACT and GOALS frameworks from "Trust Before Intelligence." Scores and assessments are algorithmic and may not reflect the vendor's complete capabilities. Always validate with your own evaluation.