Deploy Guard
Guard runs where you run it: your laptop, a home server, or a server you rent. We host nothing that holds a key.
What every install has in common
Section titled “What every install has in common”- It starts in paper mode. Real prices, no orders sent. Testnet next. Mainnet only when you type it (Paper, testnet and mainnet).
- It listens on localhost only (
127.0.0.1:8547) unless you configure otherwise. - It talks to Hyperliquid only. The relay and telemetry are off unless you turn them on (Network footprint).
- Every release can be verified before you run it (Verify a release).
- The API wallet key is created by you in the Hyperliquid app and given to Guard on your machine. It never passes through us.
Pick a page
Section titled “Pick a page”| You have | Read |
|---|---|
| a Mac | Homebrew |
| Windows | winget |
| Linux, or a server over SSH | One SSH command |
| Docker anywhere | Docker |
| no server yet | One-click templates |
filled in from your settings ·
Where it should run
Section titled “Where it should run”Next to your bot. Guard listens on localhost, so the bot and Guard belong on the same machine, or in the same private network.
Close to Hyperliquid helps a little, not a lot. Guard’s own work takes about 0.07 ms per order (Latency); the network to Hyperliquid is the larger part. Zunder’s research treats a host in Tokyo (ap-northeast-1) as next to Hyperliquid (docs/decisions.md, 5 Oct 2026).