Narrower than the shortlist you will be handed. Taxonomy management software authors and governs a controlled vocabulary: it holds the terms, their labels, their hierarchy and their mappings, and it records who agreed each one and when.
That is a specific job, and most products that appear in a search for it are built for an adjacent one. A graph database stores the vocabulary and does not govern it. A data catalogue describes assets that already exist and does not author the terms. Both are useful. Neither is this.
So the first move in any evaluation is to establish which category each shortlisted product is actually in. A feature grid laid across categories compares things that were never trying to do the same thing.
Six categories share the vocabulary of this market. The table below is from our own category research dated 2026-10-27, and taxonomy and ontology platforms compared works through it in detail.
| Category | What it is built to do | Representative products |
|---|---|---|
| Taxonomy and ontology management | Author and govern agreed meaning, with versioning and a review trail | TQ Data Foundation, PoolParty, Synaptica |
| RDF database / triplestore | Store triples, answer SPARQL, run reasoning | GraphDB (Graphwise), Virtuoso, Amazon Neptune |
| Property-graph database | Graph storage on a non-RDF model | Neo4j, TigerGraph |
| Knowledge graph platform | Virtualise data where it lives and add semantic context | Stardog, Anzo |
| Data catalogue | Discovery, lineage and policy over existing assets | Collibra, Alation, Atlan |
| Metrics semantic layer | Consistent metric definitions for BI | dbt, Cube, AtScale |
One note on naming, because it trips up shortlists: Ontotext's GraphDB product pages now redirect to Graphwise, so a comparison written against "Ontotext" is naming a brand in transition. Write GraphDB.
Eight things, and only the first three are where products in this category genuinely differ.
Governance depth and export fidelity are the two that separate products that look identical in a demo. Everything else is table stakes or is easy to verify.
With your own vocabulary, in a trial, in an afternoon. Demos are built on data chosen to work.
The historical question is the one that most often fails and the one buyers most often forget to ask. A product can have versioning, an audit log and an approvals feature and still fail this. The three are stored separately, and nothing joins them.
Four questions, in this order.
| If the problem is... | You need |
|---|---|
| Disagreement about what terms mean | Taxonomy and ontology management |
| Finding and tracking existing data assets | Data catalogue |
| Querying connected data at scale | A graph database, RDF or property depending on portability needs |
| Consistent metrics in BI | Metrics semantic layer |
Most organizations eventually need more than one, and the mistake is buying a product from one category expecting it to cover another. A catalogue with a business glossary is genuinely useful and does not govern a vocabulary. A graph database with an ontology editor bolted on stores the model and does not run the approval.
Three costs, and the first two are usually booked somewhere other than the taxonomy budget.
The third is the expensive one now that retrieval systems read the vocabulary directly. A buyer evaluating on editor features and ignoring query-time resolution is optimising for the people who maintain the taxonomy over the systems that consume it, and the consumers now outnumber the maintainers by orders of magnitude.
What this comparison deliberately does not doIt does not score the named products against each other.
Our standard is that every claim about a named vendor is sourced to that vendor's own published documentation, dated and quoted as what they publish. The category placements above meet that standard and come from research dated 2026-10-27. A per-product scoring table against the eight criteria does not exist yet, because it requires re-reading each vendor's current documentation and that has not been done.
A scored grid assembled from memory or from last year's reading would look more useful and be worth less. We will publish one when it is sourced.
Decide the category before you compare products, score on governance depth and export fidelity, and test both with your own vocabulary instead of accepting a demo.
TopQuadrant builds in the taxonomy and ontology management category, which means we are one of the options and not the whole list. The honest version of our pitch is narrow. We built for the agreement and the record of who made it, on open standards. The vocabulary and its history can leave if you decide to go elsewhere. Test that claim the same way you test everyone else's. Run the round trip. Taxonomy management covers the discipline the tooling is meant to serve.