Two ways in, described honestly
Self-hosting works today and costs nothing. Hosted access is provisioned by us rather than by a signup form — here is exactly why, and what to expect.
There is no self-serve signup yet
Most sites would put a “Start free trial” button here and route you to a form. We have not built one. Tenants in the hosted service are currently provisioned by an operator, and a login without a tenant claim is refused rather than silently creating an account. The fourteen-day trial mentioned in our own billing notes is not wired into checkout either, so we do not advertise it.
That is the honest state of version 0.3.6. It is on the roadmap, and when it ships this page changes. In the meantime the path below is genuinely quick, and the self-hosted route needs nothing from us at all.
Run it yourself
This is the fastest path and the one we would pick. The source is MIT licensed, the development stack is one command, and it works with no AI provider keys at all — summarisation falls back to deterministic extractive summaries and retrieval to a local embedding model.
You will need Docker Compose v2.24 or newer. Postgres 16 with pgvector comes up inside the stack, so there is nothing to install first.
openssl rand -base64 32 # → POSTGRES_PASSWORD
docker compose -f docker-compose.dev.yml \
--env-file .env up --build
curl -fsS http://localhost:8080/healthz
# {"status":"ok"}
open http://localhost:8080/ui/
What the first ten minutes look like
From an empty directory to an agent reading and writing durable memory.
-
Configure the environment
Copy backend/.env.example to .env and paste a generated secret into POSTGRES_PASSWORD. Nothing else is required to start — every provider setting has a working default or a deterministic fallback.
-
Bring the stack up
One docker compose command builds and starts Postgres with pgvector, runs the migrations, and starts the API and the outbox worker.
-
Confirm it is alive
Call /healthz and expect {"status":"ok"}. /readyz goes further and does a real Postgres round trip, returning 503 if the database is not reachable.
-
Open the dashboard
The operator dashboard is served at /ui/ — twenty-five pages covering memories, facts, sessions, Fabric, the knowledge base, the outbox, the audit log and the PII vault.
-
Write your first memory
Either through the dashboard, or POST /v1/memory, or by pointing an MCP client at the server and letting your agent call pcnaid_remember itself.
Or ask us for a hosted tenant
If you would rather not run Postgres, tell us what you are building and we will provision one.
A hosted tenant adds the parts that are tedious to operate: Auth0 authentication with role-based access, Stripe billing and quota enforcement, nightly backups, the public status page, the alert receiver and a support desk with a published response time.
Email support@pcnaid.com with what you are building and roughly how much you expect to store. We will come back with a tenant, an API key and the plan that fits. Once you are in, upgrading and cancelling are self-serve through Stripe Checkout and the Customer Portal.
If you already have a tenant, the dashboard is at memoryos.pndsvcs.com/ui/.
Useful before you write in
- Roughly how many memories you expect to store
- Whether you will bring your own provider keys
- Which agent clients you want to connect over MCP
- Whether you need more than one tenant
None of it is required. It just means the first reply is useful rather than a questionnaire.
{
"mcpServers": {
"pcnaid-memory-os": {
"command": "python",
"args": ["-m", "app.integrations.mcp.server"],
"cwd": "/path/to/backend",
"env": {
"PCNAID_MEMORY_API_URL": "http://localhost:8080",
"PCNAID_TENANT_ID": "…"
}
}
}
}
Then point an agent at it
Whichever route you took, the last step is the same. Memory OS ships an MCP server over stdio, so Claude Desktop, Claude Code, Codex CLI and any other stdio-capable MCP client can read and write memory as ordinary tool calls.
Eighteen tools are exposed, along with a prompt that teaches the connected agent the safe usage contract — most importantly that retrieved memory is evidence and never an instruction.