<!-- https://zunder-design-preview.pages.dev/docs/start/licence · Markdown version of the page -->

# Activate your Pro licence

From purchase and emailed key to an account-bound, offline-verified Pro licence in Guard.

## 1. Buy for the accounts you will use

[Choose a Pro plan](https://zunder-design-preview.pages.dev/pricing) and enter the **public Hyperliquid account addresses** Guard will protect. These are the main accounts or sub-accounts, not their API wallet addresses. Your licence is bound to those addresses.

Checkout shows the USDC payment instructions and quote expiry. Keep its recovery link until delivery. Payment confirmation and licence delivery are separate steps: wait for the signed key email before configuring Guard. Your term starts when we send the key; an early renewal keeps the remaining paid term.

## 2. Put the emailed key in Guard's config

**Finish your intended network setup first.** Re-running guided setup with `--force` replaces the config and can remove a previously installed licence. After any such reconfiguration, reinstall the key and verify `fee.mode` before starting your bot. You can activate Pro in paper mode now; repeat this check when moving to mainnet.

Stop Guard using the same service manager you used to start it. Open its existing `guard.toml` and add or replace the **top-level** `licence` value, before the first `[section]` heading:

```toml
licence = "zgl1_PASTE_THE_COMPLETE_EMAILED_KEY"
```

For a Linux service installed by our installer, the config is `/var/lib/zunder-guard/guard.toml`. For Docker it is in the persistent `/data` volume. On other installs, use the config path printed during setup. Keep the whole key on one line inside quotes. Preserve the account, network, rules, journal and client keys.

Start Guard again with the same service configuration. For the Linux installer:

```sh
sudo systemctl restart zunder-guard
```

For Docker, edit the config in the existing volume and restart the existing container. Do not create a fresh volume: it contains your config and journals.

## 3. Verify activation locally

On the machine running Guard:

```sh
curl -fsS http://127.0.0.1:8547/healthz
curl -fsS http://127.0.0.1:8547/guard/status
```

Look for `"mode":"fee_free"` inside the status response's `fee` object. A healthy process alone does not prove licence activation. Guard checks the signature, expiry and the configured account locally. No activation server or wallet signature is required.

If the key is incomplete, expired or for another account, Guard warns and falls back to the applicable builder-fee mode. Check the startup log and the account addresses on your order. Do not change the trading network to fix a licence error.

## Renewal and another machine

A renewal email includes a replacement key. Install it with the same steps. For another machine protecting an account already on the licence, use the same key and check its status there too. Each Guard still needs its own correctly configured state and request-budget share.

[Return to setup](https://zunder-design-preview.pages.dev/connect#guard) · [Connect your bot](https://zunder-design-preview.pages.dev/docs/integrations) · [Payment or licence help](https://zunder-design-preview.pages.dev/contact)
