Deploy AutoMem
AI long-term memory: AutoMem API and MCP bridge on FalkorDB and Qdrant
Just deployed
/data
MCP Bridge
Just deployed
Just deployed
/qdrant/data
FalkorDB
Just deployed
/data
Deploy and Host AutoMem on Railway
AutoMem is an open-source (MIT) long-term memory service for AI assistants. It stores memories in a FalkorDB graph and a Qdrant vector index, so Claude, ChatGPT, Cursor and other MCP clients can recall decisions, preferences, relationships and context across sessions through one HTTP API.
About Hosting AutoMem
This template runs AutoMem 0.16.3 as four services that build from one public GitHub repo, each pinned by version and digest: the AutoMem API (public), an MCP bridge for cloud AI clients (public), FalkorDB 4.22 and Qdrant 1.20 (both private). Graph data, vectors and downloaded embedding models sit on Railway volumes, so they survive redeploys. The API token, admin token, FalkorDB password and Qdrant API key are generated for each deploy. Add a Voyage or OpenAI key for hosted embeddings, or leave both empty to use a local model. Version bumps reach you as Railway update notices.
Common Use Cases
- Give Claude Desktop, Claude Code, Cursor or Codex a shared memory that persists between sessions and machines
- Connect ChatGPT, Claude.ai or ElevenLabs agents to the same memory through the MCP bridge
- Store project decisions, preferences and facts once and recall them by meaning, tags or time
Dependencies for AutoMem Hosting
- FalkorDB (graph store, bundled, private, on a volume)
- Qdrant (vector store, bundled, private, on a volume)
- Optional: a Voyage AI or OpenAI API key for hosted embeddings
Deployment Dependencies
- AutoMem source and docs: https://github.com/verygoodplugins/automem
- AutoMem releases: https://github.com/verygoodplugins/automem/releases
- Template repo: https://github.com/aalfath/automem-railway-template
- FalkorDB: https://docs.falkordb.com
- Qdrant: https://qdrant.tech/documentation
Implementation Details
After the deploy:
- Open the AutoMem service, copy
AUTOMEM_API_TOKENfrom its Variables tab and its public domain from Settings.https://YOUR-AUTOMEM-DOMAIN/healthshowsfalkordbandqdrantas connected. - Point a local MCP client at the API, for example
npx @verygoodplugins/mcp-automem setupwithAUTOMEM_API_URL=https://YOUR-AUTOMEM-DOMAINand the token. - For cloud clients (ChatGPT, Claude.ai), use the MCP bridge:
https://YOUR-BRIDGE-DOMAIN/mcpwith the headerAuthorization: Bearer YOUR-AUTOMEM-API-TOKEN(or?api_token=where a client can't send headers). The bridge never uses a token of its own, so a request without a token gets 401.
Embeddings: with VOYAGE_API_KEY or OPENAI_API_KEY set, AutoMem uses that provider (Voyage first). With neither, it downloads the local bge-large-en-v1.5 model (about 1.2 GB) to the volume once and runs it in the API service, which needs about 4 GB of RAM. Keep VECTOR_SIZE=1024 unless you plan a re-embed. OPENAI_API_KEY also enables memory classification and enrichment.
Updates: the repo pins every image by digest. When we bump a version, Railway shows an update on your project, and the repo's CHANGELOG.md lists breaking changes first. FalkorDB stays on 4.x, because FalkorDB 6 can't open a 4.x volume without a migration. Admin endpoints (backup, re-embed) use ADMIN_API_TOKEN.
Why Deploy AutoMem on Railway?
Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.
By deploying AutoMem on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.
Template Content

