Skip to main content
Context Components · Ontology

The map of
your entire business.

An ontology defines the entity types, relationships, and rules that hold in your business. Atlan mines the first draft from your lineage, SQL, and BI logic instead of starting you at a blank page, then versions and tests it like code.

spinner
Drag any entity. Click one to see what it means.

Interactive diagram of five connected entities: Campaign, Customer, Order, Shipment, and Support Ticket. Use tab to move between entities, enter to read what each one means, and arrow keys or drag to reposition them.

Click or drag any entity to explore the model.

Trusted by AI-forward enterprises

"Atlan captures Workday's shared language to be leveraged by AI via its MCP server. As part of Atlan's AI labs, we're co-building the semantic layer that AI needs."

Joe DosSantos

VP Enterprise Data & Analytics, Workday

"The output shifted from solid generic descriptions to something that felt like it had been written by someone who understands our business. That's the moment I stopped thinking about this as a time-saving tool and started seeing it as a strategic capability."

Sridher Arumugham

Chief Data Analytics Officer, DigiKey

"We were stunned and perplexed by the quality of the content. How could the agents create such high-quality context from lineage, SQL, and dbt logic? It shows how much business information is hidden in metadata that we can't see with human eyes. But agents consume it all and organize it."

Andrew Reiskind

Chief Data Officer, Mastercard

"We're focused on how we can scale context development as much as possible, and where can we leverage Atlan AI to build the most robust definitions across our data estate and make sure we're propagating it upstream and downstream."

Takashi Ueki

Head of Enterprise Data & Analytics, Elastic

WTF IS THE CONTEXT LAYER

A bi-weekly live series for AI leaders and builders. One burning question per episode, an open AMA floor, and guests who've actually built context infrastructure.

EP 04From Ontology to Context Layer: What Actually Changed With AI?
Join Jessica Talisman, Ontology Pipeline and Austin Kronz, Atlan, as they debate:
  • Ontologies have existed for decades. Why are enterprises funding them now?
  • What has to exist before you build an ontology?
  • Can an LLM build the ontology for you?
  • Is the context layer just a new name for the ontology?
spinner
From Ontology to Context Layer: What Actually Changed With AI?
THE AI CONTEXT GAP

One question.
Three kinds of context.

Knowledge is what a thing is and how it connects. Expertise is what follows from that. Norms are which rules apply. An ontology is where all three get declared.

Knowledge

What kind of thing is this?

A ServiceMetric, recorded by a Store, which belongs to a Region — not a raw machine reading

Expertise

What follows from that?

A Region rolls up its Stores, so a chain-level spike traces down to the stores under it

Norms

Which rule decides?

A Store closed for refurbishment is excluded from chain averages

CONTEXT COMPONENTS

No agent runs on
an ontology alone.

It says what can be true. Which data to trust, how to compute a number, and what the team decided last time all live in other structures.

What are the business’s entities, relationships, and rules?

Entity types, named relationships, and the logic that has to hold. It carries no data of its own, which is the point: it is the blueprint a knowledge graph gets filled in against.

Explore Ontology
ONTOLOGYENTITIES + RELATIONSHIPSholdsreceivescontainsCustomerAccountInvoiceChargeCLASS HIERARCHYis-aRoamingChargeRULES — ALSO PART OF THE ONTOLOGYRULE · a Charge that occurredDuring aNetworkEvent status = outage ⇒ refundEligible

ONTOLOGY

ENTITIES + RELATIONSHIPS

Customer
holds
Account
receives
Invoice
contains
Charge

CLASS HIERARCHY

Charge
is-a
RoamingCharge

RULES — ALSO PART OF THE ONTOLOGY

RULE · a Charge that occurredDuring a NetworkEvent status = outage ⇒ refundEligible
HOW IT WORKS

Don’t start from a blank page.
Atlan mines the first draft from your lineage and SQL.

The entities and relationships are already in your systems. They are just not written down.

Your business already encodes its own ontology, badly and in a dozen places: in join paths analysts repeat, in the filters every production query applies, in BI semantic logic, and in glossary entries somebody started three years ago. Atlan reads those signals and proposes the entities, relationships, and definitions they imply.

Lineage/SQL Parsing
SQL Query Parsed
CREATE TABLErevenue_aggASSELECT o.amountASnet_revenue, o.customer_id, d.regionFROMorders_raw oJOINdim_customers d ON o.customer_id= d.id
TABLE
✓
ORDERS_RAW
ANALYTICS / PROD
#amount
Acustomer_id
TABLE
✓
DIM_CUSTOMERS
ANALYTICS / PROD
Aregion
TABLE
✓
REVENUE_AGG
ANALYTICS / PROD
#net_revenue
Acustomer_id
Aregion

Treated like code, because a wrong rule is a wrong answer at scale.

A draft ontology is a starting point. The rules that matter most are usually the ones no system recorded, which is why a human owner decides what becomes canonical, what it replaces, and where it propagates.

Context Studio/Repositories/finance-revenue
revenue.yml
synced to 4 agents
Last updated 2h ago · v3.1.2
name: "revenue"
domain: finance
version: 3.1.2
definition: "Net sales after returns, post-tax"
window: "Q4 — fiscal year close"  # updated by AI · approved by @jsmith
consumers:  # Cortex · LangGraph · Genie · Claude
framework: any # LangGraph, Cortex, Genie, or your own
Recent activity
✦
AI drafted revenue.yml v3.1.2 — updated fiscal window definition
2h ago
⊘
@jsmith approved — no changes needed
2h ago
⚙
Pushed to 4 agents — all consuming v3.1.2 automatically
2h ago
Consuming this repo
Snowflake Cortex
LangGraph
Databricks Genie
Claude (MCP)
All on v3.1.2

One ontology, readable by every agent you run and every agent you have not built yet.

An ontology that only one agent framework can read is a private ontology. Atlan stores context in Apache Iceberg and serves it through whichever interface a consumer speaks, so the meaning outlives the tool that happened to need it first.

Cortex Analyst
Natural Language Query
Run
Powered by Snowflake Cortex
via Atlan MCP
Fetching context from Atlan MCP...
→ resolve_metadata · search_assets
MMetricCertified
revenue
Net sales after returns, post-tax
@jsmith
TTable
98/100
orders_fact
owner: Data Engineering
Primary transaction table
Generated SQLQuery ready
1SELECT
2 product_line,
3 SUM(net_sales) AS revenue -- metric defined by Atlan
4FROM orders_fact
5WHERE fiscal_quarter = 'Q4'
6GROUP BY product_line;

See the context layer, built live.

The Enterprise Context Layer Architecture in ActionWed, Aug 26 · 11 AM ET
The teams winning with AI are not the ones with the best models. They are the ones building context that compounds. Watch Atlan mine knowledge from your existing stack, build and certify a context layer through a development lifecycle, and deploy it to any agent platform.
spinner
Isabella Steains
Isabella SteainsStrategic Solutions Engineer

Give your agents the map
your business runs on.