Pick a graph database without making it a one-way door, and decide how much access each person and agent gets.
Keep the database decision reversible
The situation. You need a graph store now, and you are not sure TypeDB’s type system, Neo4j’s ecosystem or TerminusDB’s commit history will matter most in two years.
Write queries, schema and migrations against the contract. Switching backend is a change of one value, and the capability matrix shows ahead of time which of your queries the other backend would refuse.
Use: the query contract, from Rust
Limit. The Rust layer is the agnostic one. The TypeScript packages are not on the contract yet (graphlift#302).
Migrate from one backend to another, verified
The situation. You are leaving one database for another and cannot afford records lost in transit.
The sync command copies schema and data through both contracts. It previews unless allowed to write, and with a move it reads the target back and deletes from the source only the records it verified there.
Use: graphlift sync --move
Limit. Neo4j cannot yet be a move’s source (graphlift#930). A run holds both snapshots in memory (graphlift#867).
Catch schema drift in CI
The situation. Someone changed a production schema by hand, and the migrations no longer describe it.
Compare a live schema with the migrations directory, or with another database, and fail the pipeline when they differ: the command exits 4 on drift.
Use: graphlift db schema diff
Limit. Speciality features outside the schema contract, such as TypeDB functions or Neo4j index kinds, are not compared (graphlift#925).
Give access with a defined blast radius
The situation. Analysts and agents need answers from production, and you need to know what they can and cannot change.
Hand out the render-only surfaces freely. They hold no credentials. Hand out the execution binary where answers are needed: it is read-only unless given a flag, caps rows and time, and writes an audit line per run. On TypeDB and Neo4j the read-only default is enforced by the server, and on the edge store by the store.
Use: graphlift-exec
Limit. On TerminusDB the read-only default rests on what the renderer emits, not on the server. Authorisation inside the database stays the database’s job.
Put a graph at the edge
The situation. You want graph reads close to users on Cloudflare, without a separate graph server to run.
The edge store keeps a graph in SQLite inside a Durable Object, behind the same contract, and a sync moves a graph into or out of it.
Use: the edge store, @graphlift/edgegraph-store
Limit. The execution binary and the CLI’s query and schema commands reach the three servers, not the edge store. Reach it from Rust or through a sync.