Apache Atlas
7.2#4 in data lineage toolsFree planFree planWebAPILinuxSelf-hosted
VisitApache Atlas vs Marquez
What both publish
| Fact | Apache Atlas | Marquez |
|---|---|---|
| Authentication | Supported authentication methods include file credentials, Kerberos, LDAP or Active Directory, Keycloak OpenID Connect/OAuth2 and PAM. | Clients can send an API key using Bearer Auth when configured, while the Marquez HTTP API does not require authentication or authorization by default. |
| Deployment | The repository provides Docker build instructions and produces server, source and multiple hook distribution archives. | The deployment guide describes Docker and Kubernetes deployments and says the HTTP API server uses PostgreSQL to store dataset, job, and run metadata. |
| Integrations | Documented metadata sources include Hive, Sqoop, Falcon, Storm and HBase. | The site names Apache Airflow, Apache Spark, Apache Flink, dbt, and Dagster as integrations supported through the OpenLineage community. |
| Purpose | Apache Atlas provides open metadata management and governance capabilities to catalog, classify, govern, and support collaboration around data assets. | Marquez consumes, stores, and visualizes OpenLineage metadata for use cases including data governance, data quality monitoring, and performance analytics. |
Apache Atlas plans
- Apache AtlasFree
Marquez plans
No prices published.
Pick Apache Atlas if…
Atlas suits teams that need to catalog, classify, search, and govern metadata across data assets. It may also suit organizations seeking lineage access through a UI and REST APIs.
Pick Marquez if…
Marquez suits data teams that need to track metadata and lineage across processing applications and pipelines. It may also fit teams investigating dependencies, schema changes, or job performance.