Prop-firm traders — FTMO, FundedNext, The5ers, and the long tail of smaller firms — often run more than one challenge in parallel. They are not running different strategies on each account. They are running one strategy across all of them, with the explicit goal of parallelising pass-fee economics and accelerating the path to payouts. The naive math is straightforward: if a strategy passes a challenge with a 40% probability and the attempts were independent, running four concurrent challenges would raise the probability that at least one passes to roughly 87%. They are not independent, though — the same strategy on the same market means a bad week hits every account at once — so treat that figure as an upper bound, not an expectation. The pass-fee cost scales linearly either way.
Generic copy-trading tools were not built for this use case. They assume a signal source has one downstream destination, and the 'multi-account' modes they offer are bolt-ons. This article walks through what the routing layer has to handle when one signal feeds several challenge accounts, where the generic-router assumptions break, and what PipSync does — and explicitly does not do — about it.
What makes multi-account routing structurally different
Every firm defines its limits in its own way
Every prop firm has a daily-loss limit and a maximum-drawdown limit, and the numbers vary from firm to firm. The harder problem is that the definition of 'daily' and the calculation of 'drawdown' differ: some firms measure from the start-of-day balance, some from equity, some trail the equity high-water mark, some ignore unrealised P/L until a position closes. Read the exact definition in your firm's rulebook.
PipSync does not know or enforce any firm's drawdown rules. There is no total drawdown limit in PipSync; the optional Max Daily Loss (off by default) only refuses new copied trades for the rest of the UTC day. What you control is how much each trade can lose and how many trades can be open at once: risk per trade (percent of balance), Min Lots and Max Lots, Max Open Positions, and a default built-in guard against a second position in the same direction on the same instrument. Keeping headroom to the firm's limits is a sizing decision you make, and you watch the account on the dashboard.
Per-account symbol lists and session filters
Most firms restrict trading certain instruments or at certain times. Some ban holding positions through high-impact news; others restrict instruments (crypto, exotic FX, single-name equities) or specific hours. A signal that is perfectly valid for one account might violate the rules of another.
The generic-router failure mode: the signal fires, the strategy thinks it sent a trade to all accounts, but three of four accounts rejected the order because of a per-account restriction, and the trader's equity curves diverge in ways that are confusing to debug.
In PipSync every linked account has its own settings under the channel's per-account settings: a symbol whitelist, a session filter, Min TP, Max SL, Max Spread and a maximum risk per trade (percent of balance). Use them to mirror an account's instrument list; the session filter limits trading to the Asia, Europe or US sessions only, so it cannot exclude a specific news window. There is no news filter. If your firm restricts news trading, switch auto-trading off (signals then wait for manual approval on the Signals page), pause the channel, or disable the account around the event. The Execution Log and the Trades history show which accounts took a trade.
Position size that differs by account balance
A $25k account and a $200k account have different per-trade lot sizes. A strategy that says 'risk 0.5% per trade' produces a different absolute lot size on each. The routing layer has to compute the per-account size without forcing the user to maintain four copies of the same strategy with different sizing parameters.
In PipSync one signal can be routed to several linked accounts, and each order is sized on that account's own balance using its own risk setting (risk per trade, fixed percentage or fixed lots), within that account's Min Lots and Max Lots. The strategy stays one logical entity; the per-account sizing is mechanical translation.
Pausing one account without disconnecting the source
When one of four accounts gets close to its firm's limit, you want that account to stop trading while the source keeps feeding the other three. Disabling the whole source destroys the parallelisation that made the setup worth using in the first place.
PipSync does not pause an account for you when it nears a limit — it does not track the firm's limits. You can disable a single account, switch off auto-trading, or pause the channel yourself, and the other accounts keep receiving signals.
One signal, one order per account
A single signal generates one independent order per linked account, each with its own fill, slippage and outcome. Treating each account as its own routing destination, rather than one trade with several outcomes, is what makes a clean per-account picture possible: you can ask what your result on account 3 was from signals from source A in March and read the answer off the Trades history.
What the dashboard shows
The dashboard gives you equity curves, per-signal P/L, the Trades history and the Execution Log. Compared side by side per account, they surface patterns that are invisible at source level: one account being hit harder by news-time slippage because its broker's execution differs, or one account running closer to its limits than the others. Because PipSync does not enforce any limit, this is the view you use to decide when to pause an account yourself.
Operational rules for running one strategy on several accounts
- Run identical strategies across all accounts. Strategy drift between accounts compromises the parallelisation logic and makes debugging impossible.
- Size every account so that a normal losing streak stays well inside the firm's limits: a lower risk per trade and a lower Max Open Positions than the firm would technically allow. Leave margin for slippage and partial-fill weirdness. PipSync does not enforce the firm's limit — your sizing does.
- PipSync has no news filter. If your firm restricts news trading, switch auto-trading off or pause the channel around scheduled events (the per-account session filter only limits trading to the Asia, Europe or US sessions, so it cannot exclude a specific window). The unhedged news move on a typical major pair can blow a daily limit on its own.
- Review weekly. The Trades history and equity curves per account show patterns that are invisible at source level — broker-specific slippage, intraday timing variance, instrument-specific edge differences.
- Don't increase position size on funded accounts beyond what passed the evaluation. The temptation is real; the empirical outcome is meaningfully worse risk-adjusted performance.
What's still hard
Cross-firm correlation. If you run an account at one firm and an account at another on the same strategy, the two accounts have correlated drawdowns by construction — a bad week for the strategy hits both at once. PipSync routes each account independently and does not model cross-account correlation, so treat the combined accounts as one bet when you decide on risk per trade.
Reset-attempt economics. Some traders buy reset attempts on failed challenges. The economics are sometimes — rarely — positive, depending on the firm's reset pricing and the trader's edge. The operational guidance is to treat resets as a meaningful expense and only buy them if your edge has demonstrated durability over a meaningful sample.