Fulcrum
Fulcrum is consolidating on Esri, with Google Maps gone September 1
A side-by-side editorial comparison of Marquez and Matomo — 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.
Matomo bets on AI-traffic measurement as its differentiator while modernizing the UI for upmarket buyers.
Matomo is on a near-monthly minor-release cadence threading three concurrent themes: AI-traffic instrumentation, visual modernization (dark mode and theme refresh in 5.10.0), and privacy-compliance shortcuts aimed at EU operators. Patch releases land between minors with security and archiving fixes, and the team still ships occasional Matomo 4 backports for legacy customers.
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.
Matomo is on a near-monthly minor-release cadence threading three concurrent themes: AI-traffic instrumentation, visual modernization (dark mode and theme refresh in 5.10.0), and privacy-compliance shortcuts aimed at EU operators. Patch releases land between minors with security and archiving fixes, and the team still ships occasional Matomo 4 backports for legacy customers.
After introducing AI-agent detection in 5.6.0 and dedicated AI chatbot traffic reports in 5.8.0, Matomo is positioning itself as the analytics tool that explicitly accounts for non-human traffic — a stance neither GA4 nor Plausible has taken head-on. The 5.9.0 one-click CNIL preset and 5.10.0 UI overhaul read as moves to broaden the buyer pool beyond technical self-hosters.
Expect deeper AI-traffic features — segmentation, attribution, and per-agent breakdowns — plus the one-click compliance pattern extended from CNIL to other regulators.
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 Matomo.
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 Matomo alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Matomo is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. 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. Matomo is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. 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 Matomo alternatives in Analytics are ranked by recent ship velocity. Browse the "Matomo alternatives" section above for the current picks, or visit /alternatives/matomo for the full list with editorial commentary on each.