What is Ctrader Basics compatible with?

Direct answer

Ctrader Basics is mainly “compatible with” whatever combination lets the cTrader platform run and connect to your trading environment. In practice, this means (1) your operating system, (2) how your broker provides access to cTrader accounts and execution, and (3) whether the data and automation features you plan to use are available and permitted in your setup.

Compatibility is not a single yes/no feature. It is the result of several requirements lining up at the same time: the platform must run on your device, your broker must support the relevant account integration, and any automation must be allowed to access the necessary functions.

Mechanism and definition: what “compatible” usually means here

Think of compatibility as three layers:

Operating system layer Your computer or device must support running the cTrader application (for example, Windows). If the operating system is not supported, nothing else matters because the platform cannot start.
Broker and account integration layer Even if the platform runs, the broker integration determines what you can access: account connection, order execution behavior, and which instruments or account features are exposed through that broker’s cTrader setup. Different brokers can expose different capabilities.
Data and automation layer Some functions depend on market data quality, update frequency, and permission/connection stability. Automation (such as scripts or robots) typically requires that:

the platform can receive the necessary data,
the automation is permitted to run in that environment,
and the connection remains stable enough for the automation to behave as expected.

A helpful way to check compatibility is to define the exact feature you care about (for example, connecting an account, viewing certain data types, or running an automation) and verify that each layer supports it.

Evidence or example: how mismatches show up

A common mismatch pattern looks like this:

Your operating system can run the platform (so the app launches).
You connect a broker account successfully (so basic functionality works).
But a specific automation fails to start, shows errors, or behaves differently than expected (so the data/permission/stability layer is not aligned).

Another mismatch pattern is instrument availability:

The platform supports the general environment.
The broker connection succeeds.
Yet certain instruments, account settings, or features are not available because the broker’s cTrader implementation does not expose them to your account.

These examples highlight an important point: “compatible” often means “works end-to-end for the feature you are using,” not “works in general.”

Limitations and risks

There are material limitations to keep in mind:

Outcomes vary by market conditions, costs, execution conditions, and your account setup. Past behavior and historical relationships do not guarantee anything about future results.
A demo setup (if available) can help detect technical incompatibilities, but it may not reflect real execution conditions such as latency, spreads, and commission structure.
Automation adds failure modes: network interruptions, data gaps, permission restrictions, or changes in how the platform reports events can all cause unexpected behavior.

Because you are trying to assess compatibility, the safest approach is to treat it as a verification task rather than an assumption. If you cannot independently reproduce the expected behavior, you should not conclude that the setup is fully compatible.

Verification or next question

To verify compatibility yourself, compare your needs against each layer:

Does your device support running the cTrader application you intend to use?
Does your broker provide a cTrader account connection that exposes the features you need?
If you use automation, can it run without errors, and does it receive the data it relies on?

If you tell me which operating system you use and what you mean by “Ctrader Basics” in your context (for example, connecting an account, viewing data, or running automation), I can help you form a concrete compatibility checklist with clear validation steps and common failure modes.