How cTrader Works: Accounts, Orders, Analytics and cBots
cTrader is software for accessing a broker-provided trading account, reviewing markets, managing orders and analysing recorded activity. The account and the provider's conditions matter: the platform name alone does not establish your instruments, costs, margin rules or execution outcome.
Begin with the account you have selected
Your cTrader ID is the login used across the cTrader ecosystem; a trading account is a separate broker account linked to it. Check the broker, account number, currency, account context and selected application before interpreting a balance or history. The official cTrader ID guide explains the distinction.
A broker-branded app and a cross-broker app need not expose the same set of accounts. The separate cTrader account guide explains account selection and the difference between hedging and netting. Do not assume a universal default account type.
Follow orders through to deals and positions
| Record | Meaning | Review question |
|---|---|---|
| Order | An instruction with a type, size and any applicable price or protection settings | What was requested, and what happened to the instruction? |
| Deal | A recorded execution of all or part of an order | At what time, volume and price did execution occur? |
| Position | The resulting exposure, handled according to the account's position model | What exposure remains, and which executions changed it? |
The official positions and deals explanation describes this relationship. One order is not necessarily one deal, and a position can be changed by further executions. This matters when comparing counts, partial fills and performance records.
Review the selected order settings and the provider's conditions. A displayed price or depth view is not a promise that a requested volume will fill at that price. Do not infer a guaranteed execution speed, a universal routing model or identical mobile and desktop outcomes from the platform interface.
Review recorded results with native analysis
cTrader includes native analysis rather than only an execution screen. The Windows Analyze guide documents account-performance views. Select the intended account and period, then reconcile the available history, costs and open-position context before drawing a conclusion.
Distinguish realised balance changes from observed equity that includes open positions. Separate external cash flows from trading gains. An account-level result can include manual activity and several algorithms; it is not automatically the result of one cBot.
Understand the two cBot execution modes
The current cTrader Algo documentation supports C# and Python. A cBot is an automated strategy using that environment; a MetaTrader executable is not a cTrader bot merely because the strategy idea is similar.
| Mode | Where it runs | What to check |
|---|---|---|
| Cloud instance | cTrader's cloud environment rather than your local application | The selected instance, account, current runtime limits and cloud dependency requirements |
| Local instance | Your Windows or Mac machine with cTrader running | Application availability, connectivity and local resources |
The cloud features guide distinguishes synchronisation from execution and documents local versus cloud operation. Cloud availability does not mean that every bot, dependency or saved file behaves identically there. Review the actual instance and current constraints instead of assuming that every cBot always runs on a server.
Keep sharing and external analytics separate
A report, an authorized API connection and a trading login are different ways of exposing account information. Use the actual permission model and disclose the account context, period and any selected history. An analytics label does not independently establish account ownership or an immutable record.
MyVeridex currently offers MT4 and MT5 connections; it does not offer a cTrader connector. Do not enter cTrader credentials into an MT4/MT5 form or assume a cTrader report is accepted by an MT5 statement parser. Use the cTrader analytics guide for the currently documented native review options.
Frequently asked questions
Does using cTrader guarantee direct market access or a particular execution speed?
No such guarantee follows from the platform name. Check the actual provider, account conditions, instruction and recorded execution rather than assuming one universal routing or latency result.
Do all cBots keep running after I close the app?
No. Local instances depend on the local cTrader application and machine. Cloud instances are a separate mode with current platform and dependency limits; check the actual instance.
Is cTrader Algo limited to C#?
No. The current official documentation describes C# and Python. Check the current API and execution-environment requirements for the specific project.
Can MyVeridex currently connect to cTrader?
No. The current offered connectors are MT4 and MT5. Native cTrader analysis, report sharing and cTrader API authorization are separate workflows.
Review your trading history
Use MyVeridex trading analytics to review and share an imported trading history. Check connection support and metric definitions for your account.
Start Free 7-Day Trial