Fulcrum
Fulcrum is consolidating on Esri, with Google Maps gone September 1
A side-by-side editorial comparison of Marquez and PostHog — 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.
PostHog is filling in Logs and the mobile SDKs while quietly growing a support product.
PostHog ships weekly, and this week's batch is spread across four teams rather than concentrated in one product. Logs gets attribute filtering and a React Native capture path; the iOS SDK gains rage-click detection and a session-replay duration floor; Conversations picks up GitHub issues as an inbound support channel. Individually these are small, and the weekly digest bundles them into a single roundup entry.
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.
PostHog ships weekly, and this week's batch is spread across four teams rather than concentrated in one product. Logs gets attribute filtering and a React Native capture path; the iOS SDK gains rage-click detection and a session-replay duration floor; Conversations picks up GitHub issues as an inbound support channel. Individually these are small, and the weekly digest bundles them into a single roundup entry.
Two build-outs are running in parallel. The observability side — Logs plus the mobile SDKs — is being brought up to parity with what PostHog already offers on web, which is what makes the platform credible for mobile teams rather than web analytics with an SDK attached. The Conversations work is the more interesting thread: adding support channels moves PostHog past measuring users toward handling them, and it is being built out in the same incremental weekly rhythm as everything else.
Expect Logs and the mobile SDKs to keep receiving parity features on the weekly cadence, and expect Conversations to add further inbound channels beyond GitHub issues. The entries do not show whether Conversations is being positioned as a standalone product or a feature of the existing suite.
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 PostHog.
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 PostHog 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 PostHog 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 PostHog 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 PostHog alternatives in Analytics are ranked by recent ship velocity. Browse the "PostHog alternatives" section above for the current picks, or visit /alternatives/posthog for the full list with editorial commentary on each.