Clear setup
A simpler starting point
Begin with docs and setup steps that are designed to be followed by a whole team, not just the person who found them first.
Self-host OpenClawwith a clearer setuppath for your team
Easy Claw helps teams get OpenClaw running with practical docs, a clearer setup path, and straightforward guidance on what they still manage themselves.
The problem
OpenClaw gets harder to adopt when setup knowledge lives in scattered notes and handoffs.
Teams rarely struggle because the runtime is too complex. They struggle because the setup steps, infrastructure assumptions, and upgrade guidance are spread across too many places.
One person gets the first install working, but the next teammate has to piece together how it was done.
Host, secrets, storage, and networking decisions are easy to miss when they only live in chat threads or shell history.
Support gets slower when docs, issues, and release notes tell slightly different versions of the same story.
Upgrades feel riskier when there is no simple starting point the team can come back to.
Why Easy Claw
A clearer way to self-host OpenClaw.
Easy Claw gives technical teams a simpler way to evaluate, set up, and maintain OpenClaw without relying on guesswork.
What you still manage
Clear team expectations
Make it obvious where Easy Claw helps and where your team still owns the host, secrets, storage, and network choices.
Less repeated work
Better handoffs
Keep docs, releases, and issue history close together so the next teammate is not starting from scratch.
OpenClaw-focused
Made for OpenClaw
The project stays focused on helping teams run OpenClaw well before expanding into anything else.
How it works
Three steps from first look to first deployment.
Start with the docs, choose the release you want, then follow a setup path your team can reuse.
Read the docs
Get familiar with the setup path, system expectations, and the basics before you start changing shared infrastructure.
Open docs homeChoose a release
Check the release notes and download guidance so your team knows exactly what version it plans to run.
Review releasesFollow the setup path
Use the recommended docs to move from first install to a repeatable team setup without piecing it together from scattered notes.
Read getting startedOpen source
Code, docs, releases, and issues all live in one place.
FAQ
Common questions before you self-host.
Straight answers for teams deciding whether Easy Claw fits their setup.
What runtime is supported right now?
OpenClaw is the supported runtime right now.
Is Easy Claw a hosted service or managed control plane?
No. Easy Claw is an independent open-source project. You run the software, the runtime, and the surrounding infrastructure on systems you control.
Where do I find the canonical docs?
The docs live in Markdown in the repository under `docs/`.
How do I check a download before I run it?
Start with the GitHub release you chose, then follow the verification guide for that version.
Where should bug reports and feedback go?
GitHub Issues is the default public intake path. That keeps requests visible, searchable, and tied to the code and docs they affect.
What does my team still need to manage?
Your team is still responsible for the host, access controls, secrets, storage, network policy, backups, incident response, and any decision to roll a change into a shared or production environment.
See it in public
See the project, read the docs, and decide if Easy Claw fits your setup.
If it looks right for your team, head to GitHub, read the docs, choose a release, and start with the recommended setup path.