Deploy fulfilling-light

Deploy and Host OpenClaw Mission Control on Railway

OpenClaw Mission Control is a centralized operations and governance dashboard for running OpenClaw across teams. It brings agent management, task orchestration, approval controls, gateway operations, and activity history into one interface.

This template deploys the Railway-adapted Chinese fork maintained at wsbjj/openclaw-mission-control.

About Hosting OpenClaw Mission Control

The template provisions the frontend, backend API, PostgreSQL, and Redis services needed by Mission Control. Railway supplies the public domain, TLS, environment variables, logs, and managed persistent storage for the databases.

The backend exposes its health endpoint at /healthz. The frontend is the main operator interface and connects to the backend through Railway's private network.

Why Deploy OpenClaw Mission Control on Railway

• Run an always-on operations dashboard without maintaining a separate server.
• Keep the application, database, and queue services in one Railway project.
• Use Railway variables for authentication and service connection settings.
• Inspect deployment and HTTP logs from the Railway dashboard.
• Scale the application services independently when workload increases.

Common Use Cases

• Coordinate multiple OpenClaw agents and distributed gateways.
• Manage organizations, boards, tasks, tags, and users from one control surface.
• Route sensitive actions through approval flows and keep an activity trail.
• Expose an API-backed automation surface alongside the web interface.

Dependencies for OpenClaw Mission Control Hosting

Deployment Dependencies

• A Railway workspace where the template can create a project.
• PostgreSQL and Redis, provisioned by the template.
• A LOCAL_AUTH_TOKEN of at least 50 characters when AUTH_MODE=local.
• Optionally, Clerk configuration when using AUTH_MODE=clerk.

Configuration

The template wires DATABASE_URL, REDIS_URL, and RQ_REDIS_URL between the services. Set the authentication mode and any Clerk credentials in Railway Variables before relying on the deployment.

For local authentication:

AUTH_MODE=local
LOCAL_AUTH_TOKEN=replace-with-a-random-token-at-least-50-characters-long

Set NEXT_PUBLIC_AUTH_MODE on the frontend to the same authentication mode.

After Deployment

1. Wait for the backend and frontend deployments to become healthy.
2. Open the generated Railway domain for the frontend.
3. Sign in with the configured authentication method.
4. Configure OpenClaw gateways and begin creating boards and agents.

Source

• Railway fork: https://github.com/wsbjj/openclaw-mission-control
• Upstream project: https://github.com/abhi1693/openclaw-mission-control

Mission Control is under active development. Validate authentication, database, and gateway settings before using it for production operations.