AIToday
Top Companies' AI MovesLarge Language ModelsAI Business & IndustryTop Companies AIPublished: Aug 20, 2026, 06:30 JST3 min read

Salesforce charts layered data architecture for enterprise AI

Salesforce charts layered data architecture for enterprise AI

Key takeaway

  • Salesforce's head of data architecture says knowledge graphs are becoming critical infrastructure for enterprise AI systems.

  • As organizations move toward AI-native IT stacks, they are building layered data architectures that sit above fragmented data sources—lakehouses, operational databases, and customer profile stores—to give AI models the context needed to reason reliably.

  • The core challenge is not technology but governance: semantic descriptions of data and access policies must move up the stack so that AI can return trustworthy, explainable answers at conversational speed.

3 Key Points

  1. What happened

    Salesforce's head of data architecture, Tristan Baker, outlined how knowledge graphs are becoming a foundational layer for enterprise AI systems. He described a layered stack where lakehouses and operational databases sit below a metadata layer, with graph technology managing relationships and context across them—enabling AI agents to reason from trusted data rather than simply retrieve it.

  2. Why it matters

    Enterprise leaders are seeking conversational interfaces that return trustworthy answers in seconds, but that requires far more than a single database. Baker emphasized that the hard problem is accurately describing enterprise information so AI can make sense of it across fragmented data landscapes. Governance and semantic access policies are emerging as critical challenges; legal teams need to define data protection at the semantic level, not just within individual databases.

  3. What to watch

    Baker noted that most organizations have not yet fully solved this architecture problem. He cautioned that even the best technology yields "garbage in, garbage out" if the content exposed to it is not carefully curated—a challenge many enterprises are still grappling with.

Ask the AI about this article →

Context & Analysis

Enterprise organizations are shifting from cloud-native IT stacks to AI-native ones, and that transition is reshaping how they think about data architecture. The move reflects a fundamental change in what enterprises expect from data systems: no longer just speed and scale, but the ability to deliver trustworthy, explainable answers in a conversational interface. Knowledge graphs have emerged as the connective tissue binding fragmented data sources together—lakehouses, operational databases, customer profile stores—into a coherent system of intelligence.

Baker's framing reveals why this shift is non-trivial. The problem is not that enterprises lack data; it is that their data lives scattered across dozens of copies in incompatible systems, with no shared semantic understanding of what it means. A metadata layer can bridge that gap by translating business language into database columns, and graph technology can track relationships and context across those translations. But without careful governance—semantic policies that legal and security teams can understand and enforce—even the best AI reasoning engine will produce unreliable answers. Most organizations, Baker suggests, are still struggling to design these governance layers at the semantic level rather than hiding them inside individual databases.

FAQ

What is the layered data architecture Salesforce is describing?
It is a stack with lakehouses, operational, and time-series databases at the bottom—each optimized for different kinds of queries—followed by a metadata layer that tracks where truth about a customer lives across multiple copies and maps business terminology to underlying columns. Above that sits a graph layer that manages relationships and context connecting those pieces together.
What is the main challenge Baker identified with this approach?
Baker stated that governance is the most under-discussed challenge. As metadata moves to a higher semantic layer, access control can no longer live only inside individual databases; organizations need semantic descriptions of both their data and their access policies so that legal teams can define who should or should not access which kinds of data.
Has anyone fully solved this architecture yet?
No. Baker said, "Unless somebody's withholding information from me, I don't know anybody that's actually totally solved this one yet," noting that most systems risk becoming "garbage in, garbage out" if content is not carefully curated.
Top Companies AIRead Original Article

Also reported by SiliconANGLE AI

Get the latest Top Companies' AI Moves news every morning

For example, today's edition would include:

  • GE Vernova's New MV-UPS Could Triple Revenue Per GigawattTop Companies AI · 18h ago
  • Lam breaks ground on Oregon lab for AI chip R&DTop Companies AI · 18h ago
  • Ole Miss Study: AI Ads Fail When Consumers Feel TrickedTop Companies AI · 18h ago

AI-summarized, only the topics you pick — one digest a day via Email, Slack, or Discord.

Free · takes 30 seconds · unsubscribe anytimeWhat is AIToday? →

Ask AI

Ask AI anything about this article. Q&As are published on this page for other readers too.

Related Articles

Next articleNTT releases tsuzumi 2, compact Japanese LLM