Build without programming
Configure the strategy through understandable controls instead of writing the full cTrader C# implementation.
cBot Factory turns a rule-based forex strategy into a structured cTrader automation project. Choose the market, combine technical indicators, define Buy and Sell entries, add confirmation rules, and control how every position is managed—without starting from a blank C# file.
A trading idea is easier to test when every condition is stated clearly. cBot Factory guides you through the decisions that are often hidden inside custom code: what creates a signal, what confirms it, when the bot may enter, and how the trade is protected.
Configure the strategy through understandable controls instead of writing the full cTrader C# implementation.
Move from a written concept to a structured strategy that can be reviewed, backtested, and demo-tested.
Choose which parameters remain adjustable through the delivered cBot interface for later testing and operation.
Keep the selected indicator structure and implementation from being casually changed or copied at code level.
The builder separates market selection, signal evidence, trade management, and final validation so each part can be understood and tested.
Choose the currency pairs and timeframe, then define currency-overlap, account-mode, and hedging rules.
Select indicators, edit their parameters, define separate Buy and Sell conditions, and require confirmed candle closes.
Configure position size, stop loss, moving profit protection, partial profits, break-even, and portfolio limits.
Check the complete rule set, resolve validation warnings, and prepare the cBot for cTrader testing.
Browse supported trend, momentum, volatility, and volume indicators. Each library entry explains what the indicator measures, which parameters can be configured, and what other evidence traders commonly use with it.
Learn how closed-candle confirmation works, why Buy and Sell rules should be considered separately, how indicators can complement one another, and why backtesting must be followed by broker-specific demo testing.
Add each supported technical indicator once and edit its parameters
Build Buy-only, Sell-only, or two-direction entry logic
Require multiple closed candles before a signal qualifies
Combine trend, momentum, volatility, and volume evidence
Choose trend-following, mean-reversion, breakout, or custom logic
Configure fixed targets, trailing profit, and partial profit taking
Manage multiple pairs, overlapping currencies, and hedge rules
Expose approved settings in the cBot interface while protecting its implementation
The generated strategy is intended to operate as a cBot in a compatible cTrader environment. Your broker still controls the available instruments, symbol naming, trade size limits, account type, hedging support, spreads, commissions, leverage, and execution conditions.
Backtest with realistic costs, then run the cBot on the same broker's demo environment before considering live trading.
No. The guided builder is designed to let you describe the trading rules and editable parameters without writing the cBot implementation yourself.
Yes. You can configure Buy and Sell entry conditions separately, enable one direction, or allow both directions when their respective rules qualify.
The parameters intentionally exposed in the cBot interface can remain editable. The selected indicator set and protected implementation are not intended to be freely changed at source-code level.
The cBot is intended for cTrader environments. Symbols, volume limits, hedging support, spreads, commissions, and automation permissions vary by broker, so every build should be tested on that broker's demo account.
No. Backtests and demo tests help evaluate assumptions, but they do not predict future performance or remove execution, market, or technology risk.
cBot Factory is a software configuration service, not financial advice, brokerage service, or a guarantee of profit. Technical indicators are derived from historical market data and can produce false, late, or conflicting signals. You remain responsible for testing, deployment, monitoring, and trading decisions.