An international standard query language for property graph databases, developed by ISO/IEC to provide a declarative way to query and manipulate graph data structures. Effective implementation supports data-driven strategies and helps maintain data integrity across systems.
Graph Query Language (GQL)
Graph Query Language (GQL) is the ISO/IEC 39075 international standard for querying and manipulating property graph databases, published in 2024 after years of work by the same standards committee responsible for SQL. It gives graph data the kind of vendor-neutral, declarative query language that SQL long ago gave relational data, so that traversals, pattern matches, and mutations against nodes and edges are expressed in a portable, standardized syntax rather than a database-specific dialect.
- A first-class ISO standard - GQL is a full sibling to SQL under ISO/IEC JTC 1/SC 32, not a vendor specification or a community draft.
- Property-graph model - It operates over nodes, relationships, and their properties, the model most graph databases already use in practice.
- Declarative pattern matching - Visual, ASCII-art-style patterns describe the shape of the graph you want to match, borrowing heavily from the ideas Cypher popularized.
- Portability across engines - A standard language means queries and skills move between conforming databases instead of locking teams into one vendor.
In real API operations GQL matters most where a graph database sits behind a data API and teams want their query logic to survive a change of engine. It is the graph counterpart to how GraphQL standardized client-driven fetching and how Gremlin offered a traversal language before an ISO standard existed, and its arrival gives governance and procurement a stable specification to reference when evaluating graph-backed services. As agents increasingly reason over connected data, a standardized graph query language is a cleaner surface to expose and audit than a proprietary one.
