Spot, futures, perpetuals on one execution layer, one ledger, consistent risk controls.
The same strategy file fires emit_long on a Binance perp, emit_limit_short on a Coinbase spot, set_sl_price on a Hyperliquid future, and a YES / NO / scalar payload on a Polymarket prediction. Same Rust hot path. Same risk verbs. Different venue, identical trades[] shape.
Two paths to the same engine. Write the strategy yourself in Rhai or Python with 80+ runtime functions, the same hot path that runs in production. Or describe the strategy in plain English and let the three stage AI pipeline draft the code, critique its risk handling, and patch the gaps. Either way you ship the same .rhai file to the same backtest and the same dry-run mode. Live execution is gated pending licensed execution.
Hit BACKTEST and the same Rust engine that runs production replays your strategy against historical bars. Twelve metrics come back: Sharpe, Sortino, Calmar, max DD, win rate, profit factor. The equity curve plots over OHLCV candles.
When one run is not enough, hand it to the AI Optimizer. Pick an objective. Pick parameters to vary. The optimizer spawns an LLM agent that proposes a set, runs a backtest, reads the result, reasons about why, and proposes the next. Up to fifty iterations per run, agent reasoning visible on every step.
A four-persona crew runs beside the live strategy. Quant reads execution metrics. Market classifies the regime. Risk runs a walk-forward backtest on the proposal. Trader composes the new parameters. The status endpoint polls every four seconds. When the AI wants to widen a take-profit, it surfaces the diff and the rationale. APPROVE & APPLY pushes the new params on the next heartbeat. REJECT & HALT stops the optimizer. The default is a human in the loop.
The same in-house dashboard you see here runs every live strategy. Positions, fills, equity, drawdown gates, dry-run status, paused orders, one cockpit. Watch a crew reason, watch the engine fire, then pause, adjust, or kill mid-run without leaving the page.
Per-tier scope is the safety rail. Keys live in Infisical, never in the database. Private streams (balance, orders, fills, positions) multiplex on one /ws/private socket per venue. One JWT, one socket, control frames in flight. No reconnect storm. No fan-out cost on the operator's box.
"One engine to rule them all. And in the darkness bind them."