mirror of
https://github.com/hanzoai/bot.git
synced 2026-10-30 17:24:26 +00:00
zeekay
4bdc9ee3e4
Comprehensive rename of all openclaw references to hanzo-bot equivalents: - Package: openclaw → @hanzo/bot - Binary: openclaw → hanzo-bot - Types: OpenClaw* → Bot* - Env vars: OPENCLAW_* → BOT_* - Android: ai.openclaw.android → ai.hanzo.bot.android - iOS/macOS: ai.openclaw.* → ai.hanzo.* - Swift modules: OpenClaw* → Bot* - Plugins: openclaw.plugin.json → bot.plugin.json - Paths: .openclaw/ → .hanzo/bot/ - URLs: github.com/openclaw → github.com/hanzoai
1.8 KiB
1.8 KiB
summary, read_when, title
| summary | read_when | title | ||
|---|---|---|---|---|
| VPS hosting hub for Hanzo Bot (Oracle/Fly/Hetzner/GCP/exe.dev) |
|
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
- 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
- GCP (Compute Engine): GCP
- 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.