Running MT5 on a VPS: What Actually Matters

An Expert Advisor does not care how good your strategy is. It cares whether the terminal is running when a signal fires. If your EA lives on your desktop, every Windows update, power cut, and Wi-Fi dropout is a gap in its operation. And some of those gaps will land on the days that mattered.

A VPS. A virtual private server, moves the terminal into a data centre that stays up. That is the whole idea, and it is a real improvement for anyone running automated strategies. But the way VPS services are marketed makes it hard to tell which of the advertised numbers actually affect execution and which exist only to justify a higher price. This article is about the difference.

It is a technical guide, not a product recommendation. The provider you use is secondary to understanding what you are paying for.

Why a VPS at all

Three problems go away when the terminal moves off your desk:

• Uptime. Data centres have redundant power and networking. Your EA keeps trading through a home power cut or an ISP outage, because neither of those touches the server.
• Latency. A VPS in the same data centre as your broker's trade server is physically close to it. The network round trip between your terminal and the trade server shrinks from tens of milliseconds to single digits.
• Isolation. Nothing competes for CPU. No browser with forty tabs, no 4K video, no game. The terminal gets the machine to itself.

None of these is a guarantee of profit. They remove a class of avoidable failure, which is a different claim. A VPS does not make a losing strategy win; it stops a working strategy from losing trades it never intended to miss.

What actually matters, in order

1. Network distance to the broker's trade server

This is the only metric that meaningfully affects execution, and it is the one most services are vague about. What matters is not the distance to the broker's website, or to some generic "financial hub", it is the round-trip time to the specific server IP your account connects to, which MT5 shows you when your terminal is logged in.

Measure it yourself. Log into MT5, note the server hostname from the account's connection status, resolve it to an IP, and ping it from a trial VPS. A ping of 1, 5 ms means you are effectively co-located. A ping of 30, 80 ms means you are on the wrong continent for that broker, regardless of what the marketing page says. Any VPS provider that will not let you measure before you commit is telling you the number is not good.

2. Uptime, and how it is enforced

"99.9% uptime" is close to meaningless on its own, it is a claimed number covering a measurement window nobody defines. What you want to know is whether the host uses redundant power and networking at the facility, whether there is a status page with history, and what the restart behaviour is after a host maintenance event. A host that takes your VPS down for patching without warning at 14:00 London is worse than a home PC you control.

3. Resource sizing that matches your EA

MT5 is not a heavy application. The terminal, a normal EA, and a handful of charts run comfortably on 1, 2 CPU cores and 2 GB of RAM. That changes only if you run several EAs across many symbols, or run something alongside MT5. A Python process for machine-learning inference, a database, a logging pipeline. Those need 4+ cores and 8 GB, and 80 GB of disk if you store historical data or a model locally.

Sizing up "just in case" is the most common way to overpay. Look at your actual terminal's memory footprint on a normal trading day before you buy.

4. Whether you can install what you need

Some hosted-trading VPS products pre-install MT5 and lock down everything else. That is fine if all you run is an EA. It is a dead end the moment your workflow depends on Python, a specific library, or a DLL that MT5 needs to import. Confirm that you have full administrative access to the box, and that MT5 is permitted to load external libraries, before you build around it.

5. Price

A usable trading VPS is cheap. Expect $10, $40 per month for a spec that handles MT5 and a single EA; $50, $90 for a multi-strategy box with Python alongside. If a provider is charging $150 while refusing to publish a latency figure, you are paying for the adjective.

What does not matter, despite the marketing

• Sub-millisecond claims. A round trip under 1 ms only happens when you and the broker's server are in the same facility. That is achievable and worth having; it is not a premium feature worth a large multiple of the price. Measure the actual ping.
• GPU. MT5 does not use one. The Strategy Tester is CPU-bound. A GPU VPS is wasted money for this workload.
• Huge RAM allocations. 32 GB of RAM does nothing for an EA that uses 400 MB.
• Brand names. The data centre's location relative to your broker matters far more than the logo on the invoice.
• "Zero slippage." No host can promise this. Slippage is a property of the market and your broker's fills, not of your server. Lower latency reduces the chance that price moves between signal and fill; it does not eliminate it.

Co-located versus generic hosting

There are two kinds of VPS you will be offered, and they are not equivalent:

• Co-located with your broker's servers. Often sold by the broker itself or by a specialist host that rents rack space in the same facility. Latency of 1, 5 ms. Usually requires you to be an active client. This is the right option if your strategy is latency-sensitive.
• General-purpose VPS. Any reputable cloud host, located as close as possible to your broker's data centre region. Latency of 5, 30 ms to a broker on the same continent. Perfectly adequate for swing, intraday, and most multi-timeframe strategies.

The honest split is by strategy speed. If your EA acts on tick data or sub-minute candles, co-location is worth paying for. If it acts on 15-minute bars or slower, a general VPS in the right region is indistinguishable in practice, and cheaper.

Security: the part people skip

A VPS running MT5 is a Windows machine on the public internet with your trading credentials on it. Treat it that way:

• Use a long, unique password on the VPS account, and change the default RDP port away from 3389 to reduce automated scanning noise.
• Restrict RDP to your own IP address in the host's firewall if your provider supports it. This closes the single largest attack surface on a trading VPS.
• Do not reuse your broker password as your VPS password. They should be different credentials.
• Keep Windows and MT5 updated, but schedule updates manually. An automatic restart mid-session is exactly the failure a VPS is meant to prevent.
• Enable two-factor authentication on your broker account wherever the broker offers it. Login credentials living on a remote box deserve a second factor.

Setting it up

1. Choose a location based on your broker's server, not on yours. Find the trade server IP, then pick the region with the lowest measured ping.
2. Start with the smallest spec that fits your EA and scale up only if you see CPU or RAM pressure in Task Manager during live trading.
3. Install MT5, either pre-installed by the host or a standard download. And log in to the account you intend to trade.
4. Enable algorithmic trading in the terminal: Tools → Options → Expert Advisors → Allow algorithmic trading. Check the toolbar button too. Forgetting this is the classic "everything works but no orders execute" bug.
5. Copy your EA to the correct folder under the terminal's data directory and attach it to the charts it expects. Confirm the symbol names match your broker's naming, broker symbol prefixes and suffixes differ.
6. Check the server's time settings against your broker's server time. MT5 does its own time handling, but if you run Python alongside it, a clock drift between the two will corrupt time-stamped features.
7. Monitor for the first week. Watch for EA stops, disconnections, and memory growth. Then leave it alone.

Pitfalls worth knowing in advance

• MT5 auto-updates can restart the terminal. In some versions the terminal will close and reopen without your EA reattaching automatically. Verify that your EA is set to load automatically on the chart, and check after every update.
• A disconnected terminal keeps positions open. If MT5 loses its connection, open trades do not close themselves. Your EA's exit logic only runs while the terminal is connected, this is a market risk, not just an infrastructure one.
• Running MT5 and Python on the same box has a failure mode. If the Python process crashes, the EA may keep trading on stale features. Separate the two processes and let the EA refuse to trade when its data feed goes quiet.
• Backups are your responsibility. Snapshot the VPS after a working setup so you can restore a known-good state instead of rebuilding MT5 from scratch.

Is it worth it

For a strategy you are running with real money and cannot supervise all day, yes. The failure a VPS prevents. A missed exit or a missed entry during an outage, can cost more than a year of hosting. For a strategy still on demo, or one that trades a few times a week on the daily chart, a VPS is convenience rather than necessity.

The rule of thumb that holds up: if you would be annoyed to discover your EA was offline for four hours yesterday, you need a VPS. If you would not notice, you probably do not yet.