AI-native runtime for LMAX Digital trading strategies

No. Your strategy code connects to LMAX Digital and sends instructions according to your own logic, account permissions and integration method. TradingHost provides the runtime where that code runs.

No. LMAX Digital API access is provided by LMAX. Your firm is responsible for the LMAX account, API permissions, credentials and compliance with LMAX’s terms.

No. TradingHost is the cloud runtime where your strategy code runs. We do not provide signals, AI prediction models or pre-built bots. With TradingHost your firm writes or generates the strategy yourselves (often with Cursor or Claude Code), keeps it in GitHub as your code, and uses TradingHost to run it in production. 3Commas, Cryptohopper and similar products own the strategy logic; TradingHost runs your strategy.

AWS and DigitalOcean give you raw compute. You handle OS updates, container orchestration, log shipping, secret rotation, region failover and uptime monitoring yourself. TradingHost gives you a managed runtime purpose-built for trading strategies: GitHub-native deployment, MCP-driven control from AI IDEs, log and health surfaces out of the box. If you want to operate the infrastructure yourself, AWS works. If you want the runtime as a managed service, TradingHost is the shorter path.

Yes. TradingHost runs Python strategies; pair them with a QuickFIX-compatible adapter for FIX 4.4 or with the REST/WebSocket APIs. Java and C++ are common at institutional desks because of the mature FIX engine ecosystems and the latency profile.

Yes. TradingHost supports any language that can run inside a container. Java and C++ are particularly common at LMAX-bound institutional desks because of mature FIX engine ecosystems.

CCXT does not list LMAX Digital among supported exchanges, and neither do Freqtrade or Hummingbot. LMAX Digital is institutional and FIX-first; integrations target FIX 4.4 (with ITCH for market data), FIX 4.2 (legacy sessions), or the native REST and WebSocket APIs directly. See the Build with AI section above for the supported integration methods.

Yes. LMAX Digital launched BTC and ETH perpetual futures in Q3 2025 (cash-settled). Approved tiers can trade with up to 100x leverage; margin and liquidation parameters are tier-specific and enforced at the exchange. Your strategy code authenticates against the same FIX 4.4 or REST surface used for spot, and TradingHost runs the container regardless of whether the strategy is spot, perp or both.

LMAX onboarding is institutional in pace; once your firm has an LMAX account with FIX or REST credentials provisioned, point a TradingHost runtime at your strategy repo. The typical starter pairs a QuickFIX-compatible 4.4 adapter and an ITCH market-data consumer with your strategy logic. Linking a GitHub repo and creating a strategy is free; runtime plans are listed on the pricing page.

In your firm's GitHub-controlled secrets workflow. TradingHost reads them at runtime through GitHub repository secrets, environment secrets or your firm's approved secret-management process. TradingHost does not need custody of your FIX session credentials or REST API keys. See platform secrets for the full handling model.

No. Strategies should never need withdrawal permissions. Use scoped trading-only credentials and keep withdrawal capabilities on a separate manually-managed credential set, off the runtime entirely. Institutional onboarding typically issues separate operational and trading credentials by default.

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. See the MCP control surface for the full picture.

Both. The MCP control surface works equally well from CLI-based agents (Claude Code CLI, custom MCP clients, scripted MCP calls) and from inside an IDE. The GitHub-native deployment loop also works without any AI tooling: a regular git push to your main branch triggers a redeploy.

The runtime detects the crash and exposes the relevant logs and health information. Where supported, the affected strategy can be restarted without disrupting other strategies running in the same container. Your strategy code is still responsible for safe error handling, duplicate-order protection and risk controls. FIX sessions in particular need clean logout/relogon sequencing to avoid resend storms after a restart. See observability for the logs and health surface.

Not without co-location. LMAX Digital publishes sub-10ms ack latencies for co-located participants; that figure is conditioned on physical proximity to LMAX’s matching engine in London. The TradingHost EU region is a strong base for low-latency LMAX strategies, but a sub-10ms target requires a separate co-location arrangement directly with LMAX. Plan strategy latency budgets against the actual cloud-to-LMAX path, not the headline co-located number. See the Operational notes section above for the full guidance.

TradingHost runs in the EU and US-East regions. For LMAX Digital, the EU region is the natural choice because LMAX's matching engine is in London. See the regions page for routing and proximity details.

No. TradingHost is focused on production runtime and deployment. Backtesting belongs in your firm’s research stack, framework or AlgoBuilder.