Bybit automation control plane
Systematic edge.
Human control.
Connect an account, discover its real capabilities, allocate capital, and operate isolated trading automation from a terminal built for clarity.
Member terminal
See the entire operating picture.
A cinematic preview of account, market, strategy, execution, and risk surfaces—with realistic market structure, long and short positions, and dense operator telemetry.
Historical BTCUSDT fifteen-minute replay from 7 March 2024. Seventy-two candles include varied real open, high, low, close, and volume geometry.
Control plane
One workspace from account discovery to live operation.
Quantbot separates what the platform can support from what each installed strategy adapter is permitted to do.
Account intelligence
Know the capital you actually have.
Scan sanitized equity, available balance, margin mode, and account generation without exposing API secrets to the interface.
Dynamic capabilities
Instrument rules, not hard-coded promises.
Leverage is resolved against the instrument, account mode, risk tier, and adapter contract.
Worker isolation
Independent account boundaries.
Every connected account receives its own encrypted configuration and supervised runtime.
Market architecture
Designed for the breadth of Bybit.
The platform model spans spot and derivatives. Actual availability is always determined by the connected account and installed adapter.
Spot
Cash market automation and inventory-aware execution.
Platform capabilityLinear
USDT and USDC margined perpetual and futures contracts.
Adapter dependentInverse
Coin-margined contracts with product-specific risk rules.
Adapter dependentOptions
Options workflows through a dedicated capability contract.
Future adapterHow it works
Four deliberate steps. No hidden state.
- 1
Connect
Submit a restricted, IP-pinned Bybit API key over HTTPS.
- 2
Discover
Validate permissions and scan sanitized account capability data.
- 3
Allocate
Choose how much account equity the current strategy may use.
- 4
Operate
Start, arm, pause, monitor, and flatten through explicit controls.
Security boundary
Your exchange credentials are not dashboard data.
Keys are validated, encrypted at rest, and never returned to the browser. Quantbot requires trading-only permissions and rejects withdrawal access.
TOTP-protected access
A second factor protects control-plane actions.
Sanitized account snapshots
Only operational totals reach the interface.
Explicit live arming
Starting monitoring does not silently enable entries.
Quantbot control plane