C# / .NET
cBots, custom indicators and plugins written against the cTrader Algo API, working with the platform’s own events, chart objects and order operations.
Explore C# / .NET →Hire a cTrader developer to build custom cBots, indicators, and tools around your trading rules. Our cTrader development services include prop trading automation, trade copiers, Python development and integrations — with clear requirements, practical testing, and support after delivery.
Custom automation, analytical tools, and integrations built to work together.
Nordman Algorithms develops cTrader software for traders, prop account users, educators, and trading software vendors. Our cTrader programmers turn written rules, indicator signals, and existing code into cBots, custom indicators, scanners, trade managers, and connected trading tools.
We use C# and Python with cTrader Algo, extend the platform through plugins, and connect external systems through suitable APIs. Python projects can run their logic within cTrader or exchange data with an external model. Prop trading automation is defined around the account rules, while execution is adapted to symbol settings and broker conditions. Source code and full IP ownership are transferred on delivery.
Start with the outcome you need: automate a strategy, create an analytical tool, connect a signal source, or improve your existing cTrader software.
Turn your entry, exit, and money-management rules into a custom cBot. Build indicator-based or price-action strategies with session filters, multi-timeframe conditions, and defined position management.
Create indicators for your own calculations, market structure, chart patterns, and trading signals. Define visual output, alerts, forming and confirmed conditions, and values that a cBot can read.
Build tools around the rules of your cTrader prop account: daily loss limits, drawdown monitoring, exposure controls, and permitted trading hours. Define reset times, calculations, and automated actions before development.
Copy trading activity between cTrader accounts or supported external platforms. Configure symbol mapping, volume scaling, order updates, partial closes, and how the copier handles interruptions or unmatched positions.
Execute TradingView alerts, Telegram or Discord signals, and custom API instructions in cTrader. Add parsing, signal validation, duplicate handling, sizing rules, and a clear record of each execution attempt.
Convert strategies and indicators between cTrader and MT4, MT5, TradingView, NinjaTrader, or other supported platforms. Rebuild calculations, order logic, and chart behaviour against agreed reference examples.
Develop native cTrader cBots and indicators in Python, or connect an external Python model to your trading workflow. We define where calculations run, how data and signals are exchanged, and which component manages execution.
Fix or extend existing cTrader source code. Investigate incorrect signals, missed trades, sizing errors, and chart issues; then add the filters, settings, or behaviour required by your updated specification.
Connect trading systems, market data, reporting, and external services using cTrader Open API, FIX API, or a cTrader component. Select the interface around the required account data, trading actions, and access permissions.
Extend the cTrader workspace with custom panels, integrated services, and platform tools. Add account utilities, tailored controls, and information displays that support the way you work inside cTrader.
Track conditions across instruments and timeframes in one view. Build signal matrices, currency-strength displays, account summaries, and configurable alerts with the filters and detail you need.
Create controls for manual and semi-automated trading. Calculate position size from risk, place orders, set SL/TP, move stops to breakeven, and apply your own partial-exit or trailing rules.
Prepare cBots, indicators, and plugins for controlled distribution. Add trials, expiry rules, user or account restrictions, and suitable licence checks around the protection already provided by cTrader.
Not every requirement fits a predefined category. Send a description, screenshots of what you have in mind, reference files, or existing cBot or indicator source code — we will review it and tell you what is technically possible on cTrader and what it would take.
A cTrader programmer clarifies the expected signals, trading actions, and operating conditions first, then works to an agreed specification, fixed quote, timeline, and set of acceptance examples.
Send a description, marked-up charts, or the code you want to improve. For a bug fix, include the expected result, what actually happens, and the relevant logs. We clarify symbol settings, account rules, and external connections with you.
Your delivery includes the agreed source files and cTrader package, plus any external components in the scope. We explain installation, parameters, dependencies, and the settings used during testing.
C# and Python run inside cTrader Algo; the remaining interfaces connect authorised external applications to accounts, pricing and execution.
cBots, custom indicators and plugins written against the cTrader Algo API, working with the platform’s own events, chart objects and order operations.
Explore C# / .NET →cTrader Algo supports Python algorithms directly, so trading logic can run in the platform itself. Python is also used outside it for analytics and models that feed a cBot or an Open API service.
Explore Python →Authorised applications reach account data, market data, positions, order operations and history through the Open API, with official C# and Python SDKs. This is the route for software running outside the platform.
cTrader FIX sessions for pricing and order execution, including session handling, sequence management and recovery. Distinct from the Open API, which covers account and reporting operations.
Explore FIX Protocol →Realtime Open API communication and compatible external streaming services, with subscription state and reconnection handled in the connecting application.
Explore WebSocket API →TradingView alerts or another event source post to a receiver, which validates the instruction and passes it to the cTrader execution component.
Explore Webhook →cTrader is an FX and CFD environment. Forex is the core, other exposure comes through broker-listed CFDs, and the exact instrument list is set by the connected broker.
cBots, indicators and scanners for currency pairs and the CFDs your broker lists beside them — indices, metals, energies, commodities, shares, ETFs and crypto. Calculations and execution follow the account’s symbols and contract settings.
Forex Automation →These are underlying categories inside the platform’s CFD offering, not separate markets. Which of them your account carries — and under what contract sizes and trading hours — is set by the broker, so it is confirmed before a project is scoped.
Your project is built around a defined cTrader workflow, with the technical scope, delivery terms, and support responsibilities agreed before development.
cBots, indicators, plugins, and Open API integrations built with the cTrader Algo API by cTrader programmers who work with the platform daily.
Symbol specifications, volume increments, trading hours, account rules, and API permissions are reviewed when defining the execution logic.
Receive an agreed feature list, fixed quote, and schedule. Additional requests can be assessed separately so the original delivery remains clearly defined.
Discuss proprietary rules under an NDA when needed. Source-code delivery and ownership terms are established before work starts.
Get help with installation, input settings, and technical questions within the agreed support scope. Existing projects can be extended as your requirements change.
Our cTrader indicators are built with the same cTrader Algo API used for client projects. These examples show how we turn specific analytical requirements into working tools.
Detects Classic and Hidden SMT divergence between correlated instruments on cTrader charts.
Detects bullish and bearish Order Blocks and tracks their state through the cTrader session.
ICT session windows with pivot levels and breakout confirmation for cTrader trading workflows.
Detects bullish and bearish Fair Value Gaps and tracks mitigation on cTrader charts.
Browse our cTrader products, or ask us to build a tool around your own trading rules.
Answers about custom cBots, Python development, existing code, platform tools, and commissioning a cTrader project.
Share your trading rules, example charts, and the signals or actions you expect. Existing source files, indicator references, broker details, and integration requirements help us assess the work. A complete specification is not required at the first contact; we clarify missing details and agree the scope with you.
Yes. We review the editable C# or Python source, reproduce the issue, and define the requested changes. Work can include missed signals, incorrect sizing, new filters, chart adjustments, or changes to position management. A protected .algo package without source is not a substitute for editable code; a rebuild can be assessed from a sufficiently detailed specification.
Yes. Python can be used for native cTrader cBots and indicators. We can also connect an external Python model or analytics process through Open API or another suitable interface. The project scope defines where calculations run, which dependencies are needed, and how trading instructions reach the account.
Yes, where the account supports the proposed tools and the firm permits the workflow. We can implement daily loss monitoring, drawdown calculations, exposure limits, session filters, and agreed automated actions. The specification defines reset times and the treatment of floating profit or loss. Software controls do not guarantee a passed evaluation or compliance under every execution condition.
A trade copier reads activity on a source trading account and applies corresponding actions to receiving accounts. A signal copier interprets external instructions, such as TradingView alerts or Telegram messages, before placing cTrader orders. Both require clear rules for symbols, sizing, duplicate handling, and connection interruptions.
Yes, when source code or a detailed specification is available and the required functions can be reproduced. We rebuild the calculations, trading logic, and visual behaviour for cTrader, then compare the result with agreed examples. An indicator can also become part of a cBot when its signals and the required entry and exit rules are clearly defined.
A plugin extends the cTrader workspace with custom tools or integrated services. A scanner or dashboard helps you monitor instruments, signals, or accounts. A trade panel and trade manager provide controls for order entry and position management. A scanner or panel may be implemented as a plugin; the project is defined by the workflow you need.
Open API can connect authorised applications to cTrader market data, trading operations, account activity, and history. FIX API supports a different set of trading and pricing messages. We choose the interface according to the required functions and define authentication, request limits, reconnect behaviour, and any supporting components.
After the technical assessment, we provide a fixed quote and timeline for the agreed scope. Testing uses reference charts, expected signal and trade examples, cBot backtesting where appropriate, and demo-account checks for execution and integrations. Delivery includes the agreed source code, cTrader package, setup guidance, and technical support.
Yes. We can add trial periods, expiry rules, user or account restrictions, and suitable licence validation to cBots, indicators, and plugins. The design takes account of cTrader’s built-in protection and your distribution model. Access during renewals or connection interruptions is defined in advance; no protection method can guarantee absolute resistance to copying.
Send your trading rules, example charts, existing code, or integration requirements. We will review the materials and define a practical scope for your cTrader project.