Platform Support Overview for Gateway and Companion Apps
This page covers the platforms supported by OpenClaw Gateway and its companion apps, including macOS, Windows, iOS, Android, and Linux. It also lists VPS and hosting options for deployment.
Read this when
- Looking for OS support or install paths
- Deciding where to run the Gateway
The OpenClaw core is built with TypeScript. Node is mandatory as the runtime since the canonical state store depends on node:sqlite. Bun can still be used for installing dependencies and running package scripts; check Bun.
Companion applications are available for Windows Hub, macOS (a menu bar app), and mobile nodes (iOS and Android). Linux companion apps are on the roadmap, but the Gateway already has full support. On Windows, pick Windows Hub for the desktop experience, a native PowerShell install for terminal-oriented use, or WSL2 for the Gateway runtime most compatible with Linux.
Choose your OS
VPS and hosting
- VPS hub: VPS hosting
- Fly.io: Fly.io
- Hetzner (Docker): Hetzner
- GCP (Compute Engine): GCP
- Azure (Linux VM): Azure
- exe.dev (VM + HTTPS proxy): exe.dev
- EasyRunner (Podman + Caddy): EasyRunner
Common links
- Setup guide: Getting Started
- Windows Hub: Windows
- Gateway operations: Gateway
- Gateway settings: Configuration
- Service health:
openclaw gateway status
Gateway service install (CLI)
Pick any of these (each is supported):
- Wizard (suggested):
openclaw onboard --install-daemon - Direct:
openclaw gateway install - Configure flow:
openclaw configure→ choose Gateway service - Repair or migrate:
openclaw doctor(installs or fixes the service when prompted)
The service type depends on the OS:
- macOS: LaunchAgent (
ai.openclaw.gateway, orai.openclaw.<profile>for a named profile) - Linux or WSL2: systemd user service (
openclaw-gateway[-<profile>].service) - Native Windows: Scheduled Task (
OpenClaw GatewayorOpenClaw Gateway (<profile>)), with a per-user Startup folder login item as a fallback when task creation is blocked