Skip to content
Data Workers Docs

Atlan, Alation, or Collibra?

Straight answer: we don’t ship a native connector for Atlan, Alation, or Collibra today.

Here’s what teams on those catalogs actually do, in the order we recommend:

1. Connect the systems underneath your catalog

Section titled “1. Connect the systems underneath your catalog”

Your Atlan, Alation, or Collibra instance catalogs the same Snowflake, Databricks, BigQuery, and dbt your agents need. Connecting those systems directly delivers most of the value — schemas, lineage, query history, cost — without touching the catalog at all. This is how we recommend starting a pilot.

What you lose: curated business glossary entries and stewardship workflows that live only in the catalog. For many teams that’s acceptable for an evaluation; for the rest, see option 2.

2. Ask us to build it

Section titled “2. Ask us to build it”

Connector priority is demand-driven. If a native Atlan, Alation, or Collibra connector is what stands between you and adopting Data Workers, tell us — with a sense of which objects matter (glossary, lineage, policies, stewardship). Scale customers can raise this directly with their named engineer; custom integration work is part of that plan.

3. Build it yourself with the provider SDK

Section titled “3. Build it yourself with the provider SDK”

The catalog connector surface is an open interface. The @data-workers/catalog-provider-sdk has zero runtime dependencies and ships with a conformance kit, so you can implement a provider against your catalog’s API and validate it locally. This is the same interface our own connectors implement — a community Atlan/Alation/Collibra provider is a real project, not a hack.