A taxonomy shortlist that contains Stardog, GraphDB and TopQuadrant is comparing three different product shapes against one requirement. Two of them are databases that can hold a vocabulary. One of them is a layer built to govern it. The demo will not make that obvious, because all three can show you a hierarchy of terms on a screen within ten minutes.
The separation matters once the vocabulary has more than one owner. This comparison runs the three against the capabilities that decide whether an agreed term stays agreed, and every claim below is taken from the vendor's own published documentation so you can check every one of them.
Stardog and GraphDB are RDF databases with real strengths. Neither documents an approval step that requires a second person before a model change takes effect, and that is the capability a governed taxonomy is built on.
Three products with three different jobs, which is why a feature grid laid flat across them misleads.
One note on scope before the comparison. Graphwise also sells PoolParty, which is a genuine taxonomy manager and is a much closer comparison to us than GraphDB is. It gets its own section below, because leaving it out would make this page easy to dismiss.
Access control on where the model is written, and little above that level.
SetOption, glossed "Sets a database's configuration option (metadata).", plus DataAdd, DataRemoveContext, UserPermissionGrant and RolePermissionRevoke. The published table contains no approval event type, because there is no approval step to record.This one is widely misreported and the precise version is more useful than the loose one.
Stardog 10 introduced schema versioning: with reasoning.schema.versioning.enabled set to true, "Stardog will automatically compute a 64-bit hash from the contents of the reasoning schema graphs." The documented operation is checking the current hash to determine whether the schema has changed. It tells you that something moved. It does not tell you what moved, who moved it, or what it said before.
Pinning does exist, and it is worth being accurate about. Schema multi-tenancy lets a query bind to a named schema, and Stardog's own motivating example is version pinning: "There are two different versions of a schema that evolved over time. Older legacy applications need to use the previous version of the schema, whereas the newer applications need to use the newer version." The qualification is that you maintain the old version yourself as separate named graphs. Nothing captures a prior version for you, and it is unconnected to the versioning hash.
Separately, Stardog 7.2.1 published a versioning API, com.complexible.stardog.api.versioning, with history navigation. That package is absent from the Stardog 12.2.1 package list and class index. We cannot say when it went, only that it is in the one and not the other.
Less than the word semantic in the product name suggests, and their documentation is candid about it.
None of this makes GraphDB a poor database. It makes it a database, which is what it says it is. The error is the shortlist that treats it as a taxonomy governance platform.
PoolParty is the strongest editorial governance of anything on this page other than us, and pretending otherwise would be dishonest.
It has changeset history at project and concept level, a four-state workflow moving concepts through Draft, Suggested, Approved and Deprecated, a workflow audit that records state, assignee, comment and date, and a propose-versus-approve split expressed as two distinct permissions, Workflow Assign and Workflow Actions. If you are managing SKOS thesauri and you need a review step, it does that work competently.
Two things qualify it, both from their own documentation.
That second point deserves weight. Removing a term from an agreed vocabulary is the highest-risk edit available, and it is the one edit the workflow does not gate.
Scored against what a governed taxonomy needs. A flat feature list would compare different things.
| Capability | Stardog | GraphDB | TopQuadrant |
|---|---|---|---|
| Model authoring in the product | Yes, via Designer | No, it is a store | Yes |
| Change history on a definition | Export to external version control is the documented path | None published | Included |
| Retrieve what a term meant on a past date | No documented retrieval of a historical version | No | Included |
| Propose and approve as separate permissions | Not in the action list | Custom roles are markers only | Included |
| Approval recorded with author, date and comment | No approval event type in the audit log | None published | Included |
| Deletion governed by approval | No approval step to apply | No | Governed like any other change |
| Model hidden from unauthorised readers | Schema axioms readable regardless of named-graph permissions | Fine-grained access control is an Enterprise licence | Included |
| Open W3C standards throughout | Yes | Yes | Yes |
The last row is not a differentiator and we are not claiming it as one. All three are built on RDF and SPARQL, and that is the right foundation for all three.
A comparison that answers "never" is marketing, so plainly.
If the job is storing and querying a large RDF estate at scale, both are capable engines with real track records, and you should evaluate them on that basis. This page is the wrong place for it. Stardog's reasoning and virtual graph capabilities are genuinely strong, and if your requirement is query-time inference across federated sources it belongs on the list. GraphDB has a long operational history and a large installed base. Teams whose vocabulary has one owner, whose model changes rarely, and who do not need to answer audit questions about it, will find either sufficient and should not pay for more.
One argument of theirs deserves a straight answer, so here it is. Stardog runs a portability case of its own, positioning against being locked into a proprietary engine. That argument is sound and it is not ours alone. Standards-based storage is a real advantage they have over property graph vendors, and our claim is not that they lack portability. It is that portability of storage and governance of meaning are different problems.
We built for the case where the agreement is the asset and the store underneath it is an implementation detail.
TopQuadrant holds the terms, their hierarchy, their mappings, their owners and scope, the record of who approved each change and what it replaced, and the version a downstream system is reading. Those capabilities ship in the product. No tier gates them. Deletion is governed on the same terms as any other change, because removing a term is a change.
The difference shows up in an audit. A demo will not surface it. When someone asks which definition was authoritative in March, who agreed it, and what it replaced, the system answers. Nobody has to remember who was in the room. For the category argument see taxonomy management, taxonomy governance for how a review process is actually run, and taxonomy and ontology platforms compared for the same evaluation applied across a wider field.
Every claim on this page is quoted from published documentation. Run the same test against TopQuadrant. We would rather be checked than believed.