Runtime
Operating and review console
Uses the saved Attnom trading workspace and browser-local planning state; it does not independently place orders.
Loading page
Trading Bots / Free now
Allocate capital across preservation, systematic, and tactical bot profiles with daily loss locks and runner health checks.
Best use
A command-center view for bot allocation, mode caps, kill-switch planning, and account-wide execution discipline.
Outputs and next tools
Monitor Binance, Bitget, and Bybit spreads with demo APIs, professional operating profiles, and guarded live escalation.
Run a Binance or Bybit futures strategy desk with demo/live APIs, ranked symbols, capital-preservation, systematic, and tactical profiles, plus server-enforced risk stops.
Track net P&L, ROI, fee drag, drawdown recovery, and trade-cost pressure in one trading dashboard.
Every Attnom tool now declares its input, runtime, output, recovery path, and limitation before the work begins.
This surface governs and reviews connected bots; it is not a separate exchange execution adapter.
Operating and review console
Uses the saved Attnom trading workspace and browser-local planning state; it does not independently place orders.
Capital allocation, runner state, journal context, performance records, and operator review choices.
Readiness is checked before the primary action becomes eligible.
Mode allocation, Runner health, Loss lock with review notes and visible operating assumptions.
The workspace keeps the result close to its settings and source context.
Workspace history, exports, alert notes, and emergency-control planning remain available for review.
Errors and retries remain explicit instead of collapsing into a generic failure.
The control center should own permissions, deployment state, approvals, emergency-stop authority, and broadcast policy changes across every live runner.
Fleet authority
Single authority
Admins can see who is allowed to run what, where, and under which guardrails.
Approval memory
Change history
Changes should show owner, intent, and timing instead of behaving like silent config flips.
Broadcast policy
Risk patch ready
Teams need one place to push new caps, alerts, and kill behavior fleet-wide.
Launch flow
Step 1
Inspect which runners are live, paused, staged, or blocked before changing capital or permissions.
Step 2
Review owner, approval cadence, and recent policy changes before arming new deployments.
Step 3
Broadcast updated risk policy, alerts, or emergency controls from one central 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
Trading dashboard
Balances, recent trades, linked API status, and top-ranked signals.
Futures bot
Launch demo-first futures runs with preservation, systematic, and tactical profiles plus a guarded live preflight.
Strategy backtester
Pressure-test win rate, fees, slippage, and drawdown before live sizing.
Desk protocol
Authority first
Every permission and stop action should feel deliberate, attributable, and hard to misread.
Deployment discipline
Staged, live, and frozen runners need obvious separation so admins never act on the wrong system.
Policy continuity
Broadcast changes should carry owner, time, scope, and rollback context by default.
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