Multi-Master Trade Copier:
Groups, Shared Followers and Risks
“Multi-master trade copier” can describe two different arrangements: several independent source-to-follower groups, or several source accounts sending trades to the same follower. They need different route, position and risk checks. Having several connected accounts or trading groups does not, by itself, prove that a shared follower can receive from multiple sources.
Publisher disclosure: TradeCopier publishes this guide about its own product. Its public FAQ describes one source account sending supported instructions to connected follower accounts, and its pricing page lists account and group limits. Those pages do not document a several-masters-to-one-follower or cascaded route. Confirm the exact topology and order actions in the current dashboard or with support before using live capital. The example below is fictional platform education, not a TradeCopier execution or performance test. Product and platform sources were checked on September 23, 2026.
Separate the three account topologies
| Topology | Example | Question to verify |
|---|---|---|
| One source, several followers | Source A sends eligible instructions to Followers 1 and 2. | Which destination accounts, instruments, sizing rules and actions are supported? |
| Several independent groups | Source A serves Followers 1 and 2; Source B separately serves Follower 3. | Can the plan and dashboard hold both groups, and is each follower assigned only to its intended source? |
| Several sources, one shared follower | Sources A and B both send eligible instructions to Follower 1. | Does the product support that route and preserve source identity through opens, changes and closes? |
| Cascade or feedback route | A follower from one route becomes a source for another route, or two accounts point at each other. | Is the route explicitly supported and protected against duplicate events or a loop? Do not assume either. |
The ordinary one-to-many route is covered by TradeCopier's Forex and Futures product overview. Multiple independent groups are a different planning question from two masters sharing one follower. TradeCopier's published plans currently list one group and three total accounts on Free, five groups and fifteen accounts on Pro, and twenty groups and sixty accounts on Pro Plus. These are capacity limits, not a guarantee that every graph of account connections is available. Count both source and follower accounts under the current plan rules.
Check the route and connection before choosing sizing
Draw the intended account graph with aliases, not credentials. For each arrow, record its source, destination, platform, broker, account mode, allowed symbols and supported event types. Confirm that the same destination is permitted to receive from more than one source if that is the design. Record how the route distinguishes source A's position from source B's when either source changes a stop, partially closes or disconnects. If this behavior is undocumented or untested, mark it unresolved rather than assuming that signals are “merged” safely.
TradeCopier's cloud documentation says its hosted router can operate without an open browser, while broker/platform connections and any required connector must remain available. An offline terminal component can therefore matter for a particular route. After an interruption, compare the destination positions and logs; do not assume missed source events are replayed or that accounts resynchronize automatically.
The public configuration page describes fixed-lot, multiplier and equity-based follower sizing, plus per-account settings. It does not establish a documented percentage-of-risk allocation between two masters sharing one follower. A smaller copied lot also does not guarantee a fixed monetary loss: stop distance, contract value, currency conversion, execution and other open positions affect exposure. Decide a total follower-account risk budget before considering any per-route setting.
A two-source example shows why account mode matters
Consider a deliberately fictional EURUSD test. Follower F begins flat, the instruments and lot units are assumed equivalent, both destination orders are accepted and fully filled, and there are no unrelated orders, charges or existing positions. Source A opens a 0.20-lot buy. Source B then opens a 0.10-lot sell. These are hypothetical instructions to explain MT5 account behavior; they do not assert that TradeCopier currently supports two sources feeding F.
| Event | MT5 netting follower | MT5 hedging follower |
|---|---|---|
| Start | No EURUSD position. | No EURUSD position. |
| A buy 0.20 fills | One 0.20-lot long position. | One 0.20-lot long position. |
| B sell 0.10 fills as an opening instruction | One 0.10-lot long net position remains. | A 0.20-lot long and a separate 0.10-lot short position remain. |
MetaQuotes' MT5 trading principles explain that a netting account keeps one position per symbol and an opposite deal can reduce, close or reverse it; a hedging account can hold multiple positions of the same symbol, including opposing positions. In this example both modes have a 0.10-lot net long difference, but the hedging account has 0.30 lots of gross open positions. Their position identifiers, protection settings and margin treatment can differ. This is a comparison of platform models, not a claim about how a copier associates either source with a destination trade.
Now suppose A changes its stop or closes its source trade. A shared net position does not contain two separately protected A and B tickets. The route would need a documented policy and a source-to-destination event ledger to decide what to request and what result to expect. On a hedging account, a close must still identify the intended destination position. Do not submit another action simply because a source event was observed; check the destination order, fills and position first.
Use a small route test and retain the destination evidence
Before live use, verify the exact topology and account permissions, then test each material action in a permitted demo or simulated environment where available. A demo result does not certify live execution conditions. Keep the source account alias, route, configuration version and destination account mode with every observation. Leave credentials and private keys out of the record.
| Proposed check | Expected state to write down first | Evidence to retain |
|---|---|---|
| Connect A and B to F | Document whether the exact many-to-one route is supported; otherwise stop the test. | Route identifiers, connection method, platform versions and availability. |
| A opens a small position | Specify F's intended instrument, side and quantity. | Source event, destination request, fill and position snapshot. |
| B opens an opposing position | Specify F's intended netting or hedging state before sending. | Both source identities, linked destination orders/deals and resulting exposure. |
| A changes protection or partially closes | Identify which F position or net exposure should change. | Before/after stop and quantity, response, fills and source association. |
| A or its required connector disconnects | Document the stated handling of new or missed events; do not presume replay. | Connection and activity logs, source and destination snapshots after recovery. |
| Possible duplicate or loop | Leave cascades disabled unless support and loop handling are documented. | Route graph, any duplicate-event evidence and the resolution decision. |
Record each row as not run, pass, fail, unsupported or unresolved. A successful request submission is not proof of a completed fill; MetaQuotes' OrderSend reference requires checking the later trading result. For a shared follower, reconcile total account exposure as well as the intended source association. An absent record is unavailable evidence, not zero exposure or a passed test.
Choose the simplest verified relationship
If the task is to copy one strategy to several accounts, start with the documented source-to-followers workflow and test each destination separately. If the task is to run several strategies, determine whether independent groups meet the need before considering a shared follower. If a single follower truly must receive from multiple sources, obtain the product's exact supported route and event behavior, then verify position accounting, total exposure and recovery in that configuration. Account-group capacity alone cannot answer those questions.
Copying can reduce repeated manual entry, but it cannot guarantee matching fills, better diversification or profitable trading. Check the current setup FAQ and plan limits before connecting accounts.
Quick answers
Frequently Asked Questions
Find answers to the most common questions about this topic.
What does multi-master trade copying mean?
It may mean several independent source-to-follower groups, or several source accounts feeding the same follower. These topologies have different route and position requirements. A plan with several groups does not itself prove support for a shared follower.
Can one TradeCopier follower receive trades from several masters?
The public product pages checked on September 23, 2026 document source-to-follower copying but do not establish a several-masters-to-one-follower route. Confirm the exact combination, supported actions and source-to-position association in the current dashboard or with support before relying on it.
How is multi-master different from one master with many followers?
One master with many followers distributes one source stream to separate destination accounts. Multi-master adds more than one source. Those sources may serve separate groups or, only where specifically supported, the same follower.
What happens when two masters send opposite MT5 trades?
The destination account mode matters. On MT5 netting, an opposite deal can reduce or reverse the single position for that symbol. On MT5 hedging, a new opposite opening instruction can create a separate position. Verify the actual destination order, fills, positions and source associations.
Will the hosted router keep copying if my terminal or connector stops?
The hosted router does not require the browser dashboard to stay open. Copying still depends on available broker/platform connections and any connector required for the selected route. After an interruption, reconcile positions and logs; do not assume every missed event was replayed.
Can I cascade a follower into another master or create a loop?
Do not assume cascades or loop prevention are supported. A follower that also becomes a source can produce duplicate or feedback events unless the exact route and controls are documented and tested. Keep such a route disabled until its behavior is verified.
