Deploy Rakazo

Deploy and Host Rakazo on Railway

Rakazo is an open-source platform for persistent AI teammates, with 5,000+ GitHub stars: bots that keep their own conversations, memory and routines, and operate a real computer (browser, terminal, files and desktop) to get work done. Hosted assistants like Lindy start at $49.99 per user per month — run Rakazo on Railway for ~$10–15/month plus the model and sandbox usage you choose, and own your bots and their data.

What This Template Deploys

Four services on Railway's private network. api and worker build from the template's GitHub source; web uses the official Rakazo image pinned by digest.

About Hosting Rakazo

An agent platform needs more than a chat UI: an API with migrations, a background worker for routines, a database, shared secrets for auth and encrypted credentials, and somewhere safe for bots to run code and browsers. Rakazo runs bot computers on remote sandbox providers instead of nested Docker, which suits Railway.

On Railway, every service starts together, the web domain is wired into the API's auth and origin settings automatically, and BETTER_AUTH_SECRET, ENCRYPTION_KEY and SCREEN_PROXY_SECRET are generated and shared where needed.

Bot computers need a sandbox provider key. The template uses E2B by default (SANDBOX_PROVIDER=e2b): add E2B_API_KEY, or switch to Daytona or Box with their key, or set none for chat-only bots. Rakazo is also still in beta, and this template pins v0.2.0 while upstream moves quickly.

Typical cost: ~$10–15/month on Railway, plus your model usage and sandbox time (E2B's default sandbox is about $0.17 per hour while running, with $100 of free credit to start). Lindy's Team plan is $49.99 per active user per month for 5,000 credits.

Deploy Rakazo in Under 10 Minutes

1. Click Deploy on Railway — api, worker, web and Postgres start, and migrations run (~5–8 minutes).
2. Add E2B_API_KEY on the api service (or pick another provider) so bots get a computer.
3. Open the web URL and sign up — the first account becomes the owner.
4. Set SIGNUPS_ENABLED to false, or add SIGNUP_ALLOWLIST, so strangers can't register.
5. Connect a model (or set OPENROUTER_API_KEY), create your first bot and give it a routine.

No Docker-in-Docker. No Redis. No hand-wired auth secrets.

Common Use Cases

• Self-hosted AI assistant — "self hosted ai agent" with your own models and no per-seat fee
• Persistent AI teammates — bots that remember context and run routines on a schedule
• Browser and research automation — bots that browse, read and act on websites
• Team bots on a shared computer — several bots collaborate and delegate to subagents
• Voice assistants — talk to bots with your own ElevenLabs, OpenAI, Cartesia or Fish Audio key
• App integrations — connect tools through Composio, MCP servers or OpenAPI sources

Configuration

Close sign-ups after you register. With SIGNUPS_ENABLED=true, anyone who finds the URL can create an account on your instance.

Rakazo vs. Alternatives

Dependencies for Rakazo Hosting

• Railway account — plan for ~1–1.2 GB RAM across four services.
• A sandbox provider account (E2B, Daytona or Box) for bot computers.
• A model provider key (OpenRouter or your own), shared or per user.

Deployment Dependencies

• Rakazo GitHub — source and releases
• Rakazo Self-Hosting Guide — setup and providers
• E2B — default sandbox provider for bot computers
• Railway Volumes Documentation — persistence

Implementation Details

The api service runs prisma migrate deploy and then the Hono server on port 3100; web serves the UI on 5173 and proxies API calls over the private network; worker runs Graphile Worker on the same Postgres. WAKEUP_DRIVER=graphile keeps job scheduling in Postgres, so there's no queue service to run.

ENCRYPTION_KEY and SCREEN_PROXY_SECRET are generated once on the api service and referenced by the other services — never regenerate them. The public origin (WEB_ORIGIN, BETTER_AUTH_URL, RAKAZO_HOST) comes from the web service's domain; update it there when you add a custom domain.

Frequently Asked Questions

What is Rakazo and why self-host it? Rakazo is an open-source platform for AI teammates that keep memory, run routines and use a real computer. Self-hosting means you choose the models and sandbox provider and keep conversations and credentials in your own database.

How much does Rakazo cost compared to Lindy? About $10–15/month on Railway plus model and sandbox usage. Lindy's Team plan is $49.99 per active user per month for 5,000 credits, so costs grow with every user and task.

Why can't my bot use a browser or terminal? Bots need a sandbox provider. Check that SANDBOX_PROVIDER is set to e2b, daytona or box and that the matching API key is on the api service, then redeploy.

Do I lose bots or memory when I redeploy? No. Users, bots, memory and routines live in Postgres on a persistent volume, and workspace state is on the /data volumes. Migrations run automatically on each deploy.

Who can sign up to my Rakazo instance? Anyone, while SIGNUPS_ENABLED is true — and the first account becomes the owner. Register first, then set it to false or restrict sign-ups with SIGNUP_ALLOWLIST.

Is Rakazo production-ready? It's in beta and moves fast. This template pins v0.2.0 for stability; check the release notes before upgrading, and back up Postgres first.

Why Deploy and Host Rakazo 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 Rakazo on Railway, you get your own team of persistent AI agents — with memory, routines and real computers — on infrastructure you control, for a flat hosting cost plus the usage you choose.