Neo4j Launches Virtual Graph: Run Cypher Queries on Relational Warehouses Without Data Migration
Neo4j's Virtual Graph is now generally available, allowing users to execute Cypher queries and graph analytics directly on relational sources like Databricks and Snowflake without moving data. While traversal performance lags behind native graphs, it offers a zero-ETL entry point for large-scale graph analysis.
Graph databases and relational databases have long been viewed as distinct paradigms for data storage. The relational model excels at structured storage, while the graph model is superior for handling highly connected data and traversal queries. On November 16, 2026, Neo4j announced the General Availability (GA) of its "Virtual Graph" feature, designed to bridge this gap. This capability allows users to create a virtual Neo4j instance on top of existing relational data warehouses (such as Databricks, Snowflake, or BigQuery), enabling direct execution of Cypher queries for graph analysis and visualization without migrating data into a native Neo4j database.
The core advantage of Virtual Graph is "zero ETL." For enterprises with petabyte-scale data, copying all data into a graph database is not only costly but also complex to maintain. With Virtual Graph, data remains in its original relational store, and Neo4j acts as a query engine and visualization layer. The article notes that while this approach does not achieve the extreme traversal performance of native graph databases due to the lack of "index-free adjacency," it retains the expressive power of graph query languages and the benefits of visual graph modeling.
Using fraud detection as an example, the article demonstrates finding money laundering rings in a dataset with 10,000 accounts and 100,000 transactions. A bounded-length ring query took approximately 1.5 seconds on a native Neo4j instance; the same Cypher query on Virtual Graph took about 25 seconds. Although this is more than ten times slower, such latency is acceptable for non-real-time analytical tasks, such as overnight batch anti-money laundering checks. More importantly, it avoids the complexity of building and maintaining separate graph data pipelines.