Setting Up Multi-Account Trade Replication and Orchestration
TL;DR
Multi-account trade replication copies trades from a single source account to multiple receiving accounts automatically. Orchestration is the coordination layer on top, managing how those trades get routed, sized, filtered, and monitored across every account. This glossary covers every term you’ll encounter when setting up multi-account trade replication and orchestration, from master/follower architecture to lot sizing formulas, latency benchmarks, and prop firm compliance tactics. Terms are organized by category so you build understanding progressively, not alphabetically.
Trading one account is straightforward. Trading five or ten accounts with the same strategy, each with its own risk rules, lot sizes, and drawdown limits, is a different problem entirely.
That problem is what multi-account trade replication and orchestration solves. But the terminology around it is a mess. Different platforms use different names for the same concepts. Guides assume you already know what a “copier group” or “tandem mode” means. Product documentation defines terms only in the context of that vendor’s software.
This glossary fixes that. It covers every term a trader encounters when scaling from one account to many, organized by category so each concept builds on the last. The definitions are platform-aware (with an MT5 focus) but not locked to any single vendor. Where a wrong setting can blow a drawdown limit or trigger a prop firm violation, that’s flagged explicitly.
If you’re new to alert-driven automation, start with how TradingView automation works first. That foundation makes everything here click faster.
Core Concepts
These three terms form the foundation. Every other definition in this glossary connects back to them.
Trade Replication
The process of automatically duplicating trades from one source account to one or more receiving accounts. When the source account opens a position, the replication system detects it and opens corresponding positions on all connected accounts according to configured rules.
Replication for MT5 goes beyond simple mirroring. Advanced implementations include trade direction restrictions, balance-based sizing, magic number filtering, day-of-week filters, and slippage/spread controls that determine whether a trade gets copied at all. MQL5 community documentation covers these filter types in detail.
Why it matters: Replication is the act of copying. Without understanding what gets replicated and what gets filtered, you’ll copy trades you shouldn’t (or miss trades you should).
Trade Orchestration
Not a standard financial term like “replication” or “copying.” Orchestration refers to the coordination layer that manages how trades are routed, sized, filtered, and monitored across multiple accounts. It encompasses the rules engine, risk controls, and signal routing that sit above simple copy functionality.
Think of it this way: replication is a musician playing a note. Orchestration is the conductor deciding which musicians play, when they play, how loud, and when to stop. In practice, orchestration for multi-account trade setups means configuring per-account lot sizing, drawdown limits, symbol filters, execution delays, and failover logic so every account follows the same signal but adapts it to its own constraints.
Why it matters: Without orchestration, you just have identical copies. With it, you have accounts that respond intelligently to the same signal based on their individual rules.
Trade Copying vs. Trade Sharing
These terms sound interchangeable but they’re not. MT4Copier draws a clear line: trade copying is a one-way mirror where the master does X and every follower does X. Trade sharing distributes trades in real time but gives each recipient account its own settings, lot sizes, and risk rules while still acting on the same signal.
The distinction matters most for account managers and prop firm traders. If you run five funded accounts with different balance sizes and different drawdown thresholds, you need trade sharing, not blind copying.
Key takeaway: Replication is the act. Orchestration is the coordination layer. Copying is the simplest form of replication. Sharing is replication with per-account intelligence.
Account Architecture
These terms describe how accounts relate to each other in a replication setup.
Master Account (Leader Account)
The source account where trades originate. The copier software monitors this account and replicates its activity to all connected receivers. MT4Copier’s glossary defines it simply: the manager opens trades on the master account, and all parameters are automatically copied to follower accounts.
In some architectures, the master account trades real capital. In others, it’s a “signal-only” account that generates orders without meaningful capital behind them. Either approach works, but the choice affects how you calculate proportional lot sizing (more on that in the Lot Sizing section).
Follower Account (Receiver Account)
The receiving account that mirrors the master’s trades according to configured rules. Older documentation calls these “slave accounts,” but modern platforms have moved toward “follower” or “receiver” terminology.
Each follower can have independent settings: its own lot sizing mode, maximum position size, allowed symbols, drawdown limits, and trading hours. This per-account customization is what separates orchestrated multi-account trade replication from basic one-to-one copying.
Copier Group
A configuration where one leader drives multiple followers under a single set of shared rules. Instead of setting up individual copier configurations for each follower, you create one group that defines the default rules for all followers at once. CrossTrade’s documentation describes the benefit: settings changes apply everywhere in one save.
Copier groups simplify management enormously when you’re running five or more accounts. You change the risk percentage once and it propagates. You can still override individual follower settings within the group when needed.
Multi-Account Placement
An alternative to copier groups where a single webhook or alert is sent to multiple accounts simultaneously in one payload. Each account receives the same order independently. CrossTrade’s docs note this is simpler to configure but offers no per-account sizing customization.
These two approaches can be combined. A webhook can trigger multiple leaders, each of which distributes to its own copier group of followers. This hybrid architecture is common in setups involving more than ten accounts.
Architecture flow: Signal Source → Webhook/Alert → Orchestration Layer (copier groups or placement) → Per-Account Rules → Execution on Each Follower
For traders who want to skip the complexity of self-managed infrastructure, CloudConnect from TradeSgnl provisions a managed MT5 instance that removes VPS setup from multi-account workflows entirely.
Managed Account Models
These three models are broker-level account management structures. They’re distinct from EA-based trade copiers, and the confusion between them trips up traders constantly.
MAM (Multi-Account Manager)
A system where a manager trades a master account and each trade is replicated across individual client accounts using predefined allocation rules. Funds are not pooled. Each investor sees every position in their own account with full transparency.
MAM is the institutional choice. High-value clients prefer it because they maintain individual account ownership and can see every trade.
PAMM (Percentage Allocation Management Module)
A pooled investment system. Investors allocate funds to a shared account managed by a professional trader. Profits and losses are split by each investor’s percentage contribution. The manager places trades on a single master account, and no trade-by-trade replication is needed because everything happens in one pool.
PAMM reduces server load (one account instead of many) but gives investors less visibility into individual positions.
LAMM (Lot Allocation Management Module)
Trades are copied at the same lot size as the source, not proportionally. Soft-FX explains that the investor’s account must have enough funds to match the source’s volume. This model is used in large-capital situations where percentage-based allocation becomes impractical.
MAM vs. PAMM vs. LAMM: Quick Comparison
| Feature | MAM | PAMM | LAMM |
|---|---|---|---|
| Capital structure | Individual accounts | Pooled account | Individual accounts |
| Allocation | Proportional (flexible) | By percentage contribution | Fixed lot (same as source) |
| Client visibility | Full (every position) | Limited (pool-level) | Full |
| Best for | Institutional, high-net-worth | Passive investors | Large-capital accounts |
| Setup level | Broker-provided | Broker-provided | Broker-provided |
Important clarification: Most retail traders and prop firm traders do not use MAM, PAMM, or LAMM. These are broker-level features that require a money manager license or broker partnership. Retail and prop traders typically use EA-based trade copiers for multi-account replication and orchestration, which is what the rest of this glossary focuses on.
Lot Sizing and Allocation Methods
Choosing the wrong lot sizing mode is one of the fastest ways to blow an account or violate a drawdown rule. These five methods each serve different situations. For a deeper look at how position sizing connects to broader risk controls, see MT5 risk management strategies.
Fixed Lot Sizing
Every copied trade uses the same pre-set lot size regardless of account balance. B2Copy documents this as: “Investor’s position = Investor’s fixed position size (Ratio).”
Example: You set 0.50 lots. Every trade copies at 0.50, whether your account is at $5,000 or $50,000.
Best for: Accounts with stable balances where you want predictable position sizes. Not ideal for growing accounts because it doesn’t compound.
Proportional to Balance
Position size scales based on the ratio between follower balance and master balance.
Formula: Follower’s Lots = Master’s Lots × (Follower Balance ÷ Master Balance)
Example from B2Copy’s documentation: Master balance is $8,000. Follower balance is $2,000. Master opens 2.00 lots. Follower copies 2.00 × ($2,000 ÷ $8,000) = 0.50 lots.
Best for: Most standard setups. Keeps risk proportional across different account sizes.
Proportional to Equity
Same formula as above but uses live equity instead of balance.
Formula: Follower’s Lots = Master’s Lots × (Follower Equity ÷ Master Equity)
Why it’s different: Equity includes unrealized P&L from open positions. During a drawdown, equity drops below balance, which automatically reduces the next copied trade’s size. During a winning streak, equity exceeds balance, which increases it.
Watch out: During volatile drawdowns, this can create unexpected lot size swings. A sharp intraday move could shrink your next trade to nearly nothing, then size it back up minutes later.
Ratio Multiplier (Lot Multiplier)
A simple multiplication factor applied to the master’s position size.
Formula: Follower’s Lots = Master’s Lots × Ratio
Example: Master opens 1.00 lot. Multiplier is 0.5x. Follower copies 0.50 lots. Multiplier is 2.0x. Follower copies 2.00 lots.
MT4Copier defines this as automatically adjusting lot size based on account size, with a certain percentage of risk that varies from one account to another.
Best for: Quick calibration when you know the rough size relationship between accounts and don’t need dynamic adjustment.
Equity-Based Scaling
Lot size adjusts automatically as account equity increases or decreases over time. Unlike “proportional to equity” (which compares follower equity to master equity at the moment of trade), equity-based scaling uses the follower’s own equity trajectory to compound or de-risk.
Copygram’s documentation describes this as a method for compounding profits and maintaining dynamic risk alignment as the account grows.
Best for: Traders who want their position sizes to grow with their profits and shrink during drawdowns, without manually adjusting settings.
Execution and Latency
Latency might seem like a technical detail, but in multi-account replication, it directly translates to money lost or saved. This section covers the terms that determine how fast and accurately your trades execute across accounts.
Slippage (in Replication Context)
The price difference between the master’s fill and the follower’s fill. In single-account trading, slippage is the gap between your intended price and your actual fill. In replication, there’s an additional source: the time it takes for the copier to detect the master’s trade and submit the follower’s order.
MT4Copier quantifies this impact: at 50 to 100ms latency with 50 trades per day, average slippage of 0.3 pips costs approximately $3,000 per month, or $36,000 per year, lost purely to infrastructure slowness. At 1 to 5ms latency, slippage drops to near zero.
| Latency Range | Avg. Slippage/Trade | Monthly Cost (50 trades/day) |
|---|---|---|
| 1-5 ms | ~0 pips | ~$0 |
| 50-100 ms | 0.2-0.3 pips | ~$3,000 |
This is why infrastructure choices matter enormously when setting up multi-account trade replication and orchestration. The difference between a well-placed VPS and a poorly configured cloud relay can cost more per year than the software itself. For traders evaluating VPS options, the MT5 VPS setup guide walks through the details.
Maximum Price Deviation (MPD)
The maximum number of pips allowed between the master’s execution price and the follower’s execution price. If the price gap exceeds MPD when the follower’s order reaches the broker, the trade is rejected rather than filled at a bad price.
Setting MPD too tight means trades get rejected during normal market volatility. Setting it too loose means you accept fills far from the intended price. A typical starting point is 2 to 3 pips for major forex pairs and 5 to 10 pips for volatile instruments.
Copy Modes: Execution vs. Order
CrossTrade defines two distinct modes that affect when a trade gets copied:
Execution (Fills Only) Mode copies the trade only when the leader’s order actually fills. This is safer for prop firm accounts because you never copy an unfilled limit order.
Order Mode copies when an order is placed, before it fills. Faster, but risks copying limit orders that the leader later cancels or that never execute.
For most multi-account setups, especially those involving funded accounts, execution mode is the safer default.
Local vs. Cloud Copier
NYC Servers’ guide emphasizes that local copiers running on the same VPS as your MT5 instances deliver sub-50ms copy speeds via shared memory. Cloud copiers route signals through external servers, adding latency plus a third-party dependency.
The tradeoff: local copiers are faster but require VPS management. Cloud copiers are easier to set up but introduce network hops. Platforms like TradeSgnl that provide built-in risk controls and sub-500ms execution through a managed edge network aim to bridge this gap, giving cloud convenience with speed closer to local setups.
Risk and Compliance Controls
This section matters more than any other for prop firm traders. A single misconfigured setting here can flatten your account, trigger a rule violation, or get your accounts flagged.
Tandem Mode
Ties a copier to an account risk manager so they communicate. Here’s the problem it solves: a follower account hits its daily loss limit, and the risk manager flattens all positions. Without tandem mode, the copier keeps sending new trades to that account, immediately re-entering positions that were supposed to be closed.
With tandem mode enabled, when the risk manager flattens a follower, the copier stops sending trades to that specific account while continuing to operate normally on all others.
For prop firm traders, this is near-mandatory. Practitioners in trading forums consistently flag this as the most common cause of blown funded accounts, because the replication system doesn’t know about the risk system unless you explicitly connect them.
Auto-Sync
A background process that periodically checks whether follower positions match the leader’s positions. If a follower misses a fill due to a connection blip, broker rejection, or temporary outage, auto-sync detects the mismatch and submits a corrective order.
Without auto-sync, a missed fill means that follower account drifts out of alignment with the strategy for every subsequent trade on that symbol.
Stealth Mode
Hides automation signatures so copied orders appear identical to manually placed orders in the platform. This means removing EA identifiers, magic numbers visible in trade comments, and other metadata that flags a trade as automated.
This is relevant for prop firm accounts where firms may analyze trade patterns for signs of copying or automation. Not every firm prohibits automation, but many prohibit account-to-account trade copying, and identical timestamps or order comments across accounts are the giveaway.
Account Cycling (Round-Robin)
Distributes trades across accounts sequentially rather than simultaneously. Instead of all ten accounts entering at the same millisecond, account one enters first, then account two, then account three, and so on.
Useful for two purposes: staggering entries to avoid identical timestamps (prop firm compliance) and limiting per-account exposure when you want each account to take a subset of signals.
Prop Firm Compliance: Lot Randomization, Delay Injection, TP/SL Variation
These three practices come directly from NYC Servers’ practitioner guide for managing multiple prop firm accounts:
Lot Randomization: Apply a 0.98x to 1.02x random multiplier to each copied trade’s lot size. A 1.00 lot trade becomes 0.99 on one account and 1.01 on another. Small enough to be statistically insignificant, large enough to break pattern detection.
Delay Injection: Add a 1 to 3 second random delay between copy executions across accounts. This prevents identical entry timestamps, which is the clearest signal that accounts are linked.
TP/SL Variation: Vary take-profit and stop-loss levels by a few pips per account. One account sets TP at 1.0849, another at 1.0851. Same strategy, slightly different fingerprints.
Critical note from the same guide: Never create multiple identities at the same firm. These compliance tactics help accounts appear independently managed, which is appropriate when you genuinely hold multiple funded accounts under your own name. They are not tools for circumventing firm rules about identity or account limits.
Daily Drawdown Limits
The maximum amount an account can lose in a single day before trading is halted. In multi-account orchestration, each follower needs its own drawdown limit configured independently of the master. A $100,000 funded account with a 5% daily drawdown limit and a $50,000 account with a 4% limit need different absolute dollar thresholds even if they follow the same strategy.
This is where the orchestration layer earns its keep. Without per-account drawdown enforcement, replication becomes a liability rather than a scaling tool.
Signal Routing and Security
These terms cover how trade signals travel from their source to your MT5 accounts, and how you prevent unauthorized orders from sneaking through.
Webhook Bridge
A relay system that receives TradingView alert webhooks (HTTP POST requests containing trade instructions) and routes them to MT5 for execution. This is the core architecture behind TradingView-to-MT5 automation.
The webhook bridge parses the incoming JSON payload, extracts trade parameters (symbol, direction, lot size, stop loss, take profit), authenticates the request, and submits the order to the connected MT5 instance. For a full walkthrough of this connection, see how to connect TradingView alerts to MT5.
In multi-account setups, the webhook bridge is often the single point of entry. One alert fires, the bridge receives it, and the orchestration layer distributes it to all configured accounts with their individual rules applied.
Signal Authentication
A security mechanism that verifies the origin of incoming trade signals. TradingView’s webhook server sends an SSL certificate with each request for basic verification, but most bridge platforms add additional layers: a secret key or token embedded in the alert payload that must match the expected value before any order is processed.
Without signal authentication, anyone who discovers your webhook URL could send orders to your accounts. This is not a theoretical risk. Practitioners on Reddit have reported unauthorized trades on poorly secured webhook endpoints.
For details on configuring alerts properly, the TradingView alerts configuration guide covers the specifics of payload formatting and authentication setup.
Symbol Mapping
Translates instrument names between different brokers. One broker lists the euro-dollar pair as “EURUSD.” Another lists it as “EURUSDm” or “EURUSD.r.” Without symbol mapping, copied trades get rejected because the follower’s broker doesn’t recognize the master’s symbol name.
Any serious multi-account replication setup needs symbol mapping configured before going live, especially when followers are spread across multiple brokers.
Putting It Together: The Multi-Account Stack
Now that every term is defined, here’s how they connect in a real setup for multi-account trade replication and orchestration.
The signal chain:
- Signal Source: A TradingView strategy or indicator fires an alert based on your rules.
- Webhook Bridge: The alert hits a webhook URL as an HTTP POST request. Signal authentication verifies it’s legitimate.
- Orchestration Layer: The bridge or copier software receives the signal and applies per-account rules: lot sizing mode, symbol mapping, maximum price deviation, allowed trading hours, and drawdown limits.
- Execution: Orders are submitted to each follower account. Copier groups handle the distribution. Delay injection and lot randomization apply if configured.
- Monitoring: Auto-sync checks for missed fills. Tandem mode prevents re-entry on flattened accounts. Real-time alerts notify you of failures.
VPS Resource Planning
If you’re running self-managed infrastructure, NYC Servers’ guide provides concrete benchmarks:
| Accounts | CPU Cores | RAM | Approximate Monthly Cost |
|---|---|---|---|
| 1 | 2 | 2 GB | $25 |
| 2-3 | 2 | 4 GB | $40 |
| 5+ | 4 | 8 GB | $75+ |
Each MT5 instance consumes roughly 500MB to 1GB of RAM. These numbers assume the copier software runs on the same VPS for minimum latency.
All-in-One vs. DIY
Building a multi-account replication stack from individual components (VPS provider, copier software, risk manager, analytics dashboard) gives maximum flexibility but creates maintenance overhead. Every component needs updates, monitoring, and troubleshooting independently.
All-in-one platforms bundle the webhook bridge, orchestration layer, risk management, and hosting into a single subscription. The tradeoff is less customization but dramatically less setup time.
TradeSgnl’s plans illustrate this progression: Starter at $25/month supports one account connection, Advanced at $49/month supports three connections with a Core VPS included, and Professional at $99/month supports ten connections with a Performance VPS included. A 14-day free trial is available with no credit card required. View the full plan comparison to see which tier matches your account count.
FAQ
What’s the difference between a trade copier and a MAM account?
A trade copier is software (usually an EA or external application) that monitors a master account and replicates trades to follower accounts. Any trader can set one up. A MAM account is a broker-level feature that requires an account management agreement or money manager license. MAM is built into the broker’s infrastructure. Trade copiers are third-party tools that work on top of standard retail accounts.
How many MT5 accounts can I run on one VPS?
It depends on the VPS specs and what else is running. As a baseline, each MT5 instance needs 500MB to 1GB of RAM. A 4GB VPS comfortably runs two to three instances plus a copier. For five or more instances, plan for 8GB RAM and four CPU cores. These numbers come from practitioner benchmarks for prop firm VPS scaling.
Do prop firms allow trade copying across accounts?
It varies by firm. Many firms allow traders to operate multiple funded accounts and use the same strategy across them. What most firms prohibit is sharing strategies between different traders’ accounts or creating multiple identities. The compliance practices described above (lot randomization, delay injection, TP/SL variation) help accounts appear independently managed, which is appropriate when you legitimately hold multiple accounts under your own name. Always check your specific firm’s rules.
Which lot sizing mode should I use for accounts with different balances?
Proportional to balance is the most common choice. It automatically scales position sizes so each account risks approximately the same percentage of its balance. Fixed lot sizing works if all accounts are the same size and you want simplicity. Equity-based scaling is best for compounding, but watch for unexpected lot changes during volatile drawdowns.
What happens if a follower account misses a trade?
If auto-sync is enabled, the system detects the mismatch at its next check interval and submits a corrective order. If auto-sync is not enabled, the follower drifts out of alignment and every subsequent trade on that symbol will be offset from the leader’s position. This can create unexpected hedged positions or missing exits.
Should I use execution mode or order mode for copying?
Execution mode (fills only) is safer for most setups, especially prop firm accounts. It only copies trades that actually filled on the leader. Order mode copies when an order is placed, which is faster but can result in copying limit orders that never execute or get cancelled on the leader account.
How much does replication slippage actually cost?
At 50 to 100ms latency with 50 trades per day, MT4Copier’s data shows average slippage of 0.3 pips per trade, totaling roughly $3,000 per month. At 1 to 5ms latency, slippage is near zero. Infrastructure placement relative to your broker’s servers is the primary variable.
Can I combine copier groups with webhook-based multi-account placement?
Yes. These approaches are complementary. A webhook can fire to multiple leader accounts, and each leader can distribute to its own copier group of followers. This creates a tree structure: one signal branches to multiple leaders, each of which branches to multiple followers with their own rules. This hybrid approach is common in setups managing ten or more accounts simultaneously.