Preguntas frecuentes

Before opening a live trading account in cTrader, check regulation, country availability, account type, funding methods, minimum deposit, spreads, commissions, leverage, swaps and which Store product categories the account can use. Also confirm whether cloud cBots are enabled and whether copy trading is available for your country and client classification. Test new bots, copy strategies or TradingView automation on a demo account or with a small live size before scaling.

A cTrader broker supports trading bots when its account lets cBots run as cloud or local instances. Cloud cBots can be started from any cTrader app and continue running with your device switched off; local cBots run on Windows or Mac and stop when the app closes. Use the bot-related broker filter in Store as a shortlist, then verify symbol setup, commissions and any account-specific cloud limits on the broker page.

Compare brokers on total cost per trade, not on one number. Total cost = spread + commission + any markup, adjusted for the lot size you actually trade. A raw spread account at 0.1 pips with $7 commission per lot can be cheaper than a standard account at 1.4 pip spreads with no commission, depending on volume. Add swaps if you hold overnight, slippage if you scalp. Use declared spreads on broker pages as a starting point, then run a few sessions on a demo account to see live spreads under real volatility.

A raw spread account passes through the interbank spread, usually quoted from 0.0 pips, and charges a per-lot commission instead of widening the spread. The economics suit high-frequency or large-volume trading because total cost scales with volume rather than per-trade spread markup. Standard accounts hide the commission inside a wider spread — simpler, but often more expensive for active traders. Choose raw + commission for scalping and bots; standard for low-volume manual trading.

Mostly yes — Store products bind to your cTrader ID, which works across cTrader-affiliated brokers. The product itself becomes available wherever you are signed in with that cTID and cloud sync is enabled. The catch is performance, not access: spreads, commissions, swaps, symbol naming, leverage and execution all change between brokers, so a cBot tuned for one broker may underperform on another. Indicators behave the same way — same chart, different data feed.

Choose a prop firm in this order: rule fit, platform support, then price. For cTrader users the decisive checks are whether the firm offers cTrader accounts, the drawdown model (static, trailing, end-of-day, intraday), the daily loss limit, payout terms, consistency rules, news and weekend rules and whether cBots or copy trading are allowed. A cheaper challenge is not cheaper if its rules conflict with how your strategy actually trades.

Yes, if the prop firm explicitly allows automated trading for the challenge or funded account in question. The cBot must also comply with the firm's drawdown, daily loss, news, weekend, consistency and restricted-strategy rules. Test the bot on a demo account under identical rule settings before risking a paid challenge — successful backtesting does not prove the bot will pass a rule-bound evaluation.

Trailing drawdown is a loss limit that follows account equity or balance upward as the account grows. Profits raise the limit, so the absolute distance from the current high to the breach line stays close. This is stricter than static drawdown because a winning account has less room for future losses. Grid, martingale and high-leverage strategies are particularly vulnerable.

A consistency rule caps how much of total profit can come from a single day or a single trade. The aim is to prevent traders from passing a challenge through one oversized high-risk session. A rule like "no more than 30% of total profit from one day" forces a trader to distribute returns across multiple days, which usually means controlling daily lot size and avoiding revenge trading after losses.

The most useful Store tools for prop traders are position-size calculators, daily loss and drawdown monitors, equity-stop plugins, session and news filters, trade journals and risk-controlled cBots that pause when limits are hit. The goal is rule compliance, not just signals. No tool can pass a challenge on its own — they reduce the chance of avoidable rule breaches.

A cBot is a trading robot that runs in cTrader and analyses market conditions, places orders and manages positions according to its code and settings. cBots can run as cloud instances (any cTrader app, 24/7) or local instances (cTrader Windows or Mac). Store offers free and paid cBots; check live or demo statistics, backtesting results and risk settings before going live.

Yes, if the cBot's code includes trading actions and you start an instance on a trading account. Some cBots place and manage trades end-to-end, others only send alerts or manage open positions opened manually. Check the product description for the automation level before assuming the bot will trade by itself.

Yes. cTrader Windows and Mac include a backtesting engine that runs a cBot against historical tick or bar data over a chosen period, with adjustable spread and commission settings. Backtesting shows an equity curve, drawdown, win rate, profit factor and trade list. Remember, however, to treat backtesting results as research evidence, not a forward guarantee.

A cloud cBot instance is a cBot running in cTrader's hosted Linux-based environment, started from any cTrader app. The instance continues running independently of your device, so the bot keeps trading with the computer off. Default limits are typically one cloud instance on a demo account and up to ten on live accounts; cloud instances on demo accounts auto-stop seven days after start.

No. No trading bot can guarantee profit. Automation removes manual execution errors and emotional decisions but cannot remove spreads, slippage, leverage risk, news events or market regime changes. Any product claiming guaranteed profit is either marketing or a scam.

A trading indicator is a chart-analysis tool that processes price or volume data and displays output — trend, momentum, volatility, levels or signals — to support trading decisions. Indicators do not execute trades on their own. cTrader includes built-in indicators on every app; Store custom indicators add specialised analysis on cTrader Windows and Mac.

Indicators analyse data; they do not place trades by default. Automated execution belongs to cBots, plugins with trading permissions or Open API integrations. Some indicator products bundle alerts that can be routed to other systems, but the indicator itself does not act on the account.

Some indicators repaint — they change past signals after new price data arrives. This can make historical charts look cleaner than the indicator behaved in real time. Repainting is not always malicious: some indicators recalculate by design (e.g. ZigZag, fractals). The issue is whether the product page clearly explains repaint behaviour and whether alerts fire before or after candle close.

No, not directly. TradingView indicators are written in Pine Script and run only inside TradingView. cTrader custom indicators are written in C# or Python in cTrader Algo and run only in cTrader Windows and Mac. To use similar logic in cTrader, the indicator must be rebuilt from the Pine Script source by a developer. Multi-timeframe logic, repaint behaviour and alert conditions often need adaptation.

Yes, by rewriting them in C# or Python for cTrader Algo. Conversion is not automatic — Pine Script and cTrader Algo are different language environments with different APIs, bar-state models and alert mechanisms. If the Pine Script source is available, a cTrader Algo developer can usually reproduce the logic; if only a compiled or invite-only TradingView script is available, conversion requires reverse-engineering from observed behaviour.

Copy trading lets an investor add funds to follow another trader's strategy, so trades from the strategy are mirrored to the investor's copy account under platform rules. In cTrader this is handled in cTrader Copy, which supports cross-broker strategies. Copy trading can make you lose money — always review drawdown, fees and provider history before investing.

cTrader Copy uses funds that you transfer from your main account to a dedicated copy-trading account that follows one strategy. The strategy provider trades on their own account; their trades are copied to your copy-trading account according to allocation size and platform logic. Copy is cross-broker where supported. Stop copying at any time — your copy-trading account becomes a standalone account holding any open positions.

Yes. Copy trading is not a guaranteed-return investment. The copied strategy can lose money through poor decisions, regime changes, leverage or unexpected events; your funds can draw down or be wiped out in worst cases. Manage risk by investing only what you can afford to lose, choosing strategies with track records you can verify and stopping copying if drawdown breaches your personal limit.

Drawdown in cTrader Copy is measured as the largest peak-to-trough decline in the strategy account's equity. Maximum drawdown is the worst such decline over the record; current drawdown is the open one. Pair max drawdown with strategy age and trade count — a 5% max drawdown on a 30-day, 20-trade record is far less informative than 5% over 2 years and 800 trades.

Yes. You can stop copying a strategy at any time from your Copy account. When you stop, the copy account closes copied open positions at market and converts to a standalone account holding any residual balance. Unrealised performance and management fees are realised at stop.

A cTrader plugin is an extension that adds tools, panels, dashboards or workflow features to the trading platform. Plugins sit alongside indicators and cBots in Store as a separate product category. They can be analytical (calculators, journals, dashboards), informational (news, data widgets) or workflow-oriented (trade management panels, AI assistants).

cBots automate or manage trading logic — they place, modify and close orders according to code. Plugins extend the platform with tools, UI and external data; some plugins can include trading controls, but most are informational or workflow-oriented. If the goal is automated execution, you want a cBot; if the goal is a calculator, dashboard or panel, you want a plugin.

Yes. Both multi-platform plugins and desktop plugins run on cTrader Windows and Mac. Desktop plugins are Windows/Mac-exclusive; multi-platform plugins additionally run on Web and Mobile. Product pages should state both supported apps and where the plugin appears in the interface.

Yes. WebView plugins can integrate AI assistants — chat-style helpers for market commentary, strategy ideas, calculation or workflow guidance — because they are built as web apps and can call external AI APIs. Note that AI output is not financial advice and should be treated as a decision input. WebView plugins must not include authentication or payment forms in the web app itself.

Plugins published in cTrader Store run in a sandboxed environment with permission boundaries and confirmation flows on sensitive actions. That said, plugins can still send data to external services and can be designed to trade if granted permission — review the product description, supported permissions and data flow before installing. Test trade-capable plugins on a demo account first.

cTrader Open API is a developer interface for building external applications that connect to the cTrader backend — market data, account information, order management, dashboards, trading bots and integrations. It is language-flexible because it speaks JSON or Protocol Buffers and is commonly used with Python or C#. Open API sits alongside cBots (in-platform) and MCP (AI-agent) as one of three developer routes into cTrader.

Yes. Open API supports the trading operations available to standard cTrader accounts — placing, modifying and closing orders, plus position and account management. With trading permission, an Open API app can act on a live account exactly as the user could, so authentication, scope and risk controls should be designed before going live.

Yes. Python is one of the most common languages used with cTrader Open API, with community libraries and official examples. Typical Python use cases are market data pipelines, research notebooks, dashboards, signal bots and Telegram-style notification bots. For full in-platform automation, a cBot in Python or C# is often a simpler route than Open API.

Yes — through cTrader's Local or Remote MCP server. With Claude Code (or Claude Desktop with MCP support) configured to the cTrader MCP server, Claude can read account data, query market data, manage orders and positions, control charts (Local MCP) and execute trading actions if trading is enabled. Trading actions can be gated by a confirmation setting.

cBots run inside cTrader as in-platform algorithms (cloud or local). Open API runs outside cTrader as a network-connected developer interface (JSON/Protobuf, 50 req/sec on real-time data, 5 req/sec on historical). MCP exposes cTrader capabilities as tools for AI agents to call from natural-language prompts.

Sometimes — many brokers allow opening a new account on a different platform under the same client profile, but the original account cannot usually be "switched" to a new platform because each platform has its own account ledger. Funds may need to be transferred internally. Confirm with the broker before assuming positions or open orders carry across.

Yes — for some product types. You can install Store products, start and manage cloud cBots and use multi-platform plugins from cTrader Mobile. Store custom indicators and desktop plugins can be installed to your cTrader ID from mobile but require Windows or Mac to actually run.

Yes, if the bot is running as a cloud cBot instance. Cloud instances run in cTrader's hosted environment 24/7 and do not depend on your device staying open, removing the need for a VPS for most users. Local cBots stop when the desktop app closes or the computer disconnects.

No. Store custom indicators cannot be added to cTrader Mobile charts. Mobile supports built-in indicators only. If your workflow requires mobile, alternatives are built-in indicators, price alerts, cloud cBots that handle the logic on the server side and multi-platform plugins that include analytical UI.

Sometimes — some brokers run a single account model across multiple platforms (e.g. cTrader and TradingView via broker integration). Most brokers operate cTrader and MT4/MT5 as separate account pools, so the same email may have several accounts with different platforms and conditions. Confirm with the broker before assuming positions, balances or history will be visible across platforms.

cTrader Store is the marketplace for cTrader trading products: cBots, custom indicators, multi-platform plugins, desktop plugins and Copy strategies. Products are free or paid, linked to your cTrader ID and delivered through cloud synchronisation to compatible cTrader apps. Store is the official distribution channel — products are reviewed and source code is never uploaded.

Both. Many Store products are free and paid products may also offer trial versions with seller-defined limits or time windows. Price is not a quality signal — compare automation level, compatibility, supported apps, live or demo evidence, reviews and trial availability instead of assuming paid means better.

After purchase or free install, the product is bound to the cTrader ID active in Store at the time and synced to your cTrader apps through cloud synchronisation. The first-use path depends on product type: start a cBot in cloud or locally, open a custom indicator on a Windows or Mac chart or launch a plugin where it appears in the interface.

Refunds depend on the seller's policy and Store's refund terms, which may vary by product type and reason. If the product does not work as described, you can contact the seller and, if unresolved, report the product through Store. Refunds are not guaranteed and are evaluated case by case. Always read the product description carefully and use the trial version (if available) before purchase.

Reviews on cTrader Store come from users who installed or purchased the product. They cover usability, performance vs description and overall experience. Treat reviews as one signal alongside live or demo evidence and the product description — a few outlier reviews carry less weight than a consistent pattern.

To become a seller, create a Store seller profile, prepare a product that meets Store requirements and submit it for review. Paid sellers complete identity verification; free product publishing has lighter requirements. Strong seller pages explain use case, supported apps, settings, limitations and what users should test on a demo account — not just feature lists.

Yes. cBots are one of the core paid product categories in Store. A strong cBot listing covers strategy logic, supported symbols and timeframes, recommended account conditions, risk settings, cloud vs local compatibility, backtesting results, live or demo statistics and explicit limitations. Avoid profit guarantees — they fail review.

Yes. Sellers can attach live or demo-forward account performance to a product page, which is stronger evidence than backtesting results because it reflects real execution. Live performance still represents one broker, one period and one parameter set — disclose these for transparency. Performance shown on the product card improves filtering and conversion.

Yes. A seller profile in cTrader Store functions as a landing page for traffic from external channels. It includes your best products, categories, ratings, video previews and Copy strategies if applicable. Optimise the profile bio, choose strong featured products and link consistently from external content.

Misleading descriptions typically overpromise results (guaranteed profit, no risk), hide critical limitations (desktop-only indicator sold as multi-platform), inflate backtesting evidence (perfect historical curves without disclosure) or omit material information (broker dependence, prop-firm restrictions, repaint behaviour). Be specific about what the product does and does not do.

Trading bots are software tools, not automatically safe. Risk depends on strategy logic, settings, broker conditions, leverage and market regime. Read the product page, test the bot on a demo account, start small when going live, set risk limits and avoid guaranteed-profit claims.

No. No bot can guarantee profit. Automation removes manual execution errors and emotional decisions, but it cannot remove spreads, slippage, leverage risk, news shocks or market regime changes. Any product that claims guaranteed profit is either marketing or a scam — both are reasons not to buy.

Historical data does not fully reproduce future spreads, slippage, execution speed, swaps, broker setup or market regime. Settings tuned for past conditions may not generalise. Live trading also exposes the strategy to gaps, news and liquidity events that backtesting smoothes over. Use backtesting for hypothesis testing; use demo and small live size for validation.

Yes. Demo testing is the lowest-cost way to validate that a bot, copy strategy, plugin or TradingView automation behaves the way the product page describes — on your broker, with your settings and your symbols. Demo does not guarantee live results, but it catches the avoidable setup mistakes that account for most early losses.

Max drawdown is the largest peak-to-trough loss on a strategy or account over the measurement period, expressed as a percentage or absolute amount. It is the most important risk metric for evaluating bots, copy strategies and prop accounts because it shows the worst pain the account survived. A 30% max drawdown means the account lost 30% from a high before recovering.