Compare the evidence Embrasure collects across storage, compute, transformation, streaming, and BI systems.
Choose sources by the evidence you need, not by cloud provider. Embrasure can combine several paths for one asset and keeps their provenance separate.
| Source | Catalog | Runtime or query | Jobs and runs | Table | Column | Downstream use |
|---|---|---|---|---|---|---|
| Amazon Athena + Glue | Native | Native | OpenLineage | Yes | SQL + facets | Queries |
| Amazon Redshift | Native | Native | OpenLineage | Yes | SQL + facets | Queries |
| Amazon S3 lakehouse tables | Glue | Spark | OpenLineage | Yes | Spark facets | Jobs |
| AWS Glue jobs | Glue | Spark | OpenLineage | Yes | Spark facets | Jobs |
| Amazon EMR | Glue | Spark | OpenLineage | Yes | Spark facets | Jobs |
| Amazon DataZone | Import | Native feed | Native feed | Yes | When provided | Assets + jobs |
| BigQuery | Native | Native | OpenLineage | Yes | SQL + Google fields | Queries |
| Dataproc | BigQuery or GCS | Spark | OpenLineage | Yes | Google or Spark facets | Jobs |
| Google Data Lineage | Import | Native feed | Native feed | Yes | When provided | Assets + jobs |
| Azure SQL | Native | Native | OpenLineage | Yes | SQL + facets | Queries |
| Azure Cosmos DB | Native | Native | OpenLineage | Yes | Facets | Applications |
| Synapse + Data Factory | Purview | Native feed | Native feed | Yes | When provided | Pipelines |
| ADLS | Purview | Spark | OpenLineage | Yes | Spark facets | Jobs |
| Microsoft Purview | Import | Native feed | Native feed | Yes | When provided | Reports + pipelines |
| Snowflake | Native | ACCESS_HISTORY | OpenLineage | Yes | Native + SQL | Queries |
| Databricks | Unity Catalog | System lineage | OpenLineage | Yes | System lineage | Queries + jobs |
| PostgreSQL + Supabase | Native | Query evidence | OpenLineage | Yes | SQL + facets | Queries |
| MySQL | Native | Query evidence | OpenLineage | Yes | SQL + facets | Queries |
| Airflow | Datasets | Operator evidence | Native provider | Yes | Facets | DAGs + tasks |
| Spark + Flink | Datasets | Runtime plans | Native listener | Yes | Facets | Jobs |
| dbt | Manifest | Run artifacts | dbt project | Yes | Compiled SQL | Models |
| SQLMesh | Project export | Rendered SQL | Environments | Yes | Compiled SQL | Models |
| Fivetran | Connector assets | Run metadata | Sync runs | Yes | Enabled mappings | Replication |
| Kafka + Debezium | Topics + schemas | Connector metadata | Connector runs | Yes | Schema mappings | Topics + sinks |
| Looker + Tableau | BI catalog | Query metadata | Refresh runs | Yes | Model mappings | Explores + dashboards |
| Power BI + QuickSight | BI catalog | Query metadata | Refresh runs | Yes | Model mappings | Reports + dashboards |
| DataHub | Imported assets | Imported evidence | Imported jobs | Yes | When provided | Any imported asset |
| Custom applications | OpenLineage datasets | Application events | Application runs | Yes | Facets | APIs + services |
Runtime and warehouse-native observations carry more authority than declarations or static inference. A lower-authority source can fill a gap, but it cannot silently replace stronger contradictory evidence.
Evidence reaches the served graph only after its endpoints resolve to catalog objects inside the source binding. Unresolved evidence stays durable and can resolve after a later catalog sync or identity improvement.