c18452598a
* docs: restructure Get Started tab and improve onboarding flow - Flatten nested Onboarding group into linear First Steps flow - Add 'What is OpenClaw?' narrative section to landing page - Split wizard.md into streamlined overview + full reference (reference/wizard.md) - Move Pairing to Channels > Configuration - Move Bootstrapping to Agents > Fundamentals - Move macOS app onboarding to Platforms > macOS companion app - Move Lore to Help > Community - Remove duplicate install instructions from openclaw.md - Mirror navigation changes in zh-CN tabs - No content deleted — all detail preserved or relocated * docs: move deployment pages to install/, fix Platforms tab routing, clarify onboarding paths - Move deployment guides (fly, hetzner, gcp, macos-vm, exe-dev, railway, render, northflank) from platforms/ and root to install/ - Add 'Hosting and deployment' group to Install tab - Slim Gateway & Ops 'Remote access and deployment' down to 'Remote access' - Swap Platforms tab before Gateway & Ops to fix path-prefix routing - Move macOS app onboarding into First steps (parallel to CLI wizard) - Rename sidebar titles to 'Onboarding: CLI' / 'Onboarding: macOS App' - Add redirects for all moved paths - Update all internal links (en + zh-CN) - Fix img tag syntax in onboarding.md
44 lines
1.7 KiB
Markdown
44 lines
1.7 KiB
Markdown
---
|
||
summary: "VPS hosting hub for OpenClaw (Oracle/Fly/Hetzner/GCP/exe.dev)"
|
||
read_when:
|
||
- You want to run the Gateway in the cloud
|
||
- You need a quick map of VPS/hosting guides
|
||
title: "VPS Hosting"
|
||
---
|
||
|
||
# VPS hosting
|
||
|
||
This hub links to the supported VPS/hosting guides and explains how cloud
|
||
deployments work at a high level.
|
||
|
||
## Pick a provider
|
||
|
||
- **Railway** (one‑click + browser setup): [Railway](/install/railway)
|
||
- **Northflank** (one‑click + browser setup): [Northflank](/install/northflank)
|
||
- **Oracle Cloud (Always Free)**: [Oracle](/platforms/oracle) — $0/month (Always Free, ARM; capacity/signup can be finicky)
|
||
- **Fly.io**: [Fly.io](/install/fly)
|
||
- **Hetzner (Docker)**: [Hetzner](/install/hetzner)
|
||
- **GCP (Compute Engine)**: [GCP](/install/gcp)
|
||
- **exe.dev** (VM + HTTPS proxy): [exe.dev](/install/exe-dev)
|
||
- **AWS (EC2/Lightsail/free tier)**: works well too. Video guide:
|
||
https://x.com/techfrenAJ/status/2014934471095812547
|
||
|
||
## How cloud setups work
|
||
|
||
- The **Gateway runs on the VPS** and owns state + workspace.
|
||
- You connect from your laptop/phone via the **Control UI** or **Tailscale/SSH**.
|
||
- Treat the VPS as the source of truth and **back up** the state + workspace.
|
||
- Secure default: keep the Gateway on loopback and access it via SSH tunnel or Tailscale Serve.
|
||
If you bind to `lan`/`tailnet`, require `gateway.auth.token` or `gateway.auth.password`.
|
||
|
||
Remote access: [Gateway remote](/gateway/remote)
|
||
Platforms hub: [Platforms](/platforms)
|
||
|
||
## Using nodes with a VPS
|
||
|
||
You can keep the Gateway in the cloud and pair **nodes** on your local devices
|
||
(Mac/iOS/Android/headless). Nodes provide local screen/camera/canvas and `system.run`
|
||
capabilities while the Gateway stays in the cloud.
|
||
|
||
Docs: [Nodes](/nodes), [Nodes CLI](/cli/nodes)
|