The Data Brief · Issue #5 · Semantic Layer Series

The honest tool guide

dbt, Cube, AtScale, Looker, and the platform-native options — assessed without vendor influence

Shrikant·April 22, 2026·Updated after fact-check·9 min read
No sponsored content. No affiliate links. No vendor relationships. All tool capabilities verified against official documentation as of April 2026.

Every vendor says they are the semantic layer. That sentence has never been more true — or more confusing — than it is in 2026. The market has fragmented into standalone platforms, warehouse-native solutions, BI-embedded layers, and emerging AI-first tools.

84% of data teams still encounter conflicting versions of the same metric, with more than a third experiencing this regularly. This issue cuts through the noise. Five tools, assessed honestly. What each one does well, where it falls short, and the watch-out each vendor is unlikely to put in their own marketing materials.

The wrong question is "which tool is best?" The right question is: which tool fits my architecture, team skills, and use case today?


dbt Semantic Layer (MetricFlow)Analytics engineering–first

Ideal for: Teams with mature dbt practices who want metrics version-controlled alongside transformation code

dbt Labs acquired Transform — the company behind MetricFlow — and integrated it into dbt Cloud. Metrics are defined in YAML in the same Git repo as transformation models. BI integrations include Tableau, Google Sheets, Excel, Hex, Mode, Klipfolio, Omni, and Power BI (Preview — available via Power BI Desktop; Power BI Service requires IT-configured On-premises Data Gateway).

▲ October 2025 — dbt Labs and Fivetran announced a definitive merger agreement. The combined company approaches $600M ARR. dbt Core remains open-source. For teams evaluating long-term platform commitment, this is material context worth monitoring.
Strengths
Metrics as code — full Git history, PRs, CI/CD
Natural fit for dbt-native teams
MetricFlow is open-source (Apache 2.0)
dbt MCP Server enables AI agent access
Best-in-class metric type system
Limitations
Requires dbt Cloud Starter minimum
Caching on Enterprise and Enterprise+ only
Power BI Service requires On-premises Gateway
Not suited for embedded analytics
Fivetran merger introduces strategic uncertainty
Watch out for: The dbt Cloud dependency is real and recurring. The API that lets BI tools query metrics is paywalled. Teams on dbt Core will not get the semantic layer's most useful capability without moving to dbt Cloud. Evaluate total cost of ownership carefully.
CubeAPI-first

Ideal for: Teams building embedded analytics, custom data products, or multi-tool architectures

Cube is the most developer-friendly semantic layer — built open-source with nearly 20,000 GitHub stars. The 2025 release added roll-up anytime materializations and a WASM-powered query engine achieving sub-second P95 latency on Snowflake. Cube exposes metrics through REST, GraphQL, SQL, MDX, and DAX APIs — the broadest API surface of any standalone tool.

Strengths
Fully open-source core — no vendor lock-in
Broadest API surface (REST, GraphQL, SQL, MDX, DAX)
Best-in-class pre-aggregation and caching
Best embedded analytics support
Self-hostable for cost and data residency control
Limitations
Schema authoring requires JS or TypeScript
More engineering overhead than platform-native
Less mature governance tooling than AtScale
dbt integration via adapter, not native
Watch out for: Total cost of ownership for self-hosted Cube tends to exceed Cube Cloud once you factor in engineering time. The open-source path is real, but it is not free.
AtScaleEnterprise-scale

Ideal for: Large enterprises with complex governance requirements and Excel-heavy user bases

AtScale sits across Snowflake, Databricks, BigQuery, and on-premise systems simultaneously, exposes metrics through XMLA/MDX interfaces that Excel understands natively, and provides the deepest governance capabilities. In January 2026, AtScale joined the Open Semantic Interchange initiative and introduced an open-source Semantic Modeling Language.

Strengths
Deepest governance — RLS, audit trails, certification
Native Excel and MDX support
Works across multiple data platforms simultaneously
MCP integration for AI agent access
GigaOm 2025 Leader and Fast Mover
Limitations
Enterprise pricing — not suited for smaller teams
Additional infrastructure to deploy and manage
Heavier implementation overhead
Proprietary SaaS — smaller community
Watch out for: AtScale earns its cost at genuine scale — hundreds of users, multiple data platforms, rigorous governance requirements. If your data estate is primarily one warehouse, you are paying for capabilities you will not use.
Looker (LookML)BI-native

Ideal for: Google-first organisations and shops where analytics flows through a single BI tool

LookML is the original code-based semantic layer and remains one of the most mature modeling languages available. The 2025–2026 updates integrated Gemini NLQ, with meaningful AI accuracy improvements when grounded in LookML's governed model. Google has been developing decoupled semantic capabilities — though these are still maturing.

Strengths
Most mature modeling language — 10+ years
Deep governance within Looker ecosystem
Gemini NLQ integration improving rapidly
Large practitioner community
Limitations
Definitions locked inside Looker — do not travel
Second BI tool means replicating all metric logic
Google Cloud pricing adds up at scale
Decoupled semantic capabilities still maturing
Watch out for: LookML lock-in is the defining risk. If you leave Looker or add a second BI tool, you leave your entire metric layer behind.
Platform-native (Snowflake / Databricks)Zero-infrastructure

Ideal for: Teams fully committed to a single data platform who want the lowest-overhead path

Snowflake Semantic Views reached full GA with standard SQL querying in March 2026 and introduced automated metric discovery capabilities. Databricks Metric Views extend Unity Catalog with metric governance that inherits existing access controls.

Strengths
Zero additional infrastructure or vendor relationship
Governance inherits from existing platform controls
Standard SQL access — no new query language
Automated metric discovery reduces setup time
Native AI: Cortex Analyst, LakehouseIQ
Limitations
Definitions do not span multiple data platforms
Multi-BI environments require additional tooling
Not suited for embedded or custom analytics
Feature parity with standalone tools catching up
Watch out for: Platform-native is the right call today — until you add a second data platform or BI tool. Plan your exit ramp early. The dbt_semantic_view package is worth evaluating as a middle path for Snowflake teams.

The comparison at a glance

Criteriondbt SLCubeAtScaleLookerNative
Multi-BI portability●●●●●●●●●●○○●●○
Setup speed●●○●●○●○○●●○●●●
Governance depth●●○●●○●●●●●●●●○
AI / LLM readiness●●●●●●●●●●●○●●●
Embedded analytics●○○●●●●●○●●○●○○
Cost at small scale●●○●●●●○○●●○●●●
dbt-native teams●●●●●○●●○●○○●●○
Vendor stability●●○●●●●●●●●●●●●

● limited  ●● solid  ●●● best-in-class for this criterion · Ratings reflect architectural fit, not overall product quality.


"35% of teams still define metrics ad-hoc in BI tools or custom code — not because they don't know better, but because they haven't found a tool that fits their workflow without adding friction."

Corrections applied after fact-check — April 22, 2026
dbt Power BI — Updated from "private beta" to Preview; added On-premises Gateway caveat for Service
dbt caching — Clarified as Enterprise and Enterprise+ plans specifically
dbt Fivetran merger — Added material strategic context
Matrix AI score — dbt SL upgraded to ●●● following MCP Server launch; Vendor stability row added
Looker Modeler — Reframed to "decoupled semantic capabilities"

Next in the series

Build it: step-by-step implementation walkthrough with dbt and Cube
#TheDataBrief#SemanticLayer#dbt#DataEngineering#DataTools#DataStrategy