Guides·Guide
Get OpenClaw running on your own machine, then understand what changes when you need it in production.
TL;DR
You can install OpenClaw on your own machine in a few minutes: meet the prerequisites, get the project, add a model provider key, connect a channel, and run it.
OpenClaw runs on your own hardware, so you need a machine and a few accounts.
The high-level flow is the same on any machine. Follow the official instructions for the exact commands.
OpenClaw is model-agnostic, so you choose your provider.
Start OpenClaw, send it a goal from your channel, and watch it work: it reasons, calls the skills you enabled, and reports back. For a single personal agent on your own machine, you are done.
Installing one OpenClaw is the easy part. The hard part starts when it has to run unattended, recover when it crashes, survive version updates, and scale to many agents without you babysitting each one. At that point you are operating infrastructure, not running an app.
A managed runtime removes that work: provisioning in seconds, automatic recovery, a versioned filesystem, integrations ready on day one, and safe density so many agents share capacity without crashing. Molted runs OpenClaw this way, so you skip the production setup entirely.
One agent
Easy to babysit.
A fleet, by hand
Q.01
Installing one on your own machine is quick if you meet the prerequisites. Running many reliably in production, with recovery and updates handled, is the hard part.
Q.02
A machine, a model provider key (or a local model), at least one channel to talk to it, and the project's required tooling.
Q.03
Yes. A managed OpenClaw hosting platform runs it for you, with recovery and integrations included, so you skip the setup and the on-call.
Keep reading