openCypher is an open-source project that provides a standardized graph query language originally developed by Neo4j for querying property graphs. It enables developers to write expressive pattern-matching queries against graph databases, and its specification has been adopted by multiple graph database vendors.
openCypher
openCypher is the open specification of Cypher, the declarative, pattern-matching query language originally created by Neo4j for property graphs. Where SQL asks about rows and joins, Cypher asks about nodes and the relationships between them using an ASCII-art syntax like (a)-[:KNOWS]->(b). Opening the language up let other graph database vendors implement the same query surface instead of inventing yet another dialect.
- Property-graph model - Queries operate over nodes, relationships, and properties, matching the way graph databases actually store connected data.
- Pattern-matching syntax - Visual
MATCHpatterns describe the shape of the data you want, rather than the procedural steps to fetch it. - Multi-vendor adoption - Beyond Neo4j, engines such as Amazon Neptune, Memgraph, and RedisGraph have implemented openCypher, giving the language reach across the ecosystem.
- Path to GQL - openCypher’s design fed directly into GQL, the ISO-standard graph query language, making it the practical bridge to a formal standard.
In real API operations, openCypher shows up wherever a graph database sits behind an API — recommendation engines, fraud-detection graphs, knowledge graphs, and identity graphs all expose Cypher-driven endpoints. For anyone building or governing these APIs, a shared query language means query logic, tooling, and developer skills carry across vendors instead of locking a team into one engine. As knowledge graphs increasingly back agentic retrieval, a standardized graph query surface like openCypher becomes a predictable, machine-writable way for agents to traverse connected data.
