Run your strategy from US-East, inside the fabric Wall Street uses.
US-East is TradingHost’s US region. Runtimes deploy into a low-latency financial data centre on the East Coast, the cross-connect hub that ties together NYSE, Nasdaq, IEX, the OPRA options feed, the major US brokers and the US crypto venues that anchor the dollar trading day.
Pick US-East at deploy time when your strategy reads US market data, talks to a US broker, or trades US equities, options, futures or crypto. Your runtime sits in the fabric the broker you connect to already uses. The trading relationship, the credentials and the strategy code stay yours.
What sits nearby
- Low-latency data centre
- Eastern Time
- NYSE / Nasdaq / IEX
- OPRA participants
- CME connectivity
- IBKR / Alpaca / Tradier
- Coinbase / Gemini / EDX
- USD-pair venues
Section 01 · Fit
When US-East is the right region
US-East earns its place when your strategy depends on a US venue, a US broker or US market data. Most US capital-markets infrastructure that matters to a strategy is either in the same campus or one cross-connect away.
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 US-East if…
- US equities on NYSE, Nasdaq, IEX, MEMX, NYSE Arca, NYSE American, BX, BZX, EDGA / EDGX and major ATSes
- US options through OPRA-feed venues: NYSE Amex Options, BOX, MIAX, Nasdaq PHLX, ISE, CBOE, Cboe BZX Options
- US futures via CME Group, ICE Futures US, NYMEX and COMEX, reachable over standard low-latency paths
- US-regulated brokers: Interactive Brokers, Alpaca, Tradier, Schwab / TD Ameritrade, E*TRADE, tastytrade
- US-regulated crypto venues: Coinbase Prime, Gemini, Kraken US, Bullish, EDX Markets
- USD-pair FX through Hotspot FX (Cboe FX), EBS Americas and Currenex
- Strategies that consume the US SIP (CTS / CQS / UTP) or direct exchange feeds
Strategies that don’t
Pick a different region if…
- UK or European equities, MTFs and FX in the European session. Pick EU instead
- Asian-session strategies on JPX, HKEX, SGX, KRX or ASX. 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 East Coast cross-connect hub.
The US-East region runs inside a low-latency financial data centre on the US East Coast, chosen for broker and exchange proximity rather than for its address. Most US brokers, prime brokers, ATSes, dark pools, market data vendors and US crypto venues maintain a footprint in the same fabric.
The matching engines themselves do not live in the building. NYSE Pillar runs from Mahwah, Nasdaq from Carteret, Cboe BZX and IEX from elsewhere in northern New Jersey, and CME from Aurora, Illinois. What the region does is sit in the middle of all of them. From a runtime here, the path to each major matching engine is short and predictable — a cross-connect or short-haul fibre to the New Jersey engines, standard low-latency long-haul to Aurora.
It is a financial data centre rather than a general-purpose one, which is why every major US broker keeps a presence there. When you deploy a TradingHost runtime in US-East, you are deploying into the network fabric the rest of US capital markets already shares.
Low latency · US East Coast
US East Coast 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, SOC 2, PCI-DSS (operator-attested)
Section 03 · Venues nearby
What you can reach from US-East.
"Reach" here means a short, predictable network path from a runtime in the US-East region. Most rows are campus-resident, meaning the broker, ATS or data feed terminates in the same fabric. Equity matching engines live in their own facilities and are reached over cross-connects, short-haul fibre or low-latency long-haul. None of it rides the public internet across the country.
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.
- US equity venues
- NYSE Pillar (Mahwah), Nasdaq (Carteret), IEX, Cboe BZX / BYX / EDGA / EDGX, MEMX, MIAX Pearl Equities, NYSE American, NYSE Arca, Nasdaq BX and PSX, plus the major ATSes and dark pools.
- US options venues
- NYSE Amex Options, NYSE Arca Options, BOX, MIAX, MIAX Pearl, MIAX Emerald, Nasdaq PHLX, ISE, Nasdaq Options, CBOE, Cboe BZX Options, Cboe EDGX Options.
- US futures
- CME Group (CL, NG, ES, NQ, YM, ZN, ZB) reachable over standard low-latency long-haul to Aurora, IL. ICE Futures US, NYMEX and COMEX cross-connectable on the East Coast.
- US-regulated crypto venues
- Coinbase Prime, Gemini, Kraken US, Bullish, EDX Markets, BitGo, plus CME crypto futures for institutional flow. Many maintain primary US infrastructure inside or directly cross-connected to the region’s campus.
- US FX ECNs
- Hotspot FX (Cboe FX), EBS Americas (CME), Currenex, FXSpotStream Americas, plus ECN-style flow through prime brokers resident on the same campus.
- US brokers
- Interactive Brokers, Alpaca, Tradier, Schwab / TD Ameritrade, E*TRADE, tastytrade, Lime Trading, Webull, Tradeweb. Most maintain primary US connectivity in or via the same campus.
- US market data feeds
- SIP feeds (CTS, CQS, UTP), OPRA, NYSE OpenBook, Nasdaq TotalView, MEMOIR, plus consolidated feeds from Polygon, Databento, ICE Data Services and Bloomberg.
Section 04 · At a glance
The US-East region in eleven lines
The full shape of the US-East region, scannable. Each row points to the section or page that owns the underlying detail.
- Region code
- us-east
- Time zone
- ET · UTC-5 / UTC-4 (DST)
- Markets in session
- NYSE, Nasdaq, IEX, US options, CME futures (extended hours)
- Power redundancy
- 2N (operator-attested)
- Cooling redundancy
- N+1 (operator-attested)
- Connectivity
- Cross-connects and short-haul fibre to East Coast 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 US-East 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 US-East at deploy time
Open the deployment, select US-East 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 = "us-east" 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("us-east") 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 "US-East" means, and what it doesn’t
What "US-East" means
The US-East region places your runtime inside a low-latency financial data centre on the US East Coast, sharing a fabric with the brokers, ATSes, OPRA participants and US crypto venues that anchor the dollar trading day. Network paths from your runtime to campus-resident counterparties are short and predictable.
"US-East" does not mean a Manhattan data centre, the NYSE Pillar matching engine in Mahwah, the Nasdaq matching engine in Carteret, or the CME data centre in Aurora, Illinois. 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 NYSE, Nasdaq, IEX, CME or any other US venue. Latency depends on the venue’s infrastructure, the broker’s routing, your code and current network conditions.
- TradingHost does not place runtimes inside Mahwah, Carteret, Aurora or any specific exchange-issued cabinet. "US-East" means a runtime inside a low-latency East Coast data centre, not adjacent racks to a named matching engine.
- TradingHost does not provide kernel-bypass networking, FPGA-accelerated NICs, microwave links or millimetre-wave routes to the exchange facilities. If your strategy requires HFT-grade physical proximity, a colocation provider is the right tool.
- 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 SEC-registered, FINRA-registered or any other US-regulated permission on your behalf. The 99.99% infrastructure SLA covers the facility, not your trading activity.
FAQ
Frequently asked questions
Inside a low-latency financial data centre on the US East Coast, chosen for proximity to the major US brokers, ATSes, market data feeds and US-regulated crypto venues. What the region gives you is that network fabric, not a specific postcode.
No. NYSE Pillar runs from Mahwah, Nasdaq from Carteret, Cboe BZX and IEX from elsewhere in northern New Jersey, and CME from Aurora, Illinois. The region is the cross-connect hub that sits in the middle of all of them. From a runtime here, the path to each major matching engine is a short cross-connect or short-haul fibre hop, not a public-internet round trip.
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 to the exchange facilities, you want a colocation provider rather than a managed cloud runtime.
TradingHost does not publish or guarantee specific round-trip times. The path from a US-East runtime to campus-resident brokers is short, the path to the New Jersey matching engines is a cross-connect or short-haul hop, and the path to CME in Aurora is standard low-latency long-haul. The actual numbers depend 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 the US East Coast to European venues crosses the Atlantic. Strategies that read UK or European market data or talk to UK-regulated brokers belong in the EU region.
Yes. Region selection is a deploy-time setting. Change region = "us-east" to region = "eu" 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. SEC, FINRA, MSRB and any other US-regulated permission remains the responsibility of you and your broker. The data centre certifications belong to its operator and cover the facility, not your trading activity.
Yes, with the usual caveats. Your runtime can receive any feed your broker, exchange or data vendor is willing to deliver to it. TradingHost does not bundle a market data subscription. You arrange the feed with your broker or vendor; the runtime receives the data over the network paths the region already provides.
Yes. Customer runtimes are isolated from other customer runtimes regardless of region. A US-East 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.
Deploy your first strategy in US-East
Connect your GitHub repo, set region = "us-east", and deploy. The runtime is live in the network fabric the brokers you connect to already share.