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 how it was measured ↓
YOUR BOT. AT 3 A.M.03:00:01 UTC

Confidence: unlimited. Risk: limited.

BUY BTC · 3×
1% risk · stop set
allowed · within the limits
SCRIPTED DEMO · NO ORDERS SENT5× cap · 2% risk limit
  1. RequestedBTC · 1% risk
  2. Guard’s decisionAllowed
  3. WhyStop set. Within the limits.
Meet the real market

Scripted demo. No orders sent. Illustrative requests under 5× leverage and 2% risk limits. The replay below uses real trades and Guard’s engine.

02 / THE MARKET DOESN’T SLEEP

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% at stop
  • no stop: Guard sets one 2% away
  • 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.

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—
Inspect individual tradesEvery decision, with its reason

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.

NextNow rewind a real account From a market in motion to the trades that changed one account’s result. Your own address works here too.

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 →
  • 0.24 ms

    Guard’s own work: check, judge, sign

  • 3 ms

    Guard adds per order, median¹

  • 5 ms

    until your order reaches Hyperliquid, from Tokyo

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
How we measured it

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

03 / REWIND REAL TRADES

Big decisions.
Play them back.

You’ve seen the market move. Now rewind one account. Follow a public vault’s actual history, replayed behind Guard’s defaults.

Show me my own bot’s historyPublic address. No wallet connection.

+47.4% in the 90 days to 15 Oct 2026, through a 2.9% drawdown. Guard takes 0 of its 83 entries as they were, resizes 79 and refuses 4: +23.7%, 8.0% drawdown.

  • runs entirely in your browser
  • no wallet connection · no signature · no keys
  • nothing to approve, nothing that can move funds
  • we never see the address

Sample: a public Hyperliquid vault · its 90 days to 15 Oct 2026, 22:52 UTC, replayed when this page was built · 587 fills

Guard took nearly all of this account’s entry size: less return, a larger drawdown.

Refused: 4 open-risk cap. Resized: 78 stop added, 1 stop added and sized down.

Equity, 90 days

Behind Guard As traded halted by a stop deposit withdrawal

Account equity · USDC · includes cash flows

50,43340,83231,231
start replay ends
As traded 47,546Behind Guard 39,898
Behind Guard —As traded —

Playback reveals the recorded curves; it does not rerun the engine. Equity at the cursor is interpolated for display. Summary statistics always cover the full result.

No liquidations in this history.

Adjust your replay rules
Your rules

Every rule applies here, including the account stops.

if an order comes without a stop
RETURN, 90 DAYS
Behind Guard+23.7%
As traded+47.4%
Difference−23.7 pp
Guard cost return here
RETURN PER 1% DRAWDOWN
Behind Guard3.0
As traded16.4
Difference−13.4
less return for the risk
WORST DRAWDOWN
Behind Guard−8.0%
As traded−2.9%
Difference−5.1 pp
peak to trough
WORST DAY
Behind Guard−6.0%
As traded−3.1%
Difference−2.9 pp
daily stop at 6% · stops new entries
The daily loss stop halts new entries for the rest of the UTC day once the day’s loss reaches it. Positions already open keep running to their own stops, so a day can still close below the limit.
LIQUIDATIONS
Behind Guard0
As traded0
Difference0
4 refused · 79 resized · 0 halted

Difference = Behind Guard − As traded, using the displayed values. pp = percentage points.

The trades that mattered

largest differences between your bot and Guard
SELL BTC · Guard’s stop10 Sep 13hstop hit
As traded
—
Behind Guard
−$1.9k
Leverage
—
Stop
added
SELL BTC · Guard’s stop08 Oct 16hstop hit (hourly price)
As traded
—
Behind Guard
−$760
Leverage
—
Stop
added
SELL ETH · Guard’s stop16 Sep 02hstop hit
As traded
—
Behind Guard
−$744
Leverage
—
Stop
added
SELL PUMP · Guard’s stop07 Oct 01hstop hit (hourly price)
As traded
—
Behind Guard
−$586
Leverage
—
Stop
added
SELL BTC · Guard’s stop07 Oct 02hstop hit
As traded
—
Behind Guard
−$417
Leverage
—
Stop
added
SELL ETH · Guard’s stop12 Oct 17hstop hit (hourly price)
As traded
—
Behind Guard
−$390
Leverage
—
Stop
added
SELL SOL · Guard’s stop01 Aug 07hstop hit
As traded
—
Behind Guard
−$342
Leverage
—
Stop
added
SELL ZEC · Guard’s stop12 Oct 16hstop hit (hourly price)
As traded
—
Behind Guard
−$338
Leverage
—
Stop
added
BTC · open at the end15 Oct 22hmarked at window end
As traded
−$801
Behind Guard
+$0
Leverage
—
Stop
—
ZEC · open at the end15 Oct 22hmarked at window end
As traded
−$543
Behind Guard
+$0
Leverage
—
Stop
—
ETH · open at the end15 Oct 22hmarked at window end
As traded
+$661
Behind Guard
+$661
Leverage
—
Stop
—
The eight trades where Guard changed the result most, then the largest deposits and withdrawals, and where the replay ended early if it did
WHENTRADELEV.STOPRESULT · AS TRADED → BEHIND GUARDGUARD
10 Sep 13h SELL BTC · Guard’s stop — added — → −$1.9k stop hit
08 Oct 16h SELL BTC · Guard’s stop — added — → −$760 stop hit (hourly price)
16 Sep 02h SELL ETH · Guard’s stop — added — → −$744 stop hit
07 Oct 01h SELL PUMP · Guard’s stop — added — → −$586 stop hit (hourly price)
07 Oct 02h SELL BTC · Guard’s stop — added — → −$417 stop hit
12 Oct 17h SELL ETH · Guard’s stop — added — → −$390 stop hit (hourly price)
01 Aug 07h SELL SOL · Guard’s stop — added — → −$342 stop hit
12 Oct 16h SELL ZEC · Guard’s stop — added — → −$338 stop hit (hourly price)
15 Oct 22h BTC · open at the end — — −$801 → +$0 marked at window end
15 Oct 22h ZEC · open at the end — — −$543 → +$0 marked at window end
15 Oct 22h ETH · open at the end — — +$661 → +$661 marked at window end

How honest is this? A replay is a what-if, not a promise. Skipping or shrinking a trade can change what your bot would have done next, and prices, fees and funding after a skipped trade are taken from your real history. Losses are capped at your stop only where your bot actually had one. Results include fees and funding as Hyperliquid recorded them.

04 / PUT GUARD IN FRONT

More thunder.
Less fee.

One flat licence. Zero Guard builder fee. All the rules, however busy your bot gets.

Choose your term
  • Zero Guard builder fee
  • Every rule. Every limit.
  • Your keys stay on your machine

The licence removes Guard’s fee. Venue fees, funding and slippage still apply.

YOUR GUARD

Pro

€149/ month

Up to 3 Hyperliquid accounts

One flat price. No Guard fee per order.

Continue with Pro

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

Next: confirm your business, accounts and payment network.

Prefer pay per order? The default is 0.02% with no subscription. Paper and testnet are free. Compare against your volume → Start with pay per order →

All plans and details →

Break-even: Pro pays for itself above about $870k of orders a month, Fund above about $4M. Dollar figures at $1.17 per euro, the rate the prices were set at.

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.

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.

  • −43 pts

    max drawdown, median account

    cut by 43 points (95% interval 23–58)

    63 accounts held out

  • −67% → −17%

    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 48–73%)

    63 accounts held out

Original test split: 63 accounts, corrected after the original results had been seen. Rules and membership stayed fixed; this is not a fresh blind test. Medians; 95% bootstrap intervals. A mixed sample: ordinary active traders, long-term winners and recently liquidated accounts. Post-hoc filter sensitivity: excluding 2 now-ineligible test accounts leaves 61 accounts and 61 of 171 events flat (35.7%; 95% interval 15.5–54.1%). Those excluded accounts supply 62 of the primary split’s 123 flat events. We tested 5,940 registered rule sets on the real trades of 262 Hyperliquid accounts. The corrected replay did not support changing our defaults.

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 original defaults sample is mostly manual traders; a separate cohort now covers 148 likely bots.

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 54% to 48%. Opening the halt alone does not recover that median return. With all five engine limits opened, the median is 44%; attached stops, the position cap and costs still apply. This does not isolate their separate effects. 9 winners, training and validation accounts.

In the original 63-account test split, the median account’s full-size entry pass-through was 19% (95% interval 2–32%). Separately, across 76,071 pooled entries from 199 training and validation accounts, 39% were held by a halt (35% by the drawdown halt, once an account was already 25% down), 21% refused and 11% resized.

What-if replays: each account’s own trades over the 180 days to 6 October 2026, judged by Guard’s engine; later decisions are kept as traded.

These replay studies cover main-dex perpetuals; HIP-3, spot and outcome markets are excluded. The liquidation autopsy covers 4 Sep – 3 October 2026, read at a daily snapshot.

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.092 (95% interval −0.15 to +0.29). The original test split was rerun after unblinding to correct historical-data defects; this is not a fresh independent confirmation.

Kick the tyres. Bring your bot.

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

  • Guard

    Source available

    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?

Read the public source and prepare your setup. Signed installers are next; Replay and Watch work today.

NextAll answers on one page

Put a firewall in front of your bot.

Guard’s source is public. Join for signed 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.