Why this dispatch exists
This is the nineteenth Phase 3 dispatch and the thirteenth 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, IB management, trading platform, broker analytics, copy trading, turnkey suites, and prop firm tech. This one covers Chapter II alternative white-label platforms.
The alt-WL chapter was the Phase 1 chapter anchored to Cyprus and CySEC jurisdictional regulatory framing. The Phase 1 coverage was deep on the CySEC procurement context and covered the 10 alt-WL vendors at category level. Two procurement-relevant signals have accumulated since the Phase 1 research that warrant a per-pillar dispatch. First, the archetype synthesis arc surfaced that alt-WL procurement is rarely a platform-replacement decision; the pattern across all four archetypes is alt-WL alongside MT5 as a differentiated client experience layer. Second, the trading platform deep dive covered the platform layer broadly including the MT4 versus MT5 default-flip and the TradingView-powered emerging category, but did not cover the alt-WL vendor mix at the procurement-action-stage detail per jurisdiction.
This dispatch covers the alt-WL procurement landscape state in 2026, the per-jurisdiction extension (how the alt-WL chapter procurement maps to DMCC, FCA, ASIC operator contexts beyond the CySEC lens), the Phase 1 vendor list refreshed for 2026 procurement-relevant positioning, the multi-asset depth dimension, the customisation envelope dimension, the alt-WL-as-second-platform procurement pattern at action-stage detail, and three procurement implications for 2026.
The alt-WL procurement landscape state in 2026
Three structural realities shape alt-WL procurement through 2026:
Alt-WL is rarely a primary platform decision; the pattern is alt-WL alongside MT5 as a differentiated client experience layer. The CySEC archetype dispatch described this pattern; the trading platform deep dive reinforced it. Operators procuring alt-WL platforms in 2026 should typically expect to run the alt-WL alongside MT5 rather than replacing MT5. Some institutional-leaning operators run cTrader as the primary platform with MT5 as the secondary; some operators run Match-Trader as the primary platform for the crypto-CFD and hybrid use cases. The pure-alt-WL primary platform configuration is rare and typically requires specific procurement justification.
The vendor positioning has stabilised through 2025-2026. The alt-WL chapter vendor positioning has not consolidated or expanded materially since the Phase 1 research. cTrader continues strengthening as the institutional-leaning option; Match-Trader continues strengthening as the broker-friendly option with crypto-CFD strength; Sirix continues with bundled-platform positioning within the Leverate stack; smaller alt-WL options continue with niche positioning. The procurement-relevant 2026 implication is that the Phase 1 chapter vendor evaluation framework continues to apply with minor adjustments rather than requiring fresh research across the vendor set.
Per-jurisdiction procurement implications vary materially. The Phase 1 Cyprus and CySEC anchoring covered the EU procurement context with depth. DMCC operators procuring alt-WL face different procurement context including UAE retail leverage policy compatibility, Arabic and Hindi localisation requirements, and the crypto-CFD versus VARA-supervised crypto venue separation question. FCA operators face FCA-specific best execution disclosure requirements that alt-WL platforms handle with varying depth. ASIC operators face AU residency requirements for in-scope client data that affect platform hosting decisions. The per-jurisdiction extension is the primary procurement-relevant extension of the Phase 1 coverage.
Per-jurisdiction procurement extension
The Phase 1 chapter framed alt-WL procurement with a CySEC lens. The 2026 per-jurisdiction extension:
CySEC procurement context (Phase 1 anchor). The Phase 1 chapter covered the CySEC procurement context with depth. The procurement-relevant CySEC framework includes MiFID II best execution reporting (RTS 27 and equivalent), ESMA retail leverage caps configuration, EU data residency, and the August 2025 CySEC sanctions regime considerations covered in the CySEC archetype dispatch. The Phase 1 vendor evaluation applies cleanly.
DMCC procurement context. DMCC operators face materially different procurement context. UAE retail leverage policy is more permissive than ESMA retail caps (typically 1:200 to 1:500 on majors depending on broker risk policy); the alt-WL platform must support per-regulatory-regime leverage configuration without hardcoded ESMA defaults. Arabic and Hindi localisation requirements are procurement-relevant for the typical DMCC client geography; the alt-WL platform native language coverage varies. The crypto-CFD versus VARA-supervised crypto venue separation question (covered in the crypto exchange WL consolidation dispatch) is procurement-relevant for DMCC operators considering Match-Trader with crypto-CFD versus separate CASP-supervised venue procurement. The DMCC archetype dispatch flagged these procurement dimensions.
FCA procurement context. FCA operators face FCA SUP 17 RTS 27 best execution reporting requirements that vary in vendor handling. The procurement-relevant question is whether the alt-WL platform generates supervisor-ready RTS 27 reports or requires manual adjustment. cTrader handles RTS 27 reporting natively in CySEC-aligned deployments; FCA deployments require explicit confirmation that the reporting format meets FCA expectations. Match-Trader, Sirix, and other alt-WL platforms similarly handle RTS 27 with varying depth.
ASIC procurement context. ASIC operators face AU residency requirements for in-scope client data that affect platform hosting. The procurement-relevant question is whether the alt-WL platform supports AU-resident hosting natively or requires Sydney-region deployment from the operator with explicit configuration. cTrader’s Tokyo (TY3) data centre presence is closer to AU than European deployments but still requires explicit confirmation for ASIC residency compliance. Match-Trader and other vendors require similar per-jurisdiction confirmation.
The procurement-relevant implication is that the Phase 1 vendor evaluation framework applies across jurisdictions but with per-jurisdiction extensions that operators should request explicitly during procurement rather than accepting category-level vendor positioning.
The Phase 1 vendor list refreshed for 2026 procurement
The Phase 1 chapter covered 10 alt-WL platforms with CySEC framing. The 2026 procurement-relevant positioning:
cTrader (Spotware) continues as the strongest alt-WL procurement option for institutional-leaning CFD broker procurement. The Phase 1 verdict held; the trading platform deep dive covered the 2026 positioning. The Spotware Store published pricing model is the chapter’s published pricing benchmark; native cTrader Copy with tier-1 CySEC reference deployments; multi-asset coverage including crypto-asset; institutional execution mechanics. Procurement-appropriate for CySEC, DMCC, and hybrid operators wanting institutional positioning.
Match-Trader (Match-Trade Technologies) continues as the strongest broker-friendly alt-WL procurement option with crypto-CFD strength and Match-Trader CRM multi-tenant integration. The Phase 1 verdict held; the trading platform deep dive and broker CRM deep dive covered the 2026 positioning. Procurement-appropriate for operators with crypto-CFD or hybrid use cases.
Sirix (Leverate) continues with the bundled-platform positioning within the Leverate stack. The Phase 1 verdict held; the procurement decision is the dual lock-in to the Leverate stack rather than the Sirix platform features alone. Procurement-appropriate for operators committed to the broader Leverate stack.
TradingView-powered deployments are the emerging category covered in the trading platform deep dive. Not a single Phase 1 vendor but a category of broker deployments using TradingView’s charting interface plus trade execution integration. Procurement-appropriate as a Year-2-or-later addition to existing MT5 or cTrader procurement rather than as primary platform replacement.
Other Phase 1 alt-WL vendors continue with the Phase 1 verdicts. Most remain procurement-appropriate within their original Phase 1 framing; the 2026 procurement-relevant question is per-jurisdiction extension rather than fresh vendor evaluation.
The multi-asset depth dimension
Multi-asset depth varies materially across the alt-WL vendor set and is a procurement-relevant dimension that the Phase 1 chapter covered partially. The 2026 procurement-action-stage framing:
FX-only coverage. Some alt-WL platforms cover FX with depth but offer limited or no support for CFDs on stocks, indices, commodities, options, futures, or crypto-asset. The procurement-relevant question is whether the operator’s product set extends beyond FX; FX-only platforms are procurement-appropriate only for pure FX brokers.
FX plus CFDs on indices and commodities. The typical alt-WL coverage extends to FX plus CFDs on major indices (US500, NAS100, FTSE, DAX) and major commodities (gold, oil). The procurement-relevant implication is that this is the baseline alt-WL coverage that most CFD broker operators expect; vendors not covering this baseline are procurement-inappropriate for standard CFD broker procurement.
FX plus CFDs on indices plus commodities plus single-stock CFDs. Some alt-WL platforms extend to single-stock CFDs (typically the major US, European, and Asian listed names). The procurement-relevant question is whether the operator’s client segment trades single-stock CFDs; if yes, the platform must support the operator’s expected single-stock CFD coverage including corporate actions, dividend handling, and short-availability handling.
FX plus CFDs plus options. Some alt-WL platforms extend to options trading (typically index options and major equity options). The procurement-relevant question is whether the operator’s client segment trades options; option-trading clients are typically more sophisticated and the platform must support options-specific functionality (Greeks display, options chains, expiry handling).
FX plus CFDs plus crypto-asset. Many alt-WL platforms extend to crypto-asset CFD trading. The procurement-relevant question (covered in the crypto exchange WL consolidation dispatch) is whether crypto-CFD trading inside the alt-WL platform meets the operator’s regulatory positioning versus requiring separate CASP-supervised crypto venue procurement.
Full multi-asset coverage. Some alt-WL platforms cover the full multi-asset set including ETFs, bonds, futures, and broader derivatives. The procurement-relevant implication is that full multi-asset platforms are typically positioned for diversified-asset operators (institutional-leaning brokers serving sophisticated client segments) rather than retail CFD broker operations.
The procurement-relevant implication is that operators should explicitly evaluate multi-asset depth against the operator’s specific product set rather than accepting vendor positioning at category level. The Phase 1 chapter covered this dimension at category level; the 2026 procurement-stage RFP should request per-instrument-group capability disclosure.
The customisation envelope dimension
Customisation envelope is the procurement dimension that operators commonly underspecify. The 2026 procurement-action-stage framing:
Branding customisation. The alt-WL platform must support operator branding including logo placement, colour scheme configuration, custom domain hosting, and client cabinet branding integration. Most alt-WL vendors handle branding at category level; the procurement-relevant question is depth (can operators customise specific UX elements beyond the standard branding configuration set).
UX customisation. The alt-WL platform should support UX customisation beyond branding including custom widget placement, custom dashboard configuration per user role, and custom workflow definitions for specific client segments. Vendor differentiation on UX customisation is meaningful; some vendors support deep customisation while others restrict customisation to the standard configuration set.
Workflow customisation. Some alt-WL platforms support custom workflow definitions including custom order types, custom risk control workflows, and custom client communication flows. The procurement-relevant question is whether the operator’s specific workflow requirements are supported natively or require platform-vendor engineering investment.
Integration customisation. The alt-WL platform must support integration with the operator’s specific CRM, KYC vendor, PSP set, and analytics products. The procurement-relevant question (covered in the broker CRM deep dive and the trading platform deep dive) is whether the integration is native (vendor-supported), API-based (vendor-supported with operator-side integration work), or manual (operator-built integration without vendor support).
The procurement-relevant implication is that customisation envelope should be evaluated explicitly at procurement-stage RFP. Operators that procure on category-level vendor positioning typically discover customisation gaps in Year 1 operational testing.
The alt-WL-as-second-platform procurement pattern
The Phase 3 archetype dispatches surfaced that alt-WL procurement is rarely a primary platform decision. The 2026 procurement-action-stage framing:
The pattern. Most operators procuring alt-WL platforms run the alt-WL alongside MT5 as a secondary differentiated client experience layer. cTrader as the institutional-leaning secondary; Match-Trader as the crypto-CFD or multi-tenant secondary; TradingView-powered deployment as the differentiated client experience addition.
The procurement decision shape. The procurement decision is which secondary platform to add to existing MT5 procurement rather than which platform to procure as primary. The decision should be informed by the operator’s specific client segment requirements: institutional-leaning client segments benefit from cTrader; crypto-CFD or hybrid client segments benefit from Match-Trader; differentiated client experience client segments benefit from TradingView-powered deployment.
Per-archetype pattern. Archetype A (CySEC CFD): MT5 primary plus cTrader Year-2 secondary. Archetype B (DMCC plus VARA): MT5 primary plus cTrader secondary plus crypto-CFD on Match-Trader for VARA-side. Archetype C (hybrid): shared MT5 with broker-ID separation; cTrader on broker side for differentiation; Match-Trader procurement appropriate if operator wants Match-Trader CRM multi-tenant capability. Archetype D (CASP): not applicable; crypto exchange WL procurement layer instead.
Multi-platform procurement complexity. Operators procuring multiple platforms simultaneously face complexity including CRM integration across platforms (covered in the broker CRM deep dive), risk management aggregation across platforms (covered in the risk management deep dive), and per-platform LP routing (covered in the LP procurement deep dive). The procurement-relevant implication is that multi-platform procurement is a multi-quarter integration project; operators should plan the multi-platform procurement explicitly rather than treating each platform as a separate procurement decision.
Three procurement implications for 2026 operators
The above produces three concrete procurement implications:
Implication 1: Alt-WL procurement is typically a secondary-platform decision; plan the alt-WL alongside MT5 procurement as multi-platform integration rather than as separate decisions. The pattern across all four operator archetypes is alt-WL alongside MT5 rather than alt-WL replacing MT5. The procurement decision should be informed by which alt-WL fits the operator’s specific client segment requirements as a secondary differentiated experience layer. The multi-platform integration is a multi-quarter project that should be planned at procurement-time.
Implication 2: Per-jurisdiction procurement extension is required beyond the Phase 1 CySEC framing. Operators procuring alt-WL outside Cyprus should explicitly request per-jurisdiction capability disclosure including leverage policy configuration (DMCC), Arabic and Hindi localisation depth (DMCC), RTS 27 reporting format (FCA), and AU residency hosting (ASIC). The Phase 1 vendor evaluation framework applies but with per-jurisdiction extensions that operators should request explicitly during procurement.
Implication 3: Multi-asset depth and customisation envelope are procurement-stage RFP filters, not Year-2 deferred decisions. Operators that procure on category-level vendor positioning typically discover multi-asset depth gaps and customisation envelope limits in Year 1 operational testing. The procurement-stage RFP should request per-instrument-group capability disclosure, branding customisation depth, UX customisation depth, workflow customisation capability, and integration customisation methodology. Operators that defer these evaluations to Year 1 operational testing produce reactive procurement decisions that the Phase 1 vendor evaluation framework was specifically designed to avoid.
What comes next in the per-pillar series
Thirteen per-pillar dispatches shipped. The remaining per-pillar candidate with built-up editorial signal is:
- 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.
The per-pillar deep-dive sub-series will close at fourteen dispatches with the KYC consolidation dispatch when the H2 2026 M&A activity has settled enough to warrant the editorial coverage. Beyond the per-pillar sub-series, the Phase 3 roadmap pivots to:
- Additional vendor refresh cycles. The first refresh dispatch covered six events; future refresh dispatches will be triggered by accumulated signal rather than scheduled cadence.
- New operator archetype dispatches. Candidates include CASP plus CFD broker hybrid under EU regulation, ADGM FSRA institutional broker, and LATAM or APAC CFD broker if procurement-relevant signal accumulates.
- Cross-pillar synthesis updates. The cross-archetype matrix dispatch may receive periodic updates as vendor positioning shifts accumulate.
If you operate a broker stack with active alt-WL procurement consideration 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.