Home / Companies / WorkOS / Blog / Post Details
Content Deep Dive

Philip Rathle on why AI agents keep reaching for a knowledge graph

Blog post from WorkOS

Post Details
Company
Date Published
Author
Noelle Festa
Word Count
1,447
Company Posts That Month
32
Language
English
Hacker News Points
-
Post removed?
No
Summary

Neo4j CTO Philip Rathle argues that the company’s growing role is as an AI knowledge layer rather than solely a graph database, with more than 70% of its new business reportedly tied to AI use cases. In a discussion with WorkOS CEO Michael Grinich at the AI Engineer World’s Fair 2026, Rathle emphasized that AI models require access to an organization’s proprietary, structured context to make reliable decisions, particularly in regulated, safety-critical, or reputationally sensitive situations where deterministic answers, explainability, and access controls are essential. He described knowledge graphs as a way to reconcile fragmented enterprise data without large-scale migrations, connecting duplicate representations of entities across systems to provide agents with broader context. Rathle positioned GraphRAG as an evolution beyond vector search, combining semantic retrieval with explicit, inspectable relationships and graph querying. He also noted that multi-agent systems can compound errors, making deterministic graph-based steps, agent orchestration, and selective graph calls important design considerations. Internally, Neo4j has applied agents to software troubleshooting and engineer onboarding, supported by strong code quality, extensive testing, and strict security practices, reinforcing the broader view that structured organizational knowledge—not models alone—is central to dependable autonomous AI.

Trends Found in this Post
Trend Post Mentions Total Month Mentions Posts Companies MoM
LLM 3 1,189 251 109 -83%
Vector Search 3 525 92 52 -74%
AI Agents 1 1,180 266 113 -80%
Multi-agent systems 1 101 30 20 -80%
Use This Data

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.