Deploy ElizaOS
Self-hosted ElizaOS AI agent with dashboard, pairing login and volume
Just deployed
/data
Deploy and Host ElizaOS on Railway
ElizaOS is an open-source (MIT) framework and app for running autonomous AI agents. An agent has its own character, memory, knowledge, plugins and wallets, and can chat in its web dashboard or on connected platforms such as Discord and Telegram. It works with model providers like OpenAI, Anthropic and OpenRouter.
About Hosting ElizaOS
This template runs the official ElizaOS container image (upstream's current stable build, pinned by digest) as one service with a volume at /data. The agent's config, character, plugins, wallets and its embedded PGlite database live on that volume, so they survive redeploys and restarts. The dashboard and API are locked behind a generated ELIZA_API_TOKEN. After deploy, open the public URL, then copy the one-time pairing code from the service's Deploy Logs (Pairing code: XXXX-XXXX) to sign the browser in. First-run setup completes itself with the default "Eliza" character. Add at least one model provider key so the agent can answer.
Common Use Cases
- A personal AI assistant with long-term memory, notes, reminders and a web dashboard
- An agent that answers in Discord, Telegram or other connected chat platforms
- Experimenting with agent characters, plugins and skills on your own server
Dependencies for ElizaOS Hosting
- A model provider API key (OpenAI, Anthropic or OpenRouter), set at deploy or later
- A Railway volume for agent state (included)
Deployment Dependencies
- ElizaOS source: https://github.com/elizaOS/eliza
- ElizaOS documentation: https://docs.elizaos.ai
- Template repository: https://github.com/aalfath/elizaos-railway-template
Implementation Details
The service builds from aalfath/elizaos-railway-template, which pins ghcr.io/elizaos/eliza:sha-9e36ceb by digest and adds a small start script. When the pin is bumped there, Railway shows you an "update available" notice and you choose when to apply it; the repo's CHANGELOG.md lists breaking changes first.
Variables:
ELIZA_API_TOKEN: generated; also used asAuthorization: Bearerfor API clientsELIZA_VAULT_PASSPHRASE: generated; encrypts the agent's secret vault, so don't change it laterOPENAI_API_KEY,ANTHROPIC_API_KEY,OPENROUTER_API_KEY: optional; set at least one
If the pairing code in the logs has expired, reload the page and a new code is logged. The agent needs about 2 GB of memory.
Why Deploy ElizaOS 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 ElizaOS 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

