Strategy types
Local, composite and signal-filtered strategies. None get direct access to your API keys.
Features / Automation & Bots
BetaYour strategy suggests an action. Desk checks it against your account, the market, your limits and upcoming events before a bot can act.
AI assists. You decide.
Capabilities
Local, composite and signal-filtered strategies. None get direct access to your API keys.
Create, start, pause, resume, stop, close and review each bot's history.
Test the full bot flow with live market data and no real money.
Long, Short, Neutral and Cross grids, with a preview before launch.
How it works
The strategy, the risk check and the part that places orders are kept apart.
The strategy proposes an action for a specific account and market.
Limits, upcoming events, open positions and exchange support decide if it's allowed.
Approved actions are carried out, on paper or live where enabled.
Orders, fills and positions are compared with the intended result afterwards.
Safeguards
Bots check their settings before launch and can pause, retry or recover if something goes wrong.
Fees, price precision, minimum order size, leverage and liquidation distance are checked.
Existing positions or orders on the account can stop an unsafe start.
Known market events and current account usage can hold a bot back.
If it's unclear whether an order went through, the bot pauses instead of assuming success.
Availability
Automation & Bots are in beta. Every live setup needs its own proof of stability first.
Rules are tested before real money is involved.
Live bots start small and closely monitored, where enabled.
Higher limits follow proven stability and tested recovery.
Before you rely on it
A strategy is only one part. Permissions, operation, monitoring and recovery matter just as much.
Check the market, direction and settings a strategy proposes.
Confirm limits, exchange support, open positions and events were checked for this exact action.
Run it on paper first before trading live.
Know how pause, close-only and retry work, so a failure never runs on unnoticed.
Connected workflow