Important: This template exposes your OpenClaw gateway to the public internet. Please read the OpenClaw security documentation before deploying. If you only use chat channels (Telegram, Discord, Slack) and don't need the gateway dashboard, you can remove the public endpoint from Railway after setup.
Your OpenClaw instance is configured and running
Manage devices and channel access
Grant DM access to users who have requested access on Telegram or Discord.
Approve or reject browser/device pairing requests for the Control UI.
Health checks and data export
Performs health checks and repairs broken configuration.
Download a password-protected ZIP of your config and workspace data.
Restore from a password-protected ZIP. Overwrites config and workspace, then restarts the gateway.
Directly edit openclaw.json. Creates a backup and restarts the gateway on save.
Destructive actions that cannot be undone
Reset Setup
Deletes the config file so you can run onboarding again from scratch.
This wizard is just one way to get started. You can also run any openclaw command directly using
Railway's built-in Console ā an in-browser shell scoped to this service, no SSH client needed.
openclaw onboard
openclaw models set anthropic/claude-sonnet-4-20250514
Choose your AI provider and authentication method
Format: provider/model-name
Connect messaging platforms (optional ā can be added later)
Message @BotFather on Telegram and run /newbot
Enable MESSAGE CONTENT INTENT in Bot ā Privileged Gateway Intents
Review your configuration and start OpenClaw
openclaw wizard to
complete it, then return here. Pick a different auth method to continue in the wizard.
Reset deletes the config file so you can rerun onboarding. Channel access approval grants DM access when dmPolicy=pairing.