AI & context
6 min

Graphwise vs. TopQuadrant

Key takeaways

  • Graphwise is two products: GraphDB for storage and query, PoolParty for editorial governance. Most buyers need both.
  • GraphDB documents its custom roles as markers carrying no inherent rights, and fine-grained access control requires an Enterprise licence.
  • SHACL validation can only be enabled when a repository is created, so governability is a decision made before the model exists.
  • PoolParty's approval workflow is real and sits at Enterprise Server level or as a paid add-on. Its own documentation records that deletion is not covered by approval.
  • TopQuadrant holds the model and its governance in one layer, with deletion governed on the same terms as any other change.
In this article
Share

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.

What is Graphwise, and what are you actually buying?

Graphwise is the merged entity behind two previously separate products, and the documentation still lives in two places.

The two halves

  • GraphDB. An RDF triplestore, described by its own documentation as a "Semantic Graph Database", compliant with RDF 1.1 and SPARQL 1.1. It stores and queries. That is an accurate description and it is worth taking at face value.
  • PoolParty. A taxonomy and thesaurus manager with changeset history and a four-state approval workflow moving concepts through Draft, Suggested, Approved and Deprecated. This is where editorial governance lives in their stack.

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.

What governance does the database itself provide?

Less than the word "semantic" in the product name suggests, and their documentation is candid about it.

Three constraints documented by GraphDB itself

  • Custom roles carry no rights. Their documentation states that custom roles "have no inherent rights or restrictions associated with them, and are instead just markers that can be freely granted to any number of users." A marker on a user is not a control on an action.
  • Shape validation is a decision you make before you have a model. "SHACL support in a given repository must be enabled when that repository is created. You cannot modify an already existing repository by enabling the validation afterwards." Get that wrong on day one and the repository cannot be governed later.
  • Fine-grained access control is licensed separately. "This feature requires a GraphDB Enterprise license."

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.

What does PoolParty add, and what does it cost?

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.

Two documented limits

  • The workflow is an edition gate. "The approval workflow functionality is only available from PoolParty Enterprise Server level. It is available as an additional module for PoolParty Advanced Server." The capability that makes the product governable is not in the product you were first quoted.
  • Approval does not cover deletion. "Deletion of concepts are not covered by an approval process at the moment. This means a deleted concept can not be rejected to bring back a deleted concept." An approved taxonomy can lose a concept with no review and no way to reverse the loss.

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.

How do the two compare on the capabilities that matter?

CapabilityGraphwiseTopQuadrant
Model and governance in one productNo. GraphDB stores, PoolParty governsYes. One layer
Propose and approve as separate permissionsPoolParty only, Enterprise or paid add-onIncluded
Approval recorded with author, date and commentPoolParty onlyIncluded
Deletion governed by approvalDocumented as not coveredGoverned like any other change
Shape constraints enableable after creationNo, SHACL is set at repository creationYes
Fine-grained access controlGraphDB Enterprise licenceIncluded
Open W3C standards throughoutYesYes

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.

When is Graphwise the right choice?

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.

Where does TopQuadrant fit?

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.

Give your AI the context it's been missing

See how the TQ Data Foundation turns your enterprise knowledge into trusted, Al-ready context.