Data Stack Index / v 02.06
Verified 2026·07·03
Send a correction
Compare Same primary cluster · Catalog & discovery

Apache Atlas vs Select Star.

Apache Atlas and Select Star both anchor in catalog & discovery — 8 dimensions differ, 1 hold. Below: posture, coverage diff, and capability matrix.

Same Catalog & discovery (primary)
Differ on DeploymentLicensePricing transparencyFree tierOSS optiondbt depthOpenLineage stanceWarehouse coverage
1 ● Apache Atlas leads
6 shared
5 Select Star leads ○
● Apache Atlas

The ASF's Hadoop-native metadata framework — typed entities, classification propagation via lineage, and Ranger-enforced policies.

○ Select Star

Automated data catalog with column-level lineage parsed from query logs — being acquired by Snowflake to power Horizon Catalog.

● Pick Apache Atlas if

Organisations running Hadoop-era estates — Hive, HBase, Kafka, Impala — especially on Cloudera Data Platform, where Atlas ships as the embedded governance layer.

○ Pick Select Star if

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.

01
Strategic posture

What each is betting on.

● Apache Atlas

Born inside Hortonworks' Data Governance Initiative (announced December 2014, with enterprise partners), entered the Apache Incubator in May 2015 and graduated to a top-level ASF project in June 2017. Today it survives primarily as the governance layer embedded in Cloudera Data Platform, and as the foundation of Microsoft Purview's Data Map, which is based on Atlas and supports Atlas APIs. Release cadence has slowed markedly: 2.3.0 (Dec 2022), 2.4.0 (Jan 2025), 2.5.0 (Apr 2026).

● Select Star

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.

02
At a glance

Spec sheet diff.

Apache Atlas Select Star
Vendor Apache Software Foundation Select Star (Snowflake)
Deployment Self-hosted only SaaS only
License Open source Proprietary
Pricing OSS · paid tiers Contact sales
Free tier Yes No
OSS self-host Yes No
dbt integration None Native
OpenLineage None Consumer
Founded 2015 2020
HQ San Francisco, California, United States
Status ● active ○ acquired

Full Apache Atlas pricing → Full Select Star pricing →

Both share Primary cluster: Catalog & discovery

03
Cluster strength

Each tool's center of gravity.

Cluster Apache Atlas Select Star
Quality & testing 0/3 0/3
Catalog & discovery 3/3primary 3/3primary
Lineage & metadata 2/3 2/3

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.

04
Coverage

Where they cover different ground.

Target personas
Both Data engineer · Data steward · Governance lead
Only Apache Atlas Platform engineer
Only Select Star Analyst · Analytics engineer
Company size fit
Both Enterprise · Mid-market
Only Select Star Scaleup
Warehouse coverage
Only Apache Atlas Trino
Only Select Star BigQuery · Databricks · MSSQL · MySQL · Postgres · Redshift · Snowflake
Orchestrators
Only Apache Atlas Impala · Kafka · Spark · Sqoop · Storm
Only Select Star Airflow · Aws Glue · Fivetran · dbt Cloud · dbt Core
05
Declared features

The declared feature set.

3 of 6 declared features differ — listed first. These are each tool's self-declared key_features; a blank dot means undeclared, not impossible.

Feature Apache Atlas Select Star
PII Auto-Classification Catalog & discovery
Reverse Impact Analysis Lineage & metadata
Transformation Lineage Lineage & metadata
Business Glossary Catalog & discovery
Column-Level Lineage Lineage & metadata
Table-Level Lineage Lineage & metadata
06
Capability matrix

Where they disagree.

Catalog & discovery

4 of 9 differ
Apache Atlas Select Star
NL search
Governance flows
PII auto-classify
Free self-host
Both also haveBusiness glossary · Tag propagation · Ownership tracking
Neither doesData contracts · Access requests

Lineage & metadata

2 of 7 differ
Apache Atlas Select Star
Reverse impact
BI lineage
Both also haveColumn-level · Cross-system · Lineage API
Neither doesHistorical · Lineage diff
07
Verdict

When to pick each.

● Pick Apache Atlas if

Organisations running Hadoop-era estates — Hive, HBase, Kafka, Impala — especially on Cloudera Data Platform, where Atlas ships as the embedded governance layer. The pairing with Apache Ranger is the reason to choose it: classify a column PII in Atlas and Ranger enforces masking and access policies on the actual data, with classifications propagating automatically through lineage as data moves. That metadata-driven-security loop is still the strongest in open source. Also relevant for teams building against Microsoft Purview, whose Data Map is based on Atlas and supports Atlas APIs — the type system and REST surface transfer directly. Vendor-neutral ASF governance and a genuinely complete Apache-2.0 codebase (no open-core split) round out the case.

○ Pick Select Star if

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.

08
Strengths

What each does best.

Apache Atlas stands out for

  • [+] Classification propagation via lineage plus Apache Ranger integration — tag-based access control and data masking enforced on the data itself, not just documented in the catalog
  • [+] Rigorous typed metadata model (types, entities, first-class relationships) that handles technical and business metadata in one graph
  • [+] Vendor-neutral ASF governance and a complete Apache-2.0 codebase — no managed tier holding features back
  • [+] Column-level lineage for Hive and Impala, captured in real time by hooks since the 0.8 line — mature and battle-tested within its ecosystem

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
09
Other alternatives

Tools both also compete with.

All Apache Atlas alternatives, scored →All Select Star alternatives, scored →

A note on this comparison.

Every capability value above traces to Apache Atlas 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.

No paid placementNo vendor submissionsRankings never for sale Independence policy →