Frequently asked questions

A platform for building crypto trading strategies from visual blocks and backtesting them on real Binance history — with an engine designed so a backtest cannot use information it would not have had at the time.

Anyone who wants a rigorous backtest without programming one: build it from blocks, or describe it to the AI assistant. If you would rather drive it from code or your own AI, there is a REST API and an MCP server too.

A bot trades live on an exchange. crypto-comp is for research: it backtests strategies on historical data. It never asks for exchange API keys and never places an order.

Rules are checked when a bar closes, and the resulting order fills at the close of the NEXT bar — so a strategy can never trade at a price it saw only after deciding. A higher-timeframe value (a 4h EMA on a 15m strategy, say) is always the last CLOSED 4h bar, never the one still forming. These are locked by the engine for every run; they are shown in the builder but cannot be changed.

Each of the 115 indicator types has its own reference test: its output is compared bar by bar with an independent implementation, including deliberately wrong variants to make sure the test would notice. Whole strategies are checked the same way — frozen strategies on real data are compared trade by trade against an independent reference of the engine's rules.

No one can promise that. A backtest shows how a set of rules would have behaved on past data, with fees charged on every fill. Markets change, and real execution adds slippage and liquidity effects a bar-level backtest does not model. Treat results as research, not as a forecast or advice.

One. A backtest runs one strategy on one symbol; running several symbols in one backtest is not available. You can run the same strategy on other symbols as separate backtests.

Not available. crypto-comp is a backtesting and research tool; it does not trade.

Yes — USDT-margined perpetuals, with funding settled from the real funding-rate history and liquidation checked minute by minute on the mark price. Perpetuals need the Pro plan. Coin-margined (inverse) contracts are not supported.

Coming soon. Options market data is being collected, but nothing executes an option strategy yet — there is no option pricing or Greeks in the engine today.

Any symbol the store has data for — the builder lists exactly those, with the range stored for each, and refuses a backtest window outside that range before it runs.

Read straight from the plan configuration the launch checks enforce. Full details on the pricing page.

Pro is a subscription at $29.00 / month, paid by card through Stripe's hosted checkout. Free needs no payment and no card.

Yes — enter it at checkout. A code applies to the subscription only.

Three things: build a strategy from a plain-English description (as a validated spec), optimize a saved strategy by proposing changes and running a few backtests, and discuss one of your results. It works through the same operations you do, with your plan's limits.

Yes. Connect an OpenRouter, OpenAI or Anthropic key in Settings and paid models run on it instead of on credit. The key is encrypted before it is stored and is never shown back to you or anyone else — only its last four characters.

Free models cost nothing. A paid model is priced per token: before the call, a conservative maximum is held from your credit; afterwards, only the actual cost is charged and the rest released. With your own key, your provider bills you and nothing is charged here.

Only when you use it. Each message you send — and whatever the assistant reads with its tools, such as a strategy or a run's metrics — goes to the third-party model provider that answers it. The chat says so permanently, next to the message box.

Your account, strategies and backtests are stored in the platform's own database. Market data is stored separately and contains nothing about you.

Only your account. Every read and write is scoped to the signed-in account on the server, and a request for someone else's strategy is answered exactly as if it did not exist. Administrators can see a run's status and timing to operate the service, but not your strategy's contents or its results.

With a one-time link sent to your email, or with Google. There is no password to leak.

An API key for MCP or the REST API is stored only as a hash and shown to you once, when you create it; you can scope it and revoke it at any time. A provider key for BYOK is encrypted and bound to your account.