<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/most-semantic-layers-were-built-for-bi-what-a-semantic-layer-for-ai-requires-bpd6ufoso" -->

---
title: Most Semantic Layers Were Built for BI: What a Semantic...
description: Traditional semantic layers were designed for human analysts and BI tools, not AI agents. They lack the business context, relationship mappings, and governed...
canonical: https://daily.dev/posts/most-semantic-layers-were-built-for-bi-what-a-semantic-layer-for-ai-requires-bpd6ufoso
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Most Semantic Layers Were Built for BI: What a Semantic Layer for AI Requires | daily.dev
og:description: Traditional semantic layers were designed for human analysts and BI tools, not AI agents. They lack the business context, relationship mappings, and governed...
og:url: https://daily.dev/posts/most-semantic-layers-were-built-for-bi-what-a-semantic-layer-for-ai-requires-bpd6ufoso
og:image: https://api.daily.dev/og/posts/bPD6UFOSo.png
og:image:alt: Most Semantic Layers Were Built for BI: What a Semantic Layer for AI Requires
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Most Semantic Layers Were Built for BI: What a Semantic Layer for AI Requires

**[SD Times](https://daily.dev/sources/sdtimes)** · 6 min read · 1 upvotes · 0 comments

## Summary

Traditional semantic layers were designed for human analysts and BI tools, not AI agents. They lack the business context, relationship mappings, and governed ontologies that LLMs and autonomous agents need to reason accurately over enterprise data. An AI-ready semantic layer must provide high-fidelity business context beyond simple metric definitions, built-in governance with audit trails, token efficiency to avoid rebuilding context per query, enterprise-scale performance under concurrent AI workloads, and a single interoperable foundation for all consumers. Vendors like AtScale, Cube, and dbt Labs each address parts of the problem but fall short of full enterprise AI requirements.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://sdtimes.com/data/most-semantic-layers-were-built-for-bi-what-a-semantic-layer-for-ai-requires>

## Questions this post answers

### Why can't AI agents just use a traditional semantic layer built for BI tools?

Traditional semantic layers were designed for human analysts who could manually reconcile inconsistent metric definitions across tools. AI agents don't question conflicting definitions the way a human would; they simply pick one and act on it, so relying on a BI-era semantic layer risks agents inferring meaning, joining data at the wrong level, or double-counting figures, producing convincing but incorrect answers.

_daily.dev surfaces this kind of context as teams weigh semantic layer choices for their AI stack._

### What does an AI-ready semantic layer need to provide that a BI semantic layer doesn't?

It needs business context beyond single metric definitions (relationships, ontologies, fiscal rules), governance consistently enforced across every AI interaction, token-efficient context delivery so agents don't rebuild logic from scratch each query, and enterprise-scale performance under high-concurrency AI workloads, all on one interoperable foundation shared across agents, LLMs, BI tools, and applications.

_anyone architecting AI data infrastructure can track these requirements through daily.dev._

### How do AtScale, Cube, and dbt Labs differ in the semantic layer space?

AtScale is noted for strength in federated queries, Cube provides a developer-friendly API layer, and dbt Labs is known for strong metric consistency across data pipelines. Each was purpose-built for a specific problem rather than for enterprise AI, so AI systems using them still must rebuild business understanding from metadata and raw schemas, increasing token usage and lowering efficiency.

_developers comparing semantic layer vendors can follow this landscape on daily.dev._

## Similar posts on daily.dev

- [What is a semantic layer? A definition for the AI analytics era](https://daily.dev/posts/what-is-a-semantic-layer-a-definition-for-the-ai-analytics-era-o9fctrzko) · Metabase · 3 upvotes · 0 comments
- [Context Layer vs. Semantic Layer: Key Differences & Which One You Need](https://daily.dev/posts/context-layer-vs-semantic-layer-key-differences-which-one-you-need-b5xjqzouh) · Decube · 0 upvotes · 0 comments
- [What If We Don't Need the Semantic Layer?](https://daily.dev/posts/what-if-we-don-t-need-the-semantic-layer--oc091fmdh) · MotherDuck · 5 upvotes · 0 comments
- [Semantic Layer vs Context Layer: Key Differences](https://daily.dev/posts/semantic-layer-vs-context-layer-key-differences-m0qql7s2t) · Redis · 1 upvotes · 0 comments
- [The dream of enterprise semantics: Why this time is different](https://daily.dev/posts/the-dream-of-enterprise-semantics-why-this-time-is-different-0ivzgptcp) · InfoWorld · 0 upvotes · 0 comments

---

Tags: [#llm](https://daily.dev/tags/llm), [#ai-agents](https://daily.dev/tags/ai-agents), [#big-data](https://daily.dev/tags/big-data), [#data-engineering](https://daily.dev/tags/data-engineering), [#bi](https://daily.dev/tags/bi)

[View this post on daily.dev](https://daily.dev/posts/most-semantic-layers-were-built-for-bi-what-a-semantic-layer-for-ai-requires-bpd6ufoso)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"Most Semantic Layers Were Built for BI: What a Semantic Layer for AI Requires","url":"https://daily.dev/posts/most-semantic-layers-were-built-for-bi-what-a-semantic-layer-for-ai-requires-bpd6ufoso","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/most-semantic-layers-were-built-for-bi-what-a-semantic-layer-for-ai-requires-bpd6ufoso"},"datePublished":"2026-07-22T16:26:12.967Z","dateModified":"2026-09-13T18:52:34.255Z","description":"Traditional semantic layers were designed for human analysts and BI tools, not AI agents. They lack the business context, relationship mappings, and governed...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/6d6325b3e0e77e3841b3ba14cce7b670?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/6d6325b3e0e77e3841b3ba14cce7b670?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"SD Times","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"SD Times","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/d803c981e67b4edf928840534e1e1382","url":"https://daily.dev/sources/sdtimes"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/most-semantic-layers-were-built-for-bi-what-a-semantic-layer-for-ai-requires-bpd6ufoso","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"llm,ai-agents,big-data,data-engineering,bi","timeRequired":"PT6M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"SD Times","item":"https://daily.dev/sources/sdtimes"},{"@type":"ListItem","position":3,"name":"Most Semantic Layers Were Built for BI: What a Semantic Layer for AI Requires"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/most-semantic-layers-were-built-for-bi-what-a-semantic-layer-for-ai-requires-bpd6ufoso#faq","mainEntity":[{"@type":"Question","name":"Why can't AI agents just use a traditional semantic layer built for BI tools?","acceptedAnswer":{"@type":"Answer","text":"Traditional semantic layers were designed for human analysts who could manually reconcile inconsistent metric definitions across tools. AI agents don't question conflicting definitions the way a human would; they simply pick one and act on it, so relying on a BI-era semantic layer risks agents inferring meaning, joining data at the wrong level, or double-counting figures, producing convincing but incorrect answers. daily.dev surfaces this kind of context as teams weigh semantic layer choices for their AI stack."}},{"@type":"Question","name":"What does an AI-ready semantic layer need to provide that a BI semantic layer doesn't?","acceptedAnswer":{"@type":"Answer","text":"It needs business context beyond single metric definitions (relationships, ontologies, fiscal rules), governance consistently enforced across every AI interaction, token-efficient context delivery so agents don't rebuild logic from scratch each query, and enterprise-scale performance under high-concurrency AI workloads, all on one interoperable foundation shared across agents, LLMs, BI tools, and applications. anyone architecting AI data infrastructure can track these requirements through daily.dev."}},{"@type":"Question","name":"How do AtScale, Cube, and dbt Labs differ in the semantic layer space?","acceptedAnswer":{"@type":"Answer","text":"AtScale is noted for strength in federated queries, Cube provides a developer-friendly API layer, and dbt Labs is known for strong metric consistency across data pipelines. Each was purpose-built for a specific problem rather than for enterprise AI, so AI systems using them still must rebuild business understanding from metadata and raw schemas, increasing token usage and lowering efficiency. developers comparing semantic layer vendors can follow this landscape on daily.dev."}}]}
```

