Need a strategy automated or an indicator built for cTrader? barmenteros FX delivers production-ready cBots and custom indicators written in C# with the cTrader Algo API — tested against live broker conditions, source code included.
What You Get
Every project delivers these specific outputs:
- Fully compiled
.algofile ready to load in cTrader desktop - C# source code (
.cs) — you own it, no black-box delivery - Backtest reports from cTrader Backtesting, with equity curve screenshots
- Parameter reference and deployment documentation
- 30-day bug-fix warranty after delivery — see our warranty terms
How It Works
- Specification: You describe your strategy — entry/exit rules, risk settings, timeframe, instruments. We confirm scope and price before starting.
- Development: The cBot or indicator is built in C# with the cTrader Algo API, then tested against historical data and edge-case scenarios.
- Review and Revisions: You test against your broker. Up to 2 revision rounds are included in every quote — no extra charge.
- Delivery: Compiled
.algofile, C# source code, and documentation delivered via secure file transfer. You deploy to cTrader directly.
Who This Is For
Good fit:
- Traders on IC Markets, Pepperstone, FxPro, or any other broker that offers cTrader
- Traders with a defined strategy ready to automate — entry rules, exit conditions, risk parameters all specified
- MT4/MT5 traders migrating to cTrader who need their existing logic ported to C#
- Developers who need a second pair of eyes on a cBot that fails in live trading
Not the best fit:
- Traders without a defined strategy — we automate, we don’t design strategies
- Anyone looking for a copy of an existing cBot found online — original systems only
- If you trade exclusively on MetaTrader, see Expert Advisor Programming instead
What Makes This Different
cTrader algorithms are written in C# against the cTrader Algo API, a completely different environment from the MQL used by MetaTrader. The event model is different, position management works differently, and the way orders interact with broker infrastructure has its own set of edge cases. Developers who only know MQL4/MQL5 frequently miss these distinctions, producing cBots that pass a backtest but misfire on live accounts.
Live accounts expose conditions a backtest does not model. A backtest fills orders from historical prices; live execution depends on liquidity and network latency, which can lead to partial fills or slippage. The code accounts for these by design, not as an afterthought discovered after go-live.
Source code delivery is standard, not an add-on. Every project includes the .cs file alongside the compiled .algo. You own the system outright — modify it, extend it, or pass it to another developer without restriction. You can read what clients say about our work on our customer reviews page.
Pricing
Custom cBots and indicators start at $150 for simple single-rule automation. Standard projects with multiple conditions, risk management, and multi-instrument support typically range from $300–$1,200 depending on scope.
Every project receives a fixed-price quote before work starts — no hourly rates, no scope creep surprises. Quote turnaround is 48 hours.
Frequently Asked Questions
What is the difference between cTrader and MetaTrader programming?
cTrader algorithms are written in C#, or since version 5.4 in Python, against the cTrader Algo API. MetaTrader uses MQL4 or MQL5, a proprietary language with its own compiler and runtime. The languages, APIs, event models and broker communication layers are entirely different. A developer who knows MQL but has never built for cTrader needs to learn a new platform from scratch, or will produce code that compiles but fails in production. barmenteros FX develops for both platforms with separate, platform-specific toolchains built on real production experience.
Can you convert my MT4 EA to a cTrader cBot?
Yes. Platform conversion is a specific service. It is not a simple recompile: we rewrite the strategy logic in C# for the cTrader event model, map the MT4 order tickets the EA manages to cTrader positions and pending orders, and check that execution behaviour matches the original intent across multiple scenarios. Conversions typically cost $300–$800 depending on the complexity of the original EA. Submit a quote request with your .mq4 or .mq5 file attached for an accurate assessment.
How long does cTrader cBot development take?
Simple single-strategy cBots: 3–5 business days from confirmed specification to first delivery. Complex systems with multiple filters, risk management tiers, or multi-instrument logic: 1–2 weeks. Timeline is confirmed in your fixed-price quote before work starts. Revision rounds are included and do not extend the timeline unless the scope changes.
Do you provide the source code for custom cBots?
Yes, always. Every delivery includes the .cs source file alongside the compiled .algo. You own the code outright — no licensing terms, no usage restrictions, no requirements to credit the developer. If you want to modify the system later or pass it to another developer, you can do so without asking permission.
Which cTrader version do you develop for?
We develop for the current cTrader release and write cBots and indicators in C# with the cTrader Algo API. cBots are built and backtested in cTrader for Windows or Mac. Once built, a cBot can run locally in cTrader for Windows or Mac, or in the cloud, which every cTrader app, including Web and Mobile, supports. If your broker uses a white-label cTrader variant, include the broker name in your quote request so we can check for platform-specific deviations before quoting.