Copy trading requires always-on infrastructure. A master account generates signals, slave accounts replicate them, and every terminal in the chain must stay connected 24/7. If the master takes a trade at 3:00 AM and your home PC is in sleep mode, the slaves miss the entry. If the master closes during Asian session and your connection drops for 10 minutes, the slaves hold the position without an exit signal. A VPS eliminates this failure mode entirely.
This guide walks through every type of copy trading setup, step-by-step configuration, resource planning, and monitoring for synchronization issues.
Types of Copy Trading
Before diving into setup, understand which copy trading model fits your situation.
Local copier runs all terminals on the same VPS. The master and slaves share the same machine, and trades copy through shared files or memory with virtually zero delay. This is the simplest and most reliable configuration.
💡 Tip: For copy trading, both master and follower accounts benefit from VPS hosting. Even a few milliseconds of delay between signal and copy can mean different fill prices, especially during fast-moving markets.
Remote copier sends trades between different servers or VPS instances. Necessary when master and slave accounts are with brokers in different geographic locations. Adds network latency to the copy process.
Signal provider is a variation where you publish trades to a service (like MQL5 Signals), and subscribers automatically copy them. The infrastructure requirement is on the provider side — your master terminal must stay online.
MAM/PAMM handles allocation at the broker level. The broker’s system distributes trades to sub-accounts based on equity or lot rules. This requires no copier software, but your master account still needs 24/7 uptime.
Local Copy Trading Setup on VPS
This is the configuration most traders need. Everything runs on one VPS.
Step 1: Install Separate MT4/MT5 for Each Account
You cannot run multiple accounts from one MetaTrader installation. Each account needs its own install directory.
Download the MT4 or MT5 installer from your broker’s site. During installation, change the default path. Install your master to C:\MT4_Master\ and each slave to C:\MT4_Slave_01\, C:\MT4_Slave_02\, and so on. Log into each terminal with its respective account credentials.
Step 2: Install Copier Software
The copier runs as an EA on both the master and slave terminals. Several options exist:
Local Trade Copier (LTC) is the most widely used. It communicates through files in the MQL4/Files directory. Attach the Server EA to any chart on the master terminal. Attach the Client EA to any chart on each slave terminal. Each client needs a unique ClientNumber parameter.
💡 Tip: Each MT4 terminal uses 300-600MB of RAM; MT5 uses 600MB-1.2GB. Add 1.5GB for Windows overhead, then pick a plan with at least 20% headroom to handle tick-data spikes during high-volatility sessions.
Duplikium offers a similar approach with a web dashboard for monitoring. It connects master and slaves through a cloud relay, which adds slight latency but simplifies setup for remote copying.
Custom EAs work if you have MQL programming skills. The basic approach: the master EA writes trade events to a CSV file, the slave EA polls that file every 100-500ms. On a VPS with SSD storage, file I/O latency is under 1ms.
📊 Key Stat: NVMe SSDs respond in 0.02-0.05ms per I/O operation versus 5-15ms for HDDs — a 100-300x improvement. For tick-intensive EAs processing thousands of data points per hour, this eliminates disk as a bottleneck.
Step 3: Configure Copy Parameters
Open the copier EA’s settings on each slave and configure:
- Lot multiplier: If the master trades 1.0 lots and the slave account is half the size, set the multiplier to 0.5.
- Symbol mapping: Some brokers use different symbol names for the same pair — one uses EURUSD, another uses EURUSDm or EURUSD.raw. Map the master’s symbols to the slave’s exact symbols.
- Reverse copy: Some copiers support copying trades in the opposite direction. The master buys, the slave sells. Used for hedging setups.
- Maximum slippage: Set the maximum allowed price deviation when copying a trade. If the slave can’t fill within this range, the copy is rejected rather than filled at a bad price.
Step 4: Test with Small Lots
Before running live with real size, place a 0.01 lot trade on the master and verify it appears on every slave within one second. Check that the lot size, direction, stop loss, and take profit all copied correctly. Test a trade modification (moving the stop loss) and a manual close. All three actions — open, modify, close — must copy reliably.
Resource Requirements
This is where copy trading setups either work or fail. Traders underestimate how many resources multiple terminals consume.
Each MT4 terminal with a couple of charts uses approximately 300-400MB of RAM. MT5 terminals use 400-600MB. The copier EA adds minimal overhead — it is the terminals themselves that consume resources.
Master + 3 slaves (MT4): 4 terminals at roughly 350MB each = ~1.4GB minimum. Add 50% buffer for peak usage = ~2.1GB needed. The Standard plan at $9.99/mo handles this.
Master + 5 slaves (MT4): 6 terminals = ~2.1GB minimum, ~3.2GB with buffer. The Pro plan at $19.99/mo provides comfortable headroom.
Master + 7 slaves (MT5): 8 terminals at ~500MB each = ~4GB minimum, ~6GB with buffer. The Elite plan at $29.99/mo is the right choice here.
Keep slave terminals lean. Each slave only needs one chart with the copier EA attached — the copier monitors all trade activity regardless of the chart’s symbol. Do not load unnecessary charts or indicators on slave terminals.
Critical Settings for Copy Trading
Lot Sizing
Never leave the default “copy exact lot size” setting when master and slave accounts have different balances. A master trading 1.0 lots on a $50,000 account is risking 2%. Copying 1.0 lots to a $10,000 slave account means risking 10%. Use one of these approaches:
Proportional sizing calculates the slave’s lot based on equity ratio. If the slave has 20% of the master’s equity, it trades 20% of the master’s lot size.
Risk-based sizing keeps the percentage risk constant across all accounts regardless of balance. The master risks 2% per trade, the slave risks 2% per trade, but absolute lot sizes differ.
Fixed lot override ignores the master entirely. Every copied trade uses a preset lot size. Useful for funded accounts with strict maximum position size rules.
Symbol Mapping
Different brokers name the same instrument differently. EURUSD at one broker might be EURUSDm, EURUSD.r, or EURUSD_raw at another. If the copier can’t find the matching symbol on the slave, the copy fails silently.
In most copier software, you configure a mapping table. Open the slave broker’s Market Watch (Ctrl+M in MetaTrader) to see their exact symbol names, including any suffixes or prefixes.
✅ Best Practice: In Market Watch, right-click and “Hide All,” then add back only the symbols your EA trades. Every visible symbol is a live data stream consuming CPU and bandwidth for zero benefit.
Copy Latency
Local copying on the same VPS happens in under 1ms between accounts. This is as close to simultaneous as you can get. The master opens a position, the copier writes the signal, the slave reads it and sends the order — all within the same machine, with no network hop.
This is a significant advantage over cloud-based copy services where the signal routes through an external server, adding 50-200ms of delay. On fast-moving pairs, that delay translates into different entry prices between master and slave.
Remote Copy Trading
When the master and slave accounts need to be with brokers in different locations, you have two options.
All terminals on one VPS. Connect to different brokers from the same machine. The master connects to a London broker, the slave connects to a New York broker. Copy latency stays at zero, but the remote broker connection has 60-80ms of network latency for trade execution.
Separate VPS per location. Run the master on a London VPS and the slave on a New York VPS. Each terminal has minimal latency to its own broker, but the copy signal must travel between the two VPS instances, adding 60-80ms of copy delay.
For most traders, option one is better. The copy delay in option two means the slave always enters at a slightly different price than the master, creating tracking error that compounds over hundreds of trades.
FXVPS locations in London (LD4), New York (NY4), Tokyo (TY3), and Hong Kong (HK1) cover 195+ brokers. Choose the location nearest to your master account’s broker for the best combination of execution speed and copy reliability.
Monitoring for Sync Issues
Copy trading setups fail silently. The master takes a trade, a slave misses it due to a momentary disconnection, and you don’t notice until the end of the week when account balances have diverged.
Compare trade lists daily. Export the trade history from the master and each slave. The trade count should match. Missing trades in a slave’s log point to copy failures that need investigation.
Watch for “copy failed” errors in copier logs. Most copier EAs write detailed logs to the MQL4/Files/ or MQL5/Files/ directory. Check these logs daily for rejected orders, symbol mapping failures, or connection timeout errors.
Monitor equity divergence. If the master is up 3% for the week and a slave is only up 1.8%, missed trades or different fill prices are the cause. Investigate immediately rather than letting the divergence compound.
Set up email alerts. Configure MT4/MT5 email notifications (Tools > Options > Email) for disconnect events. If a slave terminal drops its broker connection, you want to know about it before it misses the next trade.
Why VPS Is Non-Negotiable for Copy Trading
Copy trading has a uniquely severe failure mode: divergence. When a regular EA goes offline, it misses trades. That is bad but recoverable. When a copy trading master closes a position while a slave is offline, the slave holds an unmanaged position with no exit signal, no trailing stop adjustment, and no partial close management. A 15-pip planned loss on the master becomes a 60-pip unmanaged loss on the slave.
All terminals must run 24/7. There is no workaround for this. If your master goes offline, there are no signals to copy. If a slave goes offline, it misses signals and diverges from the master.
Get Your Copy Trading Running
The Standard plan at $9.99/mo handles most setups with a master and two to three slave terminals. For five or more slaves or MT5 terminals with their higher memory requirements, the Pro plan at $19.99/mo gives you the resources you need.
Start by installing your terminals, configuring the copier on each one, and running a test trade. Once you verify that a trade on the master appears on every slave within one second, your copy trading operation runs autonomously on infrastructure built for it.
Choose your plan and centralize your copy trading on dedicated infrastructure.