The TradingHost platform
A cloud runtime and infrastructure layer for automated trading. Container runtime, deploy from GitHub, run in broker-proximate regions, controlled from your AI IDE.
TradingHost is the production layer around your strategy code. The platform handles the runtime container, deployment workflow, logs, health signals, regions, secrets and MCP control surface. Your repo stays the source of truth.
Capabilities
The platform, layer by layer
Each capability has its own landing page covering what it does, how it fits the runtime model and which strategies it suits.
Runtime
Always-on containers built for the trading loop. Sub-millisecond strategy execution, broker-API connections, market-data streams and message queues run side by side under one runtime.
Infrastructure
Dedicated hardware in financial-grade data centres. Managed Kubernetes orchestration on bare metal, picked for jitter, network proximity and predictable performance under load.
Deployments
Deploy from GitHub on every push. Atomic strategy-level updates roll forward without disturbing sibling strategies in the same runtime. Branch-based environments included.
MCP
Native Model Context Protocol surface for Cursor, Claude Code and Codex. Deploy, inspect logs, manage secrets and roll strategies from inside your editor.
Regions
EU and US-East regions placed for broker and exchange proximity. Pick the region closest to your venue so the network round trip stops being the bottleneck.
Observability
Runtime output from the running container, STDOUT and STDERR, surfaced from the control plane. See whether a deploy started, whether the broker connection succeeded and what your strategy reported, without a remote desktop session.
Secrets
Encrypted broker keys, exchange API tokens and environment variables. Secrets are injected at runtime; nothing sensitive sits in your GitHub repo or commit history.
Production runtime, not a strategy builder
TradingHost runs your strategy code. It does not write it, backtest it for you or custody venue credentials on your behalf. Whatever you can put in a container in any language can run on the platform.
Your repo owns the strategy. TradingHost owns the production environment around it.