<!-- https://zunderlabs.com/docs/deploy · Markdown version of the page -->

# Deploy Guard

Where Guard can run, what every install has in common, and which page to read for your platform.

:::note[Planned]
Guard has no release yet. Every command, image name, package name and template in this section is the plan for Guard 1.0. The GitHub organisation (`zunderlabs`), the image (`ghcr.io/zunderlabs/zunder-guard`) and the package names are planned names, not published ones.
:::

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), asks where Guard should run, and writes one command. Your key is typed on the machine where Guard runs, never on this page.

With the default rules (the page fills in your own, and asks where Guard runs):

```sh
ssh -t you@your-server "curl -fsSL https://zunderlabs.com/i | sh -s -- --rules zr1_eyJ2IjoxLCJtYXhMZXZlcmFnZSI6NSwibWF4TG9zc0F0U3RvcFBjdCI6Miwic3RvcFBvbGljeSI6ImF0dGFjaCIsImRlZmF1bHRTdG9wRGlzdGFuY2VQY3QiOjIsIm1pbkxpcURpc3RhbmNlUGN0IjoxMCwibWF4UG9zaXRpb25QY3QiOjIwMCwibWF4T3BlblJpc2tQY3QiOjYsImRhaWx5TG9zc1N0b3BQY3QiOjYsImRyYXdkb3duSGFsdFBjdCI6MjUsIm1hcmtldHMiOlsiKiJdfQ"
```

The API wallet key is typed on the server into Guard's hidden prompt; it is never part of a command.

## What every install has in common

- **It starts in paper mode.** Real prices, no orders sent. Testnet next. Mainnet only when you type it ([Paper, testnet and mainnet](https://zunderlabs.com/docs/concepts/networks)).
- **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](https://zunderlabs.com/docs/deploy/network-footprint)).
- **Every release can be verified** before you run it ([Verify a release](https://zunderlabs.com/docs/deploy/verify)).
- **The API wallet key is created by you** in the Hyperliquid app and given to Guard on your machine. It never passes through us.

## Pick a page

| You have | Read |
|---|---|
| a Mac | [Homebrew](https://zunderlabs.com/docs/deploy/packages) |
| Windows | [winget](https://zunderlabs.com/docs/deploy/packages) |
| Linux, or a server over SSH | [One SSH command](https://zunderlabs.com/docs/deploy/ssh) |
| Docker anywhere | [Docker](https://zunderlabs.com/docs/deploy/docker) |
| no server yet | [One-click templates](https://zunderlabs.com/docs/deploy/one-click) |

## 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 helps a little, not a lot. Guard's own work takes about 0.07 ms per order ([Latency](https://zunderlabs.com/docs/methods/latency)); the network to Hyperliquid is the larger part. Zunder's research treats a host in Tokyo (`ap-northeast-1`) as next to Hyperliquid (`docs/decisions.md`, 5 Oct 2026).

## Where the key lives

:::note[Planned]
How Guard 1.0 stores the API wallet key, per install (`deploy/guard/README.md`):
:::

- **A Linux server (the SSH command):** encrypted with `systemd-creds` (systemd 250 or newer: Ubuntu 24.04, Debian 12 and later), with the host key and the TPM where there is one. systemd decrypts it only when it starts the service, into memory only the service can read. A copy of the disk without the host key is useless. Root on the running machine can still read it, as root can read any process's memory. On older systemd: a file readable only by Guard's own user, and the installer warns.
- **Docker:** a file in the volume, mode 0600, owned by the container's user.
- **macOS and Windows:** the system keychain.

Everywhere: the key belongs to an API wallet that can trade but cannot withdraw, on an account that holds only what you are willing to risk. It is typed into Guard's hidden prompt, never into a command line, a URL or this site.