Read time … min

AI-native runtime for LMAX Global trading strategies

Author institutional-style FIX 4.4 strategies for LMAX Exchange in Cursor, Claude Code or any AI IDE. Deploy from GitHub into a managed cloud runtime with first-class MCP control, logs and region selection.

By the TradingHost engineering team

Section 01 · At a glance

At a glance

Broker
LMAX Global (LMAX Group)
Broker type
Forex and CFD broker; LMAX Exchange central-limit-order-book operator
Asset class
Forex, indices CFDs, commodities CFDs, metals (entity-dependent)
Supported products
90+ spot FX currency pairs, major indices CFDs, metals (XAU/USD, XAG/USD) and selected commodities. Distinctive feature: orders match on an actual central-limit-order-book exchange rather than against a broker book.
Runtime model
Containerised strategy runtime
Deployment source
GitHub
Languages
Any language that runs in a container (FIX is language-agnostic; Java and .NET client libraries are first-party)
Common integrations
LMAX FIX 4.4 (separate Market Data and Order Execution sessions), LMAX Java client library, LMAX .NET client library, NautilusTrader (community LMAX adapter), custom connectors
AI workflow integration
MCP control surface for Cursor, Claude Code, GitHub Copilot and CLI agents
TradingHost role
Runtime, deployment, logs, health checks, region selection, MCP control
LMAX role
Broker account, exchange access, central-limit-order-book matching, execution venue
Regulators
LMAX Limited (FCA firm reference 509778, UK); LMAX Group Markets Pte. Ltd. (MAS, Singapore); LMAX Global EU Limited (CySEC, Cyprus); LMAX New Zealand Limited (FSP, New Zealand); LMAX Markets (Mauritius) Limited (FSC Mauritius).
Retail leverage caps
UK (LMAX Limited, FCA) and EU (LMAX Global EU, CySEC, ESMA-aligned): 30:1 on major FX, 20:1 on non-major FX and gold, 10:1 on non-gold commodities and non-major indices, 5:1 on stocks, 2:1 on crypto CFDs. Singapore (MAS), New Zealand (FSP) and Mauritius (FSC) entities apply their per-jurisdiction rules.
Account minimums
LMAX Global accounts carry account-tier minimums (commonly cited at $10,000 to $25,000 across entities) that are higher than typical retail brokers. The trade-off is exchange-style execution rather than a broker book. Confirm the minimum with LMAX directly when onboarding.
Affiliation
TradingHost is independent and is not affiliated with LMAX Group, LMAX Limited or any LMAX entity. LMAX Digital is a separate LMAX Group crypto venue covered on the /brokers/crypto/ cluster.

Section 02 · What LMAX Global offers

What LMAX Global offers

LMAX Global offers spot FX on 90+ pairs, plus selected indices and commodities CFDs, against the LMAX Exchange central-limit-order-book matching engine via FIX 4.4 and first-party Java and .NET client libraries. The exchange model is the differentiator: orders match on a real order book rather than against a broker book. Account minimums are higher than typical retail. Specific endpoints and the full instrument list live in the LMAX docs portal.

Markets and strategy patterns

  • Central-limit-order-book FX execution on 90+ pairs
  • Latency-sensitive FX strategies in EU-region runtimes
  • Spread-tier-aware order routing strategies
  • XAU/USD and XAG/USD precious-metals strategies
  • Major indices CFD strategies (entity-dependent)
  • FIX 4.4 Market Data and Order Execution session pairs
  • Java and .NET native-client strategies

API surface

Product surfaces
90+ spot FX currency pairs, major indices CFDs (entity-dependent), metals (XAU/USD, XAG/USD) and selected commodities. LMAX is positioned as an exchange-style FX venue, with a central limit order book rather than internalised broker fills. Demo and live environments are separate FIX endpoints.
Connection methods
LMAX FIX 4.4, with separate Market Data and Order Execution FIX sessions. LMAX publishes first-party Java and .NET client libraries that wrap the FIX layer. The same instrument list and order model are exposed through the libraries and through raw FIX.
Authentication
FIX session credentials (SenderCompID, Password and host) are issued by LMAX after onboarding and account funding. The Java and .NET libraries use the same credentials. LMAX requires onboarding due diligence and meets the account minimum before issuing live FIX credentials; demo FIX is available for development against the demo environment.

For specifics, refer to LMAX

docs.lmax.com is the source of truth for FIX endpoints, the Java and .NET client APIs and connectivity details. The connectivity guide covers hosts, latency and session setup.

Section 03 · Build with AI

Build your LMAX strategy with AI

Pick an integration method, fork a TradingHost framework starter, and author your strategy in an AI IDE. LMAX FIX 4.4 is the canonical path; LMAX's Java and .NET first-party libraries wrap the FIX layer with idiomatic ergonomics. Share CFDs and crypto CFDs are not on LMAX Global.

  • LMAX FIX 4.4

    Direct FIX 4.4 session to LMAX Exchange. Separate Market Data and Order Execution sessions; the canonical institutional-style path.

    lmax.com/connectivity-guide

  • LMAX Java client library

    First-party Java client wrapping the FIX layer. Idiomatic Java types for orders, positions and market data.

  • LMAX .NET client library

    First-party .NET client wrapping the FIX layer. Idiomatic C# types and async ergonomics.

  • NautilusTrader or custom connector

    Community NautilusTrader LMAX adapter is available; or build your own connector against FIX 4.4 in any language with a FIX engine.

Framework support for LMAX products

LMAX FIX and the LMAX Java and .NET libraries span LMAX's FX surface. Indices and commodities depend on entity. Share CFDs and crypto CFDs are not part of LMAX Global's retail offering.

FrameworkFXIndicesCommoditiesCFDCrypto CFDs
LMAX FIX 4.4SupportedPartially supportedPartially supportedNot documented as supportedNot documented as supported
LMAX Java librarySupportedPartially supportedPartially supportedNot documented as supportedNot documented as supported
LMAX .NET librarySupportedPartially supportedPartially supportedNot documented as supportedNot documented as supported
NautilusTrader (community adapter)Partially supportedNot documented as supportedNot documented as supportedNot documented as supportedNot documented as supported

✓ confirmed support per docs.lmax.com. "entity-dependent" means availability depends on which LMAX entity holds the account. "no" indicates LMAX Global does not offer the product class.

TradingHost does not force a framework. It runs your project.

Author with AI

The framework starters above pair naturally with AI IDEs. The TradingHost MCP control surface closes the loop: AI tools can inspect deployments, review logs and manage the runtime alongside you, never the trade execution path.

Section 04 · Run on TradingHost

Run your code on TradingHost

LMAX Global provides the broker account and the LMAX Exchange central-limit-order-book matching engine. TradingHost provides the production environment where your LMAX-connected strategy runs.

Instead of running strategy code on a laptop, desktop machine, generic VPS or manually configured server, you deploy from GitHub into a TradingHost-managed container runtime.

You

  • Your repo contains your code.
  • Your deployment defines how it runs.
  • Your strategy connects to LMAX Exchange via FIX or the LMAX client library.

TradingHost

  • Keeps the runtime online.
  • Surfaces logs and health checks.
  • Region selection.
  • Controlled deployment surface.

Deployment flow

  1. STEP 01

    Connect GitHub

    Authorise TradingHost to access your GitHub account.

  2. STEP 02

    Link a repo or start from a framework

    Point TradingHost at your existing strategy repo, or fork a TradingHost LMAX FIX 4.4 or LMAX Java starter.

  3. STEP 03

    Deploy into a TradingHost container

    Pick a region (EU is the natural fit for LMAX Exchange, whose matching engine is in London), supply the environment values your strategy needs (LMAX FIX SenderCompID, Password, host and port; or LMAX library credentials), and deploy. TradingHost builds your container from the repo and runs your strategy on managed Kubernetes infrastructure.

  4. STEP 04

    Monitor logs and health

    Watch live logs, health and runtime state from the TradingHost dashboard. The same surface is reachable through MCP from any AI IDE, so Cursor, Claude Code or a CLI agent can read deployment state and manage the runtime alongside you.

  5. STEP 05

    Update and redeploy

    Push changes to your GitHub main branch and TradingHost redeploys automatically.

Deploy

Section 05 · Operational notes

Operational notes for LMAX Global

Things that bite you when you actually run an LMAX strategy in a containerised cloud runtime. Every claim is paraphrased from docs.lmax.com, the LMAX connectivity guide or the relevant regulator; the deployment-side guidance is from running these strategies on TradingHost.

  1. 01 · Exchange model

    LMAX matches on a real central-limit-order-book, not against a broker book

    LMAX Exchange is the LMAX Group's matching engine, operating as a central-limit-order-book FX venue rather than a market-maker broker. Orders match against resting liquidity from multiple counterparties. The implication for strategies: expect partial fills, queue-position effects, and behaviour closer to a venue than a retail broker. The Order Execution FIX session emits ExecutionReport messages for each fill against a single ClOrdID.

    SourceLMAX Exchange document library

  2. 02 · FIX session split

    Market Data and Order Execution are separate FIX sessions

    LMAX FIX 4.4 splits market data and order routing into two distinct FIX sessions, each with its own SenderCompID, Password and sequence-number tracking. A complete strategy maintains both connections simultaneously and handles their lifecycles independently. The Market Data session is heavily throughput-dominated; the Order Execution session is latency-sensitive. Connection drops, sequence resets and reconnects must be handled per session.

    SourceLMAX docs portal

  3. 03 · Account minimums

    LMAX Global account minimums are higher than retail-shop minimums

    LMAX Global accounts carry minimum deposit and balance thresholds higher than typical retail brokers; commonly cited figures are $10,000 to $25,000 across entities. This is consistent with LMAX's positioning as an institutional-tier venue rather than a retail-shop alternative. Confirm the current minimum with LMAX directly during onboarding, because thresholds vary by entity and product tier.

    SourceLMAX connectivity guide

  4. 04 · Region proximity

    LMAX Exchange's matching engine is in London; latency benefits accrue to EU-region runtimes

    LMAX Exchange's matching engine is in London. Of the two TradingHost regions, EU is the one geographically closest to it, which is what matters for FIX round-trip times. For LMAX-specific strategies, EU region selection is a meaningful latency advantage. The US-East region is the fit for the US arm of LMAX Exchange, where applicable.

    SourceLMAX connectivity guide

  5. 05 · LMAX Digital separation

    LMAX Digital is a separate LMAX Group crypto venue, covered on the crypto cluster

    LMAX Digital is the LMAX Group's institutional crypto trading venue. It runs on the same underlying exchange technology but trades different products (BTC, ETH, etc.) and is a separate FIX endpoint with separate credentials. LMAX Global covers FX and CFDs; LMAX Digital covers crypto. The TradingHost crypto cluster ships a dedicated /brokers/crypto/lmax-digital/ page; this page covers LMAX Global only.

    SourceLMAX Group entities and venues

  6. 06 · Trade reporting

    EMIR, MiFID II and per-entity reporting is LMAX's responsibility

    LMAX Limited reports under FCA / MiFID II / EMIR rules as a UK-authorised investment firm. LMAX Global EU Limited reports under CySEC / MiFID II / EMIR rules. LMAX Group Markets Pte. Ltd. reports under MAS rules. Other entities report under their respective regulators. TradingHost does not perform regulatory trade reporting on your behalf. The strategy code you run on TradingHost is your own algorithmic activity; reporting attaches to the LMAX entity holding the account.

    SourceFCA register: LMAX Limited 509778

Section 06 · Built for

Built for

TradingHost LMAX Global runtimes are best suited to:

  • Developers building strategies in AI IDEs (Cursor, Claude Code)
  • Latency-sensitive FX strategy developers
  • Java and .NET first-party-library users
  • Exchange-model (CLOB) systematic traders
  • Teams moving from MetaTrader and VPS hosting to EU-region container deployment

Connecting GitHub and creating your first strategy is free.

Section 08 · FAQ

FAQ

No. TradingHost is independent and is not affiliated with LMAX Group or any LMAX entity, and is separately not affiliated with LMAX Digital, the LMAX Group crypto venue covered on the /brokers/crypto/ cluster.

No. TradingHost is not a broker, not an exchange, and not a registered investment firm. TradingHost is a cloud runtime that runs your strategy code. The broker relationship, the account, the leverage, the execution and the regulatory protections all live with the LMAX entity that holds your account.

No. Your FIX client (or LMAX Java/.NET library) connects to LMAX Exchange and sends instructions according to your own logic. TradingHost provides the runtime where that code runs.

No. LMAX FIX and library access is provided by LMAX after account onboarding and funding. You are responsible for your LMAX account, FIX credentials and compliance with LMAX's terms.

LMAX Group operates both: LMAX Exchange is a central-limit-order-book matching engine (the exchange), and LMAX Limited (and other entities) operate as brokers routing client orders to that exchange. For retail customers it functions like a broker relationship, but order matching happens against a real exchange book rather than against a market-maker broker book. The implication is exchange-style execution behaviour (partial fills, queue position).

LMAX Global accounts carry minimum deposit and balance thresholds higher than typical retail brokers (commonly cited as $10,000 to $25,000 depending on entity and product tier). Confirm the current minimum with LMAX directly during onboarding. This is consistent with LMAX's institutional-tier positioning.

Yes. LMAX FIX 4.4 is standard FIX, so any Python FIX engine (quickfix-python, simplefix, etc.) works. The first-party LMAX libraries are Java and .NET; Python strategies reach LMAX via the FIX layer directly.

Yes. TradingHost supports any language that can run inside a container. LMAX FIX is standard FIX 4.4, so any FIX engine in any language works. LMAX additionally publishes first-party Java and .NET client libraries.

Open an LMAX Global account, complete onboarding and fund to the entity minimum. Request FIX credentials and Market Data + Order Execution session details. Fork a TradingHost LMAX FIX 4.4 starter, or connect your own GitHub strategy repo. Linking a GitHub repo and creating a strategy is free; runtime plans are listed on the pricing page.

Yes. Leverage is set by the LMAX entity. LMAX Limited (UK FCA) and LMAX Global EU Limited (CySEC) apply ESMA-aligned caps. LMAX Group Markets Pte. Ltd. (Singapore, MAS) and other entities follow their respective rules. The API surface is the same across entities.

In your GitHub-controlled secrets workflow. TradingHost reads the SenderCompID, Password and host details for both the Market Data and Order Execution sessions at runtime through GitHub repository secrets, environment secrets or your own approved secret-management process.

Yes. TradingHost supports MCP-based control for AI IDEs including Cursor, Claude Code, GitHub Copilot and CLI-based AI agents. AI tools can inspect deployments, review logs, restart strategies and manage runtime workflows. MCP is a control and observability surface, not the trade execution path.

No. EMIR and MiFID II trade reporting is the broker's responsibility. LMAX Limited reports under FCA / MiFID II / EMIR rules. LMAX Global EU Limited reports under CySEC / MiFID II / EMIR rules. LMAX Group Markets Pte. Ltd. reports under MAS rules. Other entities report under their respective regulators. TradingHost runs your code; the LMAX entity holding the account handles regulatory reporting.

No. TradingHost is focused on production runtime and deployment. Backtesting belongs in your research stack, in a framework like NautilusTrader, or in AlgoBuilder.