FXVPS
Get Started
forex vps lmax ecn ld4 latency

Best VPS for LMAX: Exchange-Model Execution, No Last Look, and LD4 Colocation

person
FXVPS
Share
Best VPS for LMAX: Exchange-Model Execution, No Last Look, and LD4 Colocation

Most retail forex brokers are, structurally, market makers with a risk desk in the middle. LMAX is not that. LMAX Exchange operates as an FCA-authorised multilateral trading facility running a central limit order book, and LMAX Global is the FCA-regulated broker entity that gives clients access to that liquidity. Orders match against firm, streamed prices from institutional liquidity providers. There is no last look, no requote mechanism, and no dealer discretion sitting between your order and the fill.

That model rewards infrastructure in a way a dealing-desk broker does not. When your fill is decided by a price-time priority queue rather than by a risk desk deciding whether to accept your order, the milliseconds between your terminal and the matching engine stop being a rounding error and start being the whole game. Here is what a VPS actually does for an LMAX account, and how to size one.

LMAX at a Glance

  • Regulation: FCA (UK), CySEC (Cyprus), FSC (Mauritius), registered Financial Service Provider (New Zealand)
  • Model: Central limit order book / exchange model — firm liquidity, no last look, no requotes
  • Entities: LMAX Exchange (MTF, institutional) and LMAX Global (broker entity for retail and professional clients)
  • Spreads: From 0.0 pips on majors during liquid sessions; commission charged per side
  • Commission: Per-side commission on notional; volume-tiered
  • Platforms: MT4, MT5, LMAX web trading GUI, mobile apps, FIX API
  • Instruments: 100+ across FX, crypto, bullion, indices and commodities, including weekend FX
  • Datacenters: Equinix LD4 (London), NY4 (New York), TY3 (Tokyo), SG1 (Singapore)
  • Client base: Skews institutional, professional and algorithmic rather than beginner retail
  • Colocation: Available for clients who want to sit inside the same facility as the matching engine

The tell in that list is the datacenter row. Brokers who describe their infrastructure as “London servers” are being vague. LMAX names the specific Equinix facilities, because the traders they court actually care.

Where LMAX’s Servers Live

LMAX runs matching infrastructure in four Equinix International Business Exchange facilities: LD4 in Slough (London), NY4 in Secaucus (New York), TY3 in Tokyo, and SG1 in Singapore. These are the same buildings that host the majority of institutional FX liquidity globally — the reason spot FX gravitates to them is that once enough banks and non-bank market makers cross-connect inside one facility, everyone else has to be there too.

LD4 is the primary venue for FX. The bulk of the interbank spot market’s electronic liquidity is concentrated within a few racks of each other in Slough, and LMAX’s London order book sits in that gravity well. NY4 handles North American flow and is where a lot of the US-hours liquidity concentrates. TY3 and SG1 serve Asian sessions.

📊 Key Stat: FXVPS measures round-trip latency of roughly 2.03ms from our London instance to LMAX. That is a same-building or near-building number. The same connection from a residential broadband line in a European capital typically lands between 30ms and 90ms, before you account for jitter.

If you want the background on why these four facility codes keep appearing across every serious broker’s infrastructure page, our Equinix data centers explained piece covers the geography.

FXVPS Latency to LMAX

FXVPS operates dedicated hardware inside Equinix LD4 and maintains instances in New York, Tokyo, Singapore and Frankfurt alongside 15+ other locations. From the London instance, the path to LMAX’s London order book stays inside the datacenter fabric rather than traversing the public internet. That is the structural reason for a ~2ms round trip rather than a marketing claim about “premium networking.”

Pick your location by which LMAX venue your account routes to:

  • London (LD4) — the default answer for FX. If you trade majors, crosses, bullion or European indices, this is the right choice.
  • New York (NY4) — if your account or strategy is routed to the North American book, or if you also run US-focused instruments.
  • Tokyo (TY3) — for Asian-session strategies trading JPY crosses and regional indices.

⚠️ Warning: Do not pick a VPS location based on where you physically live. A trader in Sydney trading EURUSD on LMAX’s London book wants a London VPS, not a Sydney one. Your own connection to the VPS is a human-latency problem measured in tens of milliseconds and it does not affect order execution at all — the VPS is what talks to the matching engine.

Why LMAX Traders Specifically Need a VPS

No Last Look Means Latency Is the Only Variable Left

At a last-look broker, a slow order gets rejected or requoted, and you experience the cost as friction. At LMAX, a slow order does not get rejected — it arrives late and matches against whatever is still resting on the book. On a fast-moving quote, “whatever is still resting” is a worse price than the one you clicked. The cost is silent and it shows up as a persistent negative skew in your fill statistics rather than as an error message.

This is why the exchange model and colocation are so tightly coupled in practice. Removing the dealer removes the excuse; the only remaining explanation for bad fills is your own network path. Our breakdown of market, instant and exchange execution models explains the mechanical difference in more depth.

Commission-Based Pricing Makes Slippage Visible

Because LMAX charges commission on top of raw spread rather than marking up the spread, your all-in cost decomposes cleanly: commission (fixed, known) plus spread (visible) plus slippage (variable, and entirely a function of your infrastructure). Traders on markup-spread accounts can hide poor execution inside a wide quote. LMAX clients cannot. That transparency is a feature, but it means the slippage line in your cost breakdown is a direct scorecard for your VPS.

💡 Tip: Run a fill-quality audit after two weeks on a colocated VPS. Export your trade history, compute the average difference between your intended price and your actual fill, and compare it to the same statistic from your previous setup. On a commission-based account this comparison is unusually clean, because nothing else in your cost stack changed.

Algorithmic and API Clients Need Always-On Hosting

LMAX’s client base skews toward FIX API users and algorithmic traders. A FIX session is a persistent TCP connection with heartbeat requirements — it is not something you want terminating because a laptop lid closed or a home router rebooted itself for a firmware update. A VPS gives you a static IP (which matters for FIX session whitelisting), 24/7 power and connectivity, and a machine that does not go to sleep.

The same argument applies to MT4 and MT5 EAs, but it is sharper for API clients because a dropped FIX session can leave working orders in an ambiguous state until reconnection.

Weekend FX and Crypto Never Close

LMAX offers weekend FX and crypto instruments that trade outside the conventional Sunday-to-Friday window. If you hold or manage exposure through those hours, a home setup that is offline while you sleep is not a monitoring gap — it is an unmanaged risk position.

🚀 Try FXVPS free for $1.99 — get 7 days on the Core VPS risk-free and measure the latency to LMAX yourself. No long-term commitment, cancel anytime.

Core Plan ($29/mo — 2GB RAM, 1 vCPU) covers a single MT4 or MT5 terminal against LMAX with a handful of EAs and a normal indicator load. If you are a discretionary trader running one platform, or an EA trader with one to three strategies, Core is correctly sized and there is no benefit to overbuying.

Pro Plan ($39/mo — 4GB RAM, 2 vCPUs) is the right default for LMAX’s typical client. Two vCPUs matter here specifically because most algorithmic setups want the platform on one core and the strategy or bridge process on another. If you run MT5 (which is heavier than MT4), multiple terminals, or a FIX API client alongside a charting platform, Pro is the plan.

Scaling Plan ($79/mo — 8GB RAM, 4 vCPUs) suits FIX API traders running their own execution logic, multi-instrument algorithmic books, or anyone managing several accounts against LMAX at once. If you are trading LMAX at institutional-ish size, $79/mo is not a line item worth optimising.

✅ Best Practice: For any strategy where fill quality is part of the edge, size up one tier from what your resource monitor says you need. CPU contention shows up as intermittent millisecond-scale delays in order dispatch, and those are exactly the delays that cost you on a price-time priority book. See dedicated cores vs shared vCPU for why this distinction matters more than raw core count.

Setting Up LMAX on Your FXVPS

  1. Choose the datacenter that matches your LMAX venue at signup. London for FX and the default retail case; New York if you are routed to the North American book; Tokyo for Asian-session work.

  2. Connect via RDP using the credentials FXVPS provides. Microsoft Remote Desktop works from Windows, macOS, iOS and Android.

  3. Download MT4 or MT5 from LMAX’s client portal, not from a generic MetaQuotes mirror. The broker-supplied installer arrives with LMAX’s server addresses already populated, which avoids the common mistake of connecting to a demo cluster and wondering why the latency looks wrong.

  4. Log in with your LMAX Global credentials and confirm the server shown matches the one in your LMAX dashboard. Live and demo environments live on separate clusters.

  5. Verify latency in the MetaTrader status bar (bottom right). From an FXVPS London instance you should see a low single-digit millisecond figure. If you are seeing 30ms+, you are almost certainly connected to a demo server or a different regional cluster.

  6. For FIX API clients: note your VPS’s static IP and submit it to LMAX for session whitelisting before your first connection attempt. Configure your FIX engine’s heartbeat and reconnect logic to survive brief network events rather than exiting on first failure.

  7. Configure auto-start and auto-login so your terminal or engine comes back automatically after a reboot. Put shortcuts in the Windows Startup folder, and for anything running headless use a Windows service wrapper rather than a logged-in session.

  8. Set up NTP time sync. On a price-time priority book, accurate local timestamps are what let you reconcile your own logs against LMAX’s fills. Our time synchronization guide covers the configuration.

Why FXVPS for LMAX Traders

LMAX built its whole proposition on removing the intermediary between you and the order book. It is a strange choice to pay for that and then hand the advantage back by routing your orders through a residential broadband connection with 60ms of latency and unpredictable jitter.

FXVPS runs dedicated hardware inside Equinix LD4 — the same facility that houses LMAX’s London order book — plus NY4-region, Tokyo and Singapore instances for traders on other venues. Dedicated CPU cores rather than oversubscribed shared vCPU, enterprise uptime, and a measured ~2ms path to LMAX. Compare plans at /pricing/ and validate the latency claim yourself on a $1.99 seven-day trial before you commit to anything.

Frequently Asked Questions

What VPS location should I pick for LMAX?

London, for the overwhelming majority of LMAX clients. LMAX’s primary FX order book runs from Equinix LD4 in Slough, and an FXVPS London instance sits in the same facility. Choose New York or Tokyo only if your account is specifically routed to the NY4 or TY3 venue.

Does LMAX support MT4 and MT5?

Yes — LMAX Global offers MetaTrader 4 and MetaTrader 5 alongside its own web trading GUI, mobile apps and FIX API. The MetaTrader route is the common path for retail and EA traders; the FIX API is what most of the algorithmic and institutional client base uses.

Will a VPS make my LMAX spreads tighter?

No. Spread is a function of the liquidity resting on LMAX’s book, and no hosting decision changes that. What a VPS changes is how much of the quoted price you actually capture at fill. On a no-last-look venue, that gap is entirely down to how long your order takes to reach the matching engine.

Do I need a VPS if I only use the LMAX web platform manually?

The case is weaker for purely manual, low-frequency discretionary trading through a browser. It strengthens sharply the moment you run EAs, a FIX session, or any strategy where an order needs to be dispatched while you are asleep or away from the machine.

Can I run a FIX API client on an FXVPS instance?

Yes. Windows Server handles FIX engines natively, and the static IP that comes with your instance is what LMAX will whitelist for your session. The Pro plan or above is the sensible floor for API work, since you want the engine and any charting or monitoring processes on separate cores.

What happens to my open LMAX positions if the VPS reboots?

Positions and working orders live on LMAX’s infrastructure, not on your machine. A reboot only interrupts your ability to see and manage them. With auto-start configured, a MetaTrader terminal reconnects within roughly a minute; a FIX engine configured as a Windows service comes back without a login.