Answers, sorted by what you’re doing.

How the copier is structured

Every copier setup in Cockpit is built from two roles:

• Provider — the account whose trades you want mirrored. This is an account you already trade on: your own broker login, a prop-firm account, whatever you're already placing trades from.
• Follower — one or more accounts that copy everything the source does. A single source can fan out to several destinations at once — useful if you're running the same trade across multiple prop-firm accounts or mirroring one strategy into a client's account.

An account can only hold one role at a time on a given instance. If an account is already a receiver somewhere, the wizard shows it greyed out with a reason rather than letting you create a conflicting setup — two uncoordinated sources trying to manage the same account is exactly the kind of thing the copier is built to prevent.

This same source → destination structure is what powers Signal Copier too. If your "source" is a Telegram or Discord channel instead of a trading account, the setup flow below is identical — you just pick the channel in step 1 instead of an account.

Creating an instance

From Cockpit → Instances, click + Create Instance. It's a three-step wizard:

1. 01Source — pick an existing connected account, or connect a new one. Which platforms you can pick from depends on your plan: MT4, MT5, cTrader, Tradovate and NinjaTrader are all available from Starter; how many of each you can connect is a plan figure. cTrader connects via OAuth instead of a password.
2. 02Destinations — add one or more receiving accounts the same way: reuse an account you've already connected, or connect a new one. Each destination needs its own full trade password (sent directly to the execution engine, never stored) unless you're reusing an account that's already tradeable. You can add as many destinations as your plan allows — click + Add another destination to fan out further.
3. 03Settings — configure lot sizing, filters, and risk protection for the whole batch. These settings apply to every destination you just added, since one shared risk configuration is what makes sense for "one source, several followers."

Hit Activate and the instance goes live immediately — no separate "save then enable" step.

If you're setting up Telegram or Discord as the source instead of a trading account, connect that channel session first (Cockpit → Accounts) so it shows up as an option in step 1.

Lot sizing

The copier supports several ways to size a copied trade relative to the source, grouped at a high level into:

• Fixed — every copied trade uses the same lot size regardless of what the source traded.
• Risk-based — lot size is calculated from a risk percentage against the destination account's balance or equity, so the position sizes to a consistent dollar risk rather than mirroring the source's raw lot.
• Proportional — lot size scales relative to the source account's size, keeping the ratio between source and destination consistent as either account's balance changes.

Each of these has more granular variants (multiplier-based scaling, per-1000-balance sizing, fee-adjusted risk sizing) available in the Settings step of the wizard or from an existing instance's settings panel — the fields are self-explanatory in context, so this article won't enumerate every mode. If you're unsure which to use, risk-based is the default and the safest starting point for prop-firm accounts, since it keeps risk consistent even as account balance moves.

Copy latency

The copier runs hosted — there's no VPS to rent and no terminal that has to stay open on your end for copying to keep working. How long each copy took is measured, not promised: Cockpit → Trades & History shows the relay time on every copied trade and the median latency across them.

Managing a live instance

Once an instance is active, it shows up in Instances as a source with its destinations mapped out visually. From there you can:

• Toggle a destination on/off without deleting it (the enabled switch turns copying on or off for that destination).
• Open a destination's settings to adjust lot sizing, filters, or risk protection after the fact.
• Watch the activity feed for real-time copy events per instance.

If you need the same source copying into a brand-new destination later, you don't have to rebuild the whole instance — just add another destination from the existing group rather than creating a second instance from scratch.