Deploy OpenClaw on Railway

Deploy OpenClaw on Railway using a one-click template and access it through the web Control UI. This is the simplest "no terminal on the server" option: Railway manages the Gateway for you.

One-click deploy

Deploy on Railway

Deploy the template

Click Deploy on Railway above.

Add a volume

Attach a volume mounted at /data (required for persistent state).

Set variables

Set the required Variables on the service:

OPENCLAW_GATEWAY_PORT=8080 (required, must match the port in Public Networking)
OPENCLAW_GATEWAY_TOKEN (required, treat as an admin secret)
OPENCLAW_STATE_DIR=/data/.openclaw (recommended)
OPENCLAW_WORKSPACE_DIR=/data/workspace (recommended)

Enable public networking

Under Public Networking, enable HTTP Proxy for the service on port 8080.

Connect

Locate your public URL in Railway -> your service -> Settings -> Domains. It can be a generated domain (often https://<something>.up.railway.app) or your attached custom domain.

Open https://<your-railway-domain>/openclaw and connect with the configured shared secret. The template defaults to OPENCLAW_GATEWAY_TOKEN; if you switch to password auth, use that password instead.

What you get

Hosted OpenClaw Gateway and Control UI
Persistent storage through the Railway Volume (/data), so openclaw.json, per-agent auth-profiles.json, channel and provider state, sessions, and workspace survive redeploys

Connect a channel

Use the Control UI at /openclaw or run openclaw onboard via Railway's shell for channel setup instructions:

Discord
Telegram (fastest, just a bot token)
All channels

Backups and migration

Export your state, config, auth profiles, and workspace:

openclaw backup create

This produces a portable backup archive containing OpenClaw state and any configured workspace. See Backup for details.

Next steps

Set up messaging channels: Channels
Configure the Gateway: Gateway configuration
Keep OpenClaw up to date: Updating