Fulcrum
Fulcrum is consolidating on Esri, with Google Maps gone September 1
A side-by-side editorial comparison of Looker and Marquez — release velocity, themes, recent moves, and the top alternatives to consider.
Looker's release feed is mostly page furniture; the shipping behind it is thin.
Most of what reaches this feed is scraped structure from Google Cloud's release-notes index — section headings, edition filters, a navigation dump — rather than releases. The real changes in the window are narrow: mobile alerts now arrive as push notifications on the Looker app, and a Table Visualization Improvements preview landed disabled by default. One note flags behaviour changes due with Looker 26.8 in May 2026.
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.
Most of what reaches this feed is scraped structure from Google Cloud's release-notes index — section headings, edition filters, a navigation dump — rather than releases. The real changes in the window are narrow: mobile alerts now arrive as push notifications on the Looker app, and a Table Visualization Improvements preview landed disabled by default. One note flags behaviour changes due with Looker 26.8 in May 2026.
Looker's development is being folded into the Google Cloud release cadence, where each Looker change is a line item in a much larger catalogue. What is visible is upkeep of the existing surface — mobile parity, visualization polish, preview flags — not new capability. On the evidence in this feed the product is in a low-signal, maintenance phase.
The 26.8 release is the next entry with actual content behind it; the pattern here suggests it arrives as a set of preview-flagged behaviour changes rather than a headline feature.
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.
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 Looker or Marquez.
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 Looker alternatives → · See all Marquez alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Looker and Marquez 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. Looker and Marquez 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 Looker alternatives in Analytics are ranked by recent ship velocity. Browse the "Looker alternatives" section above for the current picks, or visit /alternatives/looker for the full list with editorial commentary on each.
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.