Skip to content
Get ProGet Pro

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.

  1. Choose the machine where the bot runs. Use the setup below as the main route; it selects a platform-specific command.
  2. Verify the release. Follow Verify a release before running it.
  3. 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.
  4. Connect the bot. Use its integration guide, keeping the client key separate from the API wallet key.
  1. Choose the machine where the bot runs. Use the setup below as the main route; it selects a platform-specific command.
  2. Verify the release. Follow Verify a release before running it.
  3. 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.
  4. Connect the bot. Use its integration guide, keeping the client key separate from the API wallet key.
stored only in this browser · ·

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
Prepare Guard for
Mainnet setup asks for your account, equity cap and hidden API-wallet key on your machine. Starting it is a separate confirmation. Paper needs no key and sends no orders.

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.

Your system
Detected from this browser; pick another if your bot runs elsewhere.

Guard listens on 127.0.0.1:8547 only, on this machine. Every command here matches the release (zunder-guard v1.0.2).

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.

Public values: checked in this browser

Preview the guided setupIllustration · not a running Guard
this machine · what the setup asks
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.

terminal
# 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.

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
  • 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.
You haveRead
a MacmacOS machine service, or Homebrew CLI
Linux, where your bot runsthe mainnet installer with systemd encrypted credentials (Linux setup)
WindowsPowerShell installer and native machine service
a server you reach over SSHOne SSH command, run from your computer
Docker on native LinuxEncrypted mainnet container supervisor
no server yetAWS · Tokyo by default

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).

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.

Mainnet services keep an encrypted credential on the host and supply the decrypted key to Guard on standard input at every start:

InstallationCredential and restart owner
Linux binary or SSHsystemd-creds, systemd 250 or newer
Docker on native Linuxsystemd-creds on the host; systemd owns the container lifecycle
macOSSystem Keychain; system LaunchDaemon with a dedicated Guard child user
WindowsMachine-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