ZUNDER GUARD · FASTER THAN LIGHTNING.

Your bot can be wrong.
Your limits can’t.

Your bot has big ideas. Give it hard limits. Guard sizes orders from the stop, caps exposure and halts new entries when your loss limits hit. On your machine, between your bot and Hyperliquid.

Pro: up to 3 accounts. No per-order Guard fee. Compare plans

about 3 ms added per order in our paper test –.– ms the risk engine’s judgement in your browser, median of the last – how it was measured ↓
waiting for the next trade…
judged in your browser
· in your browser
sampled live from Hyperliquid
  1. 01 · RequestedWaiting for a public trade…
  2. 02 · Would forwardWaiting for a judged trade
  3. 03 · ReasonWaiting for account data

Public trade, hypothetical decision. This page sends no orders.

without a stop
+5 more rules active ↓
LIVE · HYPERLIQUID
runs in your browser, with JavaScript

The market, judged by your rules.

Every dot is a real trade on Hyperliquid, as it happens. For the largest ones, Guard reads the trader’s public account and asks one question: would your limits have let it through?

—
trades · —
—
refused · of — judged
—
resized · of — judged
LAST 48 SECONDS · SIZE = NOTIONAL · COLOUR = HEAT · SELECT A DOT not judged allowed resized refused

Your rules

  • 5× max
  • 2.0% at stop
  • no stop: Guard sets one
  • liq. ≥ 10%
  • size ≤ 200%
  • open ≤ 6%
  • daily 6%
  • drawdown 25%
  • 5/5 markets
PER TRADE
if an order comes without a stop
POSITION
MARKETS
ACROSS THE ACCOUNT
ONLY YOUR OWN GUARD CAN ENFORCE
stops only tightenalways
resume after a drawdown halta human
These act on your bot’s future orders, so they cannot be seen in other traders’ past ones.
New rules apply to the trades that arrive from now on: each trade is judged once, from the trader’s account at that moment.
Explore the decisionsReasons, markets and individual trades

Why Guard said no

0 of 0 judged trades changed
  • market not on your list0
  • no protective stop0
  • leverage above your cap0
  • too close to liquidation0
  • open risk above your limit0
  • trader past the daily loss stop0
  • trader past the drawdown halt0
  • no stop: Guard set one, sized to your risk0
  • resized: risk or size above your limit0

Refused, by market

share of each market’s trades
  • BTC—
  • ETH—
  • SOL—
  • HYPE—
  • ALTS—

Decisions

Open a trade to hold its details while the market continues.

The latest trades and what Guard decided under your rules
TIMETRADERTRADENOTIONALLEV.STOPLIQ.HEATGUARD
Waiting for the first trades from Hyperliquid…

Traders are anonymised in your browser. Every trade in BTC, ETH, SOL, HYPE, XRP, DOGE, SUI and AVAX streams from Hyperliquid’s public data; the largest are judged on this page, as many as the public API’s request budget allows.

NextCheck your own account Paste your bot’s address: replay its past, then watch it live, under these rules. In your browser, nothing installed.

EVERY ORDER GETS THE SAME TREATMENT

Big ideas meet hard limits.

  1. Read the account

    Equity, open positions and their stops, from the venue and from Guard’s own record. The riskier view wins.

  2. Size from the stop

    Your bot names a stop. Guard turns your risk limit, fees and the venue’s rounding into a quantity.

  3. Check every limit

    Leverage, open risk, the daily loss stop, the drawdown halt. One fails, the order never leaves.

  4. Send, stop, record

    The order goes out with its stop resting on the venue, and the decision is written to a checksum-chained journal that shows if a line was changed or removed.

“Trust me, bro” is not a risk policy.

Risk at the stop sets the size. Leverage and liquidation distance limit the exposure. Daily loss and drawdown limits can halt new entries.

Read all nine rules and their defaults

The nine rules

Four refuse an order, two halt new entries, two shrink it, and one adds the stop your bot forgot. You set each one; the defaults are Guard’s policy.

Market allowlistdefault all markets
REFUSES · Only markets on your list can be traded.
Required stopdefault Guard sets one
ADDS A STOP · No stop? Guard sets one, sized to your max loss at the stop. (Or refuses, if you choose.)
Max leveragedefault 5×
REFUSES · Refuses an order that would take the position above your leverage cap.
Min distance to liquidationdefault 10%
REFUSES · Refuses an order whose position would sit closer than this to its liquidation price.
Max open riskdefault 6%
REFUSES · Refuses a new trade when the loss at all stops, open positions plus this one, would pass this share of the account.
Daily loss stopdefault 6%
HALTS · Once the account is down this much since the start of the UTC day, new entries stop until the day is over.
Drawdown haltdefault 25%
HALTS · Once the account is this far below its peak, new entries stop until a human resumes.
Max positiondefault 200%
RESIZES · Shrinks an order whose position would be larger than this share of the account.
Max loss at the stopdefault 2%
RESIZES · Shrinks the order until the loss at its stop, fees included, is at most this share of the account.

Always, whatever you set: stops only tighten, a restart never resets a stop, and a drawdown halt waits for a human.

NextReplay a bot behind the nine rules Three public vaults are loaded to start; paste your own address.

BLINK. YOU MISSED IT.

Hard limits.
About 3 ms.

That is the median time Guard added per order in our paper test. Your account is already in hand. The decision is ready before your bot can explain itself.

Median bot request to Guard answer, on local SSD in Tokyo, against Hyperliquid testnet. The exchange trip is separate; this is a paper-mode measurement.

Read the measurement →
Component timings and full method
ONE ORDER, TO SCALE · FROM TOKYO
Guard’s own work: check, judge, sign0.24 ms
Guard adds per order, median3 ms
until your order reaches Hyperliquid5 ms

¹ Median of the time from your bot’s request reaching Guard to Guard’s answer, with your account judged from the live account stream and Guard’s decision journal on local SSD; measured 7 Oct 2026 in Tokyo (AWS ap-northeast-1), in paper mode against Hyperliquid testnet. The trip to Hyperliquid is not in it: from Tokyo, 4.5 ms there and back (median), so the order reaches the exchange at about 5 ms.

RESEARCH · DATA TO 6 OCTOBER 2026

Hard limits.
Smaller drawdowns.

The defaults cut the median account’s max drawdown on the held-out replay. Same trades, judged behind Guard’s rules. Here is what changed.

  • −42 pts

    max drawdown, median account

    cut by 42 points (95% interval 22–63)

    63 accounts held out

  • −60% → −18%

    worst day, median account

    as traded, then behind the defaults; no interval computed for this difference

    63 accounts held out

  • 60%

    return per unit of drawdown improved

    share of accounts (95% interval 49–71%)

    63 accounts held out

Held-out test: 63 accounts looked at once, after the rules were fixed. Medians; 95% bootstrap intervals. A mixed sample: ordinary active traders, long-term winners and recently liquidated accounts. We tested 5,940 alternative rule sets on the real trades of 262 Hyperliquid accounts. None beat our defaults on accounts they weren’t tuned on.

The numbers come with receipts.

Replays are not a promise of returns. The best traders gave up some gains behind the defaults; stops touched between fills flatter the replay. The sample is mostly manual traders.

Read the trade-offs and replay limits

It costs the best traders part of their gains: in the replay the median long-term winner’s return fell from 43% to 8%, mostly through the drawdown halt (with the halt opened alone, 13%). 9 winners, training and validation accounts.

Only about 10% of entries go through at full size (95% interval 3–18%). Of all judged entries, 43% were held by a halt (39% by the drawdown halt, once an account was already 25% down), 21% refused and 13% resized.

The replay sees Guard’s attached stops only at the account’s own fills. One-second prices show that 16% of the default stops the replay never fired were touched in between: real Guard would have closed those positions at a loss and missed any recovery. This flatters Guard somewhat.

The samples are mostly manual traders: by a public-data heuristic (exploratory), 22 of the 323 accounts measured (7%) look like bots. A dedicated bot study is running. Past behaviour, not a forecast, and no promise of returns.

A replay of each account’s last 180 days to 6 October 2026 through Guard’s engine. “Beat” means our pre-registered score, with its constraints, on accounts the rule set was not chosen on; the best challenger scored +0.023 (95% interval −0.12 to +0.23). So we kept them.

Kick the tyres. Bring your bot.

Start with a public address. No wallet connection or installation needed for the browser tools.

  • Guard

    In development

    Risk firewall between any bot or AI agent and Hyperliquid.

  • Backtest

    Try today

    Replay any address under your rules.

  • Watch

    Try today

    Your bot’s trades judged live in the browser.

  • Live market

    Try today

    Hyperliquid’s trades judged by your rules, anonymised.

What else we are building and exploring
  • Agent kit (MCP)At first release

    Guarded trading tools for Claude, Cursor and other MCP clients.

  • MonitorPlanned

    Pair the browser with your local Guard: decisions and kill switch.

  • DataPlanned

    Point-in-time Hyperliquid data: trades, books, node gossip.

    recorded since Oct 2026

  • LabsPlanned

    Research notes: honest backtesting, the signal lab.

  • Guarded ArenaPlanned

    AI agents trading in public, every veto visible.

  • MintExploring

    Toolkit for HIP-3 market deployers.

  • TerminalExploring

    Guard in the browser for manual traders.

Live: works today. Building: in progress. With Guard 1.0: ships with Guard. Planned: decided, not started. Exploring: an idea we are testing.

NextRead the docs Quickstart, concepts, integrations and the tools above.

Good questions. No smoke machine.

Can I try it without connecting a wallet?

Yes. Replay and Watch use a public Hyperliquid address in your browser. They do not place orders.

Can Guard guarantee I will not lose money?

No. Limits constrain exposure; fees, funding, slippage and price gaps still matter. The studies explain the observed benefits and their limits.

When can I install Guard?

The self-hosted release is in development. The browser tools work today; join the waitlist for release updates.

NextAll answers on one page

FEE-FREE LICENCES

More thunder. Less fee.

Switch off Guard’s 0.02% builder fee with a flat licence. Every rule stays on. Pick your firepower.

  • Fund

    €690

    a month, or €6,900 a year

    More accounts. The same uncompromising rules.

    • Zero Guard builder fee on every order
    • Up to 20 Hyperliquid accounts
    Buy Fund

    Business licence · pay in USDC. Guard 1.0 is pre-release; your term starts when we send the key.

Prefer pay per order? Guard’s default is 0.02%, with no subscription. Paper and testnet are free. See the alternative →

Building a platform? Talk to us →

Break-even: Pro pays for itself above about $870k of orders a month, Fund above about $4M.

A year costs ten months. Licence prices plus VAT where it applies. Dollar figures at $1.17 per euro, the rate the prices were set at.

Prefer to wait for launch? Get the launch offer.
Launch offer Join the waitlist before Guard 1.0.0 and get Pro free for 3 months. Join below It ends by itself after 3 months; nothing is charged afterwards.

NextAll plans and the calculator Every feature of each plan, and which one pays off at your volume.

Put a firewall in front of your bot.

Self-hosted Guard is in development. Join for beta and release updates. The browser tools are available to try today.

0.02% of each order’s value that Guard sends to Hyperliquid · no subscription · or a flat licence. Pricing

Launch offer: join before Guard 1.0.0 and get Pro free for 3 months.