diff --git a/docs/railway.mdx b/docs/railway.mdx
index e0702fa0f..a4794eb20 100644
--- a/docs/railway.mdx
+++ b/docs/railway.mdx
@@ -8,10 +8,16 @@ Deploy Clawdbot on Railway with a one-click template and finish setup in your br
Deploy on Railway
-After deploy, open:
+After deploy, find your public URL in **Railway → your service → Settings → Domains**.
-- `https:///setup` — setup wizard (password protected)
-- `https:///clawdbot` — Control UI
+Railway will either:
+- give you a generated domain (often `https://.up.railway.app`), or
+- use your custom domain if you attached one.
+
+Then open:
+
+- `https:///setup` — setup wizard (password protected)
+- `https:///clawdbot` — Control UI
## What you get
@@ -45,7 +51,7 @@ Set these variables on the service:
## Setup flow
-1) Visit `https:///setup` and enter your `SETUP_PASSWORD`.
+1) Visit `https:///setup` and enter your `SETUP_PASSWORD`.
2) Choose a model/auth provider and paste your key.
3) (Optional) Add Telegram/Discord/Slack tokens.
4) Click **Run setup**.
@@ -73,6 +79,6 @@ If Telegram DMs are set to pairing, the setup wizard can approve the pairing cod
Download a backup at:
-- `https:///setup/export`
+- `https:///setup/export`
This exports your Clawdbot state + workspace so you can migrate to another host without losing config or memory.