Deploy OpenClaw

OpenClaw is a self-hosted AI assistant that can be deployed on a cloud server. Unlike traditional chatbots, OpenClaw not only responds to requests but can also perform real actions: send messages, process data, work with files, and interact with external services.

You can interact with OpenClaw through messaging platforms, or directly via API or the command line.

Creating a Server

To run OpenClaw, create a server with an appropriate configuration in the control panel.

1. Go to Cloud Servers.
2. Click Create server.
3. Choose the region where the server will be deployed.
4. In the next step, open the Marketplace tab and select the OpenClaw image.

5. Select the server configuration. We recommend the following specifications:

• • 4 CPU cores
  • 8 GB RAM
  • 160 GB NVMe storage

6. Configure the remaining parameters (you can leave them unchanged).
7. Click Create server.

Server Setup

After the server is created, complete the initial OpenClaw configuration.

Connect to the server via SSH. The connection details (IP address, username, password, or SSH key) are available in the server control panel on the Dashboard tab.

When you log in for the first time, the OpenClaw setup wizard starts automatically. If it does not start or was closed, you can launch it manually:

openclaw onboard

Then follow these steps:

1. Review the disclaimer and accept the terms by selecting Yes.
2. In Onboarding mode, choose QuickStart.
3. In Model/auth provider, select your API key provider.
4. In Filter models by provider, choose All providers.
5. Leave Default model unchanged.
6. At Select channel (QuickStart), you can configure a messaging platform. See the instructions below to connect Telegram at this point.
7. At Configure skills now?, select No.
8. At Enable hooks?, choose Skip for now (press Space, then Enter).
9. At How do you want to hatch your bot?, select Do this later.

Connecting Telegram

To interact with OpenClaw via Telegram, you need to create your own bot and obtain an API key. This can be done using the official Telegram bot @BotFather.

In Telegram:

1. Open @BotFather and start a conversation.
2. Run the /newbot command.
3. Enter a bot name (this will be displayed in chats).
4. Enter a unique username that must end with bot (for example, openclaw_hostman_bot).

After completing these steps, BotFather will generate an API key. This key is required to integrate the Telegram bot with OpenClaw.

Return to the OpenClaw setup wizard. At Select channel (QuickStart):

• Choose Telegram
• Paste the API key you received

Complete the setup and start a conversation with your bot by sending:

/start

The bot will reply with a pairing code.

On the server, run:

openclaw pairing approve telegram <code>

Replace <code> with the pairing code you received from the Telegram bot.

Once approved, the bot is ready to use. You can send commands and interact with the agent directly through Telegram.

Web Interface

The web interface can be used to interact with the agent and manage its operation. Through it, you can communicate with the bot, check active sessions and their status, manage access tokens, and perform basic configuration. The interface is intended for administration and debugging and is not designed for public internet access.

To access the web interface, run the following command after connecting to the server via SSH:

openclaw dashboard

You will receive output similar to:

🦞 OpenClaw 2026.2.3-1 (d84eb46) — I keep secrets like a vault... unless you print them in debug logs again.

Dashboard URL: http://127.0.0.1:18789/?token=c6aaee5ae1fd9a7925892f4738f37deb01d2bd13d0c11199
Copy to clipboard unavailable.
No GUI detected. Open from your computer:
ssh -N -L 18789:127.0.0.1:18789 root@147.45.148.206
Then open:
http://localhost:18789/
http://localhost:18789/?token=c6aaee5ae1fd9a7925892f4738f37deb01d2bd13d0c11199
Docs:
https://docs.openclaw.ai/gateway/remote
https://docs.openclaw.ai/web/control-ui

This command is used to generate a token. You will need the value from the Dashboard URL line.

By default, the web interface is available only locally on the server and is not accessible externally. For remote access, it is recommended to use an SSH tunnel. On your local machine, run:

ssh -N -L 18789:127.0.0.1:18789 root@server_IP

After establishing the connection, open the URL obtained earlier in your browser:

http://127.0.0.1:18789/?token=c6aaee5ae1fd9a7925892f4738f37deb01d2bd13d0c11199