2026-01-26 08:07:33 +01:00
|
|
|
|
---
|
2026-03-19 11:42:57 -07:00
|
|
|
|
summary: "Deploy OpenClaw on Northflank with one-click template"
|
|
|
|
|
|
read_when:
|
|
|
|
|
|
- Deploying OpenClaw to Northflank
|
|
|
|
|
|
- You want a one-click cloud deploy with browser-based setup
|
2026-03-19 11:51:07 -07:00
|
|
|
|
title: "Northflank"
|
2026-01-26 08:07:33 +01:00
|
|
|
|
---
|
|
|
|
|
|
|
2026-01-30 03:15:10 +01:00
|
|
|
|
Deploy OpenClaw on Northflank with a one-click template and finish setup in your browser.
|
2026-01-26 08:07:33 +01:00
|
|
|
|
This is the easiest “no terminal on the server” path: Northflank runs the Gateway for you,
|
|
|
|
|
|
and you configure everything via the `/setup` web wizard.
|
|
|
|
|
|
|
|
|
|
|
|
## How to get started
|
|
|
|
|
|
|
2026-01-31 21:13:13 +09:00
|
|
|
|
1. Click [Deploy OpenClaw](https://northflank.com/stacks/deploy-openclaw) to open the template.
|
|
|
|
|
|
2. Create an [account on Northflank](https://app.northflank.com/signup) if you don’t already have one.
|
|
|
|
|
|
3. Click **Deploy OpenClaw now**.
|
2026-01-26 15:01:10 -08:00
|
|
|
|
4. Set the required environment variable: `SETUP_PASSWORD`.
|
2026-01-30 03:15:10 +01:00
|
|
|
|
5. Click **Deploy stack** to build and run the OpenClaw template.
|
2026-01-26 15:01:10 -08:00
|
|
|
|
6. Wait for the deployment to complete, then click **View resources**.
|
2026-01-30 03:15:10 +01:00
|
|
|
|
7. Open the OpenClaw service.
|
|
|
|
|
|
8. Open the public OpenClaw URL and complete setup at `/setup`.
|
|
|
|
|
|
9. Open the Control UI at `/openclaw`.
|
2026-01-26 08:07:33 +01:00
|
|
|
|
|
|
|
|
|
|
## What you get
|
|
|
|
|
|
|
2026-01-30 03:15:10 +01:00
|
|
|
|
- Hosted OpenClaw Gateway + Control UI
|
2026-03-16 19:50:31 -05:00
|
|
|
|
- Web setup at `/setup` (no terminal commands)
|
2026-01-26 08:07:33 +01:00
|
|
|
|
- Persistent storage via Northflank Volume (`/data`) so config/credentials/workspace survive redeploys
|
|
|
|
|
|
|
|
|
|
|
|
## Setup flow
|
|
|
|
|
|
|
2026-01-31 21:13:13 +09:00
|
|
|
|
1. Visit `https://<your-northflank-domain>/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**.
|
|
|
|
|
|
5. Open the Control UI at `https://<your-northflank-domain>/openclaw`
|
2026-01-26 08:07:33 +01:00
|
|
|
|
|
2026-03-16 19:50:31 -05:00
|
|
|
|
If Telegram DMs are set to pairing, web setup can approve the pairing code.
|
2026-01-26 08:07:33 +01:00
|
|
|
|
|
2026-03-19 11:37:47 -07:00
|
|
|
|
## Connect a channel
|
2026-01-26 08:07:33 +01:00
|
|
|
|
|
2026-03-19 11:37:47 -07:00
|
|
|
|
Paste your Telegram or Discord token into the `/setup` wizard. For setup
|
|
|
|
|
|
instructions, see the channel docs:
|
2026-01-26 08:07:33 +01:00
|
|
|
|
|
2026-03-19 11:37:47 -07:00
|
|
|
|
- [Telegram](/channels/telegram) (fastest — just a bot token)
|
|
|
|
|
|
- [Discord](/channels/discord)
|
|
|
|
|
|
- [All channels](/channels)
|
2026-03-19 11:38:51 -07:00
|
|
|
|
|
|
|
|
|
|
## Next steps
|
|
|
|
|
|
|
|
|
|
|
|
- Set up messaging channels: [Channels](/channels)
|
|
|
|
|
|
- Configure the Gateway: [Gateway configuration](/gateway/configuration)
|
|
|
|
|
|
- Keep OpenClaw up to date: [Updating](/install/updating)
|