Fulcrum
Fulcrum is consolidating on Esri, with Google Maps gone September 1
A side-by-side editorial comparison of Marquez and Tableau — release velocity, themes, recent moves, and the top alternatives to consider.
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.
Tableau's feed captures download indexes, so a cadence change is the only real news in it.
The crawled entries are Tableau's release infrastructure rather than release content: a downloads index listing every supported version, two captures of the Desktop and Web Authoring release-notes page whose feature list lives inside an embedded viz, and a stray resources link. The one substantive item is a notice that Tableau has changed its product and maintenance release cadence, published ahead of the download pages.
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.
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.
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.
The crawled entries are Tableau's release infrastructure rather than release content: a downloads index listing every supported version, two captures of the Desktop and Web Authoring release-notes page whose feature list lives inside an embedded viz, and a stray resources link. The one substantive item is a notice that Tableau has changed its product and maintenance release cadence, published ahead of the download pages.
What is visible is a versioning rhythm, not a product direction: 2026.1 shipped in March 2026 while the 2025.3 and 2025.1 lines continued taking maintenance patches, and 2025.2 moved to limited support. Because the feature list is rendered inside a visualization rather than as text, what actually changed for analysts in each release never reaches the feed.
Maintenance releases on the 2025.x lines will keep appearing alongside the newer 2026.x line, and the cadence change is the item worth watching for how far apart major releases land. The entries give no basis for calling what ships inside those releases.
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 Tableau.
Fulcrum is consolidating on Esri, with Google Maps gone September 1
Omni ships weekly, and almost every week the headline item is an AI feature
Four ODD Platform releases in two weeks, and not one of them changes the product
Baremaps got geoparquet and hillshading, then went quiet for eighteen months in incubation
Deequ ships GitHub tags whose release notes are one commit message long
Amundsen's last release was a config flag, and the feed has been silent for two years
See all Marquez alternatives → · See all Tableau alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Marquez and Tableau 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Marquez and Tableau 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.
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.
Top Tableau alternatives in Analytics are ranked by recent ship velocity. Browse the "Tableau alternatives" section above for the current picks, or visit /alternatives/tableau for the full list with editorial commentary on each.