A knowledge graph database is the storage and query engine underneath a knowledge graph. It holds the nodes, edges and statements, answers queries over them, and in some cases runs inference across them. It is infrastructure, and the phrase describes a middle tier that neither "graph database" nor "knowledge graph" quite captures.
The distinction matters because three things get called the same thing. A graph database stores connected data. A knowledge graph is the modelled, governed meaning. A knowledge graph database sits between them: a store built specifically for the kinds of statements a knowledge graph makes, including identity that survives leaving the database and semantics a machine can reason over.
Naming them separately is the quickest way to stop talking past each other in an evaluation.
| Tier | What it is | What it does not do |
|---|---|---|
| Graph database | Storage and traversal over nodes and edges | Carry portable identity or machine-readable semantics |
| Knowledge graph database | A store built for standards-based statements, with global identifiers and often a reasoner | Decide what anything means or who agreed it |
| Knowledge graph | The modelled, governed meaning itself | Store itself. It needs one of the tiers below |
Most market confusion comes from products in tier one describing themselves in tier three language. The knowledge graph vs graph database piece works through that specific collision, and types of graphs maps where each sits.
Five capabilities, and the last one is the one buyers most often leave off the list.
The last one is quietly important and often missing. Without it, a statement you asserted and a statement a reasoner derived look identical, and you cannot audit how a conclusion was reached.
For a knowledge graph database in the sense above, in practice yes, and the reason is identity rather than ideology.
The properties that distinguish this tier are global identity, standards-based semantics and declarative constraints. RDF, OWL and SHACL were designed to carry exactly those. A property-graph store can be made to approximate them, and the approximation lives in application code. That is the condition that makes a model impossible to govern.
RDF vs property graphs covers that trade in detail. The short version: property graphs are often faster to start with and the identity gap compounds.
Smaller than the market implies, and that changes which products are worth considering.
Vendor benchmarks run to billions of statements, and most enterprise knowledge graphs holding governed meaning are orders of magnitude below that. A vocabulary of ten thousand concepts with their relationships, constraints and provenance is a substantial governed asset and a trivial database workload.
The exception is when the same store is also holding operational data at volume. That is a legitimate architecture and it changes the sizing conversation entirely, because you are then buying for the analytical workload and the governed model is a passenger.
What will it not do for you?Decide anything. This is the part buyers consistently expect and never get.
A knowledge graph database will store your model, validate data against the rules you declare, and answer queries quickly. It will not tell you what "active customer" means, who gets to change that, or which definition applies in which part of the business. Those are governance questions, and no storage engine answers them.
The practical consequence is that buying this tier solves the infrastructure problem and leaves the problem that probably prompted the search. Teams that buy a knowledge graph database expecting the governance to arrive with it spend a year discovering it did not. Ontology management covers the layer that does.
Mostly on the things that are hard to change later.
Performance dominates these conversations and is usually the least decisive factor, because most enterprise knowledge graphs are far smaller than the vendor benchmarks and the queries are shaped differently. The thing that decides the next five years is whether the model can leave. How to evaluate a knowledge graph platform covers the wider process.
A knowledge graph database is the middle tier: a store built for standards-based statements with global identity and machine-readable semantics. It is necessary infrastructure and it settles nothing about meaning.
TopQuadrant builds above this tier. Our knowledge graph platform is where the model gets defined with the experts who own it, validated against declared constraints, and made resolvable to the systems that need an answer. The store underneath can be whatever your architecture already runs, provided the model can leave it. Test that with an export and a diff, on your own model.