Components of a Copy Trading Platform: Data Flow and Speed
Account connections, the engine, sizing, the order tag and alerts: the five parts of a trade copier, the path one fill takes through them, and where its time goes.
16 Oct 2026 · 5 min read
On this page
A copy trading platform that repeats your own trades between your own accounts — a trade copier — has five components: the account connections, the engine, the sizing rule, the order tag and the alerts. One fill passes through them on a fixed path: the source broker reports it, the engine sizes a copy and sends it to every follower, and each follower broker executes it at its own price. That last part is usually the largest and the most variable share of the time a copy takes.
"Copy trading" also names following someone else's trades, which is a different product: trade copier vs copy trading vs signals sets the two apart. This guide is about the tool that repeats your own trades, in general and in Trepeat's case.
What are the components of a copy trading platform?
Each of the five does one job, and a copier is only as dependable as the weakest of them:
| Component | What it does | In Trepeat |
|---|---|---|
| Account connections | Hold a live link to every account: hear the source's fills, place orders on the followers | MetaTrader through MetaApi; cTrader directly, authorised with your cTrader ID, so no cTrader password is stored. Currently demo accounts only |
| The engine | Listens to the source and acts on every fill, around the clock | One program on Trepeat's servers for every Running repeater; nothing runs on your computer |
| Sizing | Works out each follower's lot from the source lot | A fixed multiplier or an equity ratio, rounded to the follower symbol's volume step and capped by Max Volume |
| The order tag | Marks the copier's own orders, so it can tell them from yours | A magic number and an order comment on MetaTrader, a label on cTrader; automatic closes touch only tagged positions |
| Alerts and the record | Tell you when a copy did not land, and keep what happened | A failed copy is recorded with the broker's reason and raises an alert; every copy keeps its own time and how it was sized |
In Trepeat the settings that join the parts together sit on a repeater: which account is the source, which are followers, the sizing rule, and the symbol allowlist and remapping. The tag is what lets you keep trading by hand on a follower account, and the sizing rule is covered in position sizing when copying trades.
How does data flow through a trade copier?
One fill takes this path from the source account to a follower account:
- The source broker fills your order and reports the fill to the connection watching that account. Trepeat hears it over a live stream rather than on a timer: from MetaApi for MetaTrader, and from cTrader's own connection for cTrader.
- The engine turns the fill into a copy for each follower: it applies the repeater's symbol rules, names the instrument for the follower and sizes the lot. How a trade replication engine works sets out those steps one by one.
- The order goes to every follower at once, as a market order carrying the tag: through MetaApi to a MetaTrader broker, or straight to cTrader.
- Each follower broker executes it at its own price at that moment, and confirms.
- The result is recorded. A confirmed copy is stored with the time it took; a refused copy, or one not confirmed within the repeater's own limit, is recorded as failed and raises an alert.
A close travels the same path, from the source broker's report to each follower's confirmation.
| Part of the path | Who controls it | Where you see it in Trepeat |
|---|---|---|
| Source broker reports the fill | The source broker | Not in the copy's recorded time |
| Engine sizes and sends the copy | Trepeat | Trepeat engine |
| Route to the follower broker, and its execution | The network, MetaApi for MetaTrader, and the follower broker | Broker latency |
Where both were recorded, the Trades page shows each copy's Total latency split into those two parts, and the export carries both columns; see trades and positions.
What sets execution speed in copy trading?
Execution speed in copy trading is set mostly by the follower broker, then by how the copier hears fills. A copier on a live stream starts the moment the fill arrives; one that polls on a timer can wait a whole interval first. After that, the order's route and the follower broker's execution take the rest, and the follower broker's part is usually the largest and the most variable: it changes with the broker, the instrument and the market at that moment.
Where the copier runs matters less than either; see cloud vs local (VPS) trade copiers. Rather than trust one headline figure, look at each copy's own time on your accounts. Trade copier latency: how fast is enough lists every delay in order, and the scalping trade copier page says what to check when your trades are short.
What happens when one part fails?
A copier is judged by what it does when a part breaks. In Trepeat:
- A follower's connection drops. That follower is paused and the rest of the repeater carries on. Once it reconnects, unpause it in the repeater's settings, or press Run if the repeater stopped.
- The source's connection drops. The repeater stops.
- A follower misses a close while offline. On reconnect you get an alert to close that copy yourself; it is not closed later in the background.
- A broker refuses a copy. The copy is recorded as failed, with the broker's reason, and raises an alert.
- Two engine processes overlap during an update. Only one may act on an account at a time; the other tracks it without placing anything, so a fill is not copied twice.
Where Trepeat fits
Trepeat is a cloud trade copier for MetaTrader 4, MetaTrader 5 and cTrader, built from the five parts above. It currently connects demo accounts only, the type many prop-firm evaluation and funded accounts run on, and costs $15 per account per month with every feature included. How Trepeat works is the reference for its engine, and what a trade copier is starts from the beginning.