Security and self-hosting

Encryption at rest, strict multi-tenancy, and a self-hosted engine for teams that need full control. Your memories, your infrastructure, your keys.

Encryption

AES-256-GCM at rest

Project-level encryption policy in the console — completely transparent to your code. Memory bodies are unreadable at rest without the master key.

  • Toggle in Settings → Security → Encryption at rest
  • Lazy migration for existing plaintext memories
  • Set a 32-byte master key for self-hosted deployments

Self-hosting

One container, full engine

The standalone image bundles the engine, embedded Postgres + pgvector, and a local ONNX embedding model. No API keys, no external database required.

Rootless container

Runs as UID 1000 with Docker named volumes

LLM configurable

OpenAI, Vertex/Gemini, or any LiteLLM-supported model

Gateway optional

Run the multi-tenant gateway alongside for per-project keys

Self-hosting guide

Multi-tenancy

Strict isolation

Each organization gets an isolated Postgres schema. An API key for one project can never read another project's data.

Project isolation

Per-org Postgres schemas

Key scoping

Operation-type restrictions

Bank isolation

No cross-bank data leakage

Encryption

Project-level at-rest policy