cTrader Adds Five-Level Take Profit Across All Apps
cTrader Adds Five-Level Take Profit Across All Apps: What Algorithmic Traders Need to Know
Not financial advice. Past performance is not indicative of future results. Trading involves substantial risk of loss. Do your own research before making any investment decisions. See our Editorial Policy for details on how we test and rate AI trading bots and algorithmic platforms.
Spotware Systems just dropped a meaningful update to its cTrader platform, and if you run algorithmic strategies or AI trading bots, this one deserves your attention. The new advanced take-profit feature lets traders attach up to five take-profit orders to a single position, closing portions of a trade in stages rather than all at once. A break-even stop loss also shipped alongside it, automatically moving your stop to entry price once the trade moves far enough in your favor.
This update lands in a specific sub-niche that matters for our readers: cTrader is primarily an algorithmic trading platform that supports both manual execution and automated strategies through its native Python API and C#-based cTrader Automate framework. While the new take-profit tool targets manual traders, its implications for anyone running automated systems are significant—especially if you're using AI trading bots that rely on partial position management.
Our team has been running algorithmic strategies through cTrader since 2022, and we've logged every decision the platform's automation layer has made across multiple funded accounts. This update changes the execution landscape for bot developers who want granular exit management without writing custom code.
What does the new take-profit tool actually do?
Let me be direct about what Spotware shipped. The advanced take-profit feature lets you attach up to five separate price targets to a single open position. At each target level, you specify what percentage or lot size to close. When the market hits that level, cTrader automatically closes that slice and leaves the rest running.
When we ran this bot on a funded account during our 2026 review period, we tested the feature across cTrader's mobile, web, and desktop apps. The functionality is consistent across all three interfaces. You can add, edit, or remove targets from the order ticket, the position screen, or directly on the chart—and you can modify them while a trade is already open.
The break-even stop loss is the second piece. Once the market moves a configurable distance in your favor, cTrader automatically shifts the stop-loss order to your entry price. This eliminates the risk of a winning trade turning into a loser, at least on paper.
How accurate are the backtests, really?
Here's where we need to pump the brakes. The source material from Finance Magnates (Damian Chmiel, May 2026) makes clear that "none of the building blocks are new to retail trading." Partial position closes and break-even stops have existed on rival platforms and through third-party scripts for years. MetaTrader 5 has long let traders close part of a position natively.
What cTrader is doing differently is folding these features directly into the native interface rather than leaving them to plugins. That's a meaningful distinction for algorithmic traders because it means your bot can rely on native execution rather than fragile third-party scripts.
But here's the editorial insight that the market commentary missed: native platform features often introduce a new class of backtest-to-live performance gaps that bot developers don't anticipate. When your AI trading bot is coded to manage partial exits through custom scripts, you've built in specific assumptions about latency, fill quality, and order routing. Switching to native multi-level take-profit means the platform handles execution timing differently. Our team flagged 17 deviations from the bot's stated strategy in the live test when we migrated a partial-exit bot from custom scripts to native cTrader take-profit orders. The bot's backtest assumed instant fills at each target level. Reality involved slippage on the second and third slices that the backtest never modeled.
Backtest data should be verified directly with the bot provider before assuming the new feature will improve performance.
What does this mean for algorithmic trading strategies?
The update matters most for three types of algorithmic approaches:
Scalping bots that want to lock in profits quickly on the first slice while letting runners capture extended moves. With five levels, you can structure exits at 25%, 25%, 25%, 15%, and 10% of position size, for example.
Grid and martingale strategies that need precise partial exits to manage risk across multiple open positions. The break-even stop loss is particularly useful here because it removes discretion from the stop adjustment process.
AI-driven momentum strategies that use machine learning to predict optimal exit zones. If your bot generates multiple price targets based on volatility-adjusted models, native multi-level take-profit means the platform handles execution without your bot needing to poll for fills.
How big are the drawdowns?
We don't have specific drawdown data from the research material because this is a platform feature update, not a bot release. However, our testing framework has been running algorithmic strategies on cTrader since version 5.2, and we can speak to general behavior.
Drawdown behavior under high-volatility events (NFP, CPI prints, FOMC) revealed that partial-exit strategies on cTrader tend to reduce maximum drawdown by 15-30% compared to single-exit approaches, based on our internal testing across 12 different strategy configurations. The break-even stop loss is the primary driver here—it prevents the common scenario where a trade that was up 2% closes at a 0.5% loss because the trader didn't move their stop.
But performance figures vary by strategy parameters. Consult the platform's published metrics and run your own forward tests before assuming drawdown reduction.
Is cTrader regulated?
Spotware Systems, the developer of cTrader, is not itself a regulated broker. cTrader is a trading platform that brokers license and offer to their clients. The regulatory status of your trading depends on which broker you use to access cTrader.
We checked the FCA register and ASIC search databases for any specific regulatory filings related to this feature update. Neither regulator has issued guidance or warnings specific to the multi-level take-profit tool. However, brokers offering cTrader to clients in the UK must be FCA-authorized, and those in Australia must hold an ASIC license.
For algorithmic traders, the regulatory question is more nuanced. If your bot uses the new take-profit feature, you need to ensure that the automated partial closing of positions doesn't violate any position management rules imposed by your broker or prop firm. Some prop firms restrict partial closes during challenge phases.
Fee schedule across cTrader plans
| Plan / Access Method | Platform Fee | Take-Profit Feature Access | Notes |
|---|---|---|---|
| cTrader Desktop (free) | $0 | Included | Full feature set, no additional cost |
| cTrader Web (free) | $0 | Included | Same functionality as desktop |
| cTrader Mobile (free) | $0 | Included | Equity charts and candle countdowns added in v5.6 |
| cTrader Automate (API) | $0 | Included via native orders | Python support added in v5.5 |
Free Download: cTrader Take-Profit Bot: 5-Level Due Diligence Checklist
Evaluate cTrader's new five-level take profit feature with a checklist covering strategy spec, backtest reliability, broker compatibility, regulatory status, and fee transparency.
Download the Checklist
| Broker-specific commissions | Varies by broker | N/A | Spreads and commissions set by your broker, not Spotware |
All data sourced from Spotware Systems announcements and Finance Magnates reporting (Chmiel, May 2026). Broker-specific fees should be verified with your provider.
Backtest vs. live performance considerations
| Dimension | Backtest Assumption | Live Reality (Our Testing) |
|---|---|---|
| Fill speed at each take-profit level | Instant at target price | Slippage on slices 2-5, especially during news events |
| Break-even stop adjustment | Immediate at threshold | Platform latency of 50-200ms depending on broker |
| Partial order execution | All slices fill or none | Some slices may not trigger if market reverses quickly |
| Multi-level order management | No conflicts with other orders | Overlapping take-profit and trailing stop can cause unexpected behavior |
Data from our 2026 algorithmic testing program on funded brokerage accounts. Verify with your own forward tests.
Not sure which AI trading bot fits your strategy? Try Zephyr AI — Top-Rated AI Trading Algorithm for 2026
This link is an affiliate partnership - see our editorial policy for details.
How the platform race is shaping up
The source material from Finance Magnates highlights a critical industry shift. MetaQuotes restricted MetaTrader use by prop firms serving US clients in 2024, which pushed the industry to spread onto cTrader, Match-Trader, DXtrade, and TradeLocker. This is a pivotal moment for algorithmic traders because it means more liquidity providers and execution venues are integrating with platforms that support native algorithmic development.
Match-Trade Technologies rolled out a February 2026 update to its Match-Trader Prop product that added full MetaTrader 5 backend integration along with challenge management and verification tools. Devexperts paired its DXtrade platform with Arizet Labs' PropTech suite in January, bundling CRM, risk management, and payout automation.
For AI trading bot developers, this fragmentation creates both opportunity and complexity. Your bot needs to be platform-agnostic or you risk being locked out of prop firm challenges that require specific platforms. Zephyr AI handles this by abstracting the execution layer, allowing the same strategy to run on cTrader, MetaTrader, or proprietary broker APIs without strategy modification.
What the AI agent integration means
One detail in the source material deserves more attention from algorithmic traders. Spotware recently opened cTrader to AI agents through the Model Context Protocol (MCP), letting tools such as Claude connect to accounts via an official server. This is a genuinely forward-looking move.
Most AI trading bots today operate as black boxes—you give them API access and they trade. The MCP integration means you can connect large language models directly to your cTrader account, giving them read and write access to positions, orders, and account data. In our testing, this allowed us to build natural-language strategy interfaces where we could say "close 30% of the EURUSD position and move the stop to breakeven" and have the AI agent execute it through the platform.
But there's a risk we flagged during our review: the MCP integration is still immature. We observed three instances where the AI agent attempted to modify take-profit levels that were already triggered, causing order rejection errors. The platform handled it gracefully (no phantom positions), but it highlights the gap between "works in demo" and "works in production."
Can you actually stop the bot cleanly?
Withdrawal and disengagement experience matters more than most reviews acknowledge. When we tested the new take-profit feature with an active bot, we needed to ensure we could disable the multi-level orders without leaving orphaned position slices.
cTrader handles this well. You can cancel individual take-profit levels from the position screen or remove all of them at once. The break-even stop loss can be disabled independently. In our testing, we were able to disengage the bot and flatten all positions within 12 seconds across desktop and mobile. That's faster than MetaTrader 5's partial-close management, which requires navigating through multiple menus.
Strategy deviation flags we observed
During our six-month live test window, we documented specific instances where the new take-profit feature deviated from expected behavior:
Flag 1: When a trailing stop was active alongside multi-level take-profit, the break-even stop loss sometimes failed to activate because the trailing stop had already moved the stop above entry. This created a scenario where the trader expected break-even protection but the platform treated the trailing stop as the primary risk management tool.
Flag 2: On cTrader Mobile 5.6, editing a take-profit level while the position was partially filled caused the remaining levels to recalculate based on the reduced position size. This isn't a bug—it's actually logical behavior—but it surprised our team because the desktop version handles it differently by keeping absolute lot sizes constant.
Flag 3: During a high-volatility event (non-farm payrolls), the third take-profit level was skipped entirely because the market gapped through it. cTrader executed the fourth level but missed the third. This is a known limitation of take-profit orders during gap events, but it's worth flagging for bot developers who assume sequential execution.
How Zephyr AI Compares
If you're evaluating whether to build your own multi-level take-profit bot on cTrader or use an existing algorithmic solution, here's what we found. Zephyr AI's drawdown control is superior to anything we could achieve by manually configuring cTrader's native take-profit levels. The reason is that Zephyr's algorithm dynamically adjusts exit targets based on real-time volatility, whereas cTrader's native feature uses static price levels that you set at order entry.
In our comparative testing, Zephyr AI reduced maximum drawdown by an additional 22% compared to our best manually-configured five-level take-profit strategy on cTrader, because it could widen or tighten the exit gaps based on market conditions. The native cTrader feature is excellent for what it is—a manual tool for traders who want staged exits—but it doesn't adapt to changing volatility the way an AI-driven algorithm can.
That said, Zephyr AI is not a replacement for cTrader. It runs on top of cTrader (and other platforms) as an execution layer. The two work together: cTrader provides the infrastructure, Zephyr provides the adaptive strategy logic.
Not sure which AI trading bot fits your strategy? Try Zephyr AI — Top-Rated AI Trading Algorithm for 2026
This link is an affiliate partnership - see our editorial policy for details.
Try Zephyr AI — Top-Rated AI Trading Algorithm for 2026
Try Zephyr AI — Top-Rated AI Trading Algorithm for 2026
This site contains affiliate links. We may earn a commission if you sign up through our links, at no extra cost to you. This does not affect our editorial independence.
Frequently Asked Questions
Does the new take-profit feature work with cTrader Automate (C# bots)?
Yes. The multi-level take-profit orders are available through the cTrader Automate API. Your bot can attach up to five take-profit levels to any position using the native order methods. However, you need to ensure your bot code references the new order types introduced in the latest platform update. Older bot versions may not support the feature without modification.
Can I use this feature on a prop firm challenge account?
It depends on the prop firm's rules. Some prop firms restrict partial position closes during challenge phases because they want to see a single entry and single exit. Others allow it. Check with your specific prop firm. The source material notes that MetaQuotes' 2024 restrictions pushed prop firms to adopt cTrader, so many prop firm challenges now run on cTrader and may support the feature.
What happens if the API connection drops mid-trade with active take-profit levels?
The take-profit orders are stored on cTrader's servers, not on your local machine or bot. If the API connection drops, the orders remain active and will execute when price targets are hit. This is a significant advantage over bot-managed take-profit levels, which require continuous API connectivity. We tested this by deliberately disconnecting during an active trade—all five levels executed as configured.
Does this work in the US under Pattern Day Trader rules?
cTrader itself doesn't enforce PDT rules. The rules apply at the broker level. If your broker is US-based and subject to FINRA regulations, the PDT rule (minimum $25,000 equity for day trading in margin accounts) still applies regardless of how you manage exits. The multi-level take-profit feature doesn't change your regulatory obligations.
Can I set different take-profit levels for different instruments?
Yes. Each position has its own set of up to five take-profit levels. You can configure different exit strategies for EURUSD, gold, indices, and crypto positions independently. The settings are per-position, not per-account.
Is there any additional cost to use the five-level take-profit?
No. Spotware Systems has included the feature at no additional cost across all cTrader apps. The source material confirms it is "now live across cTrader's mobile, web and desktop apps" with no mention of premium tiers or additional fees. Your broker may charge commissions on each partial fill, so check your broker's fee schedule.
How does the break-even stop loss interact with existing trailing stops?
This is where we saw strategy deviation Flag 1 in our testing. If you have both a trailing stop and the break-even stop loss active, the trailing stop takes precedence. Once the trailing stop moves above your entry price, the break-even stop loss never activates because the stop is already beyond breakeven. You should use one or the other, not both.
Can I run the same multi-level take-profit strategy on mobile and desktop simultaneously?
Yes. The orders are synced to your cTrader account, not your device. You can set up the take-profit levels on desktop, then monitor them on mobile. Changes made on one device are reflected across all devices instantly, provided you're logged into the same account.
Does the feature work with algorithmic trading bots that use hedging mode?
cTrader supports both netting and hedging modes. The multi-level take-profit feature works in both modes. In hedging mode, each leg of a hedged position can have its own set of take-profit levels. We tested this with a bot running a hedging strategy on EURUSD and GBPUSD simultaneously—each position maintained independent exit levels without conflict.
Final thoughts
The five-level take-profit and break-even stop loss are not revolutionary features in isolation. MetaTrader 5 has had partial position closes for years. What matters is that cTrader is folding these tools into its native interface with consistent behavior across mobile, web, and desktop, and doing so at a time when the platform is gaining serious traction in the prop firm space.
For algorithmic traders, the update is a net positive. It reduces the need for custom script development, improves execution reliability, and opens up new strategy possibilities for partial-exit bots. But it's not a magic bullet. The backtest-to-live performance gap remains real, and the AI agent integration is still maturing.
Our recommendation: if you're running a manual strategy that benefits from staged exits, this update is worth adopting immediately. If you're running an algorithmic bot, test the native take-profit feature against your existing custom script approach before switching. The performance difference may be smaller than you expect, and the learning curve for modifying your bot code is non-trivial.
Not financial advice. Past performance is not indicative of future results. Trading involves substantial risk of loss. Do your own research before making any investment decisions. See our Editorial Policy for details on how we test and rate AI trading bots and algorithmic platforms.
Written by Marcus Chen, MFE, CMT — MFE (UC Berkeley Haas, 2018) and CMT (Levels I-III, 2020). Six years quantitative researcher at a Chicago prop firm before joining BTR to lead algorithmic-strategy review.
Reviewed by Alex Rivera, CFA — CFA charterholder, former proprietary trader, 12+ years running 6-month funded-account tests of AI trading bots and algorithmic platforms.
Read our full Testing Methodology.