A follower opens a support ticket about a EURUSD short that appeared on her account overnight. The provider swears he never took it. He did — as a manual hedge, typed straight into the terminal, and the engine could not tell the difference. Here is what actually crosses the gap between the two roles.
A follower opens a ticket about a EURUSD short that appeared on her account at 22:40. The provider says he never took that trade. He is not lying, and neither is she.
What he took was a manual hedge — typed straight into his terminal to flatten an exposure for twenty minutes while he stepped out. To him it was housekeeping, not a signal. To the replication engine it was an untagged position on a provider account, which is the precise definition of something worth copying. It went out to eleven followers, who all held it overnight and paid swap on it.
Nobody made an error. The roles were never defined clearly enough for anyone to make one.
A Provider is an account whose activity is read. A Follower is an account onto which that activity is reproduced under a policy. Those are the terms our own product uses, and they are the ones this article uses throughout.
You will meet other pairs for the same idea. Master and slave is the oldest in retail software and is being retired across the industry. Leader and investor is common on social-trading venues. Strategy provider and subscriber appears in platform-native copy services. Source and destination shows up in developer documentation. They all describe the same asymmetry: one side originates, the other side receives.
The part that trips people up is that a role belongs to a relationship, not to an account. The same account can be a Follower in one relationship and a Provider in another, at the same time, and there is nothing pathological about that.
Under a normal configuration, these cross the gap:
This list is longer and it is where the surprises live.
Manual trades on the Follower. A trade you place yourself on a Follower account carries no attribution tag. A well-built engine therefore leaves it alone entirely — it does not manage it, does not move its stop, and does not close it when the Provider closes something that happens to look similar. That is the correct behaviour, and it has a sharp edge: the engine also does not account for it. Your manual trade consumes margin, adds exposure and counts fully toward a prop firm's drawdown, while sitting outside the copier's view of your risk.
Balance operations. Deposits and withdrawals do not replicate, and they should not. But if your sizing rule is equity-based, a withdrawal from the Provider silently changes every subsequent copy size on every Follower. Worth knowing before you move money.
Costs. Swap, commission and spread are the Follower's broker's business. Two accounts holding an identical position for a week can show materially different results on the same price action purely from financing, and that is not a copier fault.
Instruments the Follower's broker does not offer. These produce a skip, not a substitution. If your Provider trades an index your broker does not list, that trade is simply absent from your account, and the only way you will know is if the skip is visible.
Anything the filters removed. News windows, session windows, spread caps and symbol blocklists all produce absences that look identical to failures unless the reason is recorded. This is why a skip log with a reason per trade is not a nicety.
TIP
Once a week, compare the Provider's trade count with each Follower's for the same period. If they differ, the difference should be fully explained by logged skips. If it is not, you have found a real problem while it is still cheap.
The opening story is the one case that catches experienced people, so it is worth stating plainly.
On a Follower, a manual trade is invisible to the engine and stays yours.
On a Provider, a manual trade is an origination and replicates like any other. There is no technical way for the engine to distinguish "a trade I meant to share" from "a trade I placed for my own reasons" — both are untagged positions on an account configured to be read. The only real controls are operational:
WARNING
Do not rely on closing a position quickly to un-send it. A copy placed and closed thirty seconds later has still crossed the spread on every Follower account, and on eleven accounts that is eleven spreads paid for a trade you did not intend to share.
The two roles need different access, and the difference is not a product decision — it is inherent to the mechanism.
A Provider account is only ever read. On MetaTrader that means a read-only investor password is sufficient, and sufficient is the whole argument: a credential that cannot place a trade cannot place a wrong trade, no matter what goes wrong upstream.
A Follower account has to be traded on, so it needs full trade access. That is unavoidable, and it is why the questions you ask about a Follower connection — what happens if the licence server is unreachable, what the circuit breakers are, how you revoke access — matter more than the ones you ask about a Provider connection.
If a tool asks for full trade credentials on an account you intend to use only as a source, ask why. There may be an answer, and you are entitled to hear it.
Because a role belongs to a relationship, chains form naturally:
Your main account is a Follower in the first relationship and a Provider in the next three. This is legitimate and common. It also introduces two things to get right.
Origination versus relay. A trade that arrives on your main account as a copy carries a tag. If the engine treated tagged positions as originations, it would relay them onward, and in a configuration where any account feeds back you would get an infinite loop. Sound engines read only untagged positions in the Provider role, carry a hop counter as a backstop, and refuse to save a configuration whose routing graph contains a cycle.
Policy composition. Your risk at the far end is the product of two policies, not one. If the first relationship sizes to 1 percent of your main account and the second sizes to 1 percent of each prop account, the prop accounts are at 1 percent — but if the second uses a multiplier off the incoming volume instead, the effective risk is whatever those two rules multiply out to. Write the chain down and do the arithmetic once.
The cleanest way to avoid the support ticket at the top of this article is to agree the boundaries before connecting anything.
The Provider is responsible for what appears on the Provider account, including trades taken for private reasons; for saying in advance what they will and will not trade; and for telling Followers when something changes materially, such as switching instruments or stepping up size.
The Follower is responsible for the replication policy — sizing, filters, breakers, update handling; for whether the instruments are tradeable on their own broker at acceptable cost; for their own account's rules, which on funded capital are not negotiable; and for the decision to be in the relationship at all.
The software is responsible for faithful, attributed, idempotent replication under the stated policy, and for making every skip and every failure visible with a reason.
Notice what is on nobody's list: an obligation on the Provider to keep doing what they did last month. Following someone's account means you receive what they do next, which is not necessarily what attracted you. That is the actual risk of the relationship, and no amount of engineering touches it.
TIP
Before connecting to a Provider you do not control, run the relationship on a demo Follower for a few weeks. You are not testing the software — you are finding out how often the Provider does something you would not have done.
The engine underneath all of this — how originations are distinguished from copies, and how the routing graph is kept acyclic — is in /blog/trade-replication-engine-explained. If the vocabulary itself is what brought you here, /blog/master-copy-meaning sorts out master, slave, provider, follower and the rest of the terminology in one place.
