Run several MetaTrader terminals on one VPS
Install each MT4 or MT5 terminal in its own folder, start it in portable mode, and size your server for the terminals and EAs you run.
- Intermediate
- Admin RDP · Windows VPS
- 3 min read
Many traders run more than one MetaTrader terminal: one per broker, one per account, or a separate terminal for testing. Each terminal needs its own folder. Portable mode is the cleanest way to set that up.
Why portable mode?
Normally MetaTrader keeps its data (EAs, settings, logs, history) in a hidden folder under your user profile. In portable mode, it keeps everything inside its own install folder. That makes each terminal self-contained: easy to copy, back up and tell apart.
1. Install each terminal into its own folder
Run the installer once per terminal. On the first screen click Settings and change the install folder, for example:
C:\MT5\BrokerA-LiveC:\MT5\BrokerA-DemoC:\MT5\BrokerB-Live
To clone an existing terminal instead, close it and copy its whole install folder to a new name.
2. Start each terminal in portable mode
The program file is terminal64.exe for MT5 and terminal.exe for MT4. Add /portable when you start it:
& "C:\MT5\BrokerA-Live\terminal64.exe" /portableTo make this the normal way you open it, create a desktop shortcut to the .exe, open its Properties, and add /portable to the end of Target, after the closing quote. Name each shortcut after the account so you never mix them up.
Always start a given terminal the same way. If you open it once without /portable, it reads a different data folder and your EAs, settings and saved logins seem to disappear. They are still in the portable folder; close the terminal and reopen it with the right shortcut.
3. Log in and set up each one
Log in to a different account in each terminal and add your EAs as in Install MetaTrader and keep your EAs running. Data now lives in each install folder under MQL5 or MQL4.
How many terminals can my server handle?
It depends on the terminals, not just their number. Each terminal uses memory and CPU for its charts, the symbols in Market Watch, the history it keeps and the EAs it runs. Some practical rules:
- Start one terminal, set it up fully, and check its memory and CPU in Task Manager (guide). Use that as your estimate for similar terminals.
- Keep total memory use comfortably below the server's RAM, with room left for Windows and updates.
- Reduce load per terminal: close charts you do not watch, hide unused symbols in Market Watch, and lower Max bars in chart in Tools → Options → Charts.
- Back-testing and optimisation are heavy; avoid running them on the server that holds your live terminals.
If CPU or memory stays high, move to a larger plan; compare them on Pricing.
Troubleshooting
- Two shortcuts open the same terminal: check the Target of each points to a different folder.
- Terminal is slow to start: a large history and many open charts take longer; trim them as described above.
Next steps
- Auto-start MetaTrader after a reboot
- Back up a Windows VPS (copy each terminal folder)
Was this guide helpful?
Still stuck?
Ask RunRacks AI for a quick answer, or open a ticket and our team will take a look at your server.
Related guides
Windows VPS & RDP
RunRacks RDP port 12230: how to connect to your Windows VPS and Admin RDP
RunRacks Windows VPS and Admin RDP servers accept Remote Desktop on port 12230, not 3389. Here is how to connect from every device and keep the port open.
- Beginner
- Windows VPS · Admin RDP
- 5 min read
Windows VPS & RDP
Allow or block multiple RDP sessions for one user
Understand why a new Remote Desktop login takes over your old session, how the single-session policy works on Windows Server, and which setting suits a team.
- Advanced
- Windows VPS
- 5 min read
Windows VPS & RDP
Create Windows users with Remote Desktop access
Give each person their own Windows login, add them to Remote Desktop Users, test the account and remove access cleanly later.
- Beginner
- Windows VPS · Admin RDP
- 2 min read