CortexDB v0.9.8 · released August 22, 2026

Run CortexDB locally

One command, no signup. Two ways in — a Docker image or a Linux binary — running on your own infrastructure at no cost. Source-available, not open source.

01 Docker

The one-command path

Multi-arch image on Docker Hub — linux/amd64 and linux/arm64. Data persists to the named volume.

Run CortexDB
docker run -d \
  --name cortexdb \
  -p 3141:3141 \
  -v cortexdb-data:/data \
  -e OPENAI_API_KEY=$OPENAI_API_KEY \
  -e ANTHROPIC_API_KEY=$ANTHROPIC_API_KEY \
  cortexdb/cortexdb:latest

Once it is up, the dashboard is at localhost:3141 and health is at localhost:3141/v1/admin/health.

Your data is stored locally, but the default configuration still calls out for model work: OpenAI for embeddings and entity extraction, Anthropic for answer generation. Consolidation runs on the box. To drop the embedding dependency too, point CORTEX_EMBEDDING_URL at a local Ollama — the profiles doc puts the cost at roughly 5pp of recall.

02 Binary

No Docker required

A single stripped executable plus bundled assets, README and docs. Untar and run.

Linux · x86_64 cortexdb-0.9.8-linux-amd64.tar.gz Download Linux · ARM64 cortexdb-0.9.8-linux-arm64.tar.gz Download
Unpack and start · amd64
tar -xzf cortexdb-0.9.8-linux-amd64.tar.gz
cd cortexdb-0.9.8-linux-amd64
./cortexdb

SHA-256 checksums are attached to every GitHub Release. macOS and Windows builds are not shipped yet — ask us if you need one.

03 First memory

Write one thing, then ask for it back

Every write is an event with a time it was observed and a key that makes it idempotent. Nothing is overwritten.

Store an experience
curl -X POST http://localhost:3141/v1/experience \
  -H 'Content-Type: application/json' \
  -d '{
    "scope": "ws:demo",
    "modality": "observation",
    "content": { "kind": "text", "text": "Priya at Acme signed for 200 seats." },
    "context": { "observed_at": "'`date -u +%Y-%m-%dT%H:%M:%SZ`'" },
    "idempotency_key": "'`uuidgen`'"
  }'

Recall returns a pack, not a list of chunks: events, episodes, facts and beliefs come back together in one round trip, already assembled into a context block.

Recall it
from cortexdb.v1 import V1Client

client = V1Client(api_url="http://localhost:3141", actor="agent:demo")

pack = client.recall(
    scope="ws:demo",
    query="What did Priya commit to?",
    view="holistic",
    include=["events", "episodes", "facts", "beliefs"],
    budgets={"max_tokens": 1200},
)

print(pack["context_block"])

pip install cortexdbai or npm i cortexdbai — both ship the same client. Full endpoint reference in the docs.

04 In the package

What lands on disk

Bundled in the tarball, and in the image at /opt/cortexdb/docs/.

  • cortexdbstripped release binary, ~80 MB
  • assets/WordNet synonym map for BM25 expansion
  • docs/GETTING_STARTED.mdfive-minute quickstart
  • docs/API_DESIGN_V1.mdendpoint design rationale
  • docs/API_REFERENCE_V1.mdfull endpoint reference
  • docs/CORTEXDB_FOR_THE_ENTERPRISE.mdsecurity, compliance, deployment
  • docs/cortexdb_customer_deck.htmlproduct overview deck
  • docs/PRODUCTION_DEPLOYMENT.mdsystemd, reverse proxy, secrets
  • README.md, LICENSE.txtterms of the source-available licence

The record

63 releases behind the version above
95 days May 20, 2026 to August 22, 2026
47 of them inside the busiest three weeks, July 3 – July 23

CortexDB keeps a record of when every fact was learned and when it held true. The changelog is that same record, kept for the database itself — every release with its full notes, the version you would have downloaded on any given date.

Read the changelog 63 releases, five series, nothing summarised away.
Start

It runs on your machine in about a minute

No account and no email. Pull the image or take the tarball, and the engine above is yours to point at your own workload.