Do You Need a VPS for Automated MT5 Trading? What Always-On Actually Requires

Short answer: yes, or something equivalent to one, and almost nobody tells you before you buy the bridge.

Every guide to connecting TradingView to MetaTrader 5 walks you through webhooks, alert syntax and Expert Advisors, and then stops. The requirement that decides whether the whole thing works on a Tuesday afternoon while you are in a meeting goes unmentioned: the terminal has to keep running.

This is not a sales pitch for hosting. It is the requirement, why it exists, and how to satisfy it for as little as possible.

Why automation needs a machine that never sleeps

The reason is structural rather than a limitation anyone chose.

TradingView fires alerts from its own servers, so your computer is irrelevant to that half. The alert reaches a bridge, which authenticates it and holds the resulting instruction. But the thing that actually places the order is an Expert Advisor running on a chart inside your MetaTrader terminal. It has to be running to pick the instruction up. NexumTrader's EA polls once per second and the dashboard marks an account offline after ten seconds without a heartbeat.

So the failure mode is this: you close the laptop, the terminal closes with it, and routing stops. No error appears. TradingView still fires, the bridge still receives, and nothing executes. The first sign is usually a trade you expected and did not get, noticed hours later.

That is why an always-on machine is a requirement and not an optimisation. It is also why the requirement scales: one terminal per account. Two prop accounts means two terminal instances running simultaneously, each with the EA on a chart of the symbol it trades.

Why Windows specifically

MetaTrader 5 is a Windows application. MetaQuotes does publish installers for macOS and Linux, and they work, but it is worth knowing what they do: the installer downloads and configures Wine, then installs the Windows build of MetaTrader inside it. It is a compatibility layer, not a native port.

For a desktop you sit in front of, that is fine. For a box that has to run unattended for weeks, it adds a layer that can fail in ways nobody will help you debug, and it puts you outside every hosting provider's prepared MetaTrader setup. When something breaks at 3am, the difference between a supported configuration and a clever one matters.

So: a Windows machine that stays on. Which leaves two sensible ways to get one.

Option 1: MetaTrader's own VPS

MetaQuotes sells hosting from inside the terminal. Click the VPS icon, pick a plan, and it migrates your environment to their infrastructure. Pricing runs from $15 per month down to $10 on an annual commitment, with a 24-hour trial.

It is the option nobody in this category recommends, because nobody earns anything from recommending it. It is also, for a lot of people, the right one.

Two technical details decide whether it works for you.

DLLs are prohibited. The service rules are explicit: "No DLLs are allowed on a Virtual terminal." An EA that imports one is stopped immediately with a critical error. A fair number of commercial EAs do import DLLs, so this disqualifies them outright.

WebRequest is permitted, and the migration carries over your allowed-URL list along with the rest of the environment.

For NexumTrader specifically: the EA imports no DLLs and communicates over WebRequest only, so it runs on MetaTrader's VPS. If you are using a different bridge, check its EA against those two rules before paying for anything.

The catch is scale. The VPS is activated from a terminal and hosts that terminal's environment. Running several accounts means several subscriptions, and the arithmetic turns against you quickly.

Option 2: a Windows VPS you rent yourself

One machine, several terminal instances, one bill. More setup, more control, and the only option that stays sane past two or three accounts.

You are buying an ordinary Windows Server box. Nothing about trading makes it special, which is worth remembering when you read hosting pages that suggest otherwise.

What to check before you pay

Check the operating system list, not the landing page. This is the single most common way people waste money here. Providers publish pages marketing "MetaTrader hosting" while their VPS product is Linux only. Running MT5 there means Wine, and every failure becomes your problem. Find the OS list in the technical specification and confirm Windows Server is actually offered.

Ask whether the Windows licence is included. Windows Server licensing is frequently billed on top of the advertised price and frequently not mentioned next to it. Ask before ordering, in writing.

Size it by terminal count. Each MT5 instance wants roughly a gigabyte of RAM to itself, more with heavy charts or indicators. Two accounts on a 2 GB box will run badly. Count your accounts, add headroom for Windows itself, and buy accordingly. This is the spec that matters, and it is the one hosting pages bury under CPU numbers.

Check for a setup fee, which some providers charge and few advertise.

Check the reboot and maintenance policy. A provider that reboots for patching without warning will silently stop your routing until the terminals are restarted. Ask whether terminals restart automatically after a reboot, and configure it yourself if not.

Which one, decided simply

The crossover sits around two accounts. Below it, per-terminal hosting is simpler and usually cheaper. Above it, one box you manage yourself wins on both cost and the number of places you have to look when something stops.

About the latency claims

Hosting pages aimed at traders compete almost entirely on milliseconds. It is worth understanding whether that number applies to you, because usually it does not.

If your setup is a TradingView strategy firing on bar close, the path is: the bar closes, TradingView sends a webhook, the bridge authenticates and queues it, and the EA collects it on its next poll. There are seconds of ordinary, unavoidable latency in that chain. Shaving three milliseconds off the final hop changes nothing you can measure.

Colocation and sub-millisecond execution are real advantages for high-frequency strategies running natively inside the terminal. They are not what a webhook-driven setup does. Buy uptime, adequate RAM and a supported operating system. Do not pay a premium for execution speed the architecture cannot use.

Check your firm's rules before you buy

If you are trading a prop account, this belongs before every other consideration in this article: some firms restrict or prohibit VPS and VPN use on trading accounts. The clauses vary, they are not always where you would expect to find them, and buying a year of hosting for an account that is not permitted to use it is an expensive way to discover the rule.

Read your firm's current terms, search for VPS, virtual and remote as well as the obvious phrasings, and if the wording is ambiguous, ask support in writing and keep the reply. How to Find the Best Prop Firm for Automated Trading covers where firms publish this and how to check.

Running several accounts on one box

The setup is repetitive rather than complicated. For each account: install a separate MetaTrader 5 instance into its own directory, log into that account, attach the EA to a chart of the symbol you route, and enter your identifier in the EA's inputs.

Three things people get wrong:

• The chart symbol matters. The EA executes on the chart it is attached to, so a signal for an instrument with no corresponding chart has nowhere to go.
• RAM is the constraint, not CPU. Terminals are memory-hungry and mostly idle otherwise.
• Automatic startup. After a reboot, Windows will not reopen your terminals unless you tell it to. Put them in Startup and confirm the EA reattaches, then test it by rebooting deliberately once, while you are watching.

FAQ

Do I need a VPS for TradingView to MT5 automation? You need a machine that stays on with the terminal running. A VPS is the usual way to get one. An always-on desktop that never sleeps and never updates unattended also works, though in practice it rarely stays that way.

Can I use a Mac? For the desktop terminal, yes: MetaQuotes provides an installer that sets up Wine and runs MetaTrader inside it. For an unattended always-on setup, a Windows machine avoids a layer of complexity you would otherwise own alone.

Does MetaTrader's own VPS work with a third-party EA? It depends on the EA. DLL imports are prohibited and an EA that uses one is stopped immediately. WebRequest is permitted, and the allowed-URL list migrates with the environment.

How much RAM do I need? Budget roughly a gigabyte per MetaTrader instance, plus headroom for Windows. Count terminals, not accounts, though for most setups those are the same number.

Will a cheaper Linux VPS work? Only through Wine, and unattended Wine is a support burden you carry alone. Check the provider's operating system list rather than its marketing page, because several advertise MetaTrader hosting on a Linux-only product.

Does a faster VPS mean better fills? Not for a webhook-driven setup. The alert path already contains seconds of latency by design. Uptime and sufficient memory matter; single-digit milliseconds do not.

This article describes the technical requirements of running MetaTrader 5 automation continuously. It is not financial, investment or trading advice, and nothing in it is a recommendation to trade, to use any strategy, or to choose any hosting or prop firm provider. It is not a statement about the current rules, terms or prices of any specific provider, and NexumTrader does not endorse, rate or recommend any of them, nor does it earn a commission from any hosting provider mentioned. Verify current specifications and terms with the provider, and your firm's current rules with your firm, before relying on any of it. Trading carries risk of loss.