Trade Copier: How They Work and What Silently Breaks Them

A trade copier mirrors trades from one account to others automatically. One account opens a position, and within a fraction of a second the same position appears on every account connected to it, resized for each one. That is the whole idea, and it is simple enough that the interesting part is entirely in what goes wrong.

This page covers how a copier works underneath, local versus cloud setups, the four failures that silently cost money, how to size positions across accounts of different sizes, and where copiers are genuinely useful rather than just clever.

• A copier multiplies an outcome, not an edge. Losses copy exactly as well as wins.
• Local copiers are faster and fragile; cloud copiers are resilient and slower.
• Symbol naming is the most common cause of a copier that "does nothing".
• Balance-proportional sizing is the only sane default across different account sizes.
• On prop firm accounts, copying is restricted almost everywhere. Read the clause first.

How a trade copier works

Three parts. A master where trades originate, a transport that carries the instruction, and a slave that reproduces it.

On MetaTrader the usual build is an expert advisor on each terminal. The master EA watches for open, modify and close events and publishes them. The slave EA subscribes and executes the equivalent action on its own account. Transport is a shared file, a local socket, or an HTTP endpoint when the accounts sit on different machines.

The slave has to do considerably more than "open the same trade":

• Resolve the master's symbol to whatever this broker calls it, suffixes included.
• Convert the master's lot size into one appropriate to this account, then round to the broker's lot step and clamp to its minimum and maximum.
• Translate stop and target prices, which will not match because the two brokers quote differently.
• Respect this broker's minimum stop distance, which may be wider than the master's.
• Reconcile after a disconnect so a reconnecting terminal does not duplicate open positions.

That last one separates a copier you can leave running from a script that works until it does not. Without reconciliation a copier will eventually double a position, and a doubled position is how an account blows a risk limit in a single move.

Local versus cloud

The honest rule: if your strategy needs single-digit millisecond copying to work, the edge is too thin to survive a live spread anyway. For almost everything else, cloud is the better trade because uptime beats speed.

Four failures that cost money

1. Symbol suffixes

The master trades EURUSD, the slave broker calls it EURUSD.raw or EURUSDm. Without suffix handling the slave silently does nothing while the terminal looks perfectly healthy: EA attached, smiling face, no errors. You discover it when you compare statements a week later. This is the number one cause of "the copier isn't working".

2. Lot rounding

Proportional sizing produces fractional lots that must be rounded to the broker's step. On a small slave account that rounding is a large share of the intended position. Rounding up quietly increases risk beyond the master's; rounding down to zero drops the trade entirely. Neither is visible from the outside.

3. Partial closes and modifications

Copying opens and closes is the easy half. A master that scales out, moves a stop to break even, or trails a stop produces a stream of modify events. A copier that ignores them leaves the slave in a materially different trade, and by the time it matters the positions have already diverged.

4. Latency during the moments that count

The slave always fills after the master. On a swing system this is irrelevant. On a system targeting a few pips it can be most of the edge, and the gap is widest exactly when it hurts: at the open and around news, when the queue is longest. Measure master-to-slave delay under load, not at rest.

Sizing across different account sizes

Whichever you pick, every slave needs its own drawdown guard. Inheriting the master's risk logic is not enough when the slave carries limits the master does not have.

Where a copier is actually worth it

• One strategy, several of your own accounts at different brokers, so you are not repeating entries by hand.
• Separating strategies from execution. Run the logic once on a master and let accounts subscribe, rather than maintaining the same EA in five places.
• Managing accounts for others where each needs its own sizing and its own risk cap.

And where it is not: a copier does not diversify anything. Four accounts on one master is the same position four times, so the losing streak arrives on all four in the same week. The correlation is exactly one, and calling it diversification is the most expensive mistake in this area.

On prop firm accounts, read the rules first

Copying from a third party or a signal service is prohibited essentially everywhere. Copying between accounts you own varies: some firms permit it, others treat identical fills across accounts as a shared strategy. Firms also cap total capital per strategy across all your accounts, which is aimed precisely at running one master across several evaluations.

Simultaneous identical fills are trivially visible in the firm's own data, and the assessment usually happens at payout review, after the work is done. The detail is in trade copiers on prop firm accounts.

What we run

Ours exists because we needed a copier that understood prop firm rules rather than one that simply mirrored fills: per-slave lot multipliers, balance-proportional sizing, symbol suffix resolution, reconciliation after disconnect, and drawdown limits enforced on the slave rather than assumed from the master.

If what you actually want is the automation without operating a copier fleet, the JPTC Algo runs on your own account at your own broker and we host it, so there is nothing to install and no VPS.

Related: how latency affects copied accounts and setting one up across multiple accounts.