Free no-transaction deployment guide
A practical acceptance matrix for deciding between separate cBot instances and one multi-symbol cBot before moving an existing strategy from one demo symbol to two instruments.
State whether one cBot instance runs on each chart or one process owns a configured symbol list. Do not mix both models in the same acceptance run.
Record the broker-specific symbol names, digits, pip and tick sizes, volume limits, session schedules and minimum protection distances for both instruments.
Make opening range, indicator periods, session times, volume and protection settings explicit per symbol instead of relying on a shared default.
Give every instance and symbol a stable label or source key and state whether the cBot may inspect or manage manual trades and other algorithms.
Decide which component owns daily loss, equity lock and maximum exposure so two instances cannot independently consume the same account-wide allowance.
Force a safe validation failure on one instrument and verify that the other instrument remains observable and no retry loop or cross-symbol state corruption occurs.
Restart the cBot with existing synthetic or demo state and confirm that labels, pending state, daily controls and duplicate suppression rebuild deterministically.
Freeze cTrader server time, UTC and any named trading timezone, including daylight-saving behavior and per-symbol market hours.
Record redacted position, pending-order and history counts around the run and require no transaction for a preflight-only test.
Backtests, Monte Carlo studies and parameter optimization do not prove multi-symbol ownership, restart or broker-rejection behavior.
Separate instances are often the smaller first deployment when each instance owns only its chart symbol and labels are isolated. A multi-symbol process can centralize account-wide state, but it needs explicit symbol scheduling, event routing and recovery tests.
No. Freeze the topology and run no-transaction or demo acceptance cases first. Credentials and autonomous live-account operation are outside the scope.
No. It proves only the agreed deployment and state-handling behavior for the captured cases, not a trading edge, future fills, drawdown or prop-firm results.
Free diagnostic resource
Review the read-only environment checks, explicit no-trade boundary and remaining real-demo evidence gate.
Open the free toolReady for a feasibility check?