Coalesce Catalog
7.5#2 in data lineage toolsFrom $150 a monthFree planWebAPIExtension
VisitCoalesce Catalog vs Marquez
What both publish
| Fact | Coalesce Catalog | Marquez |
|---|---|---|
| Audience | Coalesce Catalog is intended for data engineers and analysts and is designed for everyone in an organization to use without training. | Marquez is designed for data teams managing metadata and lineage across data processing applications and pipelines. |
| Authentication | Coalesce supports Snowflake OAuth with periodically rotating access tokens and describes it as the preferred authentication method. | Clients can send an API key using Bearer Auth when configured, while the Marquez HTTP API does not require authentication or authorization by default. |
| Integrations | Catalog integrations include warehouses and databases such as Snowflake, Databricks, BigQuery, Redshift, PostgreSQL, SQL Server, and Salesforce; BI tools such as Tableau, Power BI, Looker, Sigma, Qlik Sense, and Metabase; Airflow, dbt, Fivetran, Monte Carlo, Soda, Slack, Gmail, Okta, and Google SSO. | The site names Apache Airflow, Apache Spark, Apache Flink, dbt, and Dagster as integrations supported through the OpenLineage community. |
| Purpose | Coalesce Catalog connects across the data stack, documents assets with AI, and keeps lineage, ownership, and definitions current automatically. | Marquez consumes, stores, and visualizes OpenLineage metadata for use cases including data governance, data quality monitoring, and performance analytics. |
Coalesce Catalog plans
- DeveloperFree
- Starter$150 a month
- Business CriticalPriced on request
- EnterprisePriced on request
Marquez plans
No prices published.
Pick Coalesce Catalog if…
Coalesce Catalog suits data engineers and analysts who need searchable documentation, lineage, and governance across connected data systems. Its organization-wide design is intended for people to use without training, while the integrations and API support teams managing varied platforms.
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.