AI-native runtime for Bybit trading strategies

No. Your strategy code connects to Bybit and sends instructions according to your own logic, account permissions and integration method. TradingHost provides the runtime where that code runs.

No. Bybit API access is provided by Bybit. You are responsible for your Bybit account, API permissions, credentials and compliance with Bybit’s terms.

No. TradingHost is the cloud runtime where your strategy code runs. We do not provide signals, AI prediction models or pre-built strategies. With TradingHost you write or generate the strategy yourself (often with Cursor or Claude Code), keep it in GitHub as your code, and use TradingHost to run it in production. 3Commas, Cryptohopper and similar products own the strategy logic; TradingHost runs your strategy.

AWS and DigitalOcean give you raw compute. You handle OS updates, container orchestration, log shipping, secret rotation, region failover and uptime monitoring yourself. TradingHost gives you a managed runtime purpose-built for trading strategies: GitHub-native deployment, MCP-driven control from AI IDEs, log and health surfaces out of the box. If you want to operate the infrastructure yourself, AWS works. If you want the runtime as a managed service, TradingHost is the shorter path.

Yes. TradingHost runs Python strategies; pick the framework runtime that matches your stack or deploy your own repo.

Yes. TradingHost supports any language that can run inside a container.

Yes. CCXT's bybit exchange covers spot, linear and inverse perpetuals, USDT and USDC futures, and USDC options against v5. Deploy your CCXT strategy from GitHub into a TradingHost runtime; we run it, you keep your keys. See the CCXT framework runtime for the full setup story.

Yes, if your project is designed that way. You can run multiple strategy processes or services inside one runtime, or separate them into different runtimes for isolation and operational clarity. See the TradingHost runtime page for the multi-strategy model.

The fastest path is to fork a TradingHost framework runtime: CCXT, Freqtrade or Hummingbot for a ready-to-deploy project. Or connect your own GitHub strategy repo. Linking a GitHub repo and creating a strategy is free; runtime plans are listed on the pricing page.

In your GitHub-controlled secrets workflow. TradingHost reads them at runtime through GitHub repository secrets, environment secrets or your own approved secret-management process. TradingHost does not need custody of your API key and secret. See platform secrets for the full handling model.

No. Strategies should never need withdrawal permissions. Use scoped permissions and per-key IP whitelisting where appropriate, and keep withdrawal scope on a separate manually-managed key.

Yes. TradingHost supports MCP-based control for AI IDEs including Cursor, Claude Code, GitHub Copilot and CLI-based AI agents. AI tools can inspect deployments, review logs, restart strategies and manage runtime workflows. MCP is a control and observability surface, not the trade execution path. See the MCP control surface for the full picture.

Both. The MCP control surface works equally well from CLI-based agents (Claude Code CLI, custom MCP clients, scripted MCP calls) and from inside an IDE. The GitHub-native deployment loop also works without any AI tooling: a regular git push to your main branch triggers a redeploy.

The runtime detects the crash and exposes the relevant logs and health information. Where supported, the affected strategy can be restarted without disrupting other strategies running in the same container. Your strategy code is still responsible for safe error handling, duplicate-order protection and risk controls. See observability for the logs and health surface.

Three causes account for nearly all 10004 errors: request timestamp outside the recv_window window (default 5000 ms) due to clock drift, signature payload assembled with parameters in the wrong order, or accidentally using HMAC payload format with an RSA key (or vice versa). Sync your runtime clock or fetch Bybit server time before signing. See the Operational notes section above for the full guidance.

Bybit runs three environments with disjoint key namespaces: mainnet, testnet (api-testnet.bybit.com), and mainnet demo (api-demo.bybit.com). A key issued in any one returns 10003 on the other two. Generate a fresh key from the matching dashboard.

Accounts opened 2025 or later default to UTA 2.0. If you’re on Classic or UTA 1.0 and want cross-product margin, upgrade. The upgrade is irreversible and inverse futures lose hedge mode. Test against demo first.

No. Bybit blocks US and Mainland China IPs at the API edge with a 403 response, and KYC rejects US-resident identities. TradingHost cannot route around this; the restriction is set by Bybit.

The incident was real, large, and well-documented (FBI IC3 PSA-250226). Bybit's hot operations, withdrawals, and customer balances were unaffected; the Hacken Proof of Reserves audit dated February 26 confirmed reserves over 100% across major assets. Bybit has since isolated signing infrastructure, redesigned multisig flows, and continues monthly Merkle-tree PoR. For an algorithmic strategy user this is operational context, not a current API blocker, but treat exchange custody risk as real and size accordingly.

TradingHost runs in the EU and US-East regions. Pick the region closest to the matching engine your strategy depends on. Note that Bybit blocks US IPs at the API edge, so Bybit strategies should not route from the US-East region. See the regions page for routing and proximity details.

No. TradingHost is focused on production runtime and deployment. Backtesting belongs in your research stack, framework or AlgoBuilder.