Graph stores can be divided in property graphs, triples stores and hybrid (or exotic) systems. Each flavor has its pros and cons, all depends on your business context and what you wish to achieve. One could also separate graph stores in function of basic and enterprise features. In contrast with the relational stores there is indeed a much broader spectrum of ‘quality’. Things like encryption, clustering, high-availability and such do not show up in all systems. The triple world, in particular, can be more academic than enterprise minded. This is also reflected in prices and licensing.
As such, picking the right solution for your project can be a challenge on its own. The diversity and incoherence can be overwhelming. We have gone through this process over the years time and again, if you need guidance we’re here to help.
We have worked with and developed on top of many graph stores (both open and closed source) and have experience with pretty much all of the query API’s: SPARQL, Cypher, Gremlin as well as proprietary query languages like Graql. All of these languages have their own strength and scope, we always try to adopt the product and API which suits your (business) aims best.
Most of the graph stores are equivalent from a development point of view since 90% of the stores implement one the three main query interfaces; Cypher, SPARQL or Gremlin. Only a handful of products implement a custom language, like GRAKN.AI.
We offer complementary technology solutions and services on top of diverse system but have a special partnership with Linkurious, Neo4j, TigerGraph and Cosmos DB.