Skip to content
Get ProGet Pro

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.

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

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.

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
your server · 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 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.

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

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.

  1. The loader (installation channel pending verification) downloads install.sh, SHA256SUMS and the Sigstore bundle of that release. It verifies the bundle (signed by Guard’s release workflow on GitHub, for exactly that tag) and checks install.sh against the signed checksums. A mismatch stops it before anything runs. Without cosign on the server it fetches a pinned cosign and checks its SHA-256 first.
  2. 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.
  3. It creates a system user zunder-guard with no login shell and a state directory readable only by that user, and installs the binary.
  4. 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 paper for rehearsal.
  5. 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 with systemd-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: without systemd-creds (or without a systemd service) the installer refuses mainnet before it writes anything.
  6. It installs the hardened systemd unit on 127.0.0.1:8547 with 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-only for 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:

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.

Skip the loader and run the same checks yourself, on the server (needs cosign):

Terminal window
V=v1.0.2; R=https://github.com/zunderlabs/zunder-guard/releases/download/$V
curl -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" \
SHA256SUMS
sha256sum --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.

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