How to Build a Temporal Knowledge Graph with Graphiti
Graphiti builds knowledge graphs that track how facts change over time, so your AI agent knows what is still true. Here is how to install…
Graph database that turns messy relationships into a queryable knowledge graph
Neo4j is a graph database that stores data as nodes and relationships and queries them with Cypher. It runs on-premise or as AuraDB in the cloud, and now ships vector indexes for combining graph traversal with embeddings.
Neo4j started in 2007 and is the de facto graph database. Instead of tables and joins, you write (:Person)-[:BOUGHT]->(:Product) patterns. Traversals that would need five recursive joins in SQL run as one hop.
The 2025 releases (Neo4j 2025.x and Aura) added vector indexes plus the GraphRAG Python package, aimed at teams building retrieval over connected documents rather than isolated chunks.
Accept the modelling cost and the payoff is real. A fraud ring, a supply chain or a recommendation graph becomes something a product manager can read as a diagram. Query plans show you exactly which hops fire.
Pricing: Aura Free at no cost; Aura Professional from $65 per month for 4 GB RAM and 8 GB storage. Enterprise and on-prem licensing is quoted per core and usually starts in five figures per year.
Honest downsides: writes are slower than Postgres for bulk inserts, the community edition lacks clustering, and hiring people who can model graphs well is harder than hiring SQL developers. If your data has no meaningful relationships, a relational database will be simpler and cheaper.
Good fit: fraud detection, master data management, recommendation engines, and GraphRAG projects where relationships carry the meaning. Bad fit: straightforward CRUD apps or analytics over flat event tables — that is Postgres or ClickHouse.