Self-hosted NamiDB
Self-hosted NamiDB is the same engine that powers Cloud, packaged so you can run it locally — embedded inside your app, as a long-running server, or as a one-shot CLI. The bucket is the database, so durability is whatever your chosen storage (local disk, MinIO, S3) already gives you.
Get started
- Install — Python, Rust, Docker, CLI.
- Your first query — 30 seconds, no credentials, in-memory namespace.
Run NamiDB
How you actually wire NamiDB into your stack. Pick the one that matches the boundary you want.
- Embedded (Python) —
namidbpackage in your process. - Embedded (Rust) —
namidbcrate, same engine, no network hop. - CLI —
namidb run/explainfrom your terminal. - HTTP server — the
namidb-serverdaemon over a REST API. - Docker + MinIO — full local
stack in one
docker-compose.yml.
Cypher
The query language. NamiDB speaks a strict subset of openCypher 9 plus GQL (ISO/IEC 39075:2024).
- Supported subset — what works and what doesn’t.
- Reading data —
MATCH,WHERE,RETURN, projections, paging. - Writing data —
CREATE,MERGE,SET,DELETE. - Operators & functions — every comparison, logical, list, math, string operator and built-in function.
Libraries
The surfaces you call from your code.
- Python — sync +
acypherasync, Arrow / pandas / polars output. - Rust — the umbrella
namidbcrate. - HTTP API — REST routes and JSON types.
- Bolt (Neo4j drivers) — Bolt 4.4 / 5.0 / 5.4 listener, every official Neo4j driver works unmodified.
Storage backends
Where the bytes actually live when you run locally.
- In-memory —
memory://for tests and the 30-second taste. - Local filesystem —
file://for durable graphs on disk. - MinIO — S3-compatible bucket on your own hardware.