54147929d9
Rename GCP to Google Cloud and standardize all 6 VPS docs to follow a consistent structure: Goal, Prerequisites, Quick Path, Step-by-step, Persistence, Cost, Troubleshooting, See Also. Changes: - Rename gcp.md to google-cloud.md with redirects - Add all 6 VPS platforms to navigation (alphabetical order) - Standardize section headings across all docs - Add missing sections (Cost, Troubleshooting, See Also) where needed - Keep existing detail levels and friendly variants preserved
1.7 KiB
1.7 KiB
| summary | read_when | ||
|---|---|---|---|
| VPS hosting hub for Moltbot (Oracle/Fly/Hetzner/GCP/exe.dev) |
|
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
- Northflank (one‑click + browser setup): Northflank
- Oracle Cloud (Always Free): Oracle — $0/month (Always Free, ARM; capacity/signup can be finicky)
- Fly.io: Fly.io
- Hetzner (Docker): Hetzner
- Google Cloud (Compute Engine): Google Cloud
- exe.dev (VM + HTTPS proxy): 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, requiregateway.auth.tokenorgateway.auth.password.
Remote access: Gateway remote
Platforms hub: 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.