A graph database that fits in one file.
Written in Rust. It runs inside the app that uses it, or as one small server that speaks the protocol graph apps already use. Pre-alpha, and we say so.
What it promises- Language
- Rust
- Storage
- One file per database
- Speaks
- Bolt
- Status
- Pre-alpha
One fileIts log6 nodes · 9 relationships
nodekin>
MATCH (a:Person {name: "Ada"})-[:KNOWS]->(f)
-[:LIKES]->(t:Topic)
RETURN f.name, t.namef.namet.name
"Eva""graphs"
1 row
3,867 / 3,897
openCypher test scenarios passing on the crash-safe store
0 / 12,022
Acknowledged commits lost across 16 hard kills
30 MiB
The whole container image
0.13 s
From start to the first answer
Measured 16 October 2026: Docker on a Mac with four CPUs, 300,000 nodes and 750,000 relationships.
Five promises. Each one counted.
A database earns trust with numbers, not adjectives. Each promise below comes with the test that keeps it.
- 01One file.Each database is one file, with its write-ahead log beside it.
- 02Inside or beside.A Rust library in your process, or a small server that speaks Bolt.
- 03Familiar.The query language graph apps already use.
- 04Crash-safe.Kill it mid-write; no acknowledged commit is lost.
- 05Small.30 MiB, answering 0.13 s after it starts.
Where it is now
Pre-alpha. The Rust library and the server work today; the rest is on the list above, in that order of honesty.