Deploy Mission Control

Self-hosted control plane for AI agents: tasks, runs, costs, approvals

Deploy Mission Control

Just deployed

Deploy and Host Mission Control on Railway

Mission Control is a self-hosted control plane for operating AI agents. Dispatch tasks, inspect runs, review failures, track token spend and coordinate agent runtimes (OpenClaw, Claude Code, Codex, CrewAI, LangGraph and others) from one dashboard backed by SQLite.

About Hosting Mission Control

This template runs the official Mission Control image as a single service:

  • Mission Control (ghcr.io/builderz-labs/mission-control:2.3) on port 3000 with a public domain
  • A persistent volume at /app/.data for the SQLite database, generated secrets and backups
  • A generated admin password (AUTH_PASS), seeded on first start, so the setup wizard is already closed when the domain goes live
  • Host allowlist limited to your Railway domain, secure cookies and HSTS

After deploy:

  1. Open the service Variables tab and copy AUTH_PASS (username: AUTH_USER, default admin).
  2. Sign in at https://YOUR-RAILWAY-DOMAIN/login.
  3. For headless access (agents, scripts, the MCP server), copy the API key from Settings and send it as the x-api-key header.
  4. To connect an OpenClaw gateway, use the gateway settings on the login page or in Settings. Tasks, projects, agents, schedules, webhooks, alerts and cost tracking work without a gateway.
  5. Using a custom domain? Add it to MC_ALLOWED_HOSTS, or requests to it get 403.
  6. Changing AUTH_PASS later does not rotate the existing admin; change the password in the app instead.

Common Use Cases

  • One dashboard for tasks and runs across several agent runtimes
  • Track token use and cost per agent and per task
  • Review, approve and audit agent work with a quality gate and receipts
  • Give agents a shared task inbox through the REST API or MCP server

Dependencies for Mission Control Hosting

Deployment Dependencies

Implementation Details

  • The image runs as a non-root user, while Railway volumes are root-owned, so the template sets RAILWAY_RUN_UID=0 to let it write to /app/.data.
  • AUTH_SECRET and API_KEY are generated by the image on first start and persisted to /app/.data, so they survive redeploys.
  • In production the app rejects every Host header that is not allowlisted; MC_ALLOWED_HOSTS holds your Railway domain plus Railway's healthcheck host.
  • Mission Control is alpha software: pin the image tag and read the release notes before upgrading.

Why Deploy Mission Control 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 Mission Control 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

More templates in this category

View Template
Chat Chat
Chat Chat, your own unified chat and search to AI platform.

okisdev
117
View Template
Weaviate
Vector database with hybrid search and an API key-protected API

GitHub Locker
1
View Template
Möbius Personal AI OS
Self-hosted AI agent that builds and runs apps for you, with memory.

bento
1