FIELD REPORT
Text-to-SQL agents ship at 10 tables. They fail at 1,000.
What fifty-odd data team leaders told us about where agents break as the schema grows, and what the teams running them at scale do differently.
Read the field reportEnable agents across your 3,000 tables.
The graph query layer on top of the warehouses and lakehouses you already run. Nothing to move, nothing to copy, nothing new to keep in sync.



deploy to first query
10-hop query, billions of edges
in production today
FEATURED
FIELD REPORT
What fifty-odd data team leaders told us about where agents break as the schema grows, and what the teams running them at scale do differently.
Read the field reportWHY PUPPYGRAPH
A graph query engine, not a graph database. Query your tables as a graph, in place. No second data store or pipelines to keep it in sync.
Copy data into a dedicated graph database.
Keep the graph copy in sync
Warehouses · Lakehouses · Databases
Connect your data. Query it as a graph.
Warehouses · Lakehouses · Databases
FOR AI AGENTS
Give GraphRAG systems and AI agents a relationship-aware way to navigate thousands of enterprise tables, follow multi-hop connections, and retrieve connected context through one queryable graph model.
Define business entities and relationships across your enterprise tables as a queryable graph model. This ontology gives your agents a shared model to query.
Agents query relationships defined in the model. Invalid entity or relationship references are rejected with feedback the agent can use to revise its query.
Follow the entities and relationships defined in your ontology to retrieve connected records and multi-hop paths that give the LLM business context.
MCP clientDatabases, warehouses, and lakehouses
Start with PuppyGraph’s built-in AI assistant, or connect your own agents through MCP.
“For a user-facing application, query latency and data freshness are non-negotiable. PuppyGraph allows us to execute multi-hop graph traversals directly on our existing data platform without moving or duplicating a single row. By removing the ETL bottleneck, we eliminated pipeline maintenance entirely while delivering lightning-fast graph analytics to our end users in real time.”
Ran XiaEngineering DirectorRead the case study →“PuppyGraph is a very interesting graph query engine. It doesn’t require us to load or ETL any of the data into a specialized or proprietary database storage layer for graphs. PuppyGraph queries all our transactional and crypto data directly and performs all kinds of graph-based exploration and aggregation. It’s so powerful, and our users really enjoy this type of flexibility.”
Eric SunSr. Manager of Data PlatformRead the case study →“With PuppyGraph, standing up a new graph is a schema definition, not a data migration. We connect directly to the tables we already maintain in Snowflake and Databricks and start querying immediately. No pipelines. No second copy of the data, and no data movement.
The architecture scales with our existing data platform, even at petabyte scale. And with PuppyGraph MCP, we can query complex relationships in real time using natural language. It has become part of how we work with our data every day.”
Xinyu LiuStaff Software EngineerRead the case study →“PuppyGraph’s relationship engine has been instrumental in building our correlation platform, enabling seamless connectivity and insights. The team’s efficiency, fast response, and proactive engagement have made a significant impact, providing us with valuable guidance every step of the way.”
Naiming ChuVice President, Infrastructure and Platform Operations“PuppyGraph is the only solution we found that supports Iceberg natively at that scale, with no data loading required. You just connect to the lakehouse underneath, and the cluster itself doesn’t manage any data. Querying it as a graph in place, without duplicating a single row, is what made this viable for us”
Patrick LuLead Architect for Data and AI/ML“We run AI agents across thousands of tables and billions of edges a day. Two years ago, I’d have told you the graph side alone made this impractical at this scale. It’s one of those products where you ask: how is this just now?”
Leon GoldbergCTORead the case study →“Although Neo4j is a popular knowledge graph solution, we used PuppyGraph due to its open-source flexibility and seamless integration capabilities. PuppyGraph functions as a zero-ETL graph analytics engine that allows direct querying of data from sources like Databricks without requiring data movement. This approach reduces onboarding costs and improves performance.”
Ryan ElsingaSenior Data & AI EngineerRead the case study →“Historically, graph queries required specialized storage and compute, but now PuppyGraph is running directly on plain vanilla Iceberg tables. Just point to a table with your nodes and edges, and let PuppyGraph go. The performance you get out the other side is amazing.”
Jason ReidCo-creator, Apache Iceberg“PuppyGraph’s plug and play design is exceptionally user-friendly for newcomers to graph technology. We experienced virtually no learning curve, swiftly showcasing our first demo to the leadership team. Moreover, PuppyGraph did not increase our system complexity because it eliminated the need for data duplication, making the daily maintenance cost very low.”
Po-Chun ChangEngineering Manager“After evaluating a few different graph solutions, we struggled to find one that could scale to our data needs. PuppyGraph's approach, decopling the query engine from the storage, enabled us to connect to our data files and perform analytics across different data categories, this could assist with unlocking insights and new possibilities.”
Hongliang LiuDirector of Data Science“We found that GPEs like PuppyGraph—especially in cached mode—excel at analytical and summarization use cases, outperforming most graph databases by a wide margin.”
Namith CholappurathHead of ArchitectureRead the case study →“In traditional architectures, working with graph data usually means ETL into a dedicated graph database like Neo4j, TigerGraph, or DataStax—which adds complexity and cost. Here, this is a different route: plug a graph engine directly into your Iceberg lakehouse. Simple, unified, and more cost-effective.”
Bruno MarquiéSenior Principal Engineer“We needed a query engine that could run complex graph traversals on Iceberg tables fast enough to power a real-time product. PuppyGraph gave us sub-second performance on millions of records without requiring us to move data into a separate graph store. It's the layer that makes our architecture actually work.”
Quentin KassehFounder and CEODefine entities and relationships over your existing lakehouse tables, then query them as a knowledge graph without creating a separate data copy.
Explore knowledge graphs →Give AI agents an enforced ontology across thousands of tables. Invalid entity or relationship references are rejected with feedback.
Explore AI agents →Explore by industry
Connect identities, permissions, and assets to investigate attack paths and understand the blast radius of a compromise.
Explore cybersecurity →Trace connections across accounts, devices, and transactions to investigate coordinated fraud and follow the flow of funds.
Explore fraud & financial crime →Connect suppliers, materials, and logistics dependencies to trace origins and understand how disruptions affect downstream operations.
Explore supply chain →Connect clinical and biomedical data to explore care pathways, prescribing networks, and relationships between drugs, targets, and diseases.
Explore healthcare →No connector to write. No format to convert.
Warehouses, lakehouses and operational stores.
Build a graph model and ask questions in natural language.
Write and run openCypher or Gremlin queries.
Explore connected entities and paths in your query results.
Query your graph from JavaScript, Java, Python, or Go using Gremlin or openCypher drivers.
Connect your own AI application through MCP.
Connect the relational data you already have and start running graph queries on it. Nothing is copied, nothing is migrated, and there is no pipeline to build.
Run graph queries and explore connected data in your browser. Start with preloaded datasets, no installation required.
MATCH p = (:Device {name: 'Shared laptop'})
<-[:USES_DEVICE]-(:Account)
-[:TRANSFERRED_TO]->(:Beneficiary)
RETURN pEnterprise security
Run PuppyGraph on infrastructure you control, configure access to your graph, and review the security practices behind our software.
Run PuppyGraph in containers, on Kubernetes, or in your own AWS, Azure, or Google Cloud account. Configure connections to your existing data sources.
Use OIDC single sign-on, role-based permissions, and configured row-level filters. Review RBAC-related actions in the audit log.
Learn about vulnerability scanning, infrastructure monitoring, employee security training, and internal access controls.
Explore configuration details, optional AI data handling, company policies, and ways to contact our team.
No. It is a query engine. Your data stays in your existing stores, and there is no copy to build or keep in sync.
No. PuppyGraph queries your existing tables in place. No pipelines, no data movement.
In your environment: Docker, Kubernetes, any cloud, inside your VPC.
The Developer Edition is free forever. Enterprise pricing scales with your deployment. See pricing.
$ docker run -p 8081:8081 \
-p 8182:8182 -p 7687:7687 \
puppygraph/puppygraph:latestPulling puppygraph/puppygraph:latestStarting PuppyGraphWeb console listening on 0.0.0.0:8081Gremlin endpoint listening on 0.0.0.0:8182PuppyGraph is running# no pipelines · no second database · no data movement