One SSH command
Install Guard on a Linux server with one SSH command that checks the installer's signature first, then sets it up with your rules. The key is typed on the server, never here.
One command from your computer: it connects to your server, installs Guard after checking its signature, and walks you through the setup there. Your key is typed into the server, with hidden input, and never into a command line, a URL or this page.
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”.
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 from your computer
One command with your rules. It connects to your server, installs Guard after checking its signature, and asks you the rest there.
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 Use this alternative for a machine you already reach over SSH. For choosing the host and the complete activation sequence, start with the setup journey.
What the command does
Section titled “What the command does”- The loader (
installation channel pending verification) downloadsinstall.sh,SHA256SUMSand the Sigstore bundle of that release. It verifies the bundle (signed by Guard’s release workflow on GitHub, for exactly that tag) and checksinstall.shagainst the signed checksums. A mismatch stops it before anything runs. Withoutcosignon the server it fetches a pinnedcosignand checks its SHA-256 first. - The installer checks again: the signature, then the release archive for the server’s architecture (x86-64 or ARM64) against the signed checksums, and only then extracts it.
- It creates a system user
zunder-guardwith no login shell and a state directory readable only by that user, and installs the binary. - The setup is Guard’s own (
zunder-guard init --interactive): it shows your rules in plain words and asks to keep or edit them, then the account address and mode. The mainnet command selects--network mainnet; setup still requires separate account confirmation and a trading-equity cap. Choose--network paperfor rehearsal. - For testnet or mainnet it asks for the API wallet key with hidden input. The key is read, never echoed, never put on a command line or into the environment, checked with
zunder-guard key check, and stored withsystemd-creds: encrypted, and decrypted only for the service when it starts, which hands it to Guard on standard input. For testnet on systemd older than 250 it falls back to a file readable only by Guard’s user, and says so. Mainnet has no fallback: withoutsystemd-creds(or without a systemd service) the installer refuses mainnet before it writes anything. - It installs the hardened systemd unit on
127.0.0.1:8547with the selected network. A fresh mainnet setup without a journal leaves the service stopped and prints the exact commands for its account and service home. Rerunning guided setup against an existing mainnet journal can restart the service, so keep bots stopped; use--install-onlyfor a binary-only upgrade. Explicitly initialize a missing mainnet journal, activate your plan and start the service when ready. Do not recreate an existing journal or resume a halt as an installation step.
The mainnet command is:
ssh -t user@your-server 'curl -fsSL https://zunderlabs.com/i | sh -s -- --network mainnet'Installation for this channel is unavailable until its signed publication is verified. Prepare your rules in the setup wizard.
Keep the bot stopped until /healthz succeeds and /guard/status shows the intended account, mainnet network, risk state and fee mode. Follow the printed management commands for pairing, configuration and upgrades. Use the service’s home, not your SSH user’s default home. Installation opens no public port.
Prefer to verify by hand
Section titled “Prefer to verify by hand”Skip the loader and run the same checks yourself, on the server (needs cosign):
V=v1.0.2; R=https://github.com/zunderlabs/zunder-guard/releases/download/$Vcurl -fsSLO "$R/install.sh" -O "$R/SHA256SUMS" -O "$R/SHA256SUMS.sigstore.json"cosign verify-blob --bundle SHA256SUMS.sigstore.json \ --certificate-oidc-issuer https://token.actions.githubusercontent.com \ --certificate-identity "https://github.com/zunderlabs/zunder-guard/.github/workflows/release.yml@refs/tags/$V" \ SHA256SUMSsha256sum --ignore-missing -c SHA256SUMS && sh install.sh --network mainnet --rules zr1_…Verified OK means the checksums were signed by Guard’s release workflow on GitHub, for that tag. Then read install.sh; it is short on purpose. More: Verify a release.
Terminal and existing installations
Section titled “Terminal and existing installations”Use ssh -t so the guided installer can ask for account confirmation and hidden key input. For unattended deployment, use the AWS paper bootstrap and activate mainnet privately on the host afterwards. Never put the API wallet key in an SSH argument or environment variable.
Stop bots before reconfiguration or upgrades. Preserve the service home, licence, pairings and journals, and follow the installer’s explicit replacement warning if changing an existing paper setup to mainnet. A failed mainnet setup remains stopped. Complete activation.
This page as plain Markdown, for people and LLMs: /docs/deploy/ssh.md