Neo4j vs Whatagraph
Side-by-side trajectory, velocity, and editorial themes.
neo4j-cli ships explicitly for AI agents — Neo4j makes its 'AX' bet concrete.
Neo4j is shipping in three lanes simultaneously: developer/agent surface (the new neo4j-cli covering Aura management, Cypher, and ops, designed for human, developer and agent consumption), Aura cloud capacity and ops (2TB high-memory GCP instances, inactive-member pruning, tighter password policy), and graph analytics maturation (project-level ML model persistence in AGA, Lakehouse export from Microsoft Fabric, Cypher 25 GQL features). Dashboards and Explore are gaining interactivity in parallel.
The arc is toward treating AI agents as a first-class user of the platform, not an integration consumer. Calling out 'AX' alongside DX/UX in the CLI announcement is unusual — most database vendors are still adding MCP servers or chat assistants. Coupled with the GenAI token functions in the April Aura release and AGA's model persistence, Neo4j is consolidating the 'graph as memory substrate for AI agents' position it's been telegraphing for two years.
Likely next: an MCP server fronting the same surface as neo4j-cli, deeper GenAI-native primitives in Cypher 25 (vector ops, embeddings as first-class types), and continued Aura capacity climbs to support larger graph-RAG workloads. Microsoft Fabric integration will probably extend further given the bidirectional Lakehouse work.
Whatagraph adds Data Storage and a Snowflake source — agency reports stop waiting on live API calls.
Whatagraph is moving from 'report builder over live API connections' to 'managed data layer plus report builder.' Two recent releases anchor the shift: Data Storage lets Whatagraph store customer data on its own infrastructure with a 24-month default backfill, and Snowflake has been added as a first-party data source so warehouse tables can sit alongside paid media and web analytics in the same report. Around that, the company is filling in standard reporting depth — GeoMap widget, conditional formatting, Gauge and Heatmap widget types — plus broader integration coverage like bol. Retailer and Advertising for Benelux retail media and a rebuilt event-level CallTrackingMetrics.
The product is pushing toward becoming an agency-grade marketing reporting platform that also owns the data plumbing. Historically agencies had to choose between Whatagraph-style report builders (fast but live-API constrained) and BigQuery-based stacks (flexible but heavyweight). Whatagraph's managed Storage destination collapses that choice, and the Snowflake source pulls customer-warehouse data directly into the reporting surface — both moves widen the addressable customer set into mid-market and larger agencies.
Expect the next quarter to deepen the data layer: a SQL-style transformation interface on stored data, more warehouse sources (likely Databricks or Redshift), and a billing change that splits the storage layer from the report-builder seat licenses. The GeoMap widget will exit beta with continent-grouped drill-downs.
See more alternatives to Neo4j →
See more alternatives to Whatagraph →