PRODUCT
Live trading is hosted.
Every order has a boundary.
Live hosting, hard limits, and the strategy runtime together decide how a strategy runs. Pause, resume, and close each need your confirmation.
01Live hosting starts by fixing one instance boundary
Each instance binds one strategy, one symbol on one exchange account, and a loss cap set at creation.
Instance stateOrder behaviorOpen positions
Paused
Order behaviorStops new entries.
Open positionsDoes not close. Positions stay at the exchange.
Reduce only
Order behaviorAfter the loss cap or the plan quota is hit, the instance can only reduce.
Open positionsClosing can continue. Size cannot increase.
Stopped
Order behaviorNo further orders.
Open positionsPositions stay at the exchange until you confirm a close.
Pause only stops new entries. It does not change open positions. A full close needs its own confirmation. Pause, resume, and close are confirmed separately.
Resume keeps the open position
After resume, a process restart, or a plan renewal, the instance continues the current position. It does not close and rebuild.
Paper to live needs a new risk preview
Paper positions are not turned into live orders. Review the risk preview again before you choose live.
02Every order is checked before it reaches an exchange
Official strategies, custom strategies, and external signals use the same checks. While running, limits can only be tightened.
01Instance loss cap
02Plan permission
03Order frequency
The platform sends the order only after every check passes. If any check fails, the order is rejected, it is not sent to the exchange, and the log records the limit that fired.
Stop new entries, keep the position
A failed check stops new entries and leaves the open position for you to handle.
It does not resume the next day.
Reduce only, then stop after this round
In reduce-only, unfilled entry orders are canceled. Closing can continue.
It stops when the current round finishes, and does not start the next round.
A position mismatch enters reduce-only
If the platform record differs from the exchange, or the side is opposite, the instance enters reduce-only.
Unmatched size is not treated as room to add.
Repeated exchange errors stop entries
If an exchange keeps returning errors, instances on that exchange stop opening.
A close may still be attempted.
03A strategy only submits a request. The platform decides whether to send it
The strategy runs in a platform process. It does not hold exchange keys, and it cannot connect to an exchange on its own.
Strategy processSubmit an order request
Strategy code cannot read keys and cannot connect to an exchange on its own.
DoQuantSend after risk checks pass
The platform holds the keys and checks the request against risk limits and the plan.
Exchange accountFill the order, keep the position
The platform sends the order to your own exchange account.
The no-network limit applies to the strategy process. It does not mean the platform cannot reach an exchange.
Pro: AI strategy drafts
An AI draft can only call platform interfaces. It must run on paper before live.
External signals: open and close only
Order size is the amount entered on the instance. A larger amount in the signal rejects the order.
What it can do, and what it cannot
- Symbols and quotesUses one symbol format, and can read market data.
- Order requestsEvery order passes platform risk checks and plan checks.
- Account accessCan read balances and positions. Withdrawals and transfers between accounts are not supported.
- Paper by defaultStarts in paper mode and matches inside the platform at the current market. It does not send live orders.
The notes above describe operating boundaries. They are not a promise of returns. Funds assigned to an instance can still be lost in full.
Start from a paper grid
Bind an account and review the risk preview, then start on paper. Live trading is a later choice.
- 01Register
- 02Bind an account
- 03Check the preview
- 04Run on paper