Skip to main content
Deploy Velaclaw 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 VELACLAW_GATEWAY_PORT and VELACLAW_GATEWAY_TOKEN).
  4. Enable HTTP Proxy on port 8080.
  5. Open https://<your-railway-domain>/ and connect using the configured shared secret. This template uses VELACLAW_GATEWAY_TOKEN by default; if you replace it with password auth, use that password instead.

​
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>/ — Control UI

​
What you get

  • Hosted Velaclaw Gateway + Control UI
  • Persistent storage via Railway Volume (/data) so velaclaw.json, per-agent auth-profiles.json, channel/provider state, sessions, and 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:
  • VELACLAW_GATEWAY_PORT=8080 (required — must match the port in Public Networking)
  • VELACLAW_GATEWAY_TOKEN (required; treat as an admin secret)
  • VELACLAW_STATE_DIR=/data/.velaclaw (recommended)
  • VELACLAW_WORKSPACE_DIR=/data/workspace (recommended)

​
Connect a channel

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

​
Backups & migration

Export your state, config, auth profiles, and workspace:
This creates a portable backup archive with Velaclaw state plus any configured workspace. See Backup for details.

​
Next steps