Why this dispatch exists
This is the fourteenth Phase 3 dispatch and the eighth in the per-pillar deep-dive sub-series. The earlier per-pillar dispatches covered payments, RegTech, crypto exchange WL, LP procurement, risk management, broker CRM, and IB management. This one covers the trading platform layer.
The trading platform layer is the most consequential procurement decision in the broker stack because it constrains every downstream procurement. The CRM choice is influenced by the platform; the LP integration is constrained by the platform; the risk management vendor must integrate with the platform; the analytics widgets must be compatible with the platform; the copy trading vendors depend on the platform. Despite the layer’s importance the Phase 2 coverage was partial: Phase 1 covered the alt-WL Cyprus chapter (non-MetaTrader platforms with a CySEC lens), the Phase 2 turnkey chapter covered platform-bundled suites, and the Phase 2 crypto exchange WL chapter covered the crypto venue layer. What was missing was a dedicated dispatch on the platform layer itself, treating MT4, MT5, cTrader, Match-Trader, Sirix, and TradingView-powered platforms as a single procurement decision space.
This dispatch covers the trading platform procurement landscape state in 2026, the MT4 versus MT5 migration question and what has actually moved through 2024-2026, cTrader positioning under Spotware including the Spotware Store pricing transparency that is unique to the chapter, Match-Trader’s broker-friendly positioning with crypto-CFD strength, Sirix and other bundled platform options, the TradingView-powered emerging category, per-archetype platform fit across the four operator archetype dispatches, and three procurement implications for 2026.
The trading platform procurement landscape state in 2026
Three structural realities shape platform procurement through 2026:
MetaTrader continues dominating despite the migration narrative. Through 2023-2024 the broker industry talked extensively about migration away from MetaTrader following the MT4 sunset announcements, the App Store and Google Play removal cycles of 2022, and the general perception that MetaQuotes’s strategic direction was uncertain. By 2026 the reality is that MetaTrader continues dominating retail CFD broker deployments. MT5 has materially displaced MT4 at new broker procurement but the MT4 installed base remains large. MetaQuotes’s pricing and licensing continue along the same trajectory; broker complaints about pricing have not translated into mass migration to competing platforms.
cTrader has continued strengthening as the institutional-leaning alternative. Spotware’s continued investment in cTrader through 2024-2026 has expanded the platform’s institutional positioning. The Spotware Store pricing model (published Pro Trader, cBot subscription tiers) remains the only published pricing in the alt-WL chapter and is the procurement-relevant transparency feature that distinguishes Spotware from competitors. cTrader Copy native deployments have continued growing including tier-1 CySEC reference deployments that the Phase 2 copy trading chapter covered.
The TradingView-powered category has emerged as procurement-relevant. Through 2024-2025 TradingView’s broker-integration partnerships have continued expanding with multiple brokers offering TradingView-powered trading interfaces alongside or in place of MetaTrader. The TradingView-powered category is not a single product but a category of broker deployments using TradingView’s charting interface plus trade execution integration. The procurement-relevant question is whether the operator wants TradingView as a differentiated client experience layer alongside MT5 or as a primary platform replacement.
MT4 versus MT5 migration question
The MT4 to MT5 migration has been ongoing since MT5’s launch in 2010. The 2026 state:
MT4 installed base remains substantial despite MetaQuotes positioning. MetaQuotes positioned MT5 as the strategic platform from launch but maintained MT4 with sustained support through the 2010s. The 2022 announcement of reduced MT4 investment was widely interpreted as a sunset signal but operational support has continued through 2024-2026. The MT4 installed base remains large with hundreds of active broker deployments and a substantial retail trader base who prefer MT4’s interface and existing EA ecosystem.
MT5 dominates new broker procurement. Brokers entering procurement in 2024-2026 default to MT5 unless specific MT4 requirements (EA compatibility for a target trader segment, regional preference, legacy EA library) drive otherwise. The 2026 procurement-relevant default is MT5; MT4 procurement is increasingly niche.
Migration friction has not resolved. Operators with substantial MT4 installed bases face the same migration friction in 2026 as in 2022: client EA compatibility (most MT4 EAs do not run on MT5 without modification), client preference for MT4 interface familiarity, and the engineering cost of running parallel MT4 and MT5 instances during a multi-quarter transition. Few operators have completed full migration; most run parallel MT4 and MT5 with no firm sunset date for the MT4 side.
The MT5 capability advantage is real but not transformative. MT5 supports more instrument types (CFDs on stocks, futures, options), better order execution mechanics, native multi-currency account support, and more sophisticated charting. The capability advantage is procurement-relevant but does not transform the broker’s operational economics; the advantage compounds over years rather than producing year-1 ROI that justifies acute migration friction.
The procurement-relevant implication for the MT4 versus MT5 question is that new procurement should default to MT5 and operators with MT4 installed bases should plan migration as a multi-quarter project sized appropriately rather than treating it as a forcing decision driven by MetaQuotes positioning.
cTrader positioning under Spotware
cTrader is the strongest alt-WL platform in the chapter for institutional-leaning procurement. The 2026 procurement-relevant positioning:
The Spotware Store pricing model is the chapter’s published pricing benchmark. Spotware’s Pro Trader and cBot subscription tier pricing is published in the Store. This is the only published platform pricing in the chapter and is procurement-relevant because it constrains the broker’s per-trader cost calculation in ways that other platform vendors’ quote-based pricing does not. The procurement-relevant question for operators considering cTrader is whether the published pricing matches the operator’s expected trader segment activity profile or whether enterprise contract negotiation produces materially different economics.
Native copy trading capability with tier-1 CySEC reference deployments. The Phase 2 chapter surfaced cTrader Copy as STRONG PICK for native deployments. Tier-1 CySEC brokers running cTrader have deployed cTrader Copy with disclosed published Spotware Store pricing model and configurable closed/open network scope. This is procurement-relevant because operators procuring cTrader gain native copy trading as part of the procurement rather than as a separate decision.
Multi-asset coverage including crypto-asset. cTrader supports FX, CFDs on stocks, indices, commodities, and crypto-asset trading natively. The crypto-asset coverage is procurement-relevant for hybrid operators wanting unified platform deployment across FX, CFD, and crypto-asset (subject to the operator’s CASP authorisation if regulated crypto-asset trading is in scope).
Institutional execution mechanics. cTrader’s central limit order book matching, level-2 market depth display, and FIX API support distinguish the platform from MT5 at the execution layer. Procurement-relevant for operators with institutional-leaning client segments wanting execution transparency that MT5’s market-maker model does not natively provide.
The procurement-relevant implication for cTrader is that the platform is the strongest alt-WL procurement option for CySEC operators wanting differentiated institutional positioning. DMCC operators procuring cTrader gain the same capabilities but face the procurement question of whether the platform’s institutional positioning matches DMCC retail client expectations versus the MT5 default.
Match-Trader broker-friendly positioning
Match-Trader (from Match-Trade Technologies) has continued strengthening through 2024-2026 as the broker-friendly platform alternative. The 2026 procurement-relevant positioning:
Match-Trader CRM integration tightness. Match-Trader operates with native Match-Trader CRM integration that the broker CRM deep dive covered. The integration tightness is procurement-relevant for operators wanting single-vendor CRM-plus-platform procurement at mid-market scale.
Crypto-CFD strength. Match-Trader handles crypto-CFD trading natively with broker-friendly margin and leverage configuration. The procurement-relevant question for hybrid CFD plus crypto operators is whether the crypto-CFD capability on Match-Trader meets the operator’s regulatory positioning (the Phase 2 crypto exchange WL chapter noted Match-Trade Crypto is LIMITED for regulated crypto venue procurement, but crypto-CFD trading inside the Match-Trader platform is a different procurement decision).
Multi-tenant configuration for hybrid operators. The Match-Trader CRM multi-tenant capability covered in the broker CRM deep dive extends to Match-Trader platform deployments. Hybrid operators procuring Match-Trader as the shared platform with broker-ID separation gain multi-tenant CRM integration as part of the procurement.
Bundled risk management and IB modules. Match-Trade Technologies’ platform comes with bundled risk management and IB modules. The procurement-relevant question is whether the bundled modules are sufficient or whether specialist procurement (per the risk management deep dive and IB management deep dive) is appropriate at the operator’s scale tier.
Sirix and other bundled platform options
The bundled platform layer covers Leverate’s Sirix and other vendor-bundled options:
Sirix (Leverate) continues with the same positioning as Phase 1 coverage. Sirix is procurement-appropriate for operators using the broader Leverate stack (LXSuite CRM, Leverate liquidity, Leverate prop firm tech for hybrid operators). The dual lock-in to the Leverate platform plus CRM plus stack is the procurement-relevant decision; operators wanting flexibility should consider non-Sirix alternatives.
Quadcode platforms continue with positioning as the bundled CFD platform layer for Quadcode-anchored operators. The Phase 2 turnkey chapter covered Quadcode at suite level; the platform layer is procurement-relevant for operators specifically wanting Quadcode’s CFD platform without the full turnkey suite.
Soft-FX platforms similarly positioned as bundled CFD platform within the Soft-FX stack. Procurement-relevant for operators wanting Soft-FX’s broader CFD plus crypto platform set.
B2Broker’s stack does not include a proprietary CFD trading platform; B2Broker bundles MT4, MT5, and cTrader integration with B2Core CRM. The procurement decision for B2Broker-anchored operators is between MT4/MT5 and cTrader as the actual trading platform; B2Broker provides the surrounding stack.
The procurement-relevant implication across bundled platform options is that the decision is rarely about the platform feature set in isolation; it is about the broader stack the platform anchors. Operators procuring Sirix, Quadcode platforms, or Soft-FX platforms should evaluate the full stack value rather than the platform layer alone.
TradingView-powered emerging category
TradingView-powered broker deployments have emerged as a procurement-relevant category through 2024-2025. The 2026 state:
TradingView’s broker partnership program. TradingView operates a broker partnership program that enables brokers to integrate TradingView’s charting interface with the broker’s execution back-end. The integration is not a TradingView product; it is a TradingView-powered broker deployment where the broker retains responsibility for execution, risk management, and regulatory positioning while clients trade through a TradingView-branded interface.
The procurement decision shape. The TradingView-powered deployment is procurement-relevant for operators wanting to leverage TradingView’s brand recognition and charting strength with their retail client segments. The integration is typically deployed alongside MT5 or cTrader (operators offer TradingView as a differentiated client experience layer; MT5 or cTrader as the primary platform) rather than as a primary platform replacement. The procurement-relevant question is whether the differentiated client experience justifies the integration cost.
Vendor ecosystem. Multiple vendors have emerged offering TradingView integration assistance to brokers including platform vendors offering native TradingView compatibility (Match-Trader’s TradingView integration; cTrader’s TradingView integration). The procurement-relevant implication is that operators with existing Match-Trader or cTrader procurement can extend to TradingView-powered client experience with relatively modest additional procurement; operators without existing platform infrastructure face higher integration costs.
Procurement timing. TradingView-powered procurement is currently a Year-2 deferred decision for most mid-market operators rather than a Year-1 primary procurement. Operators considering TradingView-powered deployment in 2026 should treat it as an addition to existing MT5 or cTrader procurement rather than as a primary platform replacement.
Per-archetype platform fit
The four operator archetype dispatches surfaced platform procurement implicitly. The 2026 explicit framing:
CySEC CFD broker (Archetype A). Default MT4/MT5 procurement; cTrader as Year-2 differentiation. TradingView-powered Year-3 if client segment justifies. Match-Trader as primary procurement only if Match-Trader CRM is the procurement anchor.
DMCC plus VARA UAE broker (Archetype B). Default MT5 with Arabic and Hindi localisation procurement; cTrader for differentiated experience. crypto-CFD on Match-Trader for VARA-side procurement (separate from CASP-supervised crypto exchange WL procurement). TradingView-powered Year-2 procurement.
Hybrid prop firm plus broker (Archetype C). Default shared MT5 with broker-ID separation; per the hybrid archetype dispatch and the broker-ID segmentation procurement filter. cTrader on the broker side for differentiated experience if client segment justifies. Match-Trader procurement appropriate if operator wants Match-Trader CRM multi-tenant capability.
CASP under MiCAR (Archetype D). Trading platform procurement is the crypto exchange WL chapter decision rather than the alt-WL or MetaTrader chapter decision. CASPs do not procure MT4/MT5/cTrader/Match-Trader/Sirix as the CASP trading venue; the crypto exchange WL vendor provides the venue infrastructure.
Three procurement implications for 2026 operators
The above produces three concrete procurement implications:
Implication 1: New broker procurement should default to MT5 with explicit MT4 justification required if MT4 is selected. The MT4 to MT5 migration has matured; MT5 is the procurement-relevant default for new broker deployments. Operators selecting MT4 should document explicit justification (EA compatibility for a target trader segment, regional preference, legacy ecosystem requirements) rather than defaulting to MT4 because of historical familiarity. The procurement decision shape has shifted from “MT4 by default, MT5 by exception” to “MT5 by default, MT4 by exception” between 2022 and 2026.
Implication 2: cTrader procurement is the strongest alt-WL decision for institutional-leaning CySEC operators. The Spotware Store published pricing model, native cTrader Copy integration, multi-asset coverage including crypto-asset, and institutional execution mechanics distinguish cTrader from competitors. Operators wanting differentiated institutional positioning beyond the MT5 default should procure cTrader at Year-2 as a parallel platform deployment alongside MT5; full platform replacement is not procurement-appropriate for most operators.
Implication 3: TradingView-powered deployment is currently a Year-2-or-later decision rather than primary procurement. The category has emerged as procurement-relevant but the procurement decision shape is addition to existing MT5 or cTrader infrastructure rather than primary platform replacement. Operators considering TradingView-powered deployment in Year 1 procurement should evaluate whether the differentiated client experience justifies the integration cost; for most mid-market operators the answer is to defer to Year-2 or Year-3 after the primary platform procurement is operational.
What comes next in the per-pillar series
Eight per-pillar dispatches shipped (payments, RegTech, crypto exchange WL, LP procurement, risk management, broker CRM, IB management, trading platform). The remaining per-pillar candidates with built-up editorial signal:
- Broker analytics and market signals deep dive. The Phase 2 chapter covered the segment at category level; the vendor refresh dispatch noted FXStreet’s acquisition by ATFX and the broader 2025-2026 consolidation activity. A per-pillar dispatch would extend coverage with the trader-facing widget versus institutional data feed procurement distinction surfaced across the archetype dispatches.
- KYC and AML segment consolidation. Several pending KYC vendor mergers are expected to close in 2026 H2. A per-pillar dispatch covering the consolidated landscape will be appropriate once the M&A activity has settled.
- Copy and social trading deep dive. The Phase 2 chapter covered the segment with multiple verdicts including LIMITED for FXJunction. A per-pillar dispatch would extend coverage of the network-vs-platform-native architectural decision plus the toxic-signal-provider clawback procurement question that the chapter surfaced.
Beyond per-pillar dispatches, the Phase 3 roadmap also includes the M&A and positioning refresh sub-series and new operator archetype dispatches.
If you operate a broker stack with active trading platform procurement and the framing above does not match your direct procurement reality, that is the editorial signal we are looking for. The corpus improves through ground-truth from operators.