Semantic Layer for Enterprise AI in 2026: What Production Use Requires
Quick Answer:
Enterprise teams need three things from a semantic layer for AI in 2026: it has to be tool-agnostic, it has to enforce governance automatically across every connected tool and AI agent, and it has to be portable across clouds. Strategy Mosaic, the universal semantic layer, has been running this pattern in Fortune 500 production deployments, including Pfizer, Hilton, and GUESS, for years before agentic AI became its own category.
Strategy Software, an enterprise software company built around a semantic layer that gives AI the business context it needs, has spent 35 years doing exactly this at Fortune 500 scale. The AtScale 2026 Semantic Layer Summit on May 20 shows the growing recognition of the importance of semantics and context as enterprises embrace AI. AtScale Co-Founder and CTO David Mariani recently framed the central question for the event this way: "the biggest hurdle for enterprise AI in 2026 is not the AI, it is the meaning." That diagnosis is correct. The open question this post takes on is what production deployment actually looks like once teams accept the diagnosis. Here are five production checks every enterprise team should run before committing to a semantic layer for AI workloads and why Strategy Mosaic closes the gap.
The Diagnosis Is Right. The Open Question Is Production.
Mariani is right that meaning and definitions are the hurdle. AI engines built directly on raw data sources cannot enforce business definitions consistently, do not understand fiscal calendars or multi-currency rollups, and have no governance model that survives moving between tools. The semantic layer is the right architectural answer to this problem. AtScale has been a real contributor to that case, including participating in the Open Semantic Interchange (OSI) standard, where Strategy is a co-founding member alongside Snowflake.
A production-grade enterprise semantic layer is a governed, tool-agnostic abstraction layer that enforces a single set of business definitions across every BI tool, AI agent, and application, without moving data and without locking into any single cloud or vendor. Mosaic has been operating that pattern in large enterprise production deployments for over a decade, well before the term "agentic semantic layer" entered the category vocabulary.
What separates conference framing from production reality is not the diagnosis. The difference shows up in the depth of the answer.
Five Checks for an Enterprise Semantic Layer in 2026
Use these five checks to evaluate any platform pitched against that framing.
- Multi-cloud portability. Does the semantic layer move with your data, or is it tied to a single cloud's compute layer? If your CFO consolidates spend onto a different cloud next year, does your semantic foundation come with you, or do you rebuild every metric definition? Mosaic runs across AWS, Azure, and GCP for the same enterprise customers, and metric definitions move without rewriting.
- Tool-agnostic governance enforcement. Do governance policies apply automatically across every BI tool, AI agent, and application, or do they need to be configured per tool? The configuration-per-tool pattern is where governance silently breaks row-level security applied in Power BI does not automatically extend to a Tableau dashboard or a Claude agent reading the same data. Mosaic enforces row-level and column-level security at the semantic layer, so one policy set applies automatically across every connected tool.
- Production AI agent depth. Has this been deployed against AI agents in production at enterprise scale, or only in demos? A platform that can answer one question reliably in a controlled walkthrough is not the same as one that has been governing thousands of agent queries per day for two years. Mosaic supports two-plus years of production AI agent deployments at customers including Pfizer, Hilton, and Lotte.
- Governance observability. Can your team see, in real time, who or what queried which metric, and detect PII exposure or anomalies? Mosaic Sentinel adds three real-time governance modules: risk management, audit and compliance, and usage insights, observable across every connected tool without requiring data movement.
- Standards alignment. Is the semantic layer aligned with open standards, or is it a closed format? Mosaic supports the Model Context Protocol (MCP), Agent to Agent (A2A) and has a robust suite of APIs, so AI agents on Claude, Copilot, ChatGPT, Gemini, and AWS query the same governed semantics. Mosaic is part of the Open Semantic Interchange (OSI) co-founding group alongside Snowflake, Salesforce and Databricks.
How Strategy Mosaic Closes the Production Gap
Mosaic was built around the idea that a semantic layer should be the consistent foundation of every analytics and AI experience in the enterprise, not a per-tool feature inside one BI vendor's stack. That positioning has practical consequences worth naming directly.
Mosaic connects to over 200 data sources natively, from ArcGIS through to Power BI DAX, without moving or replicating data. Mosaic Sentinel adds the governance layer on top, with real-time risk alerts, comprehensive audit visibility, and clear usage insights observable across every connected tool. Mosaic Sentinel does this without requiring data movement and without creating vendor lock-in. Mosaic supports MCP, which lets AI agents query the unified semantic layer directly without going through an intermediate agent, and AI Sync for Linked Models, which auto-validates and re-enables AI experiences when underlying semantic models update.
Mosaic does not treat governance as a separate workflow that gets bolted onto AI later. Governance lives in the same layer that defines the metrics, and the same definitions that power dashboards power AI agents through MCP. That is what bridges the gap between pilot and production.
See how Mosaic Sentinel monitors governance across every connected tool in real time. Request a Mosaic walkthrough scoped to your current cloud and BI footprint at strategy.com/software/strategymosaic.
Frequently Asked Questions
Q: What is the difference between a semantic layer for analytics and a semantic layer for AI agents?
A: There is no architectural difference if the semantic layer is built correctly. A production grade enterprise semantic layer enforces the same business definitions and governance rules whether the consumer is a Power BI dashboard, a Tableau sheet, or an AI agent on Claude or Copilot. Mosaic uses one set of definitions and governance policies across every connected tool, including agents accessing it through the Model Context Protocol.
Q: What should enterprise teams look for in a semantic layer for production AI in 2026?
A: Five capabilities matter: multi-cloud portability, tool-agnostic governance enforcement, demonstrated production AI agent deployments, real-time governance observability, and alignment with open standards (OSI, MCP). Strategy Mosaic ships against all five, with two-plus years of production AI agent deployments and native MCP support across Claude, Copilot, ChatGPT, Gemini, and AWS.
Q: How is Strategy Mosaic different from a platform-native semantic layer like Snowflake's or Databricks'?
A: Platform-native semantic layers are tied to one cloud's compute layer. Strategy Mosaic runs across AWS, Azure, and Google Cloud and federates definitions across heterogeneous platforms without moving data. The choice depends on whether the organization plans to standardize on one platform or maintain optionality across multiple clouds and BI tools.








