Run your strategy from the EU region, behind the same front door as the venues you trade.
EU is TradingHost’s UK and European region. Runtimes deploy into a low-latency financial data centre in Europe, the network fabric that the LSE, the major European MTFs and the FX venues every European trader already routes through are reached across.
Pick EU at deploy time when your strategy reads UK or European market data, talks to a UK or EU-regulated broker, or lives in the European trading session. Your runtime sits in the fabric the venue you connect to already uses. The trading relationship, the credentials and the strategy code stay yours.
What sits nearby
- Low-latency data centre
- GMT / BST
- LSE proximity
- Cboe Europe
- Aquis Exchange
- LMAX Digital
- IBKR UK / Saxo / IG / CMC
- GBP, EUR pairs
Section 01 · Fit
When EU is the right region
EU earns its place when your strategy depends on a venue, broker or data feed that sits inside the European trading day. The network and data centre operators around the runtime are tuned for finance, and the cross-connects that matter for European markets are short.
Below is a working filter. If your workflow appears in the green list, this region is a sensible default. If it appears in the red list, you want a different region.
Strategies that fit
Pick EU if…
- UK equities on LSE, Cboe Europe BXE/CXE/DXE, Aquis Exchange or Turquoise
- European MTFs and continental venues reachable over short-haul fibre
- FX strategies that live in the European trading session
- UK-regulated brokers and CFD venues (IBKR UK, IG, Saxo, CMC, Pepperstone, OANDA)
- LMAX Digital, GFO-X and other UK-regulated institutional crypto venues
- GBP, EUR and CHF currency pairs through European ECNs
- ETFs and structured products listed on LSE or pan-European MTFs
Strategies that don’t
Pick a different region if…
- US equities, US options, US futures or any OPRA-feed strategy. Pick US-East instead
- Asian-session strategies on JPX, HKEX, SGX or KRX. Wait for an APAC region
- Strategies that need physical cabinet adjacency to a specific matching engine
Section 02 · The data centre
Inside a low-latency European financial data centre.
The EU region runs inside a low-latency financial data centre in Europe, chosen for broker and exchange proximity rather than for its address. Hundreds of trading firms, banks, brokers, market data vendors and venue operators terminate their networks inside it.
That is what proximity buys. The European venues your strategy talks to — the LSE, Cboe Europe, Aquis, Turquoise and a long list of MTFs and FX ECNs — are reached over a cross-connect or a short-haul fibre hop rather than a public-internet round trip.
It is a financial data centre rather than a general-purpose one, which is why most major UK and European brokers also keep a presence there. When you deploy a TradingHost runtime in the EU region, you are deploying into the network fabric that the rest of the industry already shares.
Low latency · Europe
European financial data centre
- Power
- 2N redundancy, dual-feed UPS
- Cooling
- N+1 chilled water
- Networks
- Direct paths to the major brokers and venues
- Compliance
- ISO 27001, ISO 50001, PCI-DSS (operator-attested)
Section 03 · Venues nearby
What you can reach from the EU region.
"Reach" here means a short, predictable network path from a runtime in the EU region. Most rows are campus-resident, meaning the venue’s own infrastructure terminates in the same fabric. A few are reached over short-haul fibre to another European metro. None of them ride the public internet across the Atlantic.
The list is descriptive, not contractual. TradingHost does not promise specific round-trip times to specific venues. What it promises is that the runtime sits in the right building.
- UK and European equity venues
- LSE matching engine, Cboe Europe BXE / CXE / DXE, Aquis Exchange, Turquoise, Equiduct, Tradegate. SIX Swiss Exchange and BME (Madrid) reachable over short-haul fibre.
- European derivatives
- ICE Futures Europe, LME, Cboe Europe Derivatives. Eurex (Frankfurt) reachable over standard low-latency long-haul.
- FX ECNs and aggregators
- EBS Market, Refinitiv FXall, Refinitiv Matching, 360T, ParFX, FXSpotStream, Hotspot FX (Cboe FX), Currenex, LMAX Exchange.
- UK-regulated crypto venues
- LMAX Digital, GFO-X, Bitstamp UK, Kraken UK and other campus-resident or directly cross-connected crypto venues.
- UK and EU brokers
- Interactive Brokers UK, IG, Saxo Bank, CMC Markets, Pepperstone UK, OANDA, Plus500. Most maintain their primary EMEA routing on the same campus or one cross-connect away.
- Market data feeds
- LSEG / Refinitiv direct feeds, Bloomberg B-PIPE, ICE Data Services, Cboe Europe market data and the major SIP-equivalent consolidated feeds for European markets.
Section 04 · At a glance
The EU region in eleven lines
The full shape of the EU region, scannable. Each row points to the section or page that owns the underlying detail.
- Region code
- eu
- Time zone
- GMT / BST · UTC+0 / UTC+1
- Markets in session
- LSE, Cboe Europe, Aquis, Euronext, European session FX, EU MTFs
- Power redundancy
- 2N (operator-attested)
- Cooling redundancy
- N+1 (operator-attested)
- Connectivity
- Cross-connects and short-haul fibre to European venues
- Cross-region traffic
- Standard internet routing to other TradingHost regions
- Supported runtimes
- All TradingHost-supported languages and frameworks
- Strategies per runtime
- One or many, depending on deployment configuration
- Deployment
- GitHub-driven, push to deploy
Section 05 · Deployment
Choose EU at deploy time
Region selection happens at deploy time, not at sign-up. There is one knob and three control surfaces that turn it. Pick whichever one matches how you already work; they all write the same value into the same deployment record.
Dashboard
Pick EU at deploy time
Open the deployment, select EU as the runtime region, save. The strategy moves on the next deploy. No tickets, no migration ceremony.
tradinghost.toml
Pin the region in your repo
Set region = "eu" inside your tradinghost.toml. The deployment flow reads the value, your runtime is created in the region, and the next push to the deploy branch re-deploys to the same region.
MCP
Drive it from your editor
Use the TradingHost MCP server in Claude, Cursor or any MCP-aware client. Issue deploy.region.set("eu") and the runtime is rescheduled into the region on the next lifecycle event.
[deployment]image = "python:3.12-slim"entrypoint = "python -m strategy.main" [runtime]restart = "always"Section 06 · Honesty
What "EU" means, and what it doesn’t
What "EU" means
The EU region places your runtime inside a low-latency financial data centre in Europe, sharing a network fabric with the European venues, brokers and market data vendors your strategy talks to. Network paths from your runtime to campus-resident venues are short and predictable.
"EU" does not name a city, a building or a cabinet, and it does not mean adjacency to a matching engine. The 99.99% infrastructure SLA covers the facility, not the venues you connect to from it. Full terms in the Terms and Conditions.
No daylight between the marketing and the product.
- TradingHost does not promise a specific round-trip time to a specific broker, exchange or market data feed. Latency depends on the venue’s infrastructure, the broker’s routing, your code and current network conditions.
- TradingHost does not place runtimes inside a specific exchange-issued cabinet. "EU" means a runtime inside a low-latency financial data centre, not adjacent racks to a named matching engine.
- TradingHost does not provide kernel-bypass networking, FPGA-accelerated NICs or microwave links. If your strategy requires HFT-grade physical proximity, a colocation provider is the right tool, not a managed cloud runtime.
- TradingHost does not act as your broker, your exchange or your market data vendor. The strategy connects directly using the credentials you supply.
- TradingHost does not provide MiFID II reporting, FCA-authorised market connectivity or any other regulated permission on your behalf.
FAQ
Frequently asked questions
Inside a low-latency financial data centre in Europe, chosen for proximity to the venues, brokers and data vendors that anchor the European session. What the region gives you is that network fabric, not a specific postcode.
No. TradingHost is a managed cloud runtime that places your strategy inside the region’s campus. It is not a colocation product and does not provide cabinet adjacency to a specific matching engine. If your strategy requires HFT-grade physical proximity, kernel-bypass networking or microwave links, you want a colocation provider rather than a managed cloud runtime.
TradingHost does not publish or guarantee specific round-trip times. The path from an EU runtime to a campus-resident venue is short, but the actual number depends on the venue’s own infrastructure, the broker’s routing, your code and current network conditions.
You can, but you should not. The path from Europe to US matching engines crosses the Atlantic. Strategies that read US market data or talk to US brokers belong in the US-East region.
Yes. Region selection is a deploy-time setting. Change region = "eu" to region = "us-east" in your tradinghost.toml (or pick the new region in the dashboard) and the next deploy reschedules the runtime there.
No. TradingHost provides infrastructure inside a data-centre campus. FCA permissions, MiFID II reporting and any regulated market access remain the responsibility of you and your broker. The data centre certifications belong to its operator and cover the facility, not your trading activity.
Yes. Customer runtimes are isolated from other customer runtimes regardless of region. An EU runtime never shares a process, a network namespace or a state directory with a runtime in another region or another customer.
The data-centre operator publishes maintenance windows at the campus level. TradingHost schedules its own runtime maintenance to minimise overlap and surfaces affected runtimes through deployment status and runtime logs. Where supported, runtimes are rescheduled onto unaffected capacity within the same region.
Yes, provided the GitHub-driven deploy flow can reach the repo. Region selection is independent of the source-control side: EU accepts deployments from cloud GitHub, GitHub Enterprise Cloud and self-hosted GitHub Enterprise Server, given network access from your CI to the TradingHost MCP control surface.
Pricing is published on the pricing page and applies the same way across supported regions at general availability.
Deploy your first strategy in the EU region
Connect your GitHub repo, set region = "eu", and deploy. The runtime is live in the network fabric the venues you trade already share.