Configure a master order, choose how it should be copied, and hit Execute. Watch the trade replicate in real time — and toggle between a local copier and a cloud copier to see the latency gap with your own eyes.
The simulator
1. Master order
2. Copy parameters
Order replicated
Master order opened, copier picked it up, subaccount mirrored. Here is the breakdown.
Simulation slowed for visibility · timings shown reflect realistic real-world milliseconds for each architecture.
What you just saw
The simulator walks through the same pipeline a real trade copier does. With the Local mode selected, the master terminal sends an order, the copier reads it from the local API in well under a millisecond, and the subaccount receives the mirrored order — total round-trip under 25 ms. Switch to Cloud mode and the master event has to travel through a vendor data centre before it reaches the subaccount broker — adding roughly 200 ms of pure network latency that the local path never pays.
The copy parameters mirror the real product. Choose Multiplier to scale the subaccount lot by a fixed ratio, Behoben to send a constant size regardless of master lot, or Risk % to compute the subaccount size from its own balance and the master’s stop-loss distance (the math is in the Pfeilführung). Rückwärts flips BUY into SELL and rearranges SL/TP. Versteckte SL/TP keeps the stop and target on the copier side rather than at the broker — the subaccount looks SL/TP-free to the broker, and the copier closes the position when price reaches the saved level.
What this is and isn’t. The simulator demonstrates the workflow, the parameters, and the realistic latency gap. It does not route live orders to a real broker — for that, install the actual software and connect MT4/MT5/cTrader accounts. The 10-day free trial gives you the full thing.
FAQ
Is the latency realistic?
Yes — within the typical observed ranges for each architecture. A local copier with master and subaccount terminals on the same Windows machine adds well under a millisecond of internal processing. A cloud copier routes through the vendor’s data centre, adding 100–500 ms depending on geography and broker proximity. The simulator uses the middle of those ranges.
What is “hidden SL/TP” actually doing?
The copier remembers the stop-loss and take-profit levels for the subaccount order, but does not send them to the broker. When the subaccount price reaches the saved level, the copier closes the position with a market order. To the broker, the subaccount looks like it has no SL/TP at all — useful when traders suspect stop-hunting or when prop firms restrict broker-side SL placement.
How does the Risk-% lot mode work?
The subaccount lot is computed as (subaccount balance × risk%) / (stop-loss distance × pip value). A 1 % risk on a 10 000 USD subaccount with a 50-pip SL works out to a roughly 0.20-lot position. The mode requires the master order to have a stop-loss — without SL, the formula has no risk denominator.
Can I configure more than one subaccount in the real product?
Yes — unlimited subaccounts in the licensed product. Each one can have its own platform (MT4, MT5, cTrader, FIX, DXtrade, MatchTrader, NinjaTrader), its own lot mode, magic-number filter, symbol mapping, and reverse setting. The simulator shows one master and one subaccount for clarity.
Why is Reverse mode useful?
Two common cases. One: you have a signal that loses consistently — reversing every trade turns the master into a profitable contra-signal. Two: hedging — running the reversed strategy on a second account locks in profit on whichever side wins. Reverse also rearranges SL/TP to preserve the same risk distance from the new direction.
Run this on real accounts
The simulator above is the workflow. The 10-day free trial is the real software, full features, no card required.
Kostenlose Testversion starten
German 
English 
Spanish 
Portuguese 
Chinese 
Japanese 
Hindi 
Arabic