Hosting multiple MT5 accounts with one TradingView alert.

The short answer

Every MT5 account needs its own running terminal. An MT5 terminal is logged into one trading account at a time, so four accounts trading at once means four terminals. You either run them yourself (several MT5 installations on one PC or VPS, each in its own folder) or rent managed terminals, one per account (SFCloud, PineConnector Edge).

Then a bridge fans one alert out to all of them. With SignalForge, a webhook without an "account" field is broadcast to every EA connected with your token; add "account": "12345678" and it only reaches that login. Lot size, risk, trading hours and Prop Firm Shield limits are set per account in the dashboard, so the signal is shared but the risk is not.

Option 1: one terminal per account on your PC or VPS

MetaQuotes' own help is explicit: to run several copies of MT5 at the same time, install each one in a different directory; two copies cannot run from the same folder. In practice:

• Run the installer once per account (your broker's or the generic MetaQuotes one) and change the installation folder each time, e.g. MT5-FTMO-100k, MT5-FN-50k. Naming folders and desktop shortcuts by account saves you from trading the wrong one.
• Optional portable mode: start each terminal with the /portable key so its data lives inside its own folder instead of the shared AppData path. Outside Program Files you only need write permission on the folder.
• Log each terminal into its account, enable Algo Trading, attach the bridge EA to one chart and allow its WebRequest URL. Since EA v3.70 the SignalForge settings live in the dashboard, so there is nothing to tune in each terminal's inputs.
• Plan the resources. RAM grows with open charts, symbols in Market Watch and history depth. For orientation only: in our own fleet, a container running one MT5 terminal plus browser access measured about 0.9 to 1.1 GB of RAM (July 2026). Measure your real setup in Task Manager before you buy a VPS size.

The upside is full control and any EA you like, and it is the cheapest route if you already pay for the machine. The downside is that you are the operations team: Windows updates, reboots, terminals that do not restart, and one machine that takes every account down with it when it fails. Some prop firms also restrict VPS or IP changes, so check your firm's policy first. Sizing a server: best VPS for MT5.

Option 2: managed MT5, one hosted terminal per account

SFCloud is our managed MT5, built for the SignalForge bridge. Each terminal runs in its own isolated container in our UK or France data centres, you open it from the browser over HTTPS, and it is ready about 30 minutes after checkout. Your broker login is written only to the terminal's own config, never to our database. You can upload your own compiled EAs (.ex5/.set, up to 10 MB); MQL5 Market EAs are not supported and .mq5 files are not compiled inside. Terminal counts: 1 with Starter + SFCloud ($9.99/mo), up to 3 with Trader + SFCloud ($19.99/mo), 5 with Pro ($29.99/mo) and 10 with Elite ($49.99/mo). SFCloud alone is $6.99/mo per terminal, without the bridge.

PineConnector Edge is PineConnector's managed MT5 hosting, included in its plans: 1 hosted terminal on Core, 3 on Plus and 5 on Pro, with extra connections beyond Pro at $35/mo each (one connection plus one hosted MT5). Its FAQ lists New York hosting, with London "coming soon" for Plus and Pro (verified 4 October 2026). Edge is designed around PineConnector's own EA rather than a general-purpose VPS; details in PineConnector Edge vs a VPS.

Monthly cost by number of accounts

What the SignalForge tiers include: Starter has trailing stop, break-even and the spread filter; Trader and above add Prop Firm Shield, news and trend filters and Telegram notifications. Starter, Trader and both SFCloud bundles have a 14-day free trial without a card; standalone SFCloud, Pro and Elite are paid from day one. The "own MT5" column excludes your PC or VPS, and no column includes the paid TradingView plan that webhooks require. PineConnector figures are from the pricing section and FAQ of pineconnector.com (4 October 2026); confirm at checkout, prices change. Full breakdown of hosted options in hosted MT5 pricing 2026.

How SignalForge routes one alert to every account

Every MT5 account you connect runs the SignalForge EA with your token. When TradingView fires, the server decides who receives the signal:

// all connected accounts
{"action":"buy","symbol":"EURUSD","sl":30,"tp":60}

// only one account (login as a quoted literal)
{"action":"buy","symbol":"EURUSD","sl":30,"tp":60,"account":"12345678"}

• Per-account execution settings live in Dashboard → Execution: position size type (fixed lot, lot from the signal or risk-based), SL/TP mode and the time filter, a grid of half-hour slots in your timezone that the EA converts to each broker's server time. Close signals are never blocked by the time filter.
• Prop Firm Shield per account (Trader and above): daily loss guards with each account's own daily limits and profit targets. See Prop Firm Shield.
• Speed: about 0.5 s median from webhook to confirmed order (measured 19 to 23 September 2026: ~56 ms server, ~116 ms network, ~250 ms EA plus broker). TradingView itself takes a few seconds to send the webhook. Each account fills at its own broker's price and spread.
• More accounts: +$3/mo per extra MT5 account (up to 3 on Starter, up to 5 on Trader), or move to Pro or Elite. Alert syntax in detail: documentation and copy TradingView signals to MT5.

Risks and rules before you scale

• Accounts of different people. FTMO's forbidden practices bar trading on another person's account and coordinated trades "in concert with other persons". FundedNext bans copying between accounts of different individuals, family and friends included, and any copying that involves one of its funded accounts, even your own; copying between your own Challenge accounts is allowed up to $300,000 combined. FTMO has no limit on the number of accounts but caps total capital at $400,000 per trader or strategy before scaling. (Official pages checked 4 October 2026.) Firm-by-firm table: copy trading multiple prop firm accounts.
• Different account sizes need different lots. A lot that fits a 100k account doubles the risk on a 50k one. Leave lot out of the alert and let each account size with its own setting, or use risk-based sizing.
• Desynchronisation. If one terminal is offline, the server queues the signal for 120 seconds and then it expires: that account misses the trade while the others take it. Filters and trading hours can also skip an entry on one account only. Check positions after restarts, and send a demo test alert to each account to confirm the broker's symbol name resolves.
• Correlated drawdown. The same strategy on five accounts turns one bad day into five daily-limit hits. Stagger risk (full on the main account, half on the rest) and let Prop Firm Shield cut each account at its own limit.

FAQ

Keep reading