Installation
patinaDB ships as a Docker image whose entrypoint is patinadb-raft, the
Raft-replicated server binary (REST + Bolt). You do not need Rust, a compiler,
or any build tooling — pull the image and run it. The image is published for
both linux/amd64 and linux/arm64 — the same tag resolves to the right
architecture on either platform.
Run the server
docker run -p 7687:7687 -p 21001:21001 \
-v patinadb-data:/data \
-e PATINADB_AUTH_PASSWORD=change-me \
patinadb/patinadb
This starts a single self-leading node (a “cluster” of one — no peers needed) and exposes:
- REST on port
21001—POST /cypher - Bolt on port
7687— for Neo4j drivers and the Neo4j Browser
/data is where the graph, engram history, and node state live — mount a
named volume or bind mount so data survives a container restart.
By default the server refuses to start with no password set, so you don’t accidentally run an open database — see Authentication & TLS for how to configure it properly. For a disposable local try-out only (never expose this):
docker run -p 7687:7687 -p 21001:21001 patinadb/patinadb --insecure-disable-auth
Query it once it’s up:
curl -s -u neo4j:change-me -X POST localhost:21001/cypher \
-H 'content-type: application/json' \
-d '{"query": "CREATE (n:Person {name: \"Ada\"}) RETURN n"}'
See Quick Start for a walkthrough, and
Configuration Reference for every server flag
(--id, --addr, --db, --bootstrap, --bolt-addr, and the rest).
Next steps
- Quick Start — a five-minute walkthrough.
- High Availability — add peers for automatic failover.
- Authentication & TLS — lock the server down before exposing it.
- Editions & Limits — what Community mode includes, and how to apply a license.