How to install OpenClaw on a VPS and get it running in minutes

On Windows, execution is done from PowerShell with the corresponding script:

Once it finishes, continue with the full onboarding. The key command is:

This command configures the model provider, authentication, Gateway, and background service in a single walkthrough. The onboarding documentation indicates that this flow usually takes around two minutes: https://docs.openclaw.ai/start/onboarding-overview.

Alternative installation for advanced users

If you do not want to use the automatic installer, the official documentation also covers installation through package managers and from source. According to the repository’s installation index, OpenClaw can be installed with npm, pnpm, and bun, as well as built from a Git clone: https://github.com/openclaw/openclaw/blob/main/docs/install/index.md.

The practical difference between install.sh and install-cli.sh is isolation. The general installer is intended to make startup easier on the current system. By contrast, install-cli.sh keeps OpenClaw and Node under a local prefix, which is useful if you do not want to touch a global Node installation or if you manage multiple environments on the same machine: https://github.com/openclaw/openclaw/blob/main/docs/install/index.md.

What OpenClaw onboarding actually does

Onboarding is not a decorative form: it is the part that turns an installed CLI into a usable agent. The documentation states that it configures the model provider and its authentication, the workspace, the Gateway, optional channels, and the daemon: https://docs.openclaw.ai/start/onboarding-overview.

In practical terms, during this step you decide which AI provider OpenClaw will communicate with, where it will work, how it will expose or keep the Gateway active, and whether it will run as a background service. If your use case requires messaging channels, such as a flow connected to Telegram or WhatsApp, treat them as optional extensions that you should activate only if they appear available and supported in your installation.

For a server, the most important flag is --install-daemon. Without the daemon, you can run OpenClaw interactively, but you will depend more on the active session. With the daemon, the process is prepared to work as a service, which makes more sense on a VPS or dedicated server.

Verification after installation

Do not consider the installation complete until you run the basic checks. The documentation recommends validating the version, general status, and Gateway with these commands: https://github.com/openclaw/openclaw/blob/main/docs/install/index.md.

openclaw --version confirms that the CLI is available. openclaw doctor reviews the configuration and helps detect environment issues. openclaw gateway status tells you whether the Gateway is active, which is a critical check if you expect OpenClaw to receive or process requests.

Common issues

• The openclaw command does not appear: check Node, the global prefix, and the PATH, as suggested by the official guide.

• Onboarding does not finish: confirm that the model provider API key is valid and that authentication was completed.

• The Gateway does not respond: run openclaw gateway status and then openclaw doctor to isolate whether the issue is related to the service, configuration, or environment.

• Windows creates friction: try native Windows if your environment is ready; if you manage Linux tools or server dependencies, WSL2 may be a more convenient path.

OpenClaw on a VPS: when it makes sense

Installing OpenClaw locally is useful for learning, reviewing the CLI, or testing a model provider. But if you want continuous availability, less dependence on your personal machine, and an environment closer to production, a VPS for OpenClaw is usually the logical option.

On a VPS, you can control resources, networking, location, and persistence. You also reduce the risk of the agent stopping because you closed your laptop, your local network changed, or you restarted a development session. If you also need to evaluate CPU, RAM, NVMe storage, or connectivity, you can review Teramont’s Hardware page to better understand the available infrastructure.

Fast alternative: preconfigured VPS for OpenClaw

If your priority is to get OpenClaw running without manually installing dependencies or logging in through SSH just to start the service, Teramont offers a specific OpenClaw Hosting option. The page indicates automatic configuration, deployment in under 60 seconds, NVMe storage, 1 Gbps network, DDoS protection, and 24/7 support: https://teramont.net/es/openclaw-hosting.

This path fits when you need to validate an idea, deliver an environment to a team, or prevent manual installation from becoming the bottleneck. Instead of preparing Node, checking PATH, running installers, and configuring the service, you start from an instance designed for OpenClaw from the beginning.

Also, if you already have a local instance or one on another server, the same page indicates that you can migrate it to the VPS and get assistance from the team to move configuration, memory, and skills: https://teramont.net/es/openclaw-hosting.

Which path to choose

Choose manual installation if you want to learn each component, debug errors, customize the installed version, or work from source. It is the best option for understanding how the CLI, Gateway, daemon, and model provider connect.

Choose a preconfigured VPS if the goal is to have OpenClaw available quickly, with fewer operational steps and a more production-ready foundation. As a final checklist: install or deploy the instance, complete onboarding, validate with openclaw doctor, check openclaw gateway status, connect only the channels you need, and scale infrastructure when usage justifies it.