Loading page
Trading Bots · Free now
Use it forRunning more than one bot and needing account-wide limits.
Good to knowOne place to see what every bot is allowed to do, and to stop all of them.
One place owns permissions and the emergency stop for every runner. Not per-bot, not per-tab.
Fleet authority
Single authority
An admin can see who is allowed to run what.
Approval memory
Change history
Every change carries a name and a timestamp. Silent config flips are how desks die.
Broadcast policy
Risk patch ready
Push a new cap to the whole fleet from one panel.
Launch flow
Step 1
Check which runners are actually live before you touch capital.
Step 2
Read the recent policy changes before arming anything new.
Step 3
Broadcast a risk policy change from one panel.
Step 4
Leave a visible approval trail whenever fleet controls change.
Desk capabilities
Emergency scope
Safe cap
$23,000
46.0% protected allocation
Core cap
$20,000
40.0% default execution mode
Tactical cap
$7,000
14.0% event-led ceiling
Loss lock
$1,400
2.8% fleet-wide daily stop
Approval cadence
6h
Live approval expires without renewed admin confirmation.
Emergency mode
FLEET
Primary stop scope for this operating window.
Fleet orchestration
Safe mode
2 runners
$23,000 ceiling with slower approvals and tighter kill sensitivity.
Core mode
2 runners
$20,000 for day-to-day execution under normal approvals.
Tactical profile
1 runners
$7,000 only if live approvals and kill switch settings are current.
Authority board
Permissions
6h review
Live changes expire without explicit admin renewal.
Deployment state
3 live / 1 staged
Separate staged runners from live runners before issuing broadcast changes.
Emergency stop
fleet scope
The primary kill path should be obvious and role-aware.
Broadcast policy
Risk patch ready
Push revised caps, alert channels, and permissions fleet-wide from here.
Approval history
Broadcast cap update
Loss lock moved to 2.8% with 6h re-approval cadence.
Fleet ownership check
4 active runners require owner confirmation before live control changes.
Emergency controls
FLEET kill scope is primary until the next admin approval.
Policy memory
Every policy push should carry scope, owner, time, and rollback note.
Desk shortcuts
Desk protocol
Authority first
Stopping a desk is a deliberate act, and it leaves a name behind it.
Deployment discipline
A staged runner must never look like a live one. That confusion costs real money.
Policy history
Every change records who, when, and how to undo it.
Trust and support
Saved bot workspaces
Free: 1
Premium: 8
Live exchange connections
Free: Demo only
Premium: 2
Support path
Trading desk
2h first response
Related desk tools