A "forex VPS" is the trading community's shorthand for a Windows RDP that hosts MetaTrader, cTrader or a custom Expert Advisor 24 hours a day. The trader's laptop is unreliable for an EA — battery, sleep mode, ISP outages, OS updates — so the strategy lives on a remote Windows that is always online. This guide walks through every operational decision: where to host, what plan tier to pick, how to install MT4 / MT5, how to think about broker latency, and how to keep the whole setup outside any KYC or identity chain.
Why a Windows RDP, not a Linux VPS?
MetaTrader 4 / 5 and cTrader are native Windows applications. They will run under WINE on Linux, but with brittle results — broker servers occasionally update protocols, EAs use Windows-specific DLLs, MQL5 tooling assumes Windows paths. Every serious EA shop ships on Windows, and the brokers test their MT4 / MT5 builds against Windows. A Windows RDP eliminates the WINE class of bugs and lets you run the same MetaTrader build the broker tests on. The cost difference between a Linux VPS at $14.99 and an entry RDP at $21.99 is small; the operational pain difference is large.
Picking a jurisdiction by latency, not by privacy alone
Forex EAs are latency-sensitive. The MT4/MT5 server keeps a TCP connection open and the EA reacts to tick updates; even 50ms of round-trip time can change the fill price on a market order or trigger an EA's slippage guard. The broker's server location dictates the optimal RDP jurisdiction. European brokers (FXCM EU, Pepperstone EU, IC Markets EU, IG, Saxo, Admiral Markets) typically host MT5 in Equinix LD4 (London) or in their own EU datacenters — pick Netherlands (AMS-IX peering, sub-10ms to LD4) or Romania for low-latency EU trading. Cyprus / Mediterranean brokers often host in LD4 or Frankfurt — Netherlands again wins. Russian brokers (Alpari Russia, ICE FX) host domestically — pick Russia RDP for sub-2ms latency. Cheap-but-less-latency-critical strategies (swing trading on H4/D1, no EAs) — Moldova at $21.99/mo with 30-40ms to LD4 is plenty.
Plan sizing for MetaTrader and EAs
MT4 itself is light — 200 MB RAM, single CPU core. MT5 is heavier — 400-600 MB. Each chart with an EA running adds roughly 50-100 MB and a small CPU baseline; chart count compounds memory. RDP-S (2 vCPU / 4 GB / 60 GB NVMe, $21.99/mo) handles 1-2 MT4/MT5 instances with up to ~10 charts comfortably — the right tier for a trader running a single broker or up to two accounts. RDP-M (4 vCPU / 8 GB / 120 GB NVMe, $23.99/mo) handles 3-5 instances, multiple EAs, and tools like Trade Manager / VPSarea-style EA loaders. RDP-L (6 vCPU / 16 GB) is for prop-firm pass-funded traders running 10+ accounts. RDP-XL (8 vCPU / 32 GB DDR5) is for serious multi-broker EA shops with 20+ instances and Python-side analytics. Most retail traders need RDP-S or RDP-M.
Installing MT4 / MT5 on a fresh ServPrivacy RDP
The standard install path: connect to the RDP via Microsoft Remote Desktop or AnyDesk; open Edge; download the broker's MT5 setup .exe directly from the broker's download URL (do not use third-party "MT5 portable" zips, they are a common malware vector); install with default options into C:\Program Files\MetaTrader 5; log in with broker credentials; attach your EA to the chart and confirm "Auto Trading" is enabled. For 24/7 operation: in MT5, set Tools → Options → Auto trading to allow EAs and disable confirmations on auto-close; pin MT5 to startup so it relaunches after Windows updates. We recommend disabling Windows Update auto-restart by setting "active hours" to 0:00-23:00 — this prevents the RDP rebooting in the middle of a trading session.
Custom Expert Advisors and licensing on a remote RDP
Most commercial EAs are licensed by trading account number, not by hardware fingerprint, so moving the EA from a local machine to the RDP works without re-licensing. A few EA vendors lock to MAC address — that is a deal-breaker on a virtualised host because the MAC will not match. If your EA license server validates against MetaTrader's internal account ID, the migration is seamless. If it validates against hardware, ask the vendor to issue a new license for the new machine. Custom MQL5 code you wrote yourself: just copy the .mq5 / .ex5 files into %APPDATA%\MetaQuotes\Terminal\<hash>\MQL5\Experts on the RDP and recompile.
Anti-detect browsers and prop-firm scenarios
Prop firms (FTMO, MyForexFunds, The5ers) typically allow VPS / RDP usage but want one trader per account. If you run multiple prop accounts, an anti-detect browser stack on the same RDP (Multilogin, GoLogin, Dolphin, Incogniton) keeps each account's browser fingerprint isolated when you log into the prop-firm dashboard. Full Windows administrator on the ServPrivacy RDP means you can install any of these tools without the host blocking them. Important: prop firms scan for VPN/RDP IPs and may flag a known datacenter IP — use the RDP for MT5 itself but log into the prop dashboard from your local browser, not from the RDP.
Backups and resilience
An EA running 24/7 on a remote RDP needs two resilience layers. First, daily MT5 profile backups — zip the %APPDATA%\MetaQuotes folder to a OneDrive or Google Drive on the RDP every 24h via Task Scheduler. Second, broker-side stop-out protection — set MT5 stop-out level conservatively, do not rely on EA exit logic alone in case the RDP loses network briefly. ServPrivacy uplink is 1-2 Gbps with redundant routing, but no host has 100% uptime. Catastrophic failure mode planning: if the RDP becomes unreachable for >5 minutes, your EA continues running but you cannot intervene; design EAs with bounded position-size limits and broker-side stop losses.
The no-KYC angle for forex traders
Why does no-KYC matter for trading specifically? Three scenarios. (1) High-tax jurisdictions: traders operating from countries with aggressive FX-trading capital-gains enforcement (UK, France, Germany) sometimes prefer their EA infrastructure not be tied to their personal name. (2) Trading-restricted jurisdictions: some countries restrict retail leverage or prohibit certain instruments; an offshore RDP using offshore broker accounts sidesteps the issue, though the trader bears full personal legal responsibility. (3) Prop-firm scaling: traders running multiple prop accounts want each piece of infrastructure to be cleanly separable. ServPrivacy ships token-based signup with no email, phone or ID; pay in BTC, XMR or 12 other chains; receive a session token; never provide identity. The RDP itself is just a Windows desktop; what you do with it is your business.
Summary checklist
Pick jurisdiction by latency to your broker (Netherlands for EU, Russia for Russian, Moldova for cost). Pick plan tier by EA count (RDP-S for 1-2, RDP-M for 3-5, RDP-L/XL for prop scaling). Install MetaTrader from the broker's URL, not third-party. Set Auto Trading + disable Windows reboot. Plan resilience: daily profile backup, broker-side stop loss. Pay in crypto, no email, token-based recovery. Live in 60 seconds.