Engram Cloud

April 26, 2026 · View on GitHub

Engram Cloud

Use Engram Cloud when you want shared, project-scoped memory across machines without giving up local-first ownership.

Local SQLite remains authoritative. Engram Cloud is optional replication + browser visibility for teams and operators.

Recommended Path (first)

If you want a working cloud setup fast, use the local smoke path first:

Start cloud + Postgres with compose
Configure local CLI server URL
Enroll one explicit project
Run explicit cloud sync

docker compose -f docker-compose.cloud.yml up -d
engram cloud config --server http://127.0.0.1:18080
engram cloud enroll smoke-project
engram sync --cloud --project smoke-project

Continue with full verification and expected outputs in Quickstart.

Public Container Image (GHCR)

Engram Cloud publishes an official image at:

ghcr.io/gentleman-programming/engram

Supported platforms:

linux/amd64
linux/arm64

Why Linux only? Docker containers run Linux in production platforms (and also inside Docker Desktop VMs on macOS/Windows), so these are the portable targets that matter for Dokploy/Coolify/Portainer/VPS deployments.

For a direct registry-based deploy example, use:

docker-compose.ghcr.yml

What Engram Cloud Is

Project-scoped replication: each sync call is tied to one explicit --project
Self-hosted cloud runtime: engram cloud serve on infrastructure you control
Browser dashboard: /dashboard/* visibility for humans/operators
Deterministic status/failure signals: clear reason codes instead of silent drift

What Engram Cloud Is Not

Not cloud-only
Not implicit “sync everything” mode
Not a replacement for local SQLite

Runtime Split (important)

Local runtime: `engram serve`

Local memory API
Local sync status endpoint: GET /sync/status

Cloud runtime: `engram cloud serve`

GET /health
GET /sync/pull, POST /sync/push
GET /dashboard/* (browser surfaces)

Cloud Docs Map

Doc	Purpose
Quickstart	One recommended path first, then authenticated mode
GHCR Compose Example	Pull-and-run deployment sample for Dokploy/Coolify/Portainer/VPS
Branding	Engram Cloud visual identity, asset usage, previews
Technical Cloud Reference	Full CLI + env/runtime details
Cloud Autosync	Background replication behavior + phase table

Next Steps

Need a first successful run? Go to Quickstart
Need exact env/runtime contracts? See DOCS.md Cloud sections
Need visual usage rules? Open Branding