OpenClaw logo
Automation & AI

OpenClaw Hosting on Your Own VPS

A private AI agent instance with its own sandbox and persistent memory, on hardware you control.

Size a server for OpenClaw

Every stop is a real configuration you can deploy. Priced per month and billed monthly, exclusive of 18% GST.

4 vCPU
2 vCPU $3.93 a month 64 vCPU
8 GB
4 GB $3.93 a month 128 GB
80 GB
20 GB $3.02 a month 2000 GB

What OpenClaw is

OpenClaw is a self-hosted AI agent. It runs autonomously against tasks you give it, keeps memory between sessions, and uses a browser sandbox to reach the web — which makes it materially different from a chat interface, and materially different to host.

The defining characteristic for hosting purposes is that agent workloads execute code and make outbound network requests that you did not write in advance. That is the whole point of an agent, and it is also why a dedicated instance matters: you want that activity in an environment where it cannot reach anything else you care about.

Model access is separate. OpenClaw calls model APIs with your own keys, so inference is billed by whichever provider you use, not by the server. The VPS runs the agent, its memory store and its sandbox — not the model.

“OpenClaw is an open-source AI assistant that runs on your own computer and meets you in the channels you already use.”

— OpenClaw, on GitHub

Why run OpenClaw on a VPS

A dedicated instance, so agent activity is isolated from anything else you run.

Your model keys stay in your own environment.

Persistent storage for agent memory across restarts.

Root access and firewall control, which matter more than usual for a workload that makes its own outbound requests.

A backup taken before a version change, so an upgrade is reversible - nightly whole-server backups are a paid add-on, and you can take one by hand first.

OpenClaw features

Autonomous task execution with persistent memory

Browser sandbox for web access

Bring your own model provider keys

Isolated environment with no shared tenancy

Backup and one-click restore around version changes (paid add-on)

Custom domain with TLS

OpenClaw hosting requirements

The recommended starting point for OpenClaw, not a hard floor — size it on the sliders.

Memory8 GB — the browser sandbox is the memory-hungry part
CPU4 vCPU for responsive sandbox sessions
Storage80 GB for memory, artefacts and local backups
Operating systemUbuntu 22.04 or 24.04 LTS
Installs onUbuntu 24.04 LTS, Ubuntu 22.04 LTS, Debian 13 (Trixie), Debian 12 Bookworm, AlmaLinux 9, AlmaLinux 8, Rocky Linux 9, Rocky Linux 8
Ready inAbout 20 minutes
Smallest server2 vCPU · 4 GB memory · 20 GB disk

How deployment works

OpenClaw is installed on the instance with its browser sandbox and a persistent store for agent memory, behind TLS on your own domain. You supply model provider keys after handover. Because agent workloads run arbitrary code and reach the open internet, our acceptable use policy applies from the moment the instance starts.

It is your server. OpenClaw is installed directly on your VPS or VDS, not inside a container we manage. You get root over SSH, you can install anything alongside it, change its configuration, or remove it entirely. We do not hold a key to it.

What people run it for

Research and monitoring

Long-running tasks that watch sources and report, without a person driving each step.

Private automation

Agent workflows over data you would not send to a hosted agent service.

Development and evaluation

A disposable instance for testing agent behaviour, backed up and rolled back.

Team tooling

An internal agent behind your own domain and access controls.

OpenClaw hosting questions

A VPS running your own OpenClaw instance, with its memory, sandbox and configuration on a server you control rather than in a shared service.

Deploy OpenClaw on your own server

Root access, your choice of size, and no container between you and the application.