Graphwise appears on most semantic shortlists as one vendor. It is two products: GraphDB, the RDF database formerly sold as Ontotext, and PoolParty, the taxonomy and thesaurus manager that came with the Semantic Web Company side of the merger. Buying "Graphwise" means deciding which of the two you need, and usually discovering you need both.
That is the distinction this comparison turns on. Graphwise sells storage and editorial governance as separate products on separate licence tiers. TopQuadrant sells one governed layer, and the capabilities that make a model trustworthy are not an upgrade path.
Graphwise is a database plus a taxonomy tool. The governance capabilities sit in the second product, behind an enterprise tier, and one of them has a documented gap at deletion.
Graphwise is the merged entity behind two previously separate products, and the documentation still lives in two places.
So the architectural question is not "GraphDB or TopBraid EDG." It is whether you want the model and its governance in one place or in two products with a licence boundary between them.
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 problem is the shortlist that treats it as a governance platform because the word semantic appears in the name.
PoolParty is the strongest editorial governance in their stack and it is genuinely real. Changeset history at project and concept level, 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.
Two things qualify it, both from their own documentation.
That second one deserves weight in an evaluation. Removing a concept from an agreed model is the highest-risk edit available and it is the one edit the workflow does not gate.
| Capability | Graphwise | TopQuadrant |
|---|---|---|
| Model and governance in one product | No. GraphDB stores, PoolParty governs | Yes. One layer |
| Propose and approve as separate permissions | PoolParty only, Enterprise or paid add-on | Included |
| Approval recorded with author, date and comment | PoolParty only | Included |
| Deletion governed by approval | Documented as not covered | Governed like any other change |
| Shape constraints enableable after creation | No, SHACL is set at repository creation | Yes |
| Fine-grained access control | GraphDB Enterprise licence | Included |
| Open W3C standards throughout | Yes | Yes |
The last row matters and we are not claiming it as a differentiator. Both are built on RDF, OWL, SHACL and SPARQL, and that is the right foundation for both of us.
A comparison that answers "never" is marketing, so plainly.
If the primary job is storing and querying a large RDF estate at scale, GraphDB is a capable engine with a long track record and you should evaluate it on that basis. If the job is managing SKOS thesauri with a review step and your organisation is happy to buy at the Enterprise tier, PoolParty does that work and does it competently. Teams who need exactly those two things, and whose governance stops at concept approval, get a coherent answer from one vendor.
We built for the case where the agreement is the asset, and the store underneath it is an implementation detail.
TopBraid EDG holds the definitions, their relationships, their owners, their 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 concept is a change.
The practical difference shows up in an audit. When someone asks which definition was authoritative in March, who agreed it and what it replaced, the system answers it. Nobody has to remember who was in the room. For the wider argument see our knowledge graphs page, knowledge graph vs graph database for why storage and meaning are different jobs, and how to evaluate a knowledge graph platform for the checklist to run this against any vendor, including us.
Graphwise sells two products. TopQuadrant sells one. Test both claims against the documentation.