Most copiers are captive to a running terminal. cTrader breaks that rule: its Open API lets the whole copy run on a server, with no chart open and no VPS to babysit. That changes what a clean multi-account setup looks like — and it introduces a few pitfalls that are specific to how cTrader prices and fills trades.
Why cTrader copying can run fully backend
On MetaTrader, the copier usually lives next to a terminal — an expert advisor on a chart, or a local app reading the master. cTrader’s Open API is different: it’s an authenticated connection straight to the trading server, so a backend service can place, mirror, and monitor orders directly.
The practical payoff is that the copier no longer depends on a machine you have to keep alive:
- No terminal, no chart — the copy flows even with every app closed.
- No VPS to maintain — nothing to crash, patch, or reconnect at 3am during a news release.
- One connection per account — the backend authenticates to each cTrader prop account and dispatches fills server-side.
Shibiki’s cTrader integration runs on exactly this model: the copier and the risk enforcement live in the backend over the Open API, so mirroring across your cTrader prop accounts keeps working without a terminal in the loop.
Open API vs cTrader Copy: the difference
cTrader also ships a built-in feature called cTrader Copy, and it’s easy to conflate the two. They solve different problems.
| cTrader Copy | Open API copier | |
|---|---|---|
| Who runs it | Broker-hosted marketplace feature | Your own backend service |
| Best for | Following a public strategy provider | Mirroring your own accounts |
| Control over sizing | Provider-defined, limited per follower | Full per-account control in your code |
| Cross-broker reach | Within the cTrader Copy ecosystem | Any account you can authenticate |
| Fit for prop rules | Third-party management can conflict | You control every order and limit |
The distinction matters for prop firms because most permit copying your own trades across your own accounts, while treating third-party management or paid signal services as something else entirely. An Open API copier you control keeps you clearly on the “your own trades” side of that line — but the rules vary and change, so confirm each firm’s copy policy in writing. The5ers and FunderPro publish account-management terms, and they aren’t interchangeable.
Handling different asset pricing and quote currencies
The subtlest cTrader pitfall is quote currency. cTrader accounts can be denominated in different currencies, and the same instrument’s profit and risk translate through the account’s currency before they hit your balance. Mirror a EUR-quoted move onto a USD-denominated account without accounting for the conversion and the copied position carries a different real risk than the master did.
This shows up in a few places:
- Pip and tick value for the same pair differs once converted into each account’s base currency.
- Cross-currency pairs add a second conversion step that a naive copier ignores.
- Equity math — the number your drawdown floor is measured against — is computed in the account currency, so identical trades can sit at different distances from the line.
A correct copier converts each leg into the destination account’s currency when it sizes the trade, rather than assuming one lot means the same risk everywhere. Get this wrong and you’ll believe every account is risking the same amount while one is quietly over-leveraged.
Position sizing across cTrader accounts
As with any copier, the cardinal error is mirroring one size to every account. cTrader prop accounts differ in size, in drawdown floor, and — per the point above — in currency, so a raw clone over-leverages the smallest account and wastes room on the largest.
Size per account, driven by each account’s own risk:
- Set a copy ratio per account so a small account never inherits a big account’s raw volume.
- Size to each account’s own drawdown line, and to the account currently nearest its floor as the binding constraint for the group.
- Run each account’s intended risk through a position size calculator, including the currency conversion, so the same signal lands correctly sized everywhere rather than uniformly sized.
Because cTrader trades in volume with fine granularity, you have more room to hit the right size per account than on some platforms — but only if the copier is doing the conversion and the per-account scaling, not forwarding a flat number.
Reconciling fills without a local terminal
The flip side of running headless is that there’s no terminal window to eyeball. When the copier lives in the backend, you need the backend to report every fill so you can verify the master and its copies actually agree.
Good reconciliation over the Open API means:
- Confirming each master fill produced a matching slave fill at the expected converted size, on every account.
- Flagging any account where the copy rejected, partially filled, or slipped beyond tolerance.
- Keeping a per-account record for drawdown and payout math while recognizing copied fills as one decision executed many times, not many independent trades — otherwise your sample size and your confidence in the edge both inflate.
This is the shape of copying Shibiki is built for on cTrader. It copies one strategy across your cTrader prop accounts entirely over the Open API — no VPS, no terminal — and auto-journals every fill on every account into a single de-duplicated record, so it computes live edge health with a Wilson confidence interval on the underlying decisions rather than the inflated fill count. And it enforces hard risk limits at the broker per account, currency-aware, so a conversion surprise or an over-sized master can’t quietly breach your tightest account while nothing is open on your screen. Run it backend, size it per account, and reconcile every fill without ever opening a chart.
Related: cTrader integration · Position size calculator · The5ers