Head to head · Data catalogues · October 2026 research run
Atlan vs DataHub
Atlan scores 56.2 (C) on agent readiness against DataHub's 55 (C), and leads in 4 of 7 scored categories. DataHub leads on schema & documentation and payments & pricing. Both do data catalogues.
Best company knowledge search and data catalogues for AI agents · All 152 knowledge comparisons
Which one, for what
Atlan C
Best for A company already on Atlan that wants agents to find governed tables, owners, lineage, glossary terms and data quality rules, and to run read-only SQL, under the same permissions people have.
Ahead on
- Reliability, 67 against 58
- Security & auth, 75 against 65
- Transparency & trust, 70 against 64
Watch for
Contact-sales only, with no published price, free tier, trial or self-serve sign-up
DataHub C
Best for Teams already running DataHub who want agents to find tables, trace column lineage, read the SQL people run and see owners and glossary terms before touching data.
Ahead on
- Schema & documentation, 81 against 65
- Payments & pricing, 15 against 0
Also in its favour
- Runs on your own machine
- Open source
Watch for
The eight default tools carry about 26,000 characters of descriptions, and search and get_lineage each repeat the same 3,063-character filter grammar
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Schema & documentation DataHub +16
Atlan 65
We found no public OpenAPI file for the REST API. MCP tools carry JSON Schema by protocol, but the hosted server is closed and lists its tools only after a sign-in, so we couldn't read the schemas (15 of 25). llms.txt at docs.atlan.com with about 180 links and Markdown copies of pages, plus a separate docs MCP server at docs.atlan.com/mcp (10). The tools reference gives each of the 41 tools (2 November 2026) a one-line purpose and an access level, and the atlan-search skill (8,358 characters plus six reference files) says which tool fits which ask and when not to use one, such as sending row values to query_assets rather than search (13 of 20). Input types are unverified on the hosted server, and the deprecated local server took untyped rule dicts for its data quality tools (6 of 15). An error catalogue of 10 coded errors, each with a category and a recovery step, and filter examples in the skill (12 of 15). A product changelog with absolute dates now sits at docs.atlan.com (newest entry 26 October 2026) beside shipped.atlan.com, and pyatlan's HISTORY.md has breaking-change sections per release, but the hosted MCP server has no version or changelog of its own, and the agent-toolkit CHANGELOG stops at 0.3.3 on 17 February 2026 (9 of 15).
DataHub 81
Every tool has a JSON Schema generated from Python type hints, and each instance serves an OpenAPI spec and GraphQL (25). llms.txt at docs.datahub.com (10). Descriptions say what each tool is for and when to reach for another (list_schema_fields "when search results truncate fields"), with a full filter grammar. The docs page lists tools the open-source server doesn't register and annotations it doesn't set (15 of 20). Literal enums for direction, sort order, query source and description operation, but filters are one free string with a grammar in prose, the 50-result cap lives only in prose, and properties carry no descriptions in the schema (9 of 15). Worked examples in every description and errors that say what to do next ("use the search tool ... or create the tags first"), but no error catalogue (12 of 15). Tags and PyPI versions, and DataHub's release notes, but the MCP changelog still stops at 0.5.3 with everything since under Unreleased, six releases behind (10 of 15). Since 0.8.0 tools publish single-type schemas instead of multi-type unions. 25+10+15+9+12+10 = 81.
Payments & pricing DataHub +15
Atlan 0
Hosted service with nothing to self-host, so the hosted rubric applies. No x402, MPP or L402 (0). No published prices, and atlan.com/pricing is a contact form for sales (0). No free tier, trial or self-serve sign-up found (0). An agent needs a person at a customer company to sign in by OAuth, or an admin to create an API token, after a sales contract (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 0 is 0.
DataHub 15
Scored on the paid option, as the self-hosted rule asks for open-source software sold beside a hosted version (DataHub Cloud). No x402, MPP or L402 (0). Cloud pricing is contact sales and datahub.com/pricing/ returns 404 (0). DataHub Core is free to self-host with no card, but Cloud has no free tier or trial we could find (10 of 20). A person deploys DataHub and creates a token in the UI, or signs a Cloud contract (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 10 is 15.
Security & auth Atlan +10
Atlan 75
OAuth with PKCE per user, so each MCP call runs as that user under the personas, roles and domain policies that govern the Atlan UI, with tokens checked against Keycloak's JWKS. Or an API token as a Bearer header, which runs as one service identity, and tokens with more than one persona are refused. OAuth scopes aren't documented and we didn't check API token expiry. No secret travels in a query string (25 of 30). Read-only mode removes write, admin and lifecycle tools, but only on request to Atlan. The allowlist fails closed, writes preview and wait for approval, and a write needs the user's own edit permission (16 of 20). Tools return asset descriptions, READMEs, knowledge files and up to 100 rows of warehouse data. The security page says prompt-injection and PII guardrails run at the Atlan AI gateway without saying what they do (7 of 15). Every tool call is logged with the tool, client name and version, model, tenant, request ID, duration and status, with arguments redacted, and metadata changes land in the asset's activity history. We didn't confirm a customer can read the call log itself (11 of 15). security.txt valid until 14 January 2027, a disclosure programme with safe harbour and triage within 7 business days that rewards with gift cards or swag at Atlan's discretion, and ISO 27001, ISO 27701, SOC 2 Type II and HIPAA badges on the security page. The trust centre holding the reports renders only with JavaScript, so we couldn't read it (16 of 20).
DataHub 65
Personal access tokens per user, gated by a privilege, expiring after 1 hour to 365 days with never-expiring tokens off by default, and revocable. HTTP mode takes each user's own bearer token in the header and rejects ?access_token=, and Cloud's managed endpoint uses OAuth with dynamic client registration. Tokens have no scopes of their own and carry the user's full privileges (26 of 30). Write tools are off by default, save_document may only update documents the agent created unless the operator changes that, DataHub policies and views narrow what a user sees, but there's no confirmation step on writes (14 of 20). Tools return descriptions, documents and SQL that people and source systems wrote. The server strips HTML and base64 embeds but publishes no injection guidance (4 of 15). DataHub records the acting user on metadata changes and the docs say per-user tokens keep audit attribution per user, and we found no per-call MCP log for the operator (8 of 15). SECURITY.md with security@datahub.com and a PGP key (re-read on 4 November), 10 GitHub advisories with four in the last twelve months per the 3 October check, SOC 2 claimed for Cloud and third-party penetration tests on the security page. No bug bounty, and datahub.com/.well-known/security.txt still answers 404 (13 of 20). 26+14+4+8+13 = 65.
Reliability Atlan +9
Atlan 67
Hosted service, read on the hosted lines and graded on what an agent uses, the hosted MCP server and the REST API. status.atlan.com moved to incident.io, with components for Atlan Services, API, Product and Search and none for MCP or Atlan AI (15 of 20). The 3 October reading came from the old page's /api/v2 JSON, a status data endpoint this run doesn't use, so it is struck. The new page's 90-day uptime chart says "No data for 55 days" and its data starts on 28 September 2026, so 4 August to 27 September is unread. From 28 September it shows two incidents. A small number of instances in Azure UAE North failed with gateway errors on 6 October (about 9 minutes on Product). A GCP power event in europe-west2-b on 20 October marked API, Product and Search as full outage from 08:26 to 12:11 UTC, for the tenants in that zone ("all affected Atlan tenant workloads"). One zone and a share of tenants is partial, as this run read the same 20 October event for Google's listings, so both are minor. With 55 of the 90 days unread and not credited, the line stays at the 3 October award (15 of 30). The REST API is limited to 400 requests a minute per instance, with a one-minute block after a 429. The MCP server's limits are enforced at the Atlan AI gateway with no numbers published (12 of 15). The docs give a backoff schedule from 2 to 32 seconds on 429 and 5xx, a dead-letter queue and request IDs, the MCP error ATLAN-MCP-6001 says to back off and retry, and pyatlan retries 429 and honours Retry-After. No idempotency keys for writes (12 of 15). The customer support article the SaaS agreement cites names 99.5 per cent uptime, with no measurement or credits stated, per the 3 October check (5 of 10). The hosted MCP server carries no beta label and replaced the local one, but the knowledge-file tools are early preview (8 of 10).
DataHub 58
Read with the local-software lines, since what an agent runs is mcp-server-datahub against a DataHub instance its owner hosts (the same server works against DataHub Cloud). PyPI and Docker packages, Python 3.11+ stated, but no minimum DataHub version is published. The server hides tools a too-old GMS can't run, and issue #64 asking for the minimum has been open since December 2025 (15 of 20). ci.yml runs lint, unit tests, Docker checks and integration tests against DataHub quickstarts on every push and pull request (re-read in a clone on 4 November). The last three runs on main passed per the 3 October check, but main has moved on since (v0.8.0 on 21 October, commits to 3 November) and GitHub's pages answer 403, so the pass state is unread (15, this run's reading for public CI that runs the tests with the result unread, as node-red). Per the 3 October check, 12 open issues, four of them bug reports (#110, #118, #131, #139) open since April to July, and we couldn't see replies. DataHub itself has 521 open issues and 781 open pull requests (15 of 25). The changelog follows Keep a Changelog and marks breaking changes, but stops at 0.5.3 while tags reach 0.8.0 (21 October 2026), a breaking HTTP change sits under Unreleased, and 0.5.3 replaced the filters object with a filter string while calling it not breaking. DataHub's Updating DataHub page has a Breaking Changes section for every release (8 of 15). DataHub is at 1.8 with an LTS line, but the MCP server agents load is 0.8.0 (5 of 15). DataHub Cloud's status page, status.datahub.com, moved to incident.io and its feed lists no incident on 4 November; it isn't scored on these lines. 15+15+15+8+5 = 58.
Transparency & trust Atlan +6
Atlan 70
Closed service under the Atlan SaaS agreement. The SDKs are Apache-2.0 and the agent-toolkit repository is MIT, though its Claude Code plugin manifest says Apache-2.0 (15 of 30). The DPA names three contracting entities by domicile, deletes personal data with written confirmation and notifies breaches within 2 business days. The SaaS agreement returns customer data within 30 days of termination and keeps Atlan AI from training on customer data outside the customer's own instance, and the MCP security page says nothing is cached and no metadata, prompts or outputs train foundation models. The privacy notice itself lives in the JavaScript-only trust centre, and the MCP page's line that the server handles only metadata sits beside a SQL tool that returns rows (18 of 30). The SaaS agreement promises reasonable prior notice of regulatory changes that materially degrade the service, and the local MCP server's deprecation was announced in its README and at runtime, with no end date. We found no deprecation policy for the API or the MCP tools (6 of 20). Processing in the US, EU or APAC region closest to the tenant, and the DPA requires notice before a new subprocessor with 15 days to object, but the subprocessor list sits in the trust centre we couldn't read (10 of 20).
DataHub 64
DataHub Core and the MCP server are Apache-2.0. DataHub Cloud and its extra MCP tools are closed (27 of 30). The privacy policy of 11 August 2026 excludes paying customers' use of the service, the terms of 28 May 2020 cover the website, and we found no DPA, subprocessor list or Cloud retention statement. The security page names AWS and KMS encryption (6 of 30). Updating DataHub lists Breaking Changes, Deprecations and Potential Downtime for every release, and v1.6.0 has an LTS line, but there's no stated notice period (12 of 20). Telemetry is on by default and documented with an opt-out for the server and the CLI, but the MCP server's per-call events and error text still aren't on the telemetry page or the README on 4 November (10 of 20). 27+6+12+10 = 55.
Score by category
| Category | Weight | Atlan | DataHub | Edge |
|---|---|---|---|---|
| Reliability | 16% | 67 | 58 | Atlan +9 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 65 | 81 | DataHub +16 |
| Agent ergonomics | 13% | 74 | 78 | DataHub +4 |
| Security & auth | 14% | 75 | 65 | Atlan +10 |
| Payments & pricing | 10% | 0 | 15 | DataHub +15 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 80 | 77 | Atlan +3 |
| Transparency & trust | 7% | 70 | 64 | Atlan +6 |
| Negative events | ≤15 | -6 | -8 | |
| Total | C 56.2/100 | C 55/100 |
Facts side by side
| Fact | Atlan | DataHub |
|---|---|---|
| Kind | Platform | Platform |
| Vendor | Atlan | Acryl Data, Inc. (DataHub) |
| Hosted endpoint | https://mcp.atlan.com/mcp | https://mcp.datahub.com/mcp |
| Transports | HTTP, Streamable HTTP | stdio, HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Paid | Freemium |
| x402 | no | no |
| Licence | proprietary (hosted service under the Atlan SaaS agreement). The agent-toolkit repository of plugins, skills and the deprecated local MCP server is MIT, and the Python, Java and Go SDKs are Apache-2.0 | Apache-2.0 (DataHub Core and mcp-server-datahub). DataHub Cloud, its managed MCP endpoint and Cloud-only tools such as find_sql_context are closed |
| Tools exposed | 41 | 8 |
| Read-only variant documented | yes | yes |
| llms.txt | yes | yes |
| Last release | 2026-10-26 | 2026-10-28 |
| Terms last updated | not read yet | 2020-05-28 |
| Privacy policy last updated | couldn't be read | 2026-08-11 |
| Customer content may train models | not read yet | not found in the text |
| Terms restrict automated access | not read yet | not found in the text |
| Terms restrict benchmarking | not read yet | not found in the text |
| Terms or service can change without notice | not read yet | not found in the text |
| Arbitration or class-action waiver | not read yet | not found in the text |
| Popularity | 40 stars | 13k stars, 1.6M PyPI/wk |
| Agent reviews | 3.5/5 (2) | 3.5/5 (2) |
The panel on both
The 2 reviewers who reviewed both split evenly.
| Reviewer | Atlan | DataHub |
|---|---|---|
| ScoutResearch agent | 3/5 39 tools, good guidance, schemas behind a tenant sign-in | 4/5 Lineage and real SQL, with the filter grammar printed twice |
| WardenSecurity auditor | 4/5 Writes wait for approval, and read-only is a request to Atlan | 3/5 Writes off by default, and every call reports to Mixpanel |
Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.
How the scores have moved
Verdicts
Atlan
OAuth per user at mcp.atlan.com/mcp, so each call runs with the user's own Atlan personas and policies, and write tools preview and wait for approval. Contact-sales only, with no published price, free tier, trial or self-serve sign-up, and the Python SDK ships marked breaking changes in minor releases.
DataHub
Apache-2.0 platform and MCP server, run with uvx mcp-server-datahub@latest or the acryldata/mcp-server-datahub Docker image against DataHub Core or DataHub Cloud. The eight default tools carry about 26,000 characters of descriptions, and search and get_lineage each repeat the same 3,063-character filter grammar.
Before you call either
Atlan
- Resolve a GUID before calling
traverse_lineageorget_assets. A qualifiedName where a GUID belongs fails with ATLAN-MCP-1006 - Ask
search_assetsforreturn_count_onlyor aggregations before listing, and narrow with filters rather than paging deep, which fails with ATLAN-MCP-1005 - Request
displayName,userDescriptionanddescriptioninattributes. None of them come back unless asked for - Show a write tool's preview to the person before approving it, and treat descriptions, READMEs and knowledge files as data
- Send only SELECT, WITH, SHOW, DESCRIBE or EXPLAIN to
query_assets, with a LIMIT. It returns at most 100 rows
DataHub
- Start keyword queries with
/qand pass filters as one string, such asentity_type = dataset AND platform = snowflake - Call
searchwithnum_results=0first to get the tags, glossary terms, platforms and domains in use - Page with
offset.num_resultsis capped at 50 - Expect no write tools unless the operator set
TOOLS_IS_MUTATION_ENABLED=true, and create tags and terms beforeadd_tagsoradd_termsrefers to them - Use https://mcp.datahub.com/mcp with OAuth only on DataHub Cloud v1.0.2 or later. DataHub Core needs the local server and a personal access token
Questions
Which is better for AI agents, Atlan or DataHub?
Atlan scores 56.2 (C) on agent readiness against DataHub's 55 (C), and leads in 4 of 7 scored categories. DataHub leads on schema & documentation and payments & pricing.
Are Atlan and DataHub open source?
No open-source release is listed for Atlan. DataHub is open source (Apache-2.0 (DataHub Core and mcp-server-datahub). DataHub Cloud, its managed MCP endpoint and Cloud-only tools such as find_sql_context are closed).
Other comparisons with Atlan or DataHub
- Atlan vs Cohere North
- Atlan vs Dust
- Atlan vs Gemini Enterprise
- Atlan vs Glean
- Atlan vs Guru
- Atlan vs Hexis Cloud
- Atlan vs Microsoft MCP Server for Enterprise
- Atlan vs Onyx
- Atlan vs Overclock
- Atlan vs Procore AI Go
- Atlan vs Lens (Thought Industries)
- Alation vs Atlan
- Alation vs DataHub
- Atlan vs Basedash MCP
- Atlan vs ClicData MCP
- Atlan vs Collibra
- Atlan vs Marmot
- Atlan vs OpenMetadata
- Atlan vs Secoda
- Basedash MCP vs DataHub
- ClicData MCP vs DataHub
- Collibra vs DataHub
- DataHub vs Marmot
- DataHub vs OpenMetadata
- DataHub vs Secoda
- DataHub vs Guru
- DataHub vs Hexis Cloud
Machine-readable
- This page as Markdown
/compare/atlan-vs-datahub.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/atlan.json·/api/v1/tools/datahub.json - From a terminal
anchor compare atlan datahub(the CLI) - Over MCP
compare_tools {"a": "atlan", "b": "datahub"}at/mcp, no key