Quickstart in paper mode
Install Guard, load your rules, and point a bot at it in paper mode. Paper mode uses Hyperliquid's real prices and sends no orders.
Paper mode is the rehearsal path you can choose before enabling real orders. It reads Hyperliquid’s real prices and your real account, judges every order with the same rules, and records what it would have done. It sends nothing to Hyperliquid’s /exchange endpoint.
1. Install and set up, with your rules
Section titled “1. Install and set up, with your rules”Run Guard on the machine where your bot runs: the setup detects your system (macOS, Linux, Windows or Docker). A server you reach over SSH is the other way. The setup carries the rules you set on this site (Backtest, Watch or the homepage), stored in your browser as a rules code that starts with zr1_; otherwise the defaults. Select paper in the setup below for this walkthrough. Mainnet setup is a separate explicit choice with host activation steps.
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 The default rules are: 5x leverage, 2% loss at the stop, no stop: Guard sets one 2% away, liquidation at least 10% away, a position at most 200% of equity, 6% open risk, 6% daily loss stop, 25% drawdown halt, all markets. The format is on Rules codes.
The setup prints a client key for your bot. The client key is not your API wallet key. Hyperliquid does not accept it. Only your Guard does. Guard listens on http://127.0.0.1:8547, on your machine only.
2. Point your bot at Guard
Section titled “2. Point your bot at Guard”One setting changes: the API URL. The private key becomes the client key the setup printed.
from eth_account import Accountfrom hyperliquid.exchange import Exchange
client_key = Account.from_key("0x...") # the client key Guard printedexchange = Exchange(client_key, base_url="http://127.0.0.1:8547", account_address="0xYourAccountAddress")filled in from your settings ·
Guides for ccxt, Freqtrade, the TypeScript SDK, MCP and TradingView are under Integrations.
3. Confirm paper mode, then send a request
Section titled “3. Confirm paper mode, then send a request”First check /guard/status reports "mode":"paper". Only then send one order your bot would normally send. In paper mode the answer your bot gets says what Guard would have done: Zunder Guard paper mode: would resize [resized]: … (nothing was sent). To see Guard’s state and its decisions:
curl -s http://127.0.0.1:8547/guard/status # mode, risk state, positions, alertscurl -s 'http://127.0.0.1:8547/guard/events?since=0' # every decision, with its rule and codeYou see the decision (allow, resize or veto), the rule that decided, and what would have been sent. Nothing reached Hyperliquid, because this is paper mode. The fields are listed in Events.
Using Pro
Section titled “Using Pro”If you bought Pro, activate the emailed licence and verify its status on this installation. You can check activation in paper mode before changing networks.
Choose your next network
Section titled “Choose your next network”- Testnet sends orders with test funds. Use it to check exchange execution and resting stops.
- Mainnet uses real funds. The mainnet installer sets up a managed service on macOS, Windows, Linux systemd or Docker on native Linux. Account confirmation, API wallet, equity cap, journal admission and explicit start remain required.
AWS provisions in paper mode first; use its private host shell for activation. Guard never promotes a paper or testnet installation automatically. Keep this rehearsal’s state separate from your mainnet journal.
This page as plain Markdown, for people and LLMs: /docs/start/quickstart.md