Deploy and Host KiroCrew AI Agent Gateway on Railway

Kiro Crew is a persistent, self-improving workspace for development work that keeps going beyond a single session. Its gateway runs your AI crew 24/7: a web dashboard, channel bots (Slack, Discord, Telegram, WeCom, Weixin, Webex), scheduled jobs (crons), authenticated webhooks and the kiro-cli agent runtime — so your agents keep working, monitoring and reacting to events while your laptop is closed.

About Hosting KiroCrew

This template runs the official ghcr.io/kirodotdev/kirocrew:stable image (gateway on port 5476) with:

a persistent volume at /home/kirocrew (config, credentials, sessions and memory survive redeploys); the start command fixes volume ownership and then drops to the image's non-root kirocrew user
KIROCREW_CORS_ORIGINS set to your Railway domain so the dashboard accepts your browser
KIROCREW_ALLOW_UNSANDBOXED=1: Railway containers do not allow user namespaces, so agent commands run without Kiro Crew's inner sandbox — the container is the isolation boundary (only add credentials you are comfortable exposing to the agent)
a healthcheck on /api/health; every other API route requires a dashboard token

After deploy (one-time, using the Railway CLI):

Install the Railway CLI, run railway link to this project, then open a shell with railway ssh --service kirocrew.
Mint a dashboard login link: su -s /bin/sh kirocrew -c "kirocrew token --ttl 2h" — open the printed link, replacing the host with your Railway domain. Links expire quickly, so open it right away.
Log in the agent runtime: su -s /bin/sh kirocrew -c "kiro-cli login" (or set KIRO_API_KEY on the service instead).
Optionally add channel credentials (SLACK_BOT_TOKEN + SLACK_APP_TOKEN + KIROCREW_OWNER_ID, DISCORD_BOT_TOKEN, TELEGRAM_BOT_TOKEN, …) as service variables and redeploy.

Common Use Cases

An always-on coding/ops agent you message from Slack, Discord or Telegram
Scheduled agent jobs and deterministic scripts (crons) with monitoring until done
Reacting to authenticated webhooks from CI, GitHub or other systems
A shared, persistent agent workspace for a small team

Dependencies for KiroCrew Hosting

Docker image ghcr.io/kirodotdev/kirocrew
A Kiro account (interactive kiro-cli login) or KIRO_API_KEY

Deployment Dependencies

Source: https://github.com/kirodotdev/KiroCrew
Docker guide: https://github.com/kirodotdev/KiroCrew/blob/main/docs/guides/docker.md

Implementation Details

Microsoft Teams, Feishu and WhatsApp channels need optional extras not included in the stock image; iMessage requires macOS. If you attach a custom domain, update KIROCREW_CORS_ORIGINS to match.

Why Deploy KiroCrew 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 KiroCrew 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.