Marquez

L3 — Unified Semantic Layer Data Lineage Free (OSS) Apache-2.0 · OSS

OSS reference implementation backend for OpenLineage. Apache-2.0 under Linux Foundation. Postgres-backed metadata server collecting lineage events. Lightweight alternative to full data catalogs when only lineage is needed.

AI Analysis

Marquez is the OSS reference implementation of OpenLineage — Apache-2.0 under Linux Foundation. Postgres-backed metadata server collecting lineage events. Lightweight alternative to full data catalogs when only lineage is the value prop. Pick Marquez when OpenLineage events are the input + simple lineage browsing is the output.

Trust Before Intelligence

Marquez's narrow scope (lineage backend, not full catalog) is intentional. From a Trust Before Intelligence lens, this is honest scope: lineage is a building block; full governance lives elsewhere (OpenMetadata, DataHub).

INPACT Score

23/36
I — Instant
4/6

Postgres-backed.

N — Natural
3/6

REST API + simple UI.

P — Permitted
3/6

Minimal RBAC. Cap rule applied.

A — Adaptive
4/6

Multi-cloud.

C — Contextual
5/6

Lineage events end-to-end. Strong C.

T — Transparent
4/6

Event log inspection.

GOALS Score

16/25
G — Governance
2/6

1/6 -> 2.

O — Observability
3/6

Lineage tracing. 2/6 -> 3.

A — Availability
3/6

3/6 -> 3.

L — Lexicon
4/6

Entity resolution via lineage.

S — Solid
4/6

5/6 -> 4.

AI-Identified Strengths

  • + OpenLineage reference implementation
  • + Apache-2.0 LF-governed
  • + Lightweight vs full catalogs

AI-Identified Limitations

  • - Lineage-only scope
  • - Smaller community
  • - Compliance via substrate

Industry Fit

Best suited for

OpenLineage-only deploymentsLightweight lineage backend

Compliance certifications

OSS Apache-2.0 only.

Use with caution for

Full catalog needs

AI-Suggested Alternatives

OpenLineage

OpenLineage is the spec; Marquez is the backend.

View analysis →
DataHub

DataHub for full catalog. Marquez for lineage-only.

View analysis →

Integration in 7-Layer Architecture

Role: L3 OpenLineage backend.

Upstream: OpenLineage events.

Downstream: Lineage UI + API.

⚡ Trust Risks

medium Used as full catalog scope

Mitigation: Use alongside OpenMetadata/DataHub for full catalog.

Use Case Scenarios

strong Lightweight OpenLineage backend

Native fit.

weak Full catalog needs

OpenMetadata/DataHub fit.

Stack Impact

L3 L3 lineage backend for OpenLineage.

⚠ Watch For

2-Week POC Checklist

Explore in Interactive Stack Builder →

Visit Marquez website →

This analysis is AI-generated using the INPACT and GOALS frameworks from "Trust Before Intelligence." Scores and assessments are algorithmic and may not reflect the vendor's complete capabilities. Always validate with your own evaluation.