Self-Hosted
Agent Memory Labs production hosting runs on managed infrastructure — you do not operate databases or servers for the default path.
Default path: install the Rust agent-memory CLI, log in, and use init --managed. Your graph lives on Ladybug with a SpacetimeDB temporal sidecar — not Neo4j or a local FastAPI server.
Hosted architecture (current production)
Managed accounts use the Rust control plane and Ladybug data plane on Agent Memory Labs infrastructure:
- agent-memory CLI — install, login, index, and doctor against the hosted backend
- am-server-rs — Rust control plane at
backend.agentmemorylabs.com - Ladybug — account-scoped graph store (
.lbug) on NVMe-backed runtimes - SpacetimeDB — temporal memory sidecar for time-aware retrieval
- MCP (OAuth) — remote tools at
mcp.agentmemorylabs.com; no localserveprocess
What "self-hosted" means today
True operator self-host of the Rust Ladybug stack is not yet documented as a supported end-user path. If you need to run everything on your own hardware, use the historical Python + Neo4j guide — clearly labeled legacy, not hosted production.
Rust/Ladybug self-host documentation may be added when the rebuild lane exposes a supported operator install path.
Legacy: Python + Neo4j + FastAPI
The previous self-hosted stack used Neo4j, a Python agentic-memory CLI, and a FastAPI am-server. That path is historical — removed from the Rust v1 hosted product and not what runs on Agent Memory Labs production today.