Decide what the graph is for before you look at a single product. Evaluations in this market go wrong early, and almost always the same way. A shortlist gets assembled from search results. The products turn out to be in different categories. The feature grid that follows compares things that were never trying to do the same job.
So the evaluation has two halves. Establish the category, then test the two or three things that are hard to change later. Everything else is detail that a trial will settle on its own.
Six product categories share this vocabulary, and a product page rarely settles which one you are looking at.
| If the problem is | The category is |
|---|---|
| Disagreement about what terms mean | Ontology and taxonomy management |
| Querying connected data at volume | A graph database, RDF or property depending on portability needs |
| Finding and tracking existing assets | Data catalogue |
| Consistent metrics across BI | Metrics semantic layer |
Most organizations eventually need more than one, and the failure is buying from one category expecting coverage of another. Knowledge graph vs data catalog covers the most common of those collisions, and knowledge graph vs graph database covers the other.
Four things, in descending order of how expensive they are to get wrong.
Notice what is absent: scale. Vendor benchmarks run to billions of statements and most governed models are orders of magnitude smaller. Almost every product in the category will handle your volume, so scale claims rarely separate anybody.
Demos run on data chosen because it works, and the three things that decide the next five years are all invisible in one.
Whether your model fits the product's assumptions. Many tools assume a single parent per concept, and your domain will eventually disagree. Load your own vocabulary and find out in week one.
What the export actually contains. Every product claims export. The question is whether constraints, alternative labels and provenance survive it, and the only way to know is to diff.
How fast approval really moves. A workflow that looks clean in a demo can take a fortnight in practice once real approvers are involved. Latency is a governance property and it is the thing that determines whether people route around the system.
More people than usually are, and the missing ones are predictable.
That last gap is worth taking seriously. An evaluation with no named future owner tends to optimise for the purchase instead of the operation. The product that wins is the one that demos best.
Four to six weeks from shortlist to decision, and longer than that is a signal rather than diligence.
Evaluations that run six months are rarely more rigorous. They are usually stalled on a decision nobody is empowered to make, and extending the trial is how that gets disguised as process. If the timebox slips twice, the thing to fix is the decision right and not the testing.
How should you score it?Weight the four tests heavily and almost everything else at zero.
Feature grids in this category run to a hundred rows, and ninety of them are satisfied by every serious product. Scoring them equally produces a total that looks rigorous and moves with whoever wrote the grid. A short weighted list is both more honest and harder to argue with.
Record why each score was given, with evidence from the trial instead of from the vendor's documentation. When somebody asks in two years why this product was chosen, the answer should be reconstructable. Questions to ask before buying covers the checklist version, and knowledge graph ROI covers measuring whether it worked, and knowledge graph tools maps the categories your shortlist is drawn from.
Establish the category first, then test portability, governance depth, query-time resolution and expert usability on your own model. Ignore scale claims. Ignore feature counts.
TopQuadrant sits in the ontology and taxonomy management category, so we are one option and not the whole shortlist. The honest version of our position is narrow: we built for the agreement and the record of who made it, on open standards, so the model can leave. Test that the same way you test everyone else. Export, diff, re-import. Our knowledge graph platform should survive that test, and if it does not we would rather you found out in a trial.