Open-source bots

HyperMirror vs Open-Source Hyperliquid Bots

Hyperliquid's API is open and well documented, so there is a healthy ecosystem of open-source copy bots. If you can read Python and run a server, you can build something that mirrors a wallet this weekend. The interesting question is not whether that works — it does — but what the next twelve months of running it costs you.

In short

Open-source Hyperliquid bots give you complete control over logic, keys and hosting, with no product fee and no vendor. HyperMirror is a hosted alternative: scoring, score-weighted allocation across up to 10 leaders in a sticky basket, one isolated sub-account per leader, automatic emergency removal and soft-issue-strike replacement, and a 0.1% builder fee on mirrored volume — with no infrastructure for you to operate.

At a glance

HyperMirror versus Open-Source Hyperliquid Bots — structural comparison
DimensionHyperMirrorOpen-Source Hyperliquid Bots
Primary venueHyperliquid onlyHyperliquid (whatever you configure)
Custody modelNon-custodial; funds stay in your own Hyperliquid accountNon-custodial: you hold your own keys and run your own code
Permission modelTrade-only agent approval plus a separate builder-fee approvalYou generate and manage your own API wallet or agent key
Can the operator withdraw your funds?No — withdrawals and transfers stay wallet-onlyThere is no operator — but a leaked key is entirely your exposure
What you copyA curated basket of up to 10 scored elite Hyperliquid tradersWhatever your code targets, usually one wallet
Portfolio constructionScore-weighted allocation; 1 leader in Starter mode, up to 10 in Full modeWhatever you implement; most reference bots copy one wallet
Position isolation / nettingOne isolated sub-account per leader; no netting between leadersOnly if you build sub-account routing yourself
Leader replacement policySticky basket: immediate removal on an emergency, otherwise 3 strike-days of documented soft issuesNot documented as a fixed rule set — rotation is left to the user or to the provider's discretion
Fee model0.1% builder fee on mirrored notional volume; no profit shareNo product fee; you pay hosting, monitoring and your own time
TransparencyOn-chain: every fill sits under your own addressTotal — you can read every line of the logic
Ops burdenHosted autopilot; nothing to run or host yourselfHigh: deployment, uptime, restarts, upgrades, key rotation
Best forSomeone who wants diversified Hyperliquid exposure without giving up custodyEngineers who want full control and are willing to operate it

Quick verdict

HyperMirror fits when you want the mechanics without operating them, and you value continuous scoring and replacement more than customisability.

Open-Source Hyperliquid Bots may fit better when you want to own and modify the logic, run your own infrastructure, and pay in effort rather than fees.

Custody and security

Self-hosting is maximally non-custodial in one sense and quietly risky in another. Nobody else can touch your funds, which is the point. But the agent or API key lives on a machine you administer, and the realistic failure mode is not a hostile vendor — it is a key in an environment file on a box with an open port, or committed to a repository during a late-night fix.

A hosted agent narrows the blast radius differently. The approval is trade-only at the protocol level, so even a compromise of the operator cannot produce a withdrawal; funds remain in your Hyperliquid account and the approval is revocable from your wallet. You are trading key-management responsibility for operator trust, and the trade is worth making explicit rather than assuming one side is simply safer.

  • Self-hosted: no operator trust required, complete key-management responsibility.
  • Hosted agent: trade-only permission, no withdrawal path, revocable at any time.
  • Neither model can withdraw from your Hyperliquid account without your wallet signature.
  • Both leave you fully exposed to the market risk of the positions themselves.

Fees and incentive alignment

Open-source software has no product fee, and that is a real advantage. The costs are elsewhere: a server, monitoring, the hours spent on the initial build, and the recurring hours spent on API changes, reconnect logic, edge cases in order handling and the incident at 2am when the process died holding a position.

HyperMirror charges 0.1% of mirrored notional volume through Hyperliquid's builder-fee mechanism — no subscription, no profit share. Whether that is cheaper depends entirely on how you value your own time and how much volume you actually mirror. For a low-volume account run by a competent engineer, self-hosting is plausibly cheaper. For anyone else, the operational tail dominates.

How copying and automation actually work

Most reference bots implement the easy 80%: watch a wallet, detect a fill, place a proportional order. What they usually do not implement is the part that determines results — deciding which wallet deserves capital, how much, and when to stop. That is a data and scoring problem, not an execution problem, and it does not have a tidy open-source answer.

HyperMirror's scoring runs on public fill history across realized PnL consistency, win rate, profit factor, position discipline and account survivability, and the composite score sets both basket membership and allocation weight. Sub-account routing is built in: one isolated sub-account per leader, so Hyperliquid's netting cannot cancel one leader's long against another's short. Building that routing, plus rebalancing and replacement logic, is substantially harder than building the mirror loop.

  • The hard parts are selection, weighting, isolation and replacement — not order placement.
  • Up to 10 leaders in Full mode, 1 in Starter mode until $100k mirrored volume.
  • Isolated sub-accounts prevent cross-leader netting and preserve attribution.
  • Rebalancing and emergency replacement run continuously without your intervention.

Risk controls and leader failure

The realistic risks of a self-hosted bot are operational: the process crashes mid-position, a reconnect duplicates an order, the API changes and errors are swallowed silently, or a rate limit hits during a fast move. Each is survivable and each requires you to be available.

A hosted system carries operator risk instead, bounded by the trade-only permission, and adds governance the typical DIY bot lacks: soft-issue strikes on decline, replacement with the leader's sub-account positions closed once three strike-days accumulate, and immediate emergency removal for severe events — with deliberate resistance to over-rotation, since a higher score alone never forces a swap and churning leaders costs turnover without adding information.

Who should choose which

Choose HyperMirror if: you want scoring, weighting, isolation and replacement without building them, you do not want to be responsible for uptime, and you accept a trade-only agent as the trust boundary.

Choose Open-Source Hyperliquid Bots if: you want to own and modify the logic, you have specific requirements no product implements, or you would rather pay in engineering time than in fees.

Limitations, on both sides

Where HyperMirror is limited: the logic is not yours to modify; leaders are chosen by score, not by you; Hyperliquid only; and you are trusting an operator within a trade-only permission boundary.

Where Open-Source Hyperliquid Bots is limited: you own uptime, key security and every incident; most reference implementations copy one wallet with no scoring or isolation; and the maintenance burden never ends — it just becomes familiar.

Methodology, in one paragraph

HyperMirror's side of every row above follows one published rule set. The Elite basket is sticky: a leader stays mirrored until a rule removes them, and a higher-scoring wallet elsewhere never forces a swap. Emergencies — account value below roughly $1,000, or no fill for 96 hours or more combined with zero trades in 7 days — remove a leader immediately. Everything softer accrues at most one strike per wallet per UTC calendar day, with three strike-days triggering replacement and a clean day resetting the counter; drawdown for that test is measured on jump-adjusted equity so deposits and withdrawals are not read as trading losses, and ROI is measured from PnL. The full table is on How it works and in the documentation.

Risk statement

Structure changes which risks you carry, not whether you carry risk. Nothing on this page is a return estimate, a recommendation, or a claim about another provider's results — check any provider's own documentation before deciding.

Past performance is not indicative of future results. Perpetual futures are leveraged instruments and carry a substantial risk of loss, including the loss of your entire position.

Methodology

Scoring and replacement are documented in full on How it works and in the Docs (Policy v3). In short: the Elite basket is sticky, emergencies remove a leader immediately, and soft issues accrue at most one strike per UTC day with three strike-days triggering replacement. Read how it works or the documentation for the full table.

Questions

Frequently asked

Is HyperMirror open source?

The scoring and allocation logic is not published, but every action it takes is a public on-chain fill under your own address, so its behaviour is verifiable against the chain even where the code is not.

Can I run my own bot alongside HyperMirror?

Technically yes, but be careful: two systems trading the same account can conflict over margin and positions. Isolated sub-accounts help, and you should still keep the responsibilities clearly separated.

What is genuinely hardest to replicate?

Continuous trader scoring and the replacement policy around it. Mirroring a wallet is a weekend project; deciding which wallets deserve capital, and when to stop giving it to them, is not.

Does self-hosting avoid the builder fee?

There is no HyperMirror fee if you are not using HyperMirror. You still pay Hyperliquid's own trading costs, plus hosting and your own time.

Diversified copy trading. On autopilot.

Score-weighted allocation across up to 10 elite Hyperliquid traders, each isolated in its own sub-account. Your funds never leave your account.

Non-custodial · Agent cannot withdraw · Cancel delegation anytime