Alation is a commercial data catalog and data intelligence platform combining search and discovery, lineage, stewardship, and data quality, deployable either as the Alation Cloud Service or on the customer's own infrastructure.
The Alation Cloud Service, or on-premises on your own infrastructure. Query Log Ingestion runs on a schedule against the warehouse's logs to compute popularity and lineage; 50-plus connectors reach sources through the Open Connector Framework, which is public, so a missing connector can be built. Data quality is a module inside the catalog rather than beside it.
How Alation answers the questions Data Catalogs turns on.
| How it works | |
| Metadata model | Behavioural before documentary: Query Log Ingestion parses the warehouse's own query logs into Popularity, Top Users and JOIN information, so the catalog builds a picture of what matters before anyone documents it. Metadata extraction supplies the structure and Document Hubs hold the prose |
| Lineage | Calculated rather than declared: from metadata extraction, query log ingestion and Compose queries together, column-level where the connector supports it and behind a feature flag on some. Manual editing fills the gaps and a public lineage API uploads what ETL tools never told anyone |
| Search and discovery | The reason to buy it, search ranked by the Popularity that query logs computed, so the table people actually use outranks the one somebody documented, with Compose as a SQL editor inside the catalog and TrustCheck warning in that editor when a query touches something flagged |
| Business glossary | A customisable Glossary Hub inside Document Hubs, which also carry policies, procedures and specifications as documentation types you define, so business terms sit in the same system as the governance prose rather than a module beside it |
| Quality checks | Alation Data Quality is a module of its own, with checks and monitors covering completeness, validity, accuracy and freshness managed inside the catalog rather than beside it |
| Custom metadata | Custom fields and custom templates on catalog objects, Document Hubs with documentation types you define, and the Open Connector Framework for building a connector Alation does not ship, with a public API covering lineage and the rest |
| Connections | |
| Connectors | Everything runs through the Open Connector Framework in two tiers, 50+ core RDBMS connectors beside 7 BI, 3 file system and 2 ELT, then an enhanced tier adding 8 more sources, 5 BI tools and Matillion. The framework is public, so a missing connector can be built rather than requested |
| Access | |
| Policy and compliance | The Data Governance App: a Policy Center holding the documents, a Workflow Center recording who approved what, a Stewardship Workbench for curating in bulk, and a dashboard over the top. TrustCheck then pushes the result into the query editor rather than leaving it on a page nobody opens |
| Access requests | Through the Workflow Center rather than a basket, name the reviewers, require a minimum number of approvals or all of them, and the outcome writes back to the catalog page. Access requests ride that same machinery; there is no separate shopping flow of the kind Collibra ships |
| Cost | |
| Billing unit | No price published (the pricing page is a call booking) but the unit is: three named-user licence levels, Creator for anyone who edits, Explorer for query-form users on the cloud service, and Viewer for everyone who only reads, with consumption tracked against allocation in admin settings |
vs Alation: Managed · Serverless · Operational complexity: Low
vs Alation: Open source (permissive) · Self-hosted · Free · Operational complexity: High · Java
vs Alation: Open source (permissive) · Self-hosted · Free · Java