Vannus / Catalog / Neo4j

Neo4j

This entry runs no foundation model. Every finding below is quoted to the vendor’s own document, or marked not disclosed where the vendor publishes nothing.

Determination
Contracting entity depends on your region or order form — read the clause.
neo4j.com · read 2026-09-16
read from terms of service · inferred from the address, not the heading

Native graph database — property graph model with Cypher query language for multi-hop reasoning, entity-relationship traversal, and explainable dependency tracing across enterprise AI tool ecosystems

Database, Enterprise
Model provenance

No foundation model. Neo4j does not run one, so this criterion does not apply and is excluded from the grade rather than counted against it. A native graph database and query engine (Cypher, ACID transactions, clustering); the database itself serves no foundation model, and its GenAI add-ons require the user to bring their own LLM provider. Established from the product’s own public documentation and what it does. If that is out of date, tell us at right of reply.

Who controls it
Data jurisdictionUnited States · a privacy notice ↗
US corporate controlRegion-dependent — a US entity contracts in some regions, another elsewhere · clause re-checked 17 Sep 2026
Contracting entityTwo contracting entities, split by where the CUSTOMER is incorporated: Neo4j Sweden AB for customers incorporated in Europe, the Middle East, Africa, China and Singapore; Neo4j, Inc. for customers incorporated in all other countries, and for transactions through a cloud-provider (CSP) marketplace. An Order Form or SOW may name a different entity, which takes precedence.
Governing lawSwedish law with exclusive jurisdiction in the courts of Malmö, Sweden (Neo4j Sweden AB); California law with exclusive jurisdiction in the state and U.S. federal courts in Santa Clara, California (Neo4j, Inc.)
Trains on your dataNo — on the vendor's default plan

Training and retention posture varies by plan. What we publish above describes the vendor’s default plan; enterprise, team and API agreements frequently differ, often materially, and a contract can override the published default entirely. Check your own plan and contract before relying on this row.

This is a separate question from the grade above. The grade measures resilience — whether the tool endures and whether you could leave it. This describes who controls the vendor. A tool can score modestly on one and strongly on the other, and many do.

On U.S. CLOUD Act reach specifically: the statute reaches a provider subject to U.S. jurisdiction over data in its possession, custody or control. Corporate control is a strong indicator of that and it is what we can evidence from published documents — but it is not the whole test. A company founded outside the U.S. can still contract through a U.S. entity or run substantial U.S. operations. Treat this as a starting point for your own review, not a legal determination, and take advice on anything that matters.

Signals on file
Data jurisdiction
United States
Zero data retention
Yes — states it retains no prompt data

The vendor's published or catalog-recorded posture — the concrete facts this grade is built from. A full audit verifies each against the vendor's current documentation.

Compliance the vendor states
SOC2GDPRHIPAA

Taken from the vendor’s own published material. Vannus does not hold these reports and has not reviewed their scope or dates — ask the vendor for the current report before relying on any of them.

How this grade is set

Vannus publishes a nine-dimension trust framework — data sovereignty, training privacy, compliance posture, operational resilience, exit portability, and more. The heaviest criterion asks whether the tool builds its own AI or resells someone else's model; where the vendor discloses it, the grade cites the vendor's own documentation. No paid placements — scoring is walled off from affiliate revenue. See the methodology →

Related tools we grade
Visit Neo4j ↗ Grade your whole stack →