Platforms
Platforms
OpenClaw itself is best run on Node, usually on macOS, Linux hosts or Windows through WSL2. Mobile clients and macOS companion apps focus on nodes, Canvas, voice, menu bar workflows and other assistive interactions.
Operating Systems and Devices
macOS
A strong fit for the CLI, Gateway and companion app together. Only prepare Xcode / CLT if you actually plan to build the app.
Linux
Excellent for always-on Gateway deployments, usually with systemd user services or your own service manager.
WSL2
Run the Gateway and CLI inside WSL2 instead of a native Windows runtime whenever possible.
iOS / Android nodes
These handle Canvas, camera, voice and mobile interaction, but they are not the primary always-on Gateway host.
VPS and Hosting Guidance
When to move to a VPS
A VPS is the right choice when you want the Gateway online 24/7, multiple channels connected at once, remote access or clear separation between worker nodes and chat entry points.
How to install services
Prefer openclaw onboard --install-daemon. If you already have config, openclaw gateway install or openclaw configure can add the service later.
Linux lingering
With systemd user services, processes may stop after logout. Run sudo loginctl enable-linger $USER when needed.
Remote access
Prefer Tailscale or a VPN. SSH tunnels are the next choice when you need to map 127.0.0.1:18789 back to the remote Gateway.