What a Trade Replication Engine Is
A trade replication engine is the software layer that watches one designated leader account and reproduces its trades on one or more follower accounts in real time. It sits between the broker connections, reads what the leader does, and decides what each follower should do in response.
In futures trading the engine connects directly to broker APIs rather than reading a screen or a chat message. That direct connection is what lets it react to a fill in the moment, apply a separate set of rules to each account, and confirm the result per account. A futures trade copier is the product built around this engine.
The engine does the same loop on every leader action. It detects the event, builds the follower orders, checks each account against its own rules, sends the orders that pass, and records the confirmations that come back.
Step One, Reading the Leader Fill
The cycle starts when the leader account does something. That can be an entry, an exit, or a change to a working order. The engine learns about it through the broker API for the leader account.
There are two ways an engine can find out. It can poll, asking the broker on a fixed timer whether anything has changed, or it can be event driven, receiving a message from the broker the moment the order event fires. Event driven detection reacts as soon as the broker reports the fill. Polling adds a wait equal to the timer interval on top of network time, which can leave followers a step behind on a fast move.
Tradecopia uses event driven detection. It reads the leader fill straight from the broker API for Tradovate, NinjaTrader, Rithmic, and TopstepX, and from your broker when you trade through TradingView. The leader is a real account you trade yourself, so the engine mirrors the fills you take rather than placing your entries for you.
Step Two, Building Each Follower Order
Once the engine has the leader event, it constructs an order for each follower rather than blindly copying one order many times. Every follower can be set up differently, so the engine assembles the order from that account's own settings.
- Instrument. The same contract the leader traded, mapped to the follower's platform.
- Direction. Buy or sell, matching the leader, unless prevent hedging logic needs to flatten an opposing position first.
- Quantity. The leader size multiplied by that follower's quantity multiplier, so a follower set to 0.5 takes half the size and one set to 2 takes double.
- Brackets. Any stop and target attached to the leader trade, carried through so the follower is protected the same way.
Building the order per account is what makes it possible to run different account sizes together. A small evaluation account and a larger funded account can follow the same leader and each take the size that fits its rules.
Step Three, Filtering Each Account Before It Sends
Before any follower order leaves, the engine checks that account against its own risk filters. This happens on every signal, per account, which is the part that makes replication practical for prop firm traders who each hold accounts with different rules.
Each follower can carry its own daily loss limit, daily profit limit, and trades limit, plus position size caps. Where the account runs on Tradovate you can also add weekly limits. If an account has already hit one of its thresholds, the engine sends it no order for that signal and leaves every other follower running. A breach can market close the affected account and pause its copying while the rest of the group trades on.
Tradecopia also shows live Distance to Drawdown for each account, the room left before that account's trailing threshold. An automatic trailing drawdown parameter is on the roadmap and is not active yet, so the Distance to Drawdown display is there to help you manage the threshold alongside the daily limits. See per-account risk controls for prop firms for the full set of filters.
Step Four, Sending, Confirming, and Logging
The orders that pass their filters are submitted to each follower's broker. The engine then waits for a fill confirmation from each account and records it. That per account confirmation is important, because it is how the engine knows the copy actually happened rather than assuming it did.
Fills, slippage, and per account results are logged so you can reconcile against your broker statements later. If a follower's order is rejected, the engine can resubmit it in a form the broker will accept rather than silently dropping the trade.
Latency, and What Actually Affects It
Replication is fast but not instant. The time between the leader fill and the follower fill depends on a few things the engine does not fully control.
- Detection method. Event driven detection removes the polling wait, so the engine starts building follower orders as soon as the broker reports the leader fill.
- Broker APIs. Each broker responds at its own speed, both when reporting the leader fill and when accepting the follower order.
- Network conditions. The round trip to each broker adds real time, which is why where the engine runs matters.
Because latency is shaped by the brokers and the network, an honest engine reports what happened per account rather than promising a fixed number. The log tells you the real fills, which is what you reconcile against.
Staying in Sync When Something Goes Wrong
A reliable engine plans for the moments when a connection drops or an order does not behave. Two mechanisms handle the common cases.
The position reconciler compares each follower against the leader and squares up any account that has drifted out of sync after a disconnect or a reconnect, so you are not left cleaning up an orphaned position by hand. Prevent hedging handles flips and reversals cleanly, so a follower does not end up holding a position opposite to the leader after a fast direction change.
These are the difference between an engine that copies well on a calm day and one you can trust across a full session.
Where the Engine Runs
The engine has to run continuously during market hours, so where it runs changes how you manage it. On Pro it runs as a desktop app on your own Windows or macOS machine, and your broker credentials stay local. On Pro+ Lite and Pro+ it runs in the cloud, always on, reachable from any browser with no local machine required.
The copy engine and its risk filters are the same on every plan. The only thing that changes is whether the engine runs on your desk or in a hosted environment. For a plain language walkthrough of the whole flow, see how futures copy trading works.