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 Neo4j — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Umami | Neo4j |
|---|---|---|
| Sector | Analytics | Analytics |
| Velocity score | 3.8 | 6.3 |
| Sparks · 30d | 0 | 0 |
| Top themes | product-analytics, session-replay, custom-dashboards, web-vitals | graph-database, aura-cloud, billing, graph-analytics |
| Last editorial update | 1mo ago | 17d ago |
| Website | Visit → | — |
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.
Neo4j Aura pushes on billing transparency, scale ceilings, and graph analytics.
Neo4j's Aura cloud is shipping across three fronts: a new self-service billing experience and Billing API, higher scale ceilings (5TB storage on AWS, 2TB high-memory on GCP), and graph-analytics depth (Native Projections, ML model persistence). The monthly Aura release rolls these up with Cypher 25 GQL compliance work.
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.
Neo4j's Aura cloud is shipping across three fronts: a new self-service billing experience and Billing API, higher scale ceilings (5TB storage on AWS, 2TB high-memory on GCP), and graph-analytics depth (Native Projections, ML model persistence). The monthly Aura release rolls these up with Cypher 25 GQL compliance work.
Aura is maturing as an enterprise managed service — financial controls, larger instances, and operational hygiene (user pruning) — while continuing to invest in the graph-data-science layer that differentiates it.
Expect continued enterprise-readiness work (billing, scale, governance) alongside GDS and GQL-compliance progress; a unified neo4j-cli also suggests more developer-CLI investment ahead.
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 Neo4j.
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
Superset's public feed is all Helm-chart packaging — the 6.x product work sits behind release votes
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Neo4j is currently shipping more aggressively (velocity 6.3 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. Neo4j is currently shipping more aggressively (velocity 6.3 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 Neo4j alternatives in Analytics are ranked by recent ship velocity. Browse the "Neo4j alternatives" section above for the current picks, or visit /alternatives/neo4j for the full list with editorial commentary on each.