DISPATCH ·

Alternative white-label platforms procurement evaluation toolkit (Phase 4 per-pillar artefact)

Thirty-ninth dispatch. Thirteenth per-pillar Phase 4 evaluation toolkit. Operationalises the alt-WL platforms deep dive's procurement filters: per-jurisdiction procurement extension beyond Phase 1 Cyprus framing (DMCC leverage 1:200-500 + Arabic/Hindi localisation, FCA RTS 27 confirmation, ASIC AU residency hosting); six multi-asset depth tiers as procurement filter; four customisation envelope dimensions (branding + UX + workflow + integration); the alt-WL-as-second-platform pattern confirmed across all four archetypes. Covers cTrader, Match-Trader, Sirix, and other alt-WL platforms as secondary platform procurement alongside operator's primary MT5 deployment.

tags · phase-4 · alt-wl-platforms · evaluation-toolkit · operational-artefact

Why this dispatch exists

This is the thirty-ninth dispatch and the fourteenth in the Phase 4 operationally-actionable artefact sub-series. The alt-WL platforms deep dive covered the per-jurisdiction extension beyond Phase 1 Cyprus framing, the six multi-asset depth tiers, the four customisation envelope dimensions, and the alt-WL-as-second-platform procurement pattern. This toolkit operationalises the procurement-stage RFP filters for operators procuring alt-WL platforms alongside their primary MT5 deployment.

Alt-WL procurement scope recap

The procurement scope spans:

cTrader (Spotware). Strongest alt-WL for institutional-leaning CFD procurement; Spotware Store published pricing benchmark.

Match-Trader. Broker-friendly alt-WL with crypto-CFD strength and Match-Trader CRM multi-tenant integration.

Sirix (Leverate). Bundled-platform positioning within Leverate stack with dual lock-in.

Other Phase 1 alt-WL vendors. TradingView-powered emerging category as Year-2-or-later addition.

Procurement-stage questionnaire (30 RFP questions)

Universal (5)

  1. Provide pricing structure including licensing fees, per-user pricing if applicable, integration costs.
  2. List certifications including ISO 27001, SOC 2 Type II.
  3. Describe customer support framework.
  4. Provide financial position disclosure.
  5. Describe product roadmap.

Per-jurisdiction extension dimensions (6, beyond Phase 1 CySEC)

  1. Describe per-regulatory-regime leverage cap configurability including specific support for ESMA 1:30 (CySEC), DMCC 1:200-500, FCA, ASIC 1:30, MAS 1:20, FSA 1:25, Korea 1:10.
  2. Describe Arabic and Hindi localisation depth (DMCC-relevant) including UI translation completeness, content translation quality, and RTL layout support for Arabic.
  3. Describe FCA SUP 17 RTS 27 best execution reporting capability with specific format confirmation.
  4. Describe AU residency hosting capability for ASIC operators with specific hosting geography confirmation.
  5. Describe Asian-language depth (Mandarin simplified/traditional, Cantonese, Japanese, Korean) for APAC operators.
  6. Describe Spanish and Brazilian Portuguese distinct localisation tracks for LATAM operators.

Multi-asset depth dimensions (6 tiers, 4 questions)

  1. Describe multi-asset coverage across the six tiers: FX-only / FX + CFDs indices + commodities (baseline) / FX + CFDs + single-stock CFDs / FX + CFDs + options / FX + CFDs + crypto-CFD / full multi-asset (ETFs + bonds + futures).
  2. (For single-stock CFDs) Describe corporate action handling including dividend handling, stock split handling, short-availability handling.
  3. (For options) Describe options trading capability including Greeks display, options chains, expiry handling.
  4. (For crypto-CFD) Describe crypto-CFD versus VARA-supervised crypto venue regulatory separation.

Customisation envelope dimensions (4)

  1. Describe branding customisation depth including logo placement, colour scheme configuration, custom domain hosting, client cabinet branding.
  2. Describe UX customisation depth including custom widget placement, dashboard configuration per user role, custom workflow definitions.
  3. Describe workflow customisation including custom order types, custom risk control workflows, custom client communication flows.
  4. Describe integration customisation including CRM, KYC, PSP, analytics, copy trading integration methodology.

Alt-WL-as-second-platform dimensions (4)

  1. Describe alt-WL-as-second-platform positioning including integration with operator’s primary MT5 deployment and consolidated operator-side reporting.
  2. Describe cross-platform CRM integration if applicable.
  3. Describe cross-platform risk management aggregation.
  4. Describe per-platform LP routing if applicable.

Vendor-specific dimensions (4)

  1. (cTrader) Describe Spotware Store published pricing positioning and operator-side per-trader cost calculation.
  2. (cTrader) Describe native cTrader Copy integration including tier-1 CySEC reference deployments.
  3. (Match-Trader) Describe Match-Trader CRM multi-tenant integration tightness.
  4. (Sirix) Describe Leverate stack lock-in implications.

Phase 4 framework alignment (3)

  1. How does your product align with the alt-WL-as-second-platform procurement pattern?
  2. How does your product handle operator’s specific archetype customisation including per-archetype weight multipliers?
  3. Describe contract terms including pricing escalation, contract length, data portability.

Reference customer questions (14)

Operational reality (6)

  1. How long has your operation been using this platform and at what client account scale?
  2. Did capability disclosure match operational reality? Specifically: multi-asset depth gaps, customisation envelope limits, integration gaps.
  3. How does platform perform at production scale including order processing latency and platform stability?
  4. (Per-jurisdiction operations) How clean is per-regulatory-regime leverage cap configuration in operational reality?
  5. (For multi-language deployments) How accurate is localisation depth for specific languages?
  6. How responsive is vendor to regulatory developments?

Procurement specifics (4)

  1. How did vendor handle procurement decision process?
  2. What contract terms did you achieve?
  3. (For Sirix) How did Leverate stack lock-in affect operational flexibility in retrospect?
  4. (For cross-vendor configurations) How did loose-coupling integration hold up across platform version upgrades?

Operational quality (4)

  1. (For multi-asset deployments) How accurate is multi-asset coverage in operational reality?
  2. (cTrader) How accurate is Spotware Store pricing positioning?
  3. (Match-Trader) How clean is Match-Trader CRM integration tightness?
  4. Would you procure this platform again given the same procurement decision context?

Demo evaluation rubric (10 tests)

Test 1: Per-regulatory-regime leverage cap configuration demonstration.

Pass: platform demonstrates per-regulatory-regime leverage configuration across operator’s specific jurisdiction set. Fail: leverage configuration hardcoded.

Test 2: Multi-language localisation demonstration with operator-specific language set.

Pass: platform demonstrates native translation depth including RTL Arabic if applicable. Fail: localisation gaps.

Test 3: Multi-asset depth demonstration across operator’s instrument set.

Pass: platform demonstrates coverage across operator’s specific instrument set with concrete examples. Fail: instrument coverage gaps.

Test 4: Customisation envelope demonstration with operator-provided branding.

Pass: platform demonstrates branding, UX, workflow, and integration customisation with operator assets. Fail: customisation envelope limited.

Test 5: Alt-WL-as-second-platform integration walkthrough.

Pass: platform demonstrates integration with operator’s primary MT5 deployment. Fail: cross-platform integration absent.

Test 6: cTrader Spotware Store pricing demonstration.

Pass: cTrader demonstrates published pricing structure with operator-side cost calculation. Fail: pricing positioning opaque.

Test 7: Match-Trader CRM multi-tenant integration demonstration.

Pass: Match-Trader demonstrates CRM multi-tenant capability. Fail: CRM integration shallow.

Test 8: TradingView-powered deployment demonstration (if procurement).

Pass: platform demonstrates TradingView-powered integration as Year-2 addition. Fail: TradingView integration shallow.

Test 9: Performance testing at operator’s expected production volume.

Pass: platform demonstrates stability at operator’s expected production volume. Fail: performance degradation.

Test 10: Disaster recovery and incident response demonstration.

Pass: platform demonstrates incident response framework. Fail: framework absent.

Integration testing protocol (8 pre-signature tests)

  1. Platform deployment in operator’s specific environment.
  2. Multi-asset configuration testing across operator’s instrument set.
  3. Per-regulatory-regime leverage configuration testing.
  4. Cross-platform integration testing with operator’s primary MT5 deployment.
  5. CRM integration testing.
  6. LP integration testing.
  7. Multi-language client cabinet testing.
  8. End-to-end production simulation including pre-market, market opening, intraday trading.

Integration testing typically 6-12 weeks for alt-WL platform deployments because cross-platform integration with operator’s primary MT5 deployment is non-trivial.

Decision documentation template (8 sections)

  1. Procurement context including alt-WL-as-second-platform rationale and per-archetype platform fit.
  2. Vendor shortlist per category.
  3. RFP evaluation per platform with per-jurisdiction extension scoring.
  4. Reference customer diligence including operational reality for multi-asset depth and customisation envelope.
  5. Demo evaluation per platform.
  6. Integration testing including cross-platform integration testing documentation.
  7. Procurement decision with primary-versus-secondary platform decision rationale.
  8. Ongoing monitoring with vendor M&A and per-jurisdiction regulatory shifts as procurement decision review triggers.

Phase 4 corpus state

  • 25 Phase 3 + 14 Phase 4 = 39 dispatches.