cBots

No. Some cBots are fully automated end-to-end. Others send signals or alerts, manage trailing stop losses, close positions on conditions or assist manual trading. The Store product page should state the automation level; if it does not, treat that as a signal to test on a demo account and read settings carefully.

Trading bots are software tools, not automatically safe. Risk depends on strategy logic, settings, broker conditions, leverage and market regime. Read the product page, test the bot on a demo account, start small when going live, set risk limits and avoid guaranteed-profit claims.

Yes. A cBot can manage open positions by moving stop loss, applying trailing logic, scaling in or out, hedging or closing on conditions. Position-management cBots are a common alternative to fully automated entry bots. Test management logic on a demo account because trade-management automation directly affects live account exposure.

Yes. A cBot can be coded to only send notifications when conditions are met, without placing or modifying any trades. Alert-only cBots are useful when you want to combine algorithmic monitoring with discretionary execution. Check permissions before installing — even an alert-only cBot will request the access rights its code declares.

Yes. A cBot can place, modify and remove stop loss and take profit orders if its code is designed to do so. Behaviour depends on the cBot's settings, the symbol's minimum distance rule and broker execution conditions. Product pages should state whether SL/TP is fixed, dynamic, trailing, optional or user-configurable.

Yes, if the cBot's code includes trading actions and you start an instance on a trading account. Some cBots place and manage trades end-to-end, others only send alerts or manage open positions opened manually. Check the product description for the automation level before assuming the bot will trade by itself.

Yes. A cBot can place, modify and remove trailing stop losses if its code is designed to do so. Trailing stop losses can be fixed-distance (e.g. 20 pips behind price), volatility-based (using ATR) or time-based (tightening over time). Server-side trailing depends on broker support; client-side trailing runs inside the cBot itself and only works while the cBot instance is running. Check whether the cBot uses server-side or client-side trailing before relying on it through restarts.

No. No trading bot can guarantee profit. Automation removes manual execution errors and emotional decisions but cannot remove spreads, slippage, leverage risk, news events or market regime changes. Any product claiming guaranteed profit is either marketing or a scam.

Yes. cTrader Windows and Mac include a backtesting engine that runs a cBot against historical tick or bar data over a chosen period, with adjustable spread and commission settings. Backtesting shows an equity curve, drawdown, win rate, profit factor and trade list. Remember, however, to treat backtesting results as research evidence, not a forward guarantee.

Yes. cTrader Windows and Mac include an optimisation engine that runs a cBot across a parameter grid and ranks results by selected criteria (net profit, drawdown, profit factor, Sharpe-like metrics). Optimisation is powerful but easy to over-use — picking the single best parameter set typically curve-fits to history. Use walk-forward or out-of-sample testing to validate optimisation results.

Yes. You can run multiple cBot instances on the same account, on the same or different symbols, with cloud runs typically limited to one on demo and up to ten on live accounts (broker-varied). Multiple cBots are not the same as diversification if they all react to the same conditions — verify symbol overlap, total exposure, max drawdown and emergency-stop coordination before stacking bots.

Yes. The same cBot can run on both demo and live cTrader accounts. Demo execution is usually closer to ideal because demo servers smooth execution; live execution exposes the cBot to real spreads, slippage and partial fills. Use demo for setup verification and live for true performance evaluation.

Yes. The same cBot product can be started as separate instances on different symbols and timeframes, each with its own parameter set. Cross-symbol behaviour can vary because spreads, volatility, swap rates and session hours differ — settings tuned for EURUSD may not transfer to gold or indices. Run backtesting for each instance individually before running them live.

Trust backtesting results only as evidence of how the cBot would have performed on historical data with the assumed spread, commission and execution model. They do not capture real slippage, latency or broker-specific behaviour and they are vulnerable to curve fitting if parameters were tuned on the same data shown. Pair backtesting with out-of-sample testing and demo-forward results.

Yes — through cloud execution. cTrader Mobile can start, manage and stop cloud cBot instances, with the bot itself running on cTrader's hosted backend rather than on the phone. Mobile does not support local cBot execution, custom indicator charts or backtesting; those workflows require Windows or Mac.

Yes — through cloud execution. cTrader Web can start, manage and stop cloud cBot instances. Local execution, custom indicator charts and backtesting are not available on Web; those require the desktop apps.

To start a cBot, open cTrader on any app, add an instance to a chart with the symbol and timeframe you want, choose cloud or local execution (local requires Windows or Mac), set the cBot's parameters and click Start. The cBot runs as an instance until you stop it or it errors out. Cloud instances continue when the app is closed; local instances stop when the desktop app closes.

A cBot runs as an instance — a running copy of the algorithm bound to one account, symbol and parameter set. Start the cBot in cloud or locally, give it a symbol and timeframe and it executes its logic until you stop it or it errors out. The same cBot product can have multiple independent instances on different symbols or accounts.

Choose a trading bot by strategy fit and risk profile first, broker compatibility second, performance evidence third. Check the strategy explanation, supported symbols and timeframes, risk settings, cloud vs local mode, live or demo evidence, drawdown and reviews. Avoid bots that promise guaranteed profit or hide drawdown — they fail under real conditions.

A cBot is a trading robot that runs in cTrader and analyses market conditions, places orders and manages positions according to its code and settings. cBots can run as cloud instances (any cTrader app, 24/7) or local instances (cTrader Windows or Mac). Store offers free and paid cBots; check live or demo statistics, backtesting results and risk settings before going live.

A cBot instance is a running copy of a cBot product, bound to one account, one symbol, one timeframe and one parameter set. The same cBot product can have multiple independent instances — for example, one on EURUSD 15-minute and another on USDJPY 1-hour — and each instance maintains its own state, trades and history.

A cloud cBot instance is a cBot running in cTrader's hosted Linux-based environment, started from any cTrader app. The instance continues running independently of your device, so the bot keeps trading with the computer off. Default limits are typically one cloud instance on a demo account and up to ten on live accounts; cloud instances on demo accounts auto-stop seven days after start.

A local cBot instance is a cBot running on your Windows or Mac machine inside the cTrader desktop app. The instance depends on the app and computer staying open; closing either stops the bot. Local instances have full .NET access, which suits cBots that need Windows-specific libraries or external dependencies.

A trading bot is software that follows predefined rules to analyse markets and place or manage orders. In cTrader, trading bots are called cBots; they are built with C# or Python in cTrader Algo (formerly cTrader Automate) and can be installed from Store as free or paid products. A bot can automate execution and reduce manual errors, but it does not remove market risk.

Live performance in cTrader Store is the published track record of a cBot or strategy from a real or demo account, attached to the product page so buyers can see actual behaviour over time. Live performance is more credible than a backtesting curve but still reflects one broker, one period and one parameter set — read the underlying account record, not only the summary metrics.

A cBot can execute and manage trades on the account it is attached to. A signal bot only identifies conditions and notifies the trader — typically by message, email or push — without placing orders. Store products should label which type they are; treat unclear labels as a reason to test on a demo account before live use.

A cBot is a cTrader trading robot, written in C# or Python and running in cTrader Algo. An EA (Expert Advisor) is the MetaTrader equivalent, written in MQL4 or MQL5. The concepts overlap, but the platforms and languages are different, so MT4/MT5 EAs do not run in cTrader. To move a strategy, the logic must be rebuilt as a cBot and re-tested.

Backtesting replays a cBot against historical data; live performance reflects current market conditions with real spreads, slippage, swaps and execution. Backtesting is useful for hypothesis testing and parameter selection; live (or demo-forward) results validate that the strategy survives current conditions. Use both.

Bot results differ across brokers because spreads, commissions, swaps, execution speed, slippage, symbol naming and session hours all change between brokers. A cBot tuned for one broker's raw spread account may underperform on another broker's standard account even with identical parameters. Re-test on the new broker's demo before assuming the same settings hold up.

A cloud cBot keeps running when cTrader is closed — even with your device off — because the instance runs in cTrader's hosted environment. A local cBot stops when you close cTrader Windows or Mac, because the instance depends on the desktop app. For 24/7 continuous trading without a VPS, choose cloud execution.