Holistics vs Neo4j
Side-by-side trajectory, velocity, and editorial themes.
Holistics turns the BI dashboard into a conversational AI surface, on customer-owned models.
Holistics is well into a BI-meets-AI productization phase, layering conversational analytics on top of its existing modeling and dashboard core. Recent releases mix consumer-grade dashboard polish (auto-run filters, K/M/B number formatting, percentile calculations) with deeper AI plumbing: bring-your-own Claude and Gemini keys, per-user AI access controls, and now an Ask AI that asks clarifying questions back. The GitHub App integration also signals enterprise-readiness work alongside the AI push.
The product is being repositioned from a self-service BI tool to an AI-mediated analytics workspace where natural-language exploration is the headline interaction. Crucially, the team is pushing AI as an infrastructure layer customers can own — BYO LLM keys, granular access policies — rather than locking customers into a vendor-managed model. The dashboard improvements look incremental, but read as ground prep for AI agents to consume and manipulate dashboards more reliably.
Expect the next quarter to bring agentic dashboard editing — Ask AI not just answering but proposing dashboards and saving them — plus expanded BYO LLM coverage (likely Azure OpenAI or open-weights via OpenRouter) to widen procurement options for enterprise buyers.
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.
See more alternatives to Holistics →
See more alternatives to Neo4j →