Fulcrum
Fulcrum is consolidating on Esri, with Google Maps gone September 1
Comparison · Analytics
Marquez vs Umami
A side-by-side editorial comparison of Marquez and Umami — release velocity, themes, recent moves, and the top alternatives to consider.
Marquez vs Umami: at a glance
What is Marquez?
Marquez spent 2024 turning a lineage store into a UI, then stopped releasing
Marquez is the reference metadata server for OpenLineage, and this window captures a concentrated push on its web interface: a column-lineage page and redesigned lineage graph in 0.45.0, data quality and job status displays in 0.47.0, and a data observability dashboard in 0.50.0 showing event stats over 24-hour and 7-day windows with per-source, per-dataset and per-job views. The API side moved in step — job tagging, dataset schema versions, paging on jobs and dataset versions, job-to-job lineage, richer metrics labels. One contributor accounts for nearly all the web work in these entries. Note that the 0.45 through 0.49 releases were all stamped within three minutes of each other and in reverse version order, so publication timestamps here do not reflect release order.
What is Umami?
Umami spent late 2025 patching Next.js CVEs, then shipped Boards and Session Replay in v3.1.0.
The window splits sharply. Four of six releases are December 2025 patches across the v2 and v3 lines, all responding to the same Next.js and React security advisories plus Docker build breakage — several shipped within days of each other because the first fix updated Next.js without the affected React versions. Then v3.1.0 in April 2026 delivered custom dashboards as Boards, Session Replay, Web Vitals performance tracking, a redesigned share page, and a large batch of fixes.
Marquez vs Umami: editorial side-by-side
Marquez
0.0ANALYTICS
Marquez spent 2024 turning a lineage store into a UI, then stopped releasing
◆ Current state
Marquez is the reference metadata server for OpenLineage, and this window captures a concentrated push on its web interface: a column-lineage page and redesigned lineage graph in 0.45.0, data quality and job status displays in 0.47.0, and a data observability dashboard in 0.50.0 showing event stats over 24-hour and 7-day windows with per-source, per-dataset and per-job views. The API side moved in step — job tagging, dataset schema versions, paging on jobs and dataset versions, job-to-job lineage, richer metrics labels. One contributor accounts for nearly all the web work in these entries. Note that the 0.45 through 0.49 releases were all stamped within three minutes of each other and in reverse version order, so publication timestamps here do not reflect release order.
◆ Where it's heading
The arc is a backend project growing a front end: lineage data that existed in the API was progressively given pages, panels and paging, and by 0.50.0 the framing had shifted from lineage graph to observability dashboard. Tagging deepened in the same period, moving from dataset tags to field-level tags to job tags. That arc stops abruptly — 0.50.0 in October 2024 is the last entry, with nothing published in the roughly two years since.
◆ Prediction
The entries give no roadmap signal past 0.50.0, and the job-to-job lineage change was explicitly framed as a prompt for a wider parent/child hierarchy discussion that no later release picks up, so that hierarchy work is best read as unfinished rather than planned.
Umami
0.0ANALYTICS
Umami spent late 2025 patching Next.js CVEs, then shipped Boards and Session Replay in v3.1.0.
◆ Current state
The window splits sharply. Four of six releases are December 2025 patches across the v2 and v3 lines, all responding to the same Next.js and React security advisories plus Docker build breakage — several shipped within days of each other because the first fix updated Next.js without the affected React versions. Then v3.1.0 in April 2026 delivered custom dashboards as Boards, Session Replay, Web Vitals performance tracking, a redesigned share page, and a large batch of fixes.
◆ Where it's heading
The security cluster is a framework dependency showing its cost — an analytics tool inheriting its release schedule from Next.js advisories. v3.1.0 is where product work resumes, and its content is telling: Session Replay and Web Vitals move Umami past pageview counting into behaviour and performance, which is the territory occupied by heavier commercial analytics rather than the lightweight privacy-first tools it grew up alongside.
◆ Prediction
Expect the next releases to build on Boards and Session Replay rather than return to the counting core, since both are new surfaces that arrived with a single release and no follow-up yet.
Alternatives to Marquez and Umami
Other Analytics products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Marquez or Umami.
Omni
Omni ships weekly, and almost every week the headline item is an AI feature
OpenDataDiscovery
Four ODD Platform releases in two weeks, and not one of them changes the product
Apache Baremaps
Baremaps got geoparquet and hillshading, then went quiet for eighteen months in incubation
Deequ
Deequ ships GitHub tags whose release notes are one commit message long
Amundsen
Amundsen's last release was a config flag, and the feed has been silent for two years
See all Marquez alternatives → · See all Umami alternatives →
Recent activity from Marquez and Umami
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 3mo agoUmamiv3.1.0: Boards, Session Replay and Web Vitals ⚡
- 8mo agoUmamiv3.0.3: Next.js security patch
- 8mo agoUmamiv2.20.2: Next.js security patch for the v2 line
- 8mo agoUmamiv2.20.1: React version fix and Docker build repairs
- 8mo agoUmamiv2.20.0: Next.js CVE fix for the v2 line
- 8mo agoUmamiv3.0.2: Next.js RSC vulnerability patch and UI fixes
- 1y agoMarquezMarquez 0.50.0 adds a data observability dashboard
- 2y agoMarquezMarquez 0.45.0 ships a column lineage page and redesigned graph
- 2y agoMarquezMarquez 0.46.0 cleans up the UI and fixes streaming terminal events
- 2y agoMarquezMarquez 0.47.0 adds data quality and job status views, job tagging
- 2y agoMarquezMarquez 0.49.0 adds job-to-job lineage to the API
- 2y agoMarquezMarquez 0.48.0 adds paging and dataset schema versions
Frequently asked questions
What is the difference between Marquez and Umami?
They serve adjacent needs but don't currently overlap on shipped themes. Marquez and Umami are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is Marquez better than Umami?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Marquez and Umami are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
What are the best alternatives to Marquez?
Top Marquez alternatives in Analytics are ranked by recent ship velocity. Browse the "Marquez alternatives" section above for the current picks, or visit /alternatives/marquez for the full list with editorial commentary on each.
What are the best alternatives to Umami?
Top Umami alternatives in Analytics are ranked by recent ship velocity. Browse the "Umami alternatives" section above for the current picks, or visit /alternatives/umami for the full list with editorial commentary on each.