Data governance
8 min

Atlan vs TopQuadrant: Where the Definition Lives and What Its History Holds

Key takeaways

  • In Atlan the definition is a glossary term with a certificate and an owner, linked to a semantic model that holds the calculation. In TQ Data Foundation the definition and the calculation are one governed asset, with the owner, the SHACL rule, and the version history on it.
  • Atlan is a capable, well-documented catalog: Draft, Verified and Deprecated certificates, admin-built approval workflows, an activity log kept for the life of the instance, a hosted MCP server marked GA, and rendering to MetricFlow and Apache Ossie.
  • Atlan's own page says a semantic layer cannot answer what a customer is and that a business glossary is a lightweight ontology. What its docs ship for concepts is terms, term relationships, and ER models; the model an agent queries is tables, joins, and metrics.
  • On versioning, Atlan's marketing page says branching, A/B testing, staged rollouts, and rollbacks. Its docs describe Draft, Active, Regenerate, redeploy in place, and an Activity tab. Both sentences are quoted with dates.
  • Atlan's tools guide credits TopQuadrant with SHACL validation and SKOS/OWL support and marks MCP support as No; our live agent-ready page serves governed context over API, SPARQL, and MCP.
In this article
Share

An analytics platform lead has Atlan running well. The Business Graph (its glossary) is populated, the owners are named, and the Finance terms carry a Verified certificate. A Context Engineering Studio repository is live, and an agent answers revenue questions from it. Then the AI platform team asks for something the catalog was never asked for. They want the definition of a customer, who approved it, the rule that tests it, and what it meant last quarter, in one record an agent can validate. That request is where the Atlan vs TopQuadrant comparison starts.

Atlan's answer is a glossary term, linked to a semantic model that holds the calculation, with a certificate and an activity log around both. TopQuadrant's answer is one governed asset on open W3C standards, holding the concept, the calculation, the owner, the validation rule, and every past version. This piece quotes each vendor's own pages, with dates.

Atlan is a well-documented catalog with named owners, certificates, approval workflows, a hosted MCP server, and a studio that renders context into the engines you already run. Its concept layer is glossary terms and table joins, its definition and its calculation are two objects, and its documented versioning is Draft to Active with a drift log. TQ Data Foundation holds all five things on one asset, on standards TopQuadrant helped write.

What is Atlan genuinely good at?

From Atlan's product documentation, because a comparison that skips its strengths helps nobody. Atlan's docs pages print no date; every one cited here was read on 2026-11-22.

CapabilityWhat Atlan's documentation saysSource
Owners and certificates on a term"Click + under Owners to assign owners for a term." / "Choose from four certificate options - Draft, Verified, Deprecated, and No certificate."Set up glossaries
Approval workflows"Change management workflows override any permissions assigned through user roles or access policies."Automate data governance
Change log"Activity logs for metadata changes are persisted throughout the lifecycle of the Atlan instance for your organization."Discovery FAQ
Hosted MCP server"Atlan MCP is hosted by Atlan and available to all tenants, with nothing to install or run." The feature maturity matrix marks it "GA", as-of 2026-11-05.Remote MCP overview; Feature maturity matrix
Renders to the engines you run"Renders the repository as dbt semantic models in MetricFlow format" and "Exports the repository as an Apache Ossie semantic model"Portability targets

The three questions below are where the documentation answers differently from ours.

What does Atlan mean by a definition?

Atlan draws the line between a concept and a metric itself, and draws it where we do. Its "Ontology vs. Semantic Layer" page (published 2026-01-30, updated 2026-10-09) says: "A semantic layer can tell you what 'revenue' means and how to calculate it. Ask it what a customer is ... those questions fall outside what a semantic layer can answer. That's ontology territory." (source). An ontology is the formal model of what a business's concepts are and how they relate. The same page says "A business glossary is a lightweight ontology." What does Atlan ship for the concept side?

Concept-side featureWhat Atlan's documentation saysSource
Glossary terms"A glossary term is the lowest unit that can exist independently inside a glossary. These terms can then be grouped into categories and linked together as related terms."What is a glossary
Data models"Atlan enables you to ingest your entity–relationship (ER) models", loaded "via an Excel template"What are data models
The model an agent queries"The semantic model: how those assets answer questions. Dimensions, facts, relationships, derived metrics, filters, and verified queries, plus the custom instructions you write to steer the agent."What is Context Engineering Studio

Read together: a concept in Atlan is a term with a definition, a certificate, an owner, and typed links. The model an agent queries holds tables, joins, and metrics. The pages we read describe no class with properties and constraints, held in a W3C standard, that bounds what an agent may join. A metrics layer can define a calculation. It cannot define a concept.

Credit where Atlan's argument is strong. Its Context Engineering Studio page, read 2026-11-22, says "Finance's 'revenue' and Sales' 'revenue' can both be correct." (source). The open question is whether the two revenues are related anywhere a machine can read. Our post Semantic Layer vs Ontology: Which One Says What a Customer Is makes that case in general.

Where do the definition and the calculation live in Atlan?

In two places, by design, and Atlan documents the design plainly. Its docs say "Context Engineering Studio (CES) generates the semantic layer AI agents need to answer questions accurately." A repository "holds two things": the linked assets, "such as tables and glossary terms", and the semantic model, "the part that doesn't exist anywhere else, and the part you edit."

QuestionWhat Atlan's pages saySource
Where does the calculation live?Derived metrics are "Measures built on top of your facts and glossary terms"What's in a context repository
What keeps the two aligned?"linking each glossary term to the metric that computes it is what keeps the two from drifting apart"What Is a Semantic Layer?, published 2025-12-19, updated 2026-07-30
What happens when the term changes?"The Activity tab shows what changed upstream since the model was last built, so you learn about drift from the tab rather than from a wrong answer." Then "click Regenerate to rebuild the model"What's in a context repository

A coherent design. The term carries the meaning and the certificate. The repository carries the math and is rebuilt when the term moves. When Finance asks which net revenue the agent used on 3 March, the answer is in two objects and a log.

What does Atlan's versioning actually document?

Two sets of sentences, both Atlan's, both dated. The marketing page promises one thing and the documentation describes another.

PageAtlan's words, verbatimDate
Context Engineering Studio (marketing)"Git-like versioning. Full history. Branching. A/B testing. Staged rollouts. Rollbacks."Undated, read 2026-11-22
Build a repository (docs)"A new repository starts in Draft. When the model looks right, activate it."Read 2026-11-22
What is Context Engineering Studio (docs)"Redeployments replace what's live in place with no downtime." / "The Activity tab keeps the full history."Read 2026-11-22

Atlan keeps history: an activity log for the life of the instance and an Activity tab per repository. What the pages we read do not describe is a rollback, a branch, a named version, or a way for a consumer to pin to the definition in force on a date. A history you can read and a version you can ask for are different things, and an audit asks for the second.

What does TopQuadrant do, in the same structure?

Our position, with the same weight and open to the same test. Every quoted sentence below is on a live TopQuadrant page, read 2026-11-22. TQ Data Foundation holds the definition as one governed asset. Our semantic layer use case page says: "Every metric carries its business definition, its owner, its calculation, and its mapping to physical columns. When the definition changes, it changes in one place and every consumer picks it up." The concept that metric measures is a class with properties and constraints, on RDF, OWL, and SHACL: the ground Atlan's own page calls "ontology territory".

Same questionWhat TopQuadrant's live pages saySource
What is a customer?"Agents receive concepts, permitted relationships, and metric logic rather than a schema dump." / "Ontology-bounded joins. Only modelled relationships are traversable."Agent-ready semantic layer
Where do the definition and the calculation live?"Definition and calculation together. The plain-language meaning and the logic live on the same governed asset."Semantic layer use case
Who owns it?"Owner per definition. Disagreement resolves to a named person and a governed change process."Agent-ready semantic layer
What did it mean last quarter?"Version history. See what the metric meant last quarter, and what changed since." / "Reproducible. Re-run a historical question against the definitions in force that day."Both pages
What leaves, and in what form?"Everything is modelled on open W3C standards, RDF, OWL, SPARQL, SHACL and SKOS, several of which our team helped author. Your context is yours: export it and go if we stop earning the work."TQ Data Foundation

What one governed asset changes

  • The rule is a test. SHACL is the W3C Shapes Constraint Language, and TopQuadrant co-authored it. "SHACL validation turns each approved definition into a test the data runs on load", and the test runs anywhere a SHACL engine runs.
  • Two functions, one word. "Divergence modelled. Where two functions need different logic, both are governed and related." The relation between the two revenues is a fact a machine can read.
  • AI proposes, your experts confirm. "AI turns what it found into draft models and definitions your team can react to." Then "Human approval turns the draft into governed, authoritative context." The approved record carries the approver, the date, the version, and the scope. Our post Ground Truth: SME-Approved vs Inferred Metadata says why each one matters to the next agent.
  • The catalog is a source. Our platform page says "Catalogs are a source we connect to". Atlan keeps discovery and the stewardship workflow; the governed definition sits above it.

What Atlan says about TopQuadrant

Atlan's own tools guide for context engineering (published 2026-05-21, updated 2026-09-21) lists TopQuadrant under "Business glossary and ontology systems". It credits "support for SKOS taxonomies, OWL ontologies, and SHACL constraint validation" and lists "SHACL validation for ontology correctness" among the pros (source). Atlan's knowledge-graph page (published 2026-07-22, updated 2026-09-21) says "A validation gate such as SHACL keeps ungoverned LLM-extracted relationships out of production graphs." (source). We agree, and every approved definition in TQ Data Foundation runs through that gate. One correction: the same tools guide marks TopQuadrant "No" under MCP Support, and our live agent-ready page says governed context is "served over API, SPARQL, and MCP for any agent framework".

How should you run the evaluation?

Four questions, answerable from the two vendors' pages and a demo in an afternoon.

Four questions that settle it

  • What is a customer, in a form a machine can check? Ask for the concept, its properties, its constraints, and the join paths an agent may take. Atlan's documented answer is a glossary term, its relationships, and an ER model. Ours is a class on OWL with SHACL shapes.
  • Is the definition on the same asset as the calculation? Change the definition in the demo and watch the metric. In Atlan the repository reports drift and you click Regenerate. In TQ Data Foundation "it changes in one place and every consumer picks it up."
  • Can you ask for the definition as of a date? Ask for last quarter's, and who changed it since. Then ask to roll back, and compare the demo with the docs.
  • What leaves, and in what standard? Atlan's documented exports are CSV, spreadsheets, Iceberg tables over SQL, MetricFlow YAML, and Apache Ossie YAML, an incubating interchange format. Of Ossie its docs say "The spec is still changing" (Portability targets). Ours is RDF, OWL, SKOS, and SHACL, with the history attached.

Where does TopQuadrant fit?

Above the catalog, as the record the catalog displays. Atlan's documented strengths are real: discovery across the estate, certificates and workflows your stewards already use, a hosted MCP server, and a studio that lands context in the engines you run. Keep them. What TopQuadrant adds is what the AI platform team asked for in the first paragraph. The concept, the calculation, the owner, the rule, and the version sit on one asset, on standards we helped write. Our post What Is Ontology Management? covers keeping that model governed. Our post What Is a Semantic Layer? says why the concept comes before the metric. Atlan answers the catalog question well. TQ Data Foundation answers what a customer is, with a name and a date on it.

Give your AI the context it's been missing

See how the TQ Data Foundation turns your enterprise knowledge into trusted, Al-ready context.