Виртуальная машина OpenClaw

Last update: June 11 2026

OpenClaw Virtual Machine is a preconfigured cloud server with a personal AI assistant. This tool allows you to interact with the AI assistant via messengers to perform various tasks and automate workflows.

The image used to deploy the server includes:

• OpenClaw — a personal AI assistant;

• Ollama — a platform for locally downloading and running large language models (LLM);

• Docker — a platform for running containerized applications;

• Docker Compose — a tool for running multi-container applications in Docker;

• nginx — a web server and reverse proxy;

• drivers required for working with graphics processing units (GPU).

Before creating the server, please review the software license agreements included in the image.

Tasks solved

• performing tasks using the AI assistant via messengers and other supported applications;

• collecting, processing, and providing information from various data sources;

• automating workflows and running background tasks.

Minimum resource requirements

vCPU count	2
RAM	8 GB
Boot volume	40 GB
GPU	Required, with at least 24 GB of memory

Create a cloud server with Label Studio

1. In the Control panel, on the top menu, click Products and select AI Marketplace.

2. Click Create server.

3. Fill in the blocks:

   • Name and placement;
   • Source;
   • GPU;
   • Configuration;
   • Disks;
   • Network;
   • optional: Access;
   • optional: Additional settings;
   • optional: Automation.

4. Check the server price.

5. Click Create server.

Name and placement

1. Enter the server name.

2. Select a location where the server will be created. The list of available GPUs depends on the location. You cannot change the location after the server is created.

Source

Select an image OpenClaw VM (Ubuntu 24.04 LTS 64-bit).

GPU

1. Click Add GPU.

2. Select the GPU type. When selecting a GPU, consider the minimum resource requirements for the image. You can see the GPU specifications and description in the Graphics Processing Units (GPU) guide.

3. Specify the number of GPUs.

After the server is created, you will be able to change the type and number of GPUs or remove GPUs. Learn more in the Change Cloud Server Configuration guide.

Configuration

1. Specify the number of vCPUs.

2. Specify the RAM size.

After the server is created, you will be able to change the configuration.

Disks

1. Select the boot disk type. When using a local disk as the boot disk, GPUs are not available.

2. Specify the disk size in GB or TB. The maximum size for all network volumes is 10,240 GB (10 TB), and for a local disk, it is 1,256 GB (1 TB).

3. If you selected the SSD Universal v2 or SSD Fast v2 disk type, specify the total read/write operations in IOPS. After the disk is created, you can change the IOPS value — reduce or increase. There is no limit to the number of IOPS changes.

4. Optional: to add additional server disks:

   4.1. Click Add volume.

   4.2. Select the volume type.

   4.3. Specify the disk size in GB or TB. The maximum size for all network volumes is 10,240 GB (10 TB), and for a local disk, it is 1,256 GB (1 TB).

   4.4. If you selected the SSD Universal v2 or SSD Fast v2 disk type, specify the total read/write operations in IOPS. After the disk is created, you can change the IOPS value — reduce or increase. There is no limit to the number of IOPS changes.

   After the server is created, you will be able to detach additional volumes from it or attach new ones.

Network

You can add the server to a new or existing subnetwork. The subnetwork can be:

• private without internet access. You will not be able to connect to the server from the internet, including via SSH or RDP;
• private with one public IP address. A static public IP address connects to the private server address via a cloud router. The server will be accessible from the internet through this public IP address;
• public, where all addresses are accessible from the internet.

Private subnetwork without internet access

1. To add an existing private subnetwork:

   1.1. In the Subnet field, select an existing subnet.

   1.2. Optional: change the default private IP address of the server.

2. To add a new private subnetwork:

   2.1. In the Subnet field, select the Private subnet type.

   2.2. Optional: change the subnetwork CIDR.

   2.3. Optional: turn on the DHCP switch. Learn more about the DHCP protocol in the Selectel blog article DHCP Protocol Principles.

   2.4. Optional: change the default gateway IP address.

   2.5. Optional: change the network where the subnetwork will be created — you can select an existing network or create a new one. If creating a new network, enter the network name.

Private subnetwork with a public IP address

1. If you already have a private subnetwork and a cloud router with internet access:

   1.1. In the Subnet field, select the Private + 1 public IP subnet type.

   1.2. In the Private field, select an existing subnet.

   1.3. Optional: change the default private IP address of the server.

2. If you do not have a private subnet or a cloud router with internet access, in the Subnet field, select the Private + 1 public IP subnet type.

   A private nat network, a router-nat router, and one public address will be created automatically. The server will be connected to the subnet in the nat network.

Public subnetwork

1. To add an existing public subnetwork:

   1.1. In the Subnet field, select an existing subnet.

   1.2. Optional: change the default public IP address of the server.

2. To add a new public subnetwork:

   2.1. In the Subnet field, select the Public subnet type.

   2.2. In the Subnet size field, select the subnet size.

Optional: Access

1. In the Password for «root» field:

   1.1. Copy the password for the root user — the user with unrestricted system privileges.

   1.2. Save the password in a secure place and do not share it in plain text.

2. Add an SSH key for the project to the server for secure connection:

   2.1. If the SSH key is not added to the cloud platform, click , enter the key name, paste the public key in OpenSSH format, and click Add.

   2.2. If the SSH key is added to the cloud platform, in the SSH key field, select an existing key.

Optional: Additional settings

1. To create a preemptible server, check the Preemptible server checkbox.

2. If you are planning to create several servers and want to increase infrastructure fault tolerance, add the server to a placement group:

   2.1. To create a new group, click , enter the group name and select a placement policy for different hosts:

   • preferred — the system will try to place the servers on different hosts. If no suitable host is available when creating the server, it will be created on the same host;

   • required — servers in the group must be placed on different hosts. If no suitable host is available when creating the server, the server will not be created.

   2.2. If the group is created, in the Placement group field, select a placement group.

3. To provide additional information or filter servers in the list, add server tags. A tag with the image name is added automatically. To add a new tag, in the Tags field, enter the tag.

Optional: Automation

1. To add a script to be executed by the cloud-init agent during the first system boot, in the User data field:

   • open the Text tab and paste the script as text;
   • or open the File tab and upload the script file.

   For examples of scripts and supported formats, see the User data guide.

Launch OpenClaw

1. In the Control panel, go to the top menu, click Products, and select AI Marketplace.

2. In the OpenClaw Virtual Machine card, click Go to GUI.

3. Enter the username — admin.

4. Enter the password — the server UUID. You can copy it in the Control panel: click Products → AI Marketplace in the top menu, then in the server menu, select Copy UUID.

5. Click Login.