The Libraries

Data & Data Infrastructure

Layer 05 of seven · Data & Data Infrastructure

Why it matters
Most enterprise AI projects stall on data rather than on models. Retrieval quality, permissions and freshness decide whether an assistant is useful or quietly wrong, and those are properties of this layer.
The bottleneck
Governance and context. Storing data is cheap and largely solved. Knowing what it means, who may see it and whether it is current is neither.
Who captures value?
Platforms that become the governed system of record, because migration is painful and permissions models are sticky. Pure storage captures much less than the layer that arbitrates access.
What could change?
Open table formats make data easier to move between engines, which weakens lock-in. Longer model context windows also change, though do not remove, how much retrieval infrastructure is required.

The city's libraries, records and archives. Models are only one part of the system: enterprises also need data that is accessible, trusted, governed, structured, searchable, permissioned and connected to business context.

A model that cannot see your data will give you a confident answer about someone else's business. This is the least glamorous layer and one of the most decisive, because the gap between a demo and a deployment is usually not model quality. It is whether the right records can be found, whether the person asking is allowed to see them, and whether anyone can explain afterwards where the answer came from.

Operational databasesRUNS THE BUSINESSThe systems of record: transactions, customers, inventory. AI that acts on stale data makes expensive mistakes, so freshness is a requirement.Warehouse / lakehouseSNOWFLAKE, DATABRICKSWhere analytical data is consolidated, modelled and governed. The permissions model here decides what an AI system is allowed to see.Vector searchFINDS BY MEANINGEmbeddings let you search by meaning rather than exact wording. This is the piece that lets a model retrieve the right document instead of guessing.Retrieval and contextGROUNDED ANSWERSRetrieval augmented generation: the model is handed the relevant records, with permissions applied, so its answer reflects your business rather than the open internet.The modelANSWERS WITH EVIDENCESame model, better answers, because the context came from governed data instead of a guess.The demo works without this. The deployment does not.

Tap or hover a box to see what it does

Models are only half the system. Warehouses, operational databases and vector search decide whether an answer is grounded in your business or in someone else's.

Warehouses and lakehouses

Where analytical data is consolidated, modelled and governed. The lakehouse pattern merged the cheap storage of a data lake with the governance and query behaviour of a warehouse, mostly on open table formats.

publicSNOW

Snowflake

What it does

Runs a cloud data platform for storing, governing and querying enterprise data, with AI features layered on top.

Why it matters

Models are only as useful as the data they can reach. Whoever holds the governed copy of enterprise data is well placed to sit between it and any model.

What could go wrong

Consumption pricing means efficiency gains can reduce revenue, and open table formats make it easier for customers to move.

Position in the ecosystem
private

Databricks

What it does

Provides a lakehouse platform combining data engineering, analytics and machine learning on open table formats.

Why it matters

It made the argument that you should not have to choose between a warehouse and a data lake, and a lot of enterprise AI work now happens where the data already sits.

What could go wrong

Competing directly with both cloud providers and warehouse vendors, and private valuations set expectations that public markets may not repeat.

Public market exposure

Privately held. Investors include Microsoft and several large asset managers, so exposure is indirect and partial.

Position in the ecosystem

Operational databases and streaming

The systems that run the business in real time, plus the pipelines that move events between them. Agents acting on yesterday's data cause expensive mistakes, so freshness is an architectural requirement rather than a nicety.

publicMDB

MongoDB

What it does

Provides a document database, delivered mainly as the Atlas managed service, with integrated vector search.

Why it matters

Retrieval matters more than most people expect. Putting vector search next to operational data removes a moving part from AI application architectures.

What could go wrong

Cloud providers bundle similar capability, and vector search is being added to nearly every database.

Position in the ecosystem
publicORCL

Oracle

What it does

Runs Oracle Cloud Infrastructure with a strong GPU cluster business, and sells the databases and applications that hold a great deal of enterprise data.

Why it matters

It sits in two layers at once. The database estate gives it a claim on enterprise data, and OCI has become a meaningful venue for large scale AI training capacity.

What could go wrong

Building GPU capacity is capital hungry and the customer list is concentrated. Committed backlog is a promise, not yet revenue.

Position in the ecosystem
publicCFLT

Confluent

What it does

Commercialises Apache Kafka as a managed platform for streaming data between systems.

Why it matters

Agents that act on stale data cause expensive mistakes. Streaming is how enterprise context stays current rather than nightly.

What could go wrong

Kafka is open source and self hosting is a permanent competitive alternative.

Position in the ecosystem

Search, vectors and knowledge

Retrieval turns a general model into one that knows about your business. Vector search finds records by meaning rather than exact wording, and metadata, lineage and permissions decide what may be returned to whom.

publicESTC

Elastic

What it does

Provides search, observability and security analytics built on Elasticsearch, including vector search.

Why it matters

Search is the retrieval step in most practical enterprise AI systems, and Elastic already sits on a lot of the relevant text.

What could go wrong

Crowded search market, licence history that pushed some users to forks, and competition from cloud native services.

Position in the ecosystem
publicPLTR

Palantir

What it does

Sells data integration and decision platforms to governments and large enterprises, increasingly packaged around AI driven workflows.

Why it matters

It solved the boring problem first. Getting messy institutional data into one usable model is most of the work, and it is very hard for a customer to unpick later.

What could go wrong

Lumpy government contracting, delivery that depends on skilled people, and a valuation that leaves little room for disappointment.

Position in the ecosystem
publicSAP

SAP

What it does

Provides enterprise resource planning software that runs core finance, supply chain and HR processes for many large firms.

Why it matters

The transactional record of how a business actually operates lives here. That context is hard to reproduce and expensive to move.

What could go wrong

Long migration cycles, and customers who resist paying more for AI features on top of existing licences.

Position in the ecosystem

How to think about the economics

  • GrowthHigh

    How quickly demand in this part of the ecosystem is expanding.

  • Capital intensityLow

    How much money has to be spent up front before revenue arrives.

  • Competitive moatHigh

    How difficult it is for a credible new entrant to take the business.

  • Customer concentrationLow

    How much revenue depends on a small number of buyers.

  • Disruption riskModerate

    How exposed the layer is to a technical or commercial shift.

This is a framework for thinking about the economics of a layer, not a recommendation. An important AI company, a strategically advantaged company, an investable security and an attractively valued security are four different things.

Where value may accrue

Switching costs, governance position and gravity. Data has a habit of staying where it lands, and the vendor holding the permissions model is very hard to displace incrementally.

Key terms in this layer

Vector search
Searching by meaning rather than exact wording. Records are converted into numerical embeddings, and the system finds the closest matches, which is how an AI assistant retrieves the right document instead of guessing.
ExampleMongoDB Atlas Vector Search and Elastic both offer it.
Related termsRetrieval augmented generation (RAG)Foundation model
Retrieval augmented generation (RAG)
Handing the model the relevant records, with permissions applied, before it answers. This is what turns a general model into one that knows about your business.
ExampleA support assistant that reads your policy documents at answer time rather than relying on memory.
Related termsVector searchInference

Related questions

What is agentic AI?

Most AI use is still reactive: you ask, it answers. An agent is given a goal instead, and works out the intermediate steps, calling tools, reading data and looping until it decides the task is finished. That shift is why permissions, audit trails and identity suddenly matter so much. A chatbot that is wrong wastes your time. An agent that is wrong can take an action on your behalf, which is a different category of problem.

Sources and further reading (3)+
  1. 1Investor relations and product documentation · Snowflake
  2. 2Lakehouse architecture documentation · Databricks
  3. 3Atlas Vector Search documentation · MongoDB
Last fact-checked: 29 August 2026

The AI ecosystem changes rapidly. Company positions, technologies and market data reflect information available at the date above.