Deploy Guard
Where Guard can run, what every install has in common, and which page to read for your platform.
Guard runs where you run it: your laptop, a home server, or a server you rent. We host nothing that holds a key.
The setup below takes what you set on this site (your rules, the account you watched), detects your system, and writes one command to run on the machine where your bot runs (a server over SSH is the other way). Every command matches Guard’s v1.0.2 release. Your key is typed on the machine where Guard runs, never on this page.
The setup journey
Section titled “The setup journey”- Choose the machine where the bot runs. Use the setup below as the main route; it selects a platform-specific command.
- Verify the release. Follow Verify a release before running it.
- Choose your network explicitly. Mainnet setup asks for account confirmation and an equity cap, then leaves activation to you. Choose paper for a rehearsal without orders.
- Connect the bot. Use its integration guide, keeping the client key separate from the API wallet key.
The setup journey
Section titled “The setup journey”- Choose the machine where the bot runs. Use the setup below as the main route; it selects a platform-specific command.
- Verify the release. Follow Verify a release before running it.
- Choose your network explicitly. Mainnet setup asks for account confirmation and an equity cap, then leaves activation to you. Choose paper for a rehearsal without orders.
- Connect the bot. Use its integration guide, keeping the client key separate from the API wallet key.
Your settings from this site
The default rules. Set your own on the playground, or paste a rules code.
- 5× max
- 2% at stop
- no stop: Guard sets one 2% away
- liq. ≥ 10%
- size ≤ 200%
- open ≤ 6%
- daily 6%
- drawdown 25%
- 5/5 markets
- mainnet setup
Markets are set on the playground. Your rules are saved in this browser and used everywhere on this site.
Where Guard runs
Next to your bot: run the command on the machine where your bot runs. If that is a server you reach over SSH, pick “On a server”.
Other ways to run it: On a server (SSH) · AWS cloud · Packages · Docker.
Windows: the native PowerShell installer is not verified for this release yet. Docker Desktop is the other way once its channel is verified.
Guard listens on 127.0.0.1:8547 only, on this machine. Every command here matches the release (zunder-guard v1.0.2).
Ubuntu 24.04 or Debian 12 is best: the key is stored encrypted with systemd-creds. No port is opened; Guard listens on 127.0.0.1:8547.
AWS · Tokyo by default. We create the server and install Guard after you confirm in AWS. Already have a server? Use SSH or Docker on that machine.
On your own account at the platform; we never see the server. Its operators could in principle read Guard's state: use an account holding only what you are willing to lose. Details: AWS deployment.
Your account. Your keys stay with you.
Only public addresses go here. Paper needs no private key; for testnet and mainnet, enter your API wallet key on the machine running Guard.
Which keys will I need?API wallet & optional alerts
For testnet and mainnet. Create an API wallet in the Hyperliquid app: it can trade, it cannot withdraw. Guard asks for its key with hidden input on the server and stores it encrypted for the service. API wallets
A webhook URL is a bearer secret too. Add it on the server, in Guard's config, after the setup. Configuration
Public values: checked in this browser
Preview the guided setupIllustration · not a running Guard
v1.0.2: installation channel unavailable. No installation or activation has run.Selected mode: mainnet. Prepare your public account and rules while publication is verified.
Run this where your bot runs
One command with your rules, on this machine. It installs Guard after checking the release’s signature and asks you the rest here.
Tokyo is preselected; you can change the region in AWS. Your rules and public account address travel with the launch button. Review the permissions and create the stack—Guard installs automatically in paper mode.
AWS bills the server, disk and public IPv4 address. No inbound ports or trading keys. After installation, open the stack’s ConsoleShell output. Complete your selected mode locally; the launch button itself always bootstraps paper.
AWS activation guide →# v1.0.2 installation channel is not published or verified yet.# Selected mode: mainnet. Keep preparing your rules; installation is disabled. Hover or focus a part of the command to see what it does.
Inspect the installer & verify its signature
Every command on this page matches the release (zunder-guard v1.0.2). Prefer to read first? curl -fsSLO https://zunderlabs.com/i && less i, then sh i --rules …. Or verify by hand: Verify a release.
Check it, then point your bot at it
On the machine where Guard runs:
curl -fsS http://127.0.0.1:8547/healthz# {"status":"ok"}: Guard is upcurl -fsS http://127.0.0.1:8547/guard/status# version, mode, network, account and state, read-only What every install has in common
Section titled “What every install has in common”- The command names the network. Mainnet requires your account confirmation, API wallet, equity cap and scoped journal. Paper remains available for a rehearsal (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.
Alternatives to the main setup
Section titled “Alternatives to the main setup”| You have | Read |
|---|---|
| a Mac | macOS machine service, or Homebrew CLI |
| Linux, where your bot runs | the mainnet installer with systemd encrypted credentials (Linux setup) |
| Windows | PowerShell installer and native machine service |
| a server you reach over SSH | One SSH command, run from your computer |
| Docker on native Linux | Encrypted mainnet container supervisor |
| no server yet | AWS · Tokyo by default |
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 matters more than anything Guard does. Guard adds about 3 ms per order; the trip to Hyperliquid is the larger part: 4.5 ms there and back from Tokyo, 238 ms from Frankfurt (medians; Latency). When the account stream is not current Guard reads the account first, one more round trip. Run Guard and your bot in Tokyo (AWS ap-northeast-1), with Guard’s data directory on a local SSD: its decision journal is synced to disk before each order goes out. Zunder’s research treats a host in Tokyo (ap-northeast-1) as next to Hyperliquid (docs/decisions.md, 5 Oct 2026).
Several Guards on one machine
Section titled “Several Guards on one machine”One Guard guards one account. Hyperliquid allows 1,200 of request weight a minute per IP address, and a Guard alone sizes its budgets for all of it. Running several Guards on one machine (or behind one IP address)? Give each ip_share = 1/N, written as a decimal: "0.5" for two, "0.3333" for three (init --ip-share 0.5, or ip_share in guard.toml), every one of them, the first included, so that together they stay within the limit and each keeps a reserve for its own stops and closes (Config keys). Give each its own home and listen port, and start them a few seconds apart.
Guard refuses a share too small to keep it safe: at most three Guards per IP address with the main dex alone, two with one HIP-3 dex, one with two. Your bots’ own calls to Hyperliquid and this site’s browser tools spend the same 1,200, so leave them room.
Where the key lives
Section titled “Where the key lives”Mainnet services keep an encrypted credential on the host and supply the decrypted key to Guard on standard input at every start:
| Installation | Credential and restart owner |
|---|---|
| Linux binary or SSH | systemd-creds, systemd 250 or newer |
| Docker on native Linux | systemd-creds on the host; systemd owns the container lifecycle |
| macOS | System Keychain; system LaunchDaemon with a dedicated Guard child user |
| Windows | Machine-encrypted credential with restricted ACLs; SCM service with a virtual account |
Mainnet has no plaintext-file fallback. Host administrators still control the machine and its processes. Keep the host secure and the API wallet limited to trading, without withdrawal authority.
Paper reads no API wallet key. Testnet has separate per-user storage, described by its setup prompt. Your private API wallet key is entered on the host through hidden input, never in a command argument, a URL or this site.
This page as plain Markdown, for people and LLMs: /docs/deploy.md