Run your strategy next to the venues it trades.
TradingHost runtimes deploy into low-latency financial data centres, the network fabric the venues, brokers and market data vendors already share.
Two regions today: EU and US-East, each placed for broker and exchange proximity. Pick whichever sits closest to the venue your strategy depends on. Region selection happens at deploy time, not at sign-up.
Section 01 · Available regions
Two regions, both placed for proximity
Both regions sit in low-latency financial data centres chosen for broker and exchange proximity. The two pages below own the detail: the data centre, the venues you can reach, the spec sheet, the boundary.
Section 02 · How to choose
How to pick a region
Region selection is one decision. Pick the region that sits closest to the venue your strategy depends on, not the region nearest your office. A US-based trader whose strategy reads LSE feeds belongs in the EU region. A European trader whose strategy talks to Alpaca belongs in US-East.
If the strategy spans both regions, say a US/EU pairs trade, the cleanest pattern is two runtimes, one per region, each handling the leg whose venue is nearest its own data centre. Cross-region traffic between TradingHost runtimes is standard internet routing, not a fast lane.
Region is a deploy-time setting. Change region in your tradinghost.toml or in the dashboard and the next deploy reschedules the runtime in the new region. There is no account-level region lock, no migration ticket and no data to copy.
FAQ
Frequently asked questions
Region selection is only valuable if the region puts you closer to the venue you trade. EU and US-East between them cover the LSE, the major European MTFs, the FX ECNs that anchor the European session, NYSE, Nasdaq, IEX, OPRA, the major US brokers and the US-regulated crypto venues. Adding regions that nobody actually trades from would be marketing, not infrastructure.
Pick the region whose data centre sits closest to the venue or broker your strategy depends on. UK and European workflows belong in the EU region. US equities, options, futures and crypto belong in US-East. If your strategy genuinely spans both regions, deploy two runtimes and split the workload by venue.
Yes. Region selection is a deploy-time setting, not an account-level setting. Change region in your tradinghost.toml or in the dashboard and the next deploy reschedules the runtime in the new region.
TradingHost adds regions when there is a clear cluster of customers whose strategies need them. APAC region demand is on the public roadmap. Until it launches, strategies that read JPX, HKEX, SGX or KRX market data are best run on a colocation provider rather than on TradingHost.
Pick a region and deploy
Connect your GitHub repo, pick the region whose data centre sits closest to your venues, and deploy your first strategy. Region is a single line in tradinghost.toml.