AI-native runtime for Deribit options strategies

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

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

No. TradingHost is the cloud runtime where your strategy code runs. We do not provide signals, AI prediction models or pre-built bots. 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.

CCXT's `deribit` exchange covers options, perpetual and expiry futures including unified options methods. Deploy your CCXT-based project from GitHub into a TradingHost container and inject Deribit's `client_id` and `client_secret` as secrets. Native Deribit JSON-RPC over WebSocket and FIX 4.4 are also supported; the runtime is language- and library-agnostic. See the CCXT framework runtime for the full setup story.

Yes. Deribit lists BTC, ETH and SOL options (European-style, cash-settled) as well as linear USDC options on additional altcoins. TradingHost runs the strategy container, deployment, logs and health, and the Deribit API runs the execution. Greeks are exposed on the venue’s tickers, and Portfolio Margin can be enabled at the Deribit account level for cross-instrument margin offsets.

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 such as CCXT 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 Deribit `client_id` and `client_secret`. See platform secrets for the full handling model.

Portfolio Margin runs scenario shocks across the whole book (price and IV) and uses the worst-case as the requirement, materially reducing margin for hedged or spread options books. Standard Margin treats each position independently with no offsets. If your strategy holds offsetting options and futures legs, Portfolio Margin generally lowers capital requirements; if you are running directional inventory, Standard Margin is simpler. Both can run in segregated or cross-collateral mode.

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.

That means the API key, secret or signature did not validate. Common causes: pasting a testnet key against www.deribit.com (or vice versa), clock skew on the timestamp field in HMAC signature auth, an incorrect signature string (format is `timestamp + "\n" + nonce + "\n" + data`, both newlines required), or the key was revoked. Re-check the key in the Deribit console and confirm the environment hostname matches the key.

Yes. Testnet lives on `https://test.deribit.com/api/v2`, `wss://test.deribit.com/ws/api/v2` and FIX `test.deribit.com:9881`. Accounts, balances, sub-accounts and API keys are separate from production. A common pattern is to set `DERIBIT_ENV=test` in the container and resolve the base URL from that.

Coinbase closed its acquisition of Deribit on August 14, 2025. From a strategy author’s perspective, nothing changed at the API or instrument level: hostnames (www.deribit.com, test.deribit.com), authentication, FIX sessions, instrument naming and the JSON-RPC surface continue as before. The brand is now presented as "Deribit by Coinbase". Future integration with Coinbase platforms has been signalled but no merged endpoint has been published.

TradingHost runs in the EU and US-East regions. Pick the region closest to the matching engine your strategy depends on. 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.