Introduction
What clawops is, and what it leaves to OpenClaw.
clawops provisions and operates self-hosted OpenClaw on AWS, GCP, Azure or any Linux box you can reach over SSH.
It owns the layer between "I want an agent" and "an agent is running": the VM, the firewall, the container, secrets, health checks and the upgrade path. It does not author your agents, that is OpenClaw's job.
The shape of it
Plans you read before they run
clawops plan emits a JSON artifact you review, diff and commit. clawops apply executes
exactly that. Nothing reaches your cloud account straight from a natural-language instruction.
Pulumi handled for you
clawops installs the CLI it needs on first use, generates its own state passphrase, and checks your state bucket exists before a deploy can fail on it.
Typed MCP tools
Every operation is a tool with explicit safety annotations, so a coding agent knows what is read-only, what is destructive, and what needs confirmation.
Known limits
Single-node, no TLS automation, no cost estimation.
Before you start
This line requires OpenClaw 2.0
clawops 2.x deploys OpenClaw >= 2026.9.2 and refuses anything older. For OpenClaw
<= 2026.7.1-2, use npm install -g @clawops/cli@legacy. Coming from 1.x?
clawops migrate moves an existing deployment across, keeping its state and device identity.
See OpenClaw compatibility.
Where things live
These pages cover using clawops. Design decisions, ADRs and the project roadmap live in
docs/ in the repository. They are written
for contributors rather than operators.