OpenObserve
OpenObserve is shipping a 0.91 patch every few days while 0.92 stabilises alongside it
A side-by-side editorial comparison of Neo4j and Whatagraph — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Neo4j | Whatagraph |
|---|---|---|
| Sector | Analytics | Analytics |
| Velocity score | 7.5 | 5.0 |
| Sparks · 30d | 2 | 0 |
| Top themes | graph-database, agent-native, mcp, genai | agency-reporting, data-integrations, warehouse-sources, report-readability |
| Last editorial update | 7d ago | 18h ago |
| Website | — | — |
Neo4j is turning Aura into an agent-native graph platform, MCP and all.
Neo4j Aura's changelog reads as a two-front push: agent-native access (a hosted MCP endpoint, a self-validating Cypher Copilot, conversational document-to-graph modeling) and enterprise self-service (SSO, user-management APIs, one-click Community-to-Aura migration). The core database keeps shipping too — Cypher 25's DISJOINT BY, GA graph types, filtered and higher-fidelity vector search — but the platform layer is where the energy is.
Whatagraph is building a data layer under the reports — storing data instead of fetching it live.
Whatagraph ships in two registers. The visible one is report readability: automated conditional formatting with a single base color, clearer charts and tables, faster template search, and a themes panel consolidated into one place. The less visible one is architectural — the Basis integration was rebuilt to store data rather than load it live from the API each time a report opens, which fixed slow widgets and dropped connections and aligned reported spend with Basis billing totals. Integration breadth continues in parallel with Ahrefs Rank Tracker, WhatConverts, and Snowflake.
Neo4j Aura's changelog reads as a two-front push: agent-native access (a hosted MCP endpoint, a self-validating Cypher Copilot, conversational document-to-graph modeling) and enterprise self-service (SSO, user-management APIs, one-click Community-to-Aura migration). The core database keeps shipping too — Cypher 25's DISJOINT BY, GA graph types, filtered and higher-fidelity vector search — but the platform layer is where the energy is.
The direction is consistent: make the graph reachable by AI agents without setup, and make Aura the default destination for self-managed users. MCP, Document Intelligence, and guided Community-Edition migration all lower the friction between an LLM (or a self-hosted database) and a managed Aura graph.
Expect the previews to harden into GA — Document Intelligence and Hi-Fidelity Quantized vector search — and MCP for Aura to expand past its three starter tools toward write-heavy agent workflows and the promised VDC support.
Whatagraph ships in two registers. The visible one is report readability: automated conditional formatting with a single base color, clearer charts and tables, faster template search, and a themes panel consolidated into one place. The less visible one is architectural — the Basis integration was rebuilt to store data rather than load it live from the API each time a report opens, which fixed slow widgets and dropped connections and aligned reported spend with Basis billing totals. Integration breadth continues in parallel with Ahrefs Rank Tracker, WhatConverts, and Snowflake.
The storage-first rebuild is the pattern worth watching. Whatagraph's original model — pull from every vendor API when a client opens a report — is what makes agency reporting slow and fragile, and the company is steadily replacing it with pre-synced data it holds itself. Snowflake as a source points the same way: first-party and offline data joining paid media inside the report. The polish items are real but downstream of that; readable charts matter more once the numbers load reliably and reconcile with the platform's own billing.
The Basis rebuild reads as a template rather than a one-off, so other live-API integrations with the same slowness and drop problems are the likely next candidates for storage-backed rewrites and per-client source structure.
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 Neo4j or Whatagraph.
OpenObserve is shipping a 0.91 patch every few days while 0.92 stabilises alongside it
Dagster is spending this cycle on scale problems in the UI and correctness in asset state
A weekly three-platform release train where offline computer vision is the only real bet.
Usermaven is outgrowing the pixel — CRM and payment conversions now count as native events.
Chord's changelog has become a Chord AI changelog — the CDP is being answered by a conversation.
AgencyAnalytics is selling AI search visibility as a metered add-on, not a feature.
See all Neo4j alternatives → · See all Whatagraph alternatives →
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 7.5 vs 5.0), with 2 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 7.5 vs 5.0), with 2 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 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.
Top Whatagraph alternatives in Analytics are ranked by recent ship velocity. Browse the "Whatagraph alternatives" section above for the current picks, or visit /alternatives/whatagraph for the full list with editorial commentary on each.