Evidence-linked database · Rust

Connected.
Sourced.

Documents, graphs and search in one Rust binary,
with the source text one edge away.

One binary. Free in production under the FSL.

Synthetic case select a node

Accounts handsets / CGQL

rook_77Handset 8813
Selected relation · 1 of 3

One binary.

JSON documents / Typed edges
BM25 + vectors / CGQL + Lua

Documents, typed edges, full-text and vector search in one Rust process with one file on disk. It runs next to your application: no cluster, no sidecar services, no embedding provider unless your workload needs one. Free to run in production under the Functional Source License.

Coming from ArangoDB

You already know
how to write this.

If you built on ArangoDB Community Edition and need somewhere to go, CGQL keeps FOR … FILTER … SORT … LIMIT … RETURN, @bind values, _key, _from and _to, and bounded traversals. One binary replaces the cluster.

Read the migration introduction
CGQL / accounts registered on each handset
FOR a IN accounts
  FILTER a.case == @case
  FOR h IN 1..1 OUTBOUND a._id registered_on
    COLLECT handset = h.label WITH COUNT INTO n
    SORT n DESC
    LIMIT 10
    RETURN { handset, n }

Five-minute start

Pull it. Run it.
Ask it something.

Run Community straight from Docker Hub. The image includes the HTTP API, web console and CLI. Your database lives in a persistent Docker volume.

The image is Linux amd64; Apple Silicon needs Docker’s amd64 emulation. This local example binds to loopback with authentication off.

Open http://127.0.0.1:3000 for the console, then follow the developer quick start. You can also build from source.

Shell / Docker
docker pull --platform linux/amd64 cognigraph/cognigraph:latest
docker run -d --name cognigraph --platform linux/amd64 \
  -p 127.0.0.1:3000:3000 \
  -v cognigraph-data:/data \
  -e COGNIGRAPH_AUTH_ENABLED=false \
  -e COGNIGRAPH_EMBEDDING_PROVIDER=none \
  -e COGNIGRAPH_CGQL_MUTATIONS_ENABLED=true \
  cognigraph/cognigraph:latest
curl --fail --retry 10 --retry-all-errors --retry-delay 1 \
  http://127.0.0.1:3000/health/database

Enterprise

When a fact needs
a chain of custody.

Community stores the edges your application creates. Enterprise adds the workflow that constructs them from text: every fact keeps its source chunk and byte span, construction rules are reviewable, refusals are counted, and policy, approval and promotion are separate signed roles.

Governed construction

Follow the evidence

Handset 8813 extraction

extractions/handset-8813

A synthetic case built for this website. The highlight is the exact text behind the selected relationship, and the span is its UTF-8 byte range.