One interface · every account
You trade once.
Every account
follows in seconds.
Entry, stop, target, close — each one goes out to every connected account at the same moment, sized to that account's own balance. When one exchange fails, the rest still fill and you get told which one didn't.
- Hyperliquid180ms
- Bybit240ms
- Binance310ms
- OKX420ms
- Gate.io260ms
- KuCoinfailed
- Toobit380ms
Supported exchanges
The numbers
Measured, not promised
The numbers behind the promise, from the repo's own test suite and the verified three-account demo.
- 0
- Exchanges
- 0+
- Backend tests
- 0%
- Of balance
- 0ms
- Fan-out dispatch
behind one interface
passing, on every run
committed as margin on every entry
measured on a three-account demo
How it goes
How it goes
- 01
Connect trade-only keys
Each account is verified on connect and refused outright if the key can withdraw. Keys are encrypted at rest and never returned to the browser.
- 02
Trade once
One ticket sets side, leverage and the stop and target percentages. The engine sizes each account from its own balance and dispatches every leg concurrently.
- 03
Watch it land
Per-leg results arrive as they happen. A failed leg raises a notice that stays on screen until you dismiss it — no toast that disappears while you look away.
Why it holds up
Six constraints, not six buttons
Every trade obeys these. They are guarantees someone is trusting with their capital, so they earn their space.
One failure stays one failure
Every account gets its own connection, its own rate limit and its own deadline. An exchange going down costs that account the trade and nobody else.
Sized to each balance
Every account commits 99% of its own USDT. A $50 account and a $5,000 account take the same leverage and the same stop percentage, at very different dollar sizes.
Stops move everywhere at once
Drag the stop on the chart, edit it in the ticket, or change it on the position row — all three push the same amendment to every account.
Keys that cannot withdraw
Trade-only is enforced at connect wherever the exchange exposes the permission; a key that can move money is refused outright.
The exchange is the source of truth
Positions are re-read from each venue on a timer, so a stop that fired on the exchange closes the leg here — and a position the platform wrote off is put back.
One account, whole
Every account gets its own page and a PDF statement in the language its partner reads — money only, no percentages that invite misreading.
See it
The fan-out, live
Signed in, this is your own last trade, leg by leg. Signed out, the diagram runs the demo so the promise still teaches itself.
- Hyperliquid180ms
- Bybit240ms
- Binance310ms
- OKX420ms
- Gate.io260ms
- KuCoinfailed
- Toobit380ms
Security
It holds live trading credentials
Keys are encrypted at rest with rotatable Fernet keys, never logged, never included in an API response, and verified as non-withdrawable at connect time wherever the exchange exposes a permission endpoint. Where it cannot be proven, the account is flagged rather than silently trusted.
- Keys encrypted at rest with rotatable Fernet keys — never logged, never in an API response.
- Trade-only enforced at connect: a key that can withdraw is refused outright wherever the exchange lets us check.
- Credentials are never sent back to the browser, not even masked for display.
- Where an exchange publishes no permission endpoint, the account is flagged rather than silently trusted.
- A platform-wide halt switch (STOP_ALL) that stops new routing instantly and cannot be cleared from the panel.
- Connect an account
Straight answers
Questions an operator asks
Straight answers, including the ones it costs nothing to be honest about.
Not yet. The eight adapters are written from vendored exchange documentation and unit-tested against mocked transports, but none has been run against a live exchange or testnet. Verify on testnet before committing real capital.
Hyperliquid, Bybit, Binance, OKX, Gate.io, KuCoin, Toobit and LBank sit behind one interface. Capability differences — native versus emulated stops, per-symbol versus per-account leverage — are handled behind the adapter seam, never in trading logic.
No. Every key is verified as trade-only at connect, and refused outright where withdrawal rights are detected. On exchanges that publish no permission endpoint, the check is reported as unprovable and the account is flagged rather than quietly trusted.
Sizing is 99% of an account's available USDT balance, with leverage on top. An account denominated in anything else is reported on the dashboard as unusable — it is never traded on a guess.
One open trade per account. An entry whose fill is unconfirmed counts as possibly holding one, so a second order can never stack on a position that may already be there.
That account fails alone and raises a persistent notice that stays until you dismiss it — the others still fill. A leg that failed after its order went out is re-read from the exchange, so a fill is never reported as a failure.
Trade once. Every account follows.
Connect a trade-only key and the next order fans out to every account at once — sized to each balance, protected, and reported leg by leg.