Deploy Rakazo (Single Container)
Persistent AI teammates with memory and routines. BYO model key
Just deployed
/var/lib/postgresql/data
Just deployed
/data
Deploy and Host Rakazo on Railway
Rakazo is an open-source platform for persistent AI teammates: bots with their own conversations, memory, routines and history, that you talk to from a web app. Bring your own model key (OpenRouter, Anthropic, or an OpenAI-compatible endpoint), and optionally give bots a cloud computer through E2B or Daytona.
About Hosting Rakazo
A Rakazo deployment is a long-running api, a background worker, a web UI and Postgres. This template bundles the api, worker and web UI into one container because the api and worker share bot files on disk, and Railway attaches a volume to exactly one service. Postgres runs as a separate Railway service with its own persistent volume. The container is a thin wrapper over upstream's published image that fixes volume ownership and boots all three processes with migrations applied first.
On first boot the container migrates the database, then starts the api, worker and web UI. That takes about a minute. Every secret the app needs (session signing, at-rest encryption, screen proxy) is generated for you at deploy time.
Common Use Cases
- Running a small team of persistent bots that remember context across conversations and keep their own notes and artifacts.
- Giving bots scheduled routines and delegated subtasks through the built-in worker, without hosting a separate queue.
- Bring-your-own-model agent chat: point the deployment at OpenRouter or any OpenAI-compatible endpoint and every call is billed to your key.
- With a sandbox provider key, letting bots open a real desktop: browser, terminal and files inside an isolated E2B or Daytona computer.
Dependencies for Rakazo Hosting
Deployment Dependencies
- A Railway account. Postgres and all secrets are provisioned by the template.
- Optional: an OpenRouter key, either at deploy time or connected in the UI after signup.
- Optional: an E2B or Daytona key if bots should get cloud computers.
Implementation Details
- Enter your email in
OWNER_EMAILand click deploy. Two services come up: Postgres and Rakazo. - Open the Rakazo service's public URL and sign in with
OWNER_EMAILand the generatedOWNER_PASSWORDfrom the Rakazo service's Variables tab. Change the password in account settings. - Bots can chat once a model is connected. If you did not paste an OpenRouter key at deploy time, connect a model in the UI after signup; the app verifies the key against the provider before storing it, encrypted.
- Bot computers are off by default (
SANDBOX_PROVIDER=none) because Docker inside Railway is not possible. To enable desktops, setSANDBOX_PROVIDERtoe2bordaytonaplus the matching API key variable on the Rakazo service, then redeploy.
Who can sign up: only you. First boot creates the OWNER_EMAIL account and
public registration is closed (SIGNUPS_ENABLED=false), so strangers who find
your URL are refused. To invite others, set SIGNUP_ALLOWLIST (emails or
@domains) and SIGNUPS_ENABLED=true, then redeploy.
Troubleshooting:
- Deploy healthcheck keeps failing: first boot runs migrations before
serving; give it two minutes. Past that, read the Rakazo deploy logs: the
boot script announces each step. Railway probes with the host
healthcheck.railway.app, which the image always allows. - 403 "Blocked request" in the browser:
RAKAZO_HOSTmust equal the public domain. The template wires this; only touch it if you add a custom domain, in which case set it to the custom hostname. - Never regenerate
ENCRYPTION_KEYon an existing deployment: it encrypts every stored provider key, and changing it makes them all unreadable.
Upgrades: the image tag is pinned (v0.13.0-r2). To move to a newer Rakazo release,
update the Rakazo service's image tag and redeploy. Migrations run on every
boot. Bot conversations and memory live in Postgres; agent homes and artifacts
live on the /data volume; both survive redeploys.
Why Deploy Rakazo on Railway?
Railway runs the whole stack (app, worker, database, persistent storage, TLS, domains) in one place with no server to operate. The template wires the database, generates every secret, and applies migrations on boot, so the gap between clicking deploy and talking to your first bot is about two minutes.
Template Content
OWNER_EMAIL
Your email. The first boot creates this account; sign in with it and OWNER_PASSWORD.

