Fulcrum
Fulcrum is consolidating on Esri, with Google Maps gone September 1
A side-by-side editorial comparison of Deequ and Umami — release velocity, themes, recent moves, and the top alternatives to consider.
Deequ ships GitHub tags whose release notes are one commit message long
Deequ is a data quality library for Spark, and it releases per Spark version — tags carry a -spark-3.5 or -spark-4.0 suffix, so the same code line ships more than once. The release notes are whatever the last commit message said, which here means each entry is a single line. Four releases landed in a month between March and April 2026, and only two of them contain any product change: a Range analyzer with DQDL rule support, and a processRowsTyped API for typed outcome access.
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.
Deequ is a data quality library for Spark, and it releases per Spark version — tags carry a -spark-3.5 or -spark-4.0 suffix, so the same code line ships more than once. The release notes are whatever the last commit message said, which here means each entry is a single line. Four releases landed in a month between March and April 2026, and only two of them contain any product change: a Range analyzer with DQDL rule support, and a processRowsTyped API for typed outcome access.
The visible work points in one direction — making check results programmatically consumable rather than just readable. A typed outcome API and a rule language binding are what you build when Deequ is being called from a pipeline that reacts to the result, not from a notebook where a human reads it. The column-pruning override added alongside the Range analyzer suggests the same attention on the cost side, keeping analyzers from scanning columns they do not reference.
The entries are too thin to support a confident read of what comes next; the only clear pattern is that each change will ship separately against Spark 3.5 and Spark 4.0, so the version skew between those branches will keep widening.
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.
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.
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.
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 Deequ or Umami.
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
Marquez spent 2024 turning a lineage store into a UI, then stopped releasing
Amundsen's last release was a config flag, and the feed has been silent for two years
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Deequ 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Deequ 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.
Top Deequ alternatives in Analytics are ranked by recent ship velocity. Browse the "Deequ alternatives" section above for the current picks, or visit /alternatives/deequ for the full list with editorial commentary on each.
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.