Atlan vs Select Star.
Atlan and Select Star both anchor in catalog & discovery — 2 dimensions differ, 3 hold. Below: posture, coverage diff, and capability matrix.
Enterprise catalog and governance plane positioned as the AI context layer — connectors, lineage, contracts, and an MCP server for agents.
Automated data catalog with column-level lineage parsed from query logs — being acquired by Snowflake to power Horizon Catalog.
Mid-market and enterprise organisations with a real data-governance function — a CDO, stewards, a defined glossary programme — who need a polished, integration-rich catalog with strong column-level lineage and an opinionated view of how AI agents should consume metadata.
Data teams on Snowflake, BigQuery, Databricks, or Redshift plus dbt and a mainstream BI tool who want a catalog that documents itself — column-level lineage, popularity metrics, ER diagrams, and auto-generated docs parsed from query logs rather than curated by hand.
What each is betting on.
Series C ($105M, May 2024) led by GIC and Meritech at a ~$750M valuation. Through 2025–2026 repositioned around 'The Context Layer for AI' — Iceberg-native metadata lakehouse, MCP server for AI agents, Context Engineering Studio. Named a Gartner MQ and Forrester Wave leader 2025. Heavy enterprise positioning; no self-serve free tier.
Snowflake announced a definitive agreement to acquire Select Star's team and platform technology on November 24, 2025 (Snowflake blog; Select Star blog by founder/CEO Shinji Kim). Terms undisclosed. Stated plan: fold Select Star's lineage and discovery into Snowflake's Horizon Catalog to power agentic experiences like Snowflake Intelligence and Cortex Code. Founded 2020 in San Francisco. The public /pricing page has been removed (it now redirects to the homepage).
Each tool's current strategic narrative, verbatim from its profile.
How each tool describes the other.
Atlan's page doesn't directly mention Select Star. See the Atlan detail page.
Select Star cross-shops with atlan, secoda, alation, and collibra among proprietary catalogs, and with datahub, openmetadata, and amundsen on the open-source side — its own site maintains comparison pages against most of these. Its wedge has always been automation-first lineage: where enterprise suites lead with stewardship workflows and OSS catalogs lead with portability, Select Star leads with column-level lineage extracted from query logs with minimal setup, proven at unusual scale (Block used it to automate lineage across an exabyte-scale warehouse). It consumes OpenLineage events, so Airflow and pipeline lineage land in the same graph as warehouse and BI lineage. What it is not is a data-quality engine: there are no monitors, tests, or anomaly detection, which is why the quality-testing cluster scores zero — pair it with a dedicated tool if you need runtime checks.
Each quote is pulled from the named tool's own "Where it fits" write-up.
Spec sheet diff.
| Atlan | Select Star | |
|---|---|---|
| Vendor | Atlan | Select Star (Snowflake) |
| Deployment | Hybrid | SaaS only |
| Founded | 2019 | 2020 |
| HQ | Singapore | San Francisco, California, United States |
| Status | ● active | ○ acquired |
Full Atlan pricing → Full Select Star pricing →
Both share Primary cluster: Catalog & discovery · License: Proprietary · Pricing: Contact sales · Free tier: No · OSS self-host: No · dbt integration: Native · OpenLineage: Consumer
Each tool's center of gravity.
| Cluster | Atlan | Select Star |
|---|---|---|
| Lineage & metadata | 3/3 | 2/3 |
| Quality & testing | 0/3 | 0/3 |
| Catalog & discovery | 3/3primary | 3/3primary |
Scored 0–3 per cluster on the same rubric across all tools. A 0 means the cluster isn't the tool's focus, not that the feature is absent. See the methodology.
Where they cover different ground.
The declared feature set.
5 of 8 declared features differ — listed first.
These are each tool's self-declared key_features; a blank dot means
undeclared, not impossible.
| Feature | Atlan | Select Star |
|---|---|---|
| Data Contracts Quality & testing | ||
| OpenLineage-Native Lineage & metadata | ||
| Reverse Impact Analysis Lineage & metadata | ||
| Table-Level Lineage Lineage & metadata | ||
| Transformation Lineage Lineage & metadata | ||
| Business Glossary Catalog & discovery | ||
| PII Auto-Classification Catalog & discovery | ||
| Column-Level Lineage Lineage & metadata |
Where they disagree.
Catalog & discovery
2 of 9 differ| Atlan | Select Star | |
|---|---|---|
| Data contracts | ||
| Access requests |
Lineage & metadata
1 of 7 differ| Atlan | Select Star | |
|---|---|---|
| Historical |
When to pick each.
Mid-market and enterprise organisations with a real data-governance function — a CDO, stewards, a defined glossary programme — who need a polished, integration-rich catalog with strong column-level lineage and an opinionated view of how AI agents should consume metadata. Particularly strong for teams already on a modern stack (Snowflake or Databricks plus dbt plus Looker or Tableau) where Atlan's SQL parser and OpenLineage ingestion can light up lineage with relatively little manual work. The 2025 MCP-server pitch lands well for organisations actively wiring up Claude, Cursor, or internal agents and wanting a single governed surface those agents query for context.
Data teams on Snowflake, BigQuery, Databricks, or Redshift plus dbt and a mainstream BI tool who want a catalog that documents itself — column-level lineage, popularity metrics, ER diagrams, and auto-generated docs parsed from query logs rather than curated by hand. A natural fit for lean-governance organisations that want automated PII tagging with propagation instead of a steward-heavy programme, and for Snowflake-centric shops that read the pending acquisition as a roadmap tailwind: the technology is slated to become part of Horizon Catalog.
What each does best.
Atlan stands out for
- Polished UX and onboarding — consistently scores top in analyst rankings on time-to-value relative to peers
- Lineage built from four signal sources (SQL parsing, native APIs, OpenLineage events, manual) gives broad coverage without forcing one approach
- Iceberg-native 'Metadata Lakehouse' architecture (rolled out in 2025) decouples metadata storage from compute and supports versioned/time-travel views
- First-class MCP server and AI-agent context surface — the 2025 repositioning is real product, not just marketing
Select Star stands out for
- Automated column-level lineage parsed from warehouse query logs is the differentiator — proven at very large scale (Block's case study covers lineage automation at exabyte scale)
- Fast time-to-value — auto-generated documentation, popularity/usage metrics, and entity-relationship diagrams appear from metadata without manual curation
- Governance automation — automated PII tagging with tag propagation through lineage, plus RBAC/ABAC policy controls in the Data Access Control module
- Credible AI surface — Ask AI natural-language search, an MCP server exposing metadata and lineage to agents, and automated semantic model generation
Tools both also compete with.
All Atlan alternatives, scored →All Select Star alternatives, scored →
A note on this comparison.
Every capability value above traces to Atlan or Select Star's own structured spec, which links back to its source — nothing here is averaged or smoothed across the two.
Notice something inaccurate? Send a correction.