Hex
Hex is rebuilding analytics around an agent — now an MCP client that pulls context from anywhere.
A side-by-side editorial comparison of Umami and Apache Superset — release velocity, themes, recent moves, and the top alternatives to consider.
Umami v3.1.0 ships custom dashboards and session replay on top of the v3 rewrite.
v3.1.0 is the headline: Boards (custom dashboards composed on a row/column canvas), Session Replay, Web Vitals performance tracking, a redesigned share page, and a long fix list. Underneath sit a December stretch of CVE patches across both v3 and v2 lines (Next.js security update), and the November v3.0.0 launch that established the new UI and architecture.
Superset's public feed is all Helm-chart packaging — the 6.x product work sits behind release votes
What this feed surfaces for Superset is almost entirely Helm-chart version bumps and Apache release-vote threads, not application-level changelog. The substantive work — the 6.1.0 release candidates — appears only as PMC voting emails. Day-to-day, the visible cadence is chart packaging for Kubernetes operators.
v3.1.0 is the headline: Boards (custom dashboards composed on a row/column canvas), Session Replay, Web Vitals performance tracking, a redesigned share page, and a long fix list. Underneath sit a December stretch of CVE patches across both v3 and v2 lines (Next.js security update), and the November v3.0.0 launch that established the new UI and architecture.
Umami is moving past privacy-friendly pageview counting toward full product analytics — Boards turns it into a build-your-own dashboard tool, Session Replay adds qualitative behavior data, and Web Vitals brings performance into the same surface. The v3 rewrite was the foundation; v3.1 is where the surface area starts widening.
Expect deeper Session Replay tooling next — privacy filters, search/filter across replays, integration with Boards. Funnels and cohort analysis are the natural follow-ons given the dashboard composition primitive. The maintained v2 line will likely shrink to security-only patches.
What this feed surfaces for Superset is almost entirely Helm-chart version bumps and Apache release-vote threads, not application-level changelog. The substantive work — the 6.1.0 release candidates — appears only as PMC voting emails. Day-to-day, the visible cadence is chart packaging for Kubernetes operators.
The chart releases are clustering tightly (four 0.17.x patches in two days), which signals active deployment-side iteration ahead of a 6.1.0 cut still moving through release-candidate votes. The product direction itself isn't legible from these entries — the feed is pointed at the chart repo, not the changelog.
Expect 6.1.0 to graduate from rc to a tagged release once the vote passes, followed by a corresponding chart bump. The chart-patch cadence likely continues in the meantime.
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 Umami or Apache Superset.
Hex is rebuilding analytics around an agent — now an MCP client that pulls context from anywhere.
Fulcrum is in steady maintenance mode, polishing its field-mapping and mobile data-capture core.
Lightdash keeps sanding down the edges of self-serve BI, chart by chart.
Apify is rebuilding the Actor platform as MCP-first agent infrastructure.
Duplicate Apache Superset row — same Helm-chart packaging feed, no distinct product signal
Tinybird funnels customers from Classic to Forward while widening connectors and SDK coverage.
See all Umami alternatives → · See all Apache Superset alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — open-source — within Analytics. Apache Superset is currently shipping more aggressively (velocity 5.0 vs 3.8), 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. Apache Superset is currently shipping more aggressively (velocity 5.0 vs 3.8), 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 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.
Top Apache Superset alternatives in Analytics are ranked by recent ship velocity. Browse the "Apache Superset alternatives" section above for the current picks, or visit /alternatives/superset for the full list with editorial commentary on each.