Deploy and Host Mission Control on Railway

About Mission Control

Mission Control is an open-source dashboard for AI agent orchestration. It centralizes agent lifecycle, task dispatch, cost visibility, audit/security signals, and team operations in one self-hosted interface backed by SQLite.

About Hosting

Mission Control is designed for self-hosted deployment. Railway provides a zero-infrastructure-management platform that runs the official Docker image directly from GHCR, making it the simplest path to a production-ready instance without managing servers, networking, or container orchestration manually.

Tech Stack

• Next.js 16 + TypeScript
• SQLite (embedded, no external DB required)
• Docker image deployment via GHCR

Why Deploy

Deploying Mission Control gives your team full ownership over agent operational data. There are no third-party SaaS dependencies, no usage-based pricing surprises, and no data leaving your infrastructure. It is especially suited for teams running sensitive workloads or operating in regulated environments.

Why Railway + Docker Image

• Fast one-click deployment using official upstream image
• Pinned version (v2.0.1) for reproducibility and stability
• No source build needed on Railway, lower failure surface
• Easy to run in standalone mode without OpenClaw gateway

Common Use Cases

• Build a centralized internal AI agent operations console
• Track multi-agent tasks and execution history
• Review security posture and operational telemetry in real time
• Run small teams with minimal infrastructure overhead

Use Cases

• Coordinate multi-agent pipelines from a single dashboard
• Monitor cost and token usage across agent runs
• Maintain an audit trail for compliance and incident response
• Onboard new team members to agent workflows with low overhead

Dependencies for Mission Control

Mission Control has minimal external dependencies by design. SQLite is embedded and requires no separate database service. The only runtime requirement is the Docker image itself, which bundles the Next.js app and all Node.js dependencies.

Deployment Dependencies

Environment Variables (Template Defaults)

• PORT=3000
• NEXT_PUBLIC_GATEWAY_OPTIONAL=true
• MC_ALLOW_ANY_HOST=true
• AUTH_USER=admin
• AUTH_PASS=${{secret(24, "ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789")}}
• API_KEY=${{secret(64, "abcdef0123456789")}}
• AUTH_SECRET=${{secret(64, "abcdef0123456789")}}

Post-Deploy

1. Open /setup or /login on your Railway domain.
2. Connect OpenClaw gateway later if needed, or stay in standalone mode.
3. Optional: attach a persistent volume to /app/.data for durable local state.