GraphDB 11.4 Release Notes
16/06/2026
Important
GraphDB 11.4 introduces several major new features and critical bug fixes. A new Geo tab has been added to the SPARQL view in Workbench, which brings versatile and configurable map visualization capabilities for geographic data. Large Language Model capabilities have been improved with MCP prompts, which allow you to provide SPARQL templates to the MPC client for better accuracy when using LLM tools. On the security side, GraphDB now supports for encryption at repository level, managing the keys at the instance level. You can now also attach OAuth authentication flows to GraphDB (instead of to the fixed user/pass) through the newly exposed access to the AuthenticatingHttpRequestInterceptor in the GraphDBHTTPRepositoryManagerBuilder and GraphDBHTTPRepositoryBuilder. This allows the implementation of a custom interceptor which can attach custom information, including security information, to all request to GraphDB.
With the upcoming deprecation of OpenAI’s Assistants API, GraphDB now no longer supports Assistants API. The default LLM model used by GraphDB has been changed to the Completions API. Until the official deprecation of the Assistants API in August 2026, you will be able to migrate existing Talk to Your Graph agents and conversations that use the model to Completions-compatible agents and conversations. Check the Migrating GraphDB configurations page for more information on how to perform this conversion, as well as for details on the current versions of the external components and connectors.
Additionally, GraphDB 11.4 includes numerous other bug fixes and smaller improvements, enhancing overall product stability and user experience.
The development of the features in this release was partially funded by the EnrichMyData (GA nu: 101070284) Horizon Europe 
research project.
Visualize geospatially linked data using the Geo tab
You can now visualize explore SPARQL results that contain geographically linked data using the new Geo tab in the SPARQL view in the GraphDB Workbench. The Geo tab uses maps from OpenStreetMaps and OpenTopoMap. Results are rendered as points, lines or polygons, and can be styled through the SPARQL query itself using custom SPARQL properties.
Per-repository encryption
GraphDB now supports encryption at rest via a 256-bits master key on instance level and a Data Encryption Key (DEK) for each individual repository using AES-256-GCM. By separating DEKs per repository and maintaining an instance-level master key, the system achieves a secure, low-overhead encryption approach that is flexible.
MCP prompts for more accurate results when using LLM tools
You can improve the SPARQL generation by providing user-generated MCP prompts — pre-validated SPARQL templates with arguments that can be changed. The MCP prompts allow the LLM to write informed SPARQL queries instead of generating queries from scratch.