Neo4j vs Hex
Side-by-side trajectory, velocity, and editorial themes.
Neo4j bends Aura toward GenAI: unstructured docs in, queryable graphs out
Neo4j's changelog is almost entirely Aura, its managed cloud. The last month layers two things onto the graph core at once: GenAI-facing ingestion (document-to-graph, vector datatypes, natural-language query) and enterprise plumbing (user-management APIs, project lifecycle, engine concurrency fixes).
The clear direction is lowering the barrier to graph adoption for AI builders — turning PDFs and DOCX into a modeled graph and letting users query in plain language rather than Cypher. In parallel, the Aura API is maturing into something DevOps and IAM teams can automate against, which is the groundwork for larger enterprise footprints.
Expect Document Intelligence to move from preview toward general availability and to tie more tightly to the vector/embedding import path, positioning Aura as a retrieval backend for GenAI apps.
Hex is remaking its notebook into an agent that both uses and plugs into MCP
Hex is converting its analytics notebook into an AI agent platform. It now runs as an MCP client, is invocable from Codex, and ships generative data apps built from prompts, while keeping its model roster current with Kimi K2.7 and Fable 5 and giving admins default-model and branding controls. Integration and governance work — a Figma connector, AWS IAM-role support, signed embedding — rounds out the core.
The arc points at Hex as connective agent infrastructure: consuming external context and tools via MCP, distributing itself into other agent surfaces like Codex, and letting analysts assemble apps and dashboards from prompts. Expect the agent, rather than the notebook grid, to become the primary interface, with model choice and governance layered on top.
Likely next steps deepen the agent's tool-use over MCP connections and push generative apps further toward production embedding and governance controls.
See more alternatives to Neo4j →
See more alternatives to Hex →