Read time … min

Deploy CCXT-Based Trading Strategies on TradingHost

Run open-source CCXT trading projects from GitHub on always-on TradingHost runtimes.

CCXT connects your strategy to over 100 cryptocurrency exchanges through one consistent interface. TradingHost gives that strategy a production runtime.

By the TradingHost engineering team
  • GitHub-native deployment
  • 100+ exchanges via one interface
  • Six supported languages
  • REST and WebSocket included
  • Always-on runtime
  • Region proximity to exchanges
  • Encrypted API keys
  • Streaming logs
  • MCP-ready

Introduction

New to CCXT?

If you have written any code that talks to a cryptocurrency exchange, you have probably noticed that every exchange does things slightly differently. Binance has its own API. Bybit has another. OKX has a third. Symbols are named differently. Errors are returned differently. Order types vary.

CCXT solves this. It is open-source software, free to use, MIT licensed, that gives your code one consistent way to talk to any of 100+ exchanges. You write your strategy once and it can connect to Binance, Bybit, OKX, Coinbase, Kraken, and 100+ others without rewriting the integration each time.

CCXT does not contain trading strategies. It is the connectivity layer. You bring the strategy. CCXT handles the conversation with the exchange.

TradingHost is where that strategy runs in production. Instead of leaving your strategy on a laptop or a generic VPS, you deploy your CCXT-based code to a TradingHost cloud runtime that stays online, manages your API keys securely, and streams logs back to you.

Section 01 · At a glance

At a glance

What CCXT is
Open-source exchange connectivity software, MIT licensed
Maintained by
The CCXT project on GitHub
Exchanges supported
100+ centralised and decentralised
Languages
JavaScript, TypeScript, Python, C#, PHP, Go
API support
REST and WebSocket (WebSocket merged into the free package, October 2022)
Deployment source
GitHub
TradingHost role
Runtime, deployment, logs, secrets, region selection
CCXT role
Exchange API connectivity
Affiliation
TradingHost is independent and is not affiliated with CCXT
Best for
Multi-exchange crypto strategies, arbitrage, market data workers, portfolio automation

Section 02 · Where CCXT fits

How CCXT fits into the trading stack

CCXT is exchange-connectivity infrastructure. Several major open-source trading frameworks use it under the hood, including Freqtrade, Hummingbot, and OctoBot. CCXT is the foundational layer; those frameworks are full trading systems built on top of it.

That means you can deploy CCXT in two ways on TradingHost:

  • Path 01

    Direct

    Write your own strategy code in any of the six CCXT-supported languages. Your code calls CCXT directly to fetch market data, place orders, and manage positions.

  • Path 02

    Through a framework

    Use Freqtrade, Hummingbot, Jesse, or another framework that uses CCXT internally. You configure the framework, the framework uses CCXT to talk to exchanges, and TradingHost runs the whole thing.

Both paths work the same way from TradingHost’s perspective. You bring a GitHub repo. We run it.

You
Your strategy code owns the trading logic.
CCXT
CCXT standardises the exchange API.
Exchange
Your exchange account receives the orders.
TradingHost
Runs the strategy process and streams logs.

Section 03 · Why on TradingHost

Why deploy CCXT on TradingHost

A CCXT-based strategy needs to run continuously to be useful for live trading. Running on a laptop, desktop, or generic VPS introduces operational drag, including process supervision, restarts, dependency management, log scattering, and manual deployment.

TradingHost gives a CCXT strategy a production-oriented runtime designed for long-running trading processes.

What you get

  • GitHub-native deployment
  • Always-on container runtime
  • Multi-strategy support inside one runtime
  • Encrypted API key storage
  • Region selection close to your exchange
  • Streaming logs and basic health
  • Strategy-level start, stop, restart, inspect
  • Update one strategy without restarting the runtime
  • MCP-compatible AI IDE workflows

What you keep

  • Full control over your strategy code
  • Direct ownership of your exchange accounts and API permissions
  • Your choice of language across the six CCXT supports

Section 04 · Supported exchanges

Supported exchanges

Every TradingHost broker page is a place where you can deploy a CCXT-based strategy. The same deployment pattern, your CCXT repo plus your exchange API keys plus a TradingHost runtime, works for every one of the 100+ exchanges CCXT supports.

Five popular pairings are linked below. For the full directory of 100+ CCXT-supported crypto exchanges, see /brokers/crypto/.

ExchangeCCXT support
Binance/brokers/crypto/binance/Spot, USDT-M, COIN-M, optionsBybit/brokers/crypto/bybit/Spot, derivativesOKX/brokers/crypto/okx/Spot, futures, optionsCoinbase/brokers/crypto/coinbase/SpotKraken/brokers/crypto/kraken/Spot, futures
  • CCXT
  • your exchange
  • TradingHost runtime

The same pairing works for every CCXT-supported exchange. Hyperliquid, KuCoin, Bitget, MEXC, Gate.io, dYdX and 100+ others all run the same CCXT-on-TradingHost pattern. Find your venue in the full crypto broker directory.

View all 100+ crypto exchanges

Section 05 · Deployment flow

How a CCXT deployment works

A CCXT-based strategy on TradingHost follows the same deployment pattern as any GitHub-based project.

  1. STEP 01

    Connect or create a repo

    Sign in with GitHub and connect an existing CCXT-based repository, or create one from a TradingHost CCXT template.

  2. STEP 02

    Define your runtime entry point

    TradingHost reads your project’s runtime configuration to know how to build and start your strategy.

  3. STEP 03

    Add encrypted exchange API keys

    Add your exchange API keys as TradingHost secrets. They are encrypted and injected into your runtime at start.

    /platform/secrets/
  4. STEP 04

    Choose a region

    Select a region close to your exchange’s matching engine. AWS Tokyo for Binance Spot, AWS Frankfurt for many EU-domiciled exchanges.

    /platform/regions/
  5. STEP 05

    Deploy

    TradingHost starts your strategy in a managed container. Logs stream back to the dashboard.

    /platform/observability/
Deploy →

Section 06 · REST and WebSocket

REST and WebSocket

CCXT supports both REST polling and WebSocket streaming in the same package. The WebSocket functionality, formerly the commercial CCXT Pro product, was merged into the free CCXT package in October 2022 (CCXT version 1.95+).

In plain terms, REST means your code asks the exchange "what's the price now?" repeatedly. WebSocket means your code subscribes once and the exchange pushes updates as they happen. WebSocket is generally better for always-on strategies because it uses fewer requests, has lower latency, and pushes fills in real time. REST is simpler for lower-frequency strategies that can tolerate polling intervals.

Both run on the same TradingHost runtime. The choice is yours, not a TradingHost or CCXT licensing decision.

Section 07 · What we don’t do

What TradingHost does not do

  • TradingHost does not act as your exchange.
  • TradingHost does not provide trading strategies or financial advice.
  • TradingHost does not require withdrawal permissions from your exchange account.
  • TradingHost does not custody your exchange API keys beyond encrypted runtime injection.
  • TradingHost does not guarantee strategy performance, exchange uptime, or market connectivity.

Section 08 · FAQ

FAQ

No. TradingHost is independent. CCXT is open-source, MIT-licensed software maintained by the CCXT project.

No. CCXT Pro WebSocket functionality was merged into the free CCXT package in October 2022. From CCXT version 1.95+, all WebSocket support is included in the free, MIT-licensed package.

CCXT supports JavaScript, TypeScript, Python, C#, PHP, and Go. Any of these can run on a TradingHost runtime.

Over 100 cryptocurrency exchanges, including major centralised exchanges (Binance, Bybit, OKX, Coinbase, Kraken, KuCoin, Bitget, Gate, HTX, MEXC) and decentralised exchanges (Hyperliquid, dYdX, Paradex, Apex).

No. Your CCXT-based strategy code places trades through your own exchange API credentials. TradingHost runs the process.

Yes. A TradingHost runtime can host multiple strategy processes. Strategy-level start, stop, restart, and inspect actions can target one strategy without restarting the whole runtime.

You add them to TradingHost as encrypted secrets. They are injected into your runtime at start and are not stored in your repository.

Choose a region close to your exchange’s matching engine. Binance Spot is generally lowest-latency from AWS Tokyo. EU-domiciled exchanges often perform best from AWS Frankfurt. See /platform/regions/ for the full list.

Yes. With TradingHost MCP, compatible AI IDEs can read your runtime, redeploy CCXT strategies, inspect logs, and manage deployments. See /platform/mcp/.

No. CCXT is exchange connectivity only. For backtesting, see frameworks like Freqtrade, Backtrader, or vectorbt, all of which can use CCXT for live execution.

Deploy your first CCXT strategy

Connect GitHub, choose a CCXT template or your own repo, add your exchange API keys, choose a region, and launch into a TradingHost runtime.