Enabling Virtual Graph

This is the public preview documentation of Neo4j Virtual Graph. To provide feedback, please use the feedback form you were granted access to.

During the public preview, we advise you not to use sensitive or production data with Virtual Graph.

We recommend you to use the latest Neo4j version available when trying out Virtual Graph in public preview.

As of Neo4j Enterprise Edition 2026.10, a single DBMS can contain one Virtual Graph database, and multiple standard or composite databases.

Virtual Graph is configured outside the main Neo4j neo4j.conf except for two settings:

  • internal.virtual_graph.enabled = true

  • internal.virtual_graph.home = [readable directory]

These settings will change for the public release of Neo4j Virtual Graph.

Enable Virtual Graph by setting these two, where [readable directory] is an existing and readable directory in your file system. Neo4j won’t start if that directory does not exist or is missing required files, see Virtual Graph home.

Database name and upgrades

The Virtual Graph database must be named neo4j. If you are upgrading a DBMS that already has a standard database named neo4j, rename that database before setting up Virtual Graph. Alternatively, deploy Virtual Graph on a new DBMS.

Virtual Graph home

Virtual Graph requires three files in its home directory:

The content of the directory and the content of each file is only checked and evaluated at Neo4j boot time. If a file is missing or invalid or Virtual Graph cannot open an initial remote connection, the boot process fails.