Announcing Ontology Support, Improved Data Model Visualization, Entra ID auth Support & More [v3.51.108 Release Notes]

It’s time to kick off 2026 in style with the first G.V() release of the year featuring more user experience improvements and some exciting new features. 

Here’s what’s waiting for you in this release of G.V():

• G.V() now supports Entra ID authentication for Apache AGE on Azure Database for PostgreSQL
• A brand-new design for our graph data model visualization tool
• A first step towards ontology support for RDF, allowing you to extract the ontology from your triplestore

Let’s check it out!

A Shiny New Graph Data Model View

As the G.V() team is working towards building more complex data model visualization (and curation) tools, we needed a better engine to handle the task.

In today’s release, relationships between nodes are now displayed with far less overlap, and edge routing improves readability, particularly on complex data models. Interacting with elements on the view now helps provide you with more clarity on how they connect as well.

Extracting Ontologies Directly from Your Triplestore

G.V() continues to expand support for RDF use cases, and this month’s focus has been on ontologies.

In today’s release, G.V() now loads RDFS/OWL ontology statements directly from your triplestore that you can then explore interactively (using the improved graph data model view covered above!). This is the first step of a series of new features that will progressively make G.V() more ontology aware.

As a quick example, here’s a (truncated) display of the HOBBIT Ontology on G.V():

So what’s in store for the future of RDF support in G.V()? Expect more on that in February, but here’s a look at the horizon:

• New graph data model views to quickly visualize class hierarchies, disjointedness and other ontology-defined facts
• Ontology-aware SPARQL query autocomplete
• Ontology-backed data validation

Until then, let us know what you think of today’s new ontology support features.

Microsoft Entra ID Authentication Support for Apache AGE

Did you know the Azure supports a fully managed Apache AGE service on Azure Database for PostgresSQL? Well, they do!

In the previous release last December, G.V() introduced support for Apache AGE (“A Graph Extension”). Apache AGE is tightly integrated on Azure with full support for Entra ID, allowing you to authenticate using secure, temporary credentials.

You can now easily configure G.V() to fetch temporary Entra ID credentials via the Azure CLI when connecting to your Azure-hosted Apache AGE graph database. Simply run az login , and you’re good to go! G.V() also supports advanced configuration options such as using managed identities or authenticating against a specific Azure tenant.

Conclusion

While this month’s release isn’t stuffed full of new features, it marks a number of important directions of where the product is headed next. 

We want to continually make the developer experience smoother and more productive with upgrades to the UX and visualization engine being top of mind. We’re always expanding new graph database and triplestore support with a focus this quarter on bolstering RDF use cases in particular, and finally, we’ll be devoting a lot of energy on enterprise features like authentication and more going forward. 

Let us know what you think! 

What are you waiting for? Try out the latest version of G.V() today and level up your graph game in no time.