Skip to main content
HomeFeaturesMulti-Account Copier
Feature · multi-account fan-out

Multi-account signal copier — one signal, all your accounts

A multi-account signal copier executes one incoming signal on several broker accounts at the same time. PipSync fans a single Telegram, Discord, TradingView or webhook signal out to every account you connect — across MT4, MT5, cTrader, Match-Trader, Binance Futures and Bybit — and applies separate risk settings to each one.

Start free — no credit cardSee pricing

Risk warning: CFDs are complex instruments with a high risk of losing money rapidly due to leverage. 70–80% of retail investor accounts lose money when trading CFDs. Risk disclosure · Past performance.

The accounts do not have to live on the same platform. The same Telegram channel can drive an MT5 live account at your broker and a Match-Trader evaluation account at a prop firm in parallel, each with its own position sizing, symbol filters and trade limits. Parsing, risk checks and order routing all run in PipSync's cloud, so nothing on your side has to stay online.

Multi-account copying at a glance

Fan-out modelOne signal source → all connected destination accounts, each order built per account
Mixable platformsMT4, MT5, cTrader, Match-Trader, Binance Futures, Bybit — combinable in one setup (live in public beta)
Per-account riskFixed lots or percent-risk sizing, SL/TP mapping, symbol filters and trade limits set individually per account
Account limits by planBasic: 1 broker account · Pro: 2 · Advanced: 6 (per pipsync.io/pricing)
Multi-account copy-factoryListed on the Advanced plan (€299/month); Enterprise adds a public API and webhook fan-out
InfrastructureFully cloud-based — no VPS, no EA, no terminal that must stay open per account

How do I set up one signal source for several accounts?

Everything is configured in the PipSync dashboard; you never duplicate channels or install anything per account.

  1. Connect your signal source once

    Add the Telegram channel, Discord server, TradingView alert or webhook you want to copy from. One source feeds all destinations — you do not set it up again per account.

  2. Connect each destination account

    Add your broker accounts one by one: MT4, MT5, cTrader, Match-Trader, Binance Futures or Bybit. They can sit at different brokers and on different platforms. Your plan sets how many you can connect (1 on Basic, 2 on Pro, 6 on Advanced).

  3. Set risk rules per account

    Give each account its own sizing (fixed lots or percent-risk), SL/TP mapping, symbol filters and trade limits. A small evaluation account and a larger live account can follow the same signal with very different volumes.

  4. Test on demo before fanning out

    Run the route against a demo account first and review how each signal was parsed and sized. Only enable the remaining accounts once the per-account behavior matches what you expect.

How does one signal reach multiple accounts at the same time?

PipSync parses each incoming signal once, then builds a separate order for every connected destination account. The parsed signal — symbol, direction, entry, stop-loss, take-profit — is shared; the resulting order is not. Sizing, SL/TP mapping and filters are applied per account before anything is submitted.

Because this happens server-side, adding an account does not add infrastructure on your end. There is no second terminal, no second EA and no second VPS — the classic reason multi-account copying used to get expensive and fragile with terminal-based copiers.

Can I copy the same signal to accounts on different platforms?

Yes — that is the main point of PipSync's fan-out. Each destination platform has its own connection type (MT4 via a bridge, MT5 via an API bridge, cTrader via Spotware's Open API, Match-Trader via REST + WebSocket, Binance Futures and Bybit via your exchange API keys), and one setup can mix them freely.

A concrete example: a trader follows one Telegram channel and wants it executed on an MT5 live account at their broker and on a Match-Trader account at a prop firm. In PipSync that is one source with two destinations — same parsed signal, two independently sized and filtered orders.

  • Live destinations in the public beta: MT4, MT5, cTrader, Match-Trader, Binance Futures, Bybit
  • Each destination account connects with its own credentials and its own connection settings
  • Per-account symbol filters let one account skip instruments another account trades

Why do prop traders run one signal source into several accounts?

Prop traders often hold evaluation or funded accounts at more than one firm at once — for example on FTMO, The5%ers or FundedNext (reachable through their MetaTrader backends) alongside a Match-Trader-based firm. Manually re-entering the same signal on each account is slow and error-prone; a multi-account copier executes them together from one source.

Per-account risk settings matter most here: each firm has its own drawdown and sizing rules, so each account needs its own percent-risk value, trade limits and symbol filters rather than one shared setting. PipSync enforces these server-side before an order is sent.

One caveat you should take seriously: prop-firm rules differ, and some firms restrict copy trading, automation or trading the same signals across multiple accounts. Check your firm's terms before enabling any automated execution — that responsibility stays with you.

Can each account have its own lot size and risk settings?

Yes, and this is what separates real multi-account copying from simply duplicating orders. Every destination account gets its own configuration: fixed lots or percent-risk sizing, how the signal's SL/TP map onto the order, maximum open trades, and which symbols it is allowed to trade.

With percent-risk sizing the same signal scales automatically to each account's size, so a small evaluation account and a larger live account take proportionate — not identical — volume. A signal that violates one account's rules is blocked for that account without affecting the others' settings.

How many accounts can I connect on each PipSync plan?

Account limits come straight from the pricing page: Basic (€49/month) includes 1 broker account and 3 signal sources; Pro (€99/month) includes 2 broker accounts and 10 sources; Advanced (€299/month) includes 6 broker accounts, 25 sources and multi-account copy-factory trading.

The Enterprise tier (listed at €1999/month, via sales) extends Advanced with a public API, webhook fan-out and custom broker integrations. There is also a free plan (€0, no credit card required) to set up and test before committing to a paid tier.

Try it on the free plan

Connect a signal source and a broker account, watch PipSync parse and route in real time, and upgrade only if you need more. No credit card required to start.

Start free — no credit cardSee pricing

Risk warning: CFDs are complex instruments with a high risk of losing money rapidly due to leverage. 70–80% of retail investor accounts lose money when trading CFDs. Risk disclosure · Past performance.

FAQ

Frequently asked questions

Can I copy one Telegram signal to multiple MT5 accounts?

Yes. Connect the Telegram channel once and add each MT5 account as a destination; PipSync executes the parsed signal on all of them with separate risk settings per account. How many accounts you can connect depends on your plan: 1 on Basic, 2 on Pro, 6 on Advanced.

Written by the PipSync team · Reviewed by Tobias Russmann, Director, PipSync · Published · Last updated

PipSync is a cloud-based signal automation platform that routes trading signals from Telegram, Discord, TradingView alerts and custom webhooks to broker accounts on MetaTrader 4, MetaTrader 5, cTrader, Match-Trader, Binance Futures and Bybit — with server-side risk management and no VPS required. PipSync is an execution tool, not a signal provider and not investment advice.

PipSync is a signal execution tool. It does not provide trading signals, does not guarantee any trading results and is not investment advice. Trading leveraged products involves substantial risk of loss. See the full risk disclosure and performance disclaimer.