Deploy to AWS
Launch Guard in your AWS account with Tokyo preselected, your rules prefilled and automatic installation in paper mode.
Your rules. Your server. One launch button.
Section titled “Your rules. Your server. One launch button.”Choose your rules and public account below, then Deploy to AWS. The button opens a prefilled CloudFormation review. Sign in if needed, acknowledge the permissions and create the stack. No template upload or terminal command is needed to provision Guard.
AWS is our cloud deployment route for this release. Already running your bot on another host? Use SSH, Docker or the local installer there. Keep Guard beside your bot to avoid adding a network hop.
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 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 template is source-available in the public Guard repository. The launch link uses an identical versioned S3 copy because AWS quick-create requires an S3 template URL.
Use Deploy to AWS to open AWS’s quick-create review screen in Asia Pacific (Tokyo). The stack bootstraps Guard in paper mode; mainnet credentials and activation stay in your private host shell.
- Sign into your AWS account and review the Tokyo region. The wizard prefills your Rules code and public Hyperliquid Account address; verify them. You can change the region in AWS. No trading or licence key belongs in these fields.
- Review one Graviton instance, 16 GiB encrypted storage, an outbound public IPv4 address, and a dedicated VPC. No NAT gateway is created. AWS bills compute, storage and IPv4 separately. Leave ExposePort set to no; your bot runs on this instance with Guard.
- Acknowledge the IAM role and create the stack. Its role permits Session Manager and reporting this stack’s bootstrap result; it cannot read your Parameter Store values. CREATE_COMPLETE is only reported after installation and a successful Guard health check. Failure or a 20-minute timeout fails the creation.
- Open Outputs → ConsoleShell to connect in your browser. Run Verify. Choose PairPaper for a rehearsal, or follow NextStep for mainnet setup on the host. The shell is AWS Systems Manager; no SSH key or inbound SSH port is needed.
- Complete mainnet activation privately: confirm the account and equity cap, supply the API wallet key through hidden input, activate your plan, explicitly initialize a missing mainnet journal and start the service. Check readiness before starting the bot. A licence changes fee mode, not the network.
For a failed installation, inspect the CloudFormation events; if the instance is preserved, use sudo tail -n 100 /var/log/cloud-init-output.log and sudo journalctl -u zunder-guard in its SSM shell.
Deleting or replacing the instance retains its boot volume to protect Guard’s configuration and journal. A replacement does not automatically reuse that volume. Back up state before changes; when cleaning up a disposable test, delete the stack and then its retained EBS volume, identified by the stack’s name and zunder:stack tag. Retained volumes continue to incur storage charges.
From running server to connected bot
Section titled “From running server to connected bot”A successful provider deployment is the first checkpoint. On the server, check Guard’s health and status, pair your bot to obtain its client key, and configure the bot’s endpoint. Keep client keys in the bot’s own secret storage. Replay or send a paper request and inspect Guard’s decision before changing networks.
For a Pro purchase, get your licence, then follow licence activation. Provisioning a server does not buy or activate a licence. Pay-per-order remains available through setup.
This page as plain Markdown, for people and LLMs: /docs/deploy/one-click.md