Skip to content
RemoteClaw

Railway

Deploy RemoteClaw on Railway with a one-click template and access it through the web Control UI. This is the easiest “no terminal on the server” path: Railway runs the Gateway for you.

Quick checklist (new users)

  1. Click Deploy on Railway (below).
  2. Add a Volume mounted at /data.
  3. Set the required Variables (at least REMOTECLAW_GATEWAY_PORT and REMOTECLAW_GATEWAY_TOKEN).
  4. Enable HTTP Proxy on port 8080.
  5. Open https://<your-railway-domain>/remoteclaw and connect using your REMOTECLAW_GATEWAY_TOKEN.

One-click deploy

Deploy on Railway

After deploy, find your public URL in Railway → your service → Settings → Domains.

Railway will either:

  • give you a generated domain (often https://<something>.up.railway.app), or
  • use your custom domain if you attached one.

Then open:

  • https://<your-railway-domain>/remoteclaw — Control UI

What you get

  • Hosted RemoteClaw Gateway + Control UI
  • Persistent storage via Railway Volume (/data) so config/credentials/workspace survive redeploys

Required Railway settings

Public Networking

Enable HTTP Proxy for the service.

  • Port: 8080

Volume (required)

Attach a volume mounted at:

  • /data

Variables

Set these variables on the service:

  • REMOTECLAW_GATEWAY_PORT=8080 (required — must match the port in Public Networking)
  • REMOTECLAW_GATEWAY_TOKEN (required; treat as an admin secret)
  • REMOTECLAW_STATE_DIR=/data/.remoteclaw (recommended)
  • REMOTECLAW_WORKSPACE_DIR=/data/workspace (recommended)

Connect a channel

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

Backups & migration

Export your configuration and workspace:

Terminal window
remoteclaw backup create

This creates a portable backup archive you can restore on any RemoteClaw host. See Backup for details.

Next steps