DISPATCH ·

Brokerage hosting procurement evaluation toolkit (Phase 4 per-pillar artefact)

Thirty-second dispatch. Sixth per-pillar Phase 4 evaluation toolkit. Operationally-actionable artefact for Chapter XIV brokerage hosting procurement covering the foundational layer that constrains every other procurement decision. Unique characteristics: 3-7 year colo contract terms make hosting procurement decisions especially consequential and especially difficult to reverse; multi-IBX procurement from Day 1 for institutional Archetype H; per-jurisdiction data residency procurement filter; cross-connect provisioning timelines; DR and business continuity SLAs tied to FCA SYSC operational resilience and MiFID II Article 16 expectations; separate retail VPS partner procurement for client-facing operations. The toolkit covers institutional colo procurement, low-latency network procurement, broker platform managed hosting procurement, and retail VPS partner procurement separately.

tags · phase-4 · brokerage-hosting · colo · evaluation-toolkit · operational-artefact

Why this dispatch exists

This is the thirty-second dispatch and the seventh in the Phase 4 operationally-actionable artefact sub-series. The earlier Phase 4 dispatches covered the RFP scoring framework opener, KYC, RegTech, broker CRM, LP procurement, and payments procurement evaluation toolkits. This dispatch covers the sixth per-pillar evaluation toolkit: brokerage hosting procurement.

Brokerage hosting procurement is the foundational layer that constrains every other procurement decision. The brokerage hosting deep dive and the earlier Phase 1 hosting framework covered the per-jurisdiction data residency requirements (CySEC EU residency, FCA UK preference, DMCC UAE-onshore for VARA-aligned firms, ASIC AU residency, per-jurisdiction APAC residency from MAS, SFC, FSA, KFSC), the institutional colo procurement at LD4/NY4/TY3/FR2/HK1/SG1/DX1/DX2, the low-latency network layer between IBXs, the broker platform managed hosting layer for MT4/MT5 server clusters, the retail VPS partner procurement for client-facing operations, and the institutional Archetype H requirement for multi-IBX procurement from Day 1.

The 2026 procurement-relevant question for hosting spans four distinct procurement decisions: institutional colo procurement (operator’s own broker stack hosting), low-latency network procurement (connectivity between IBXs for cross-region trading), broker platform managed hosting procurement (specialist MT4/MT5 server cluster hosting), and retail VPS partner procurement (operator-recommended VPS for clients running EAs). Each procurement decision has distinct evaluation criteria; the toolkit below covers them separately.

The unique characteristic of hosting procurement among the Phase 4 toolkits is contract length: 3-7 year terms at colo make hosting procurement decisions especially consequential because operator switching costs at the hosting layer are materially higher than at the application layer. Operators should treat hosting procurement with appropriate gravity rather than as routine vendor procurement.

Brokerage hosting procurement scope recap

The brokerage hosting procurement scope spans four distinct procurement decisions:

Institutional colo procurement. Operator’s own broker stack hosting at IBXs relevant to the operator’s regulatory positioning and LP execution profile. Equinix LD4 (London FX primary), NY4/NY5/NY6 (Secaucus US trading), TY3 (Tokyo), FR2 (Frankfurt EU residency), HK1 (Hong Kong), SG1 (Singapore APAC), DX1/DX2 (Dubai UAE residency), AM3 (Amsterdam EU redundancy), SY3 (Sydney AU residency). Beeks Group at FR2 plus other IBXs for managed compute alternative. Universal procurement requirement.

Low-latency network procurement. Connectivity layer between IBXs for operators running cross-region trading. Avelacom, Lucera, TNS/Waypoint Trading Solutions. Procurement-relevant for institutional cross-region operations including hybrid Archetype C with cross-jurisdiction operations and institutional Archetype H with multi-IBX deployment.

Broker platform managed hosting procurement. Specialist MT4/MT5 server cluster hosting for operators not running infrastructure in-house. Commercial Network Services (CNS) at $35-70/month published pricing; Pulsant for UK sovereign data residency at 12 UK DCs. Procurement-relevant for lean-to-mid-market CFD broker operations.

Retail VPS partner procurement. Operator-recommended VPS partners for client-facing operations (clients running EAs need stable low-latency VPS). ForexVPS.net (40+ broker integrations, broker partnership program, EUR 22-44/month); ChartVPS (SOC 2 Type I, $50-450/month across tiers); FXVM (ThinkHuge HK entity creates GDPR Article 46 SCC requirement for EU broker partnerships). Procurement-relevant across all CFD-touching archetypes.

The toolkit below covers institutional colo as the primary procurement; low-latency network, broker platform managed hosting, and retail VPS partner procurement follow secondary procurement frameworks with abbreviated evaluation criteria.

Procurement-stage questionnaire template

The questionnaire template includes 33 specific RFP questions structured by procurement component plus framework dimension.

Universal dimensions (5 questions per the Phase 4 opener)

  1. Provide your pricing structure including per-cabinet pricing, per-cross-connect pricing, per-kW power pricing, optional managed services pricing, and ongoing contract escalation methodology.
  2. List your relevant certifications including SOC 2 Type II, ISO 27001, PCI DSS where relevant, Cyber Essentials Plus for UK operations, and jurisdiction-specific certifications.
  3. Describe your customer support structure including dedicated technical account management, 24/7 support availability for production incidents, and operator-side escalation paths.
  4. Provide your most recent financial position disclosure including public-company filings if applicable (Equinix NASDAQ, Beeks Group LSE AIM) or parent company disclosure framework.
  5. Describe your product roadmap including IBX expansion plans, technology investments, and operator-relevant infrastructure roadmap.

Institutional colo dimensions (10 questions)

  1. List your IBX presence including specific data centres relevant to operator’s regulatory positioning (LD4, NY4/NY5/NY6, TY3, FR2, HK1, SG1, DX1/DX2, AM3, SY3, others).
  2. Describe per-jurisdiction data residency capability including specific IBXs that satisfy operator’s regulatory framework data residency requirements.
  3. Describe your ecosystem density per relevant IBX including LP presence, ECN presence, exchange presence, and operator-specific counterparty proximity verification.
  4. Describe your cross-connect provisioning timelines including initial provisioning time, expansion provisioning time, and emergency provisioning capability.
  5. Provide cabinet specifications including power density options (typical financial colo at 5-15 kW per cabinet), cooling capability, and physical security framework.
  6. Describe your fiber and copper cross-connect pricing per IBX including installation costs, monthly recurring costs, and bulk pricing options.
  7. Describe your Equinix Fabric or equivalent software-defined cross-connect capability including dynamic provisioning, virtual connections, and API integration.
  8. Describe your bare metal or managed compute options if relevant including operator-side procurement integration.
  9. Describe your incident response framework including outage notification timing, operator-side communication during incidents, and SLA credit framework.
  10. Provide reference operators in similar archetype with deployment scale and operational tenure information per IBX.

Low-latency network dimensions (5 questions)

  1. (Low-latency network procurement, applicable for cross-region operations) List your network coverage including IBXs reached, exchange PoPs covered, and per-region latency characteristics.
  2. Describe your network latency characteristics with operator-specific cross-region requirements including specific IBX-to-IBX latency metrics.
  3. Describe your network reliability framework including redundancy, failover capability, and operator-side incident response.
  4. Describe your API-driven provisioning capability if available (relevant for Lucera SDN positioning, Avelacom programmatic provisioning).
  5. Describe your post-Genesis-Trading institutional positioning if applicable including counterparty exposure framework and operator-side risk mitigation.

Broker platform managed hosting dimensions (5 questions)

  1. (Broker platform managed hosting procurement, applicable for lean-to-mid-market CFD operations) Describe your MT4/MT5 server cluster hosting capability including specific platform versions supported, plugin compatibility, and broker-specific tuning.
  2. Provide your pricing structure including per-server pricing, per-environment pricing, and additional service pricing.
  3. Describe your DR and business continuity framework tied to FCA SYSC operational resilience and MiFID II Article 16 expectations including specific RTO and RPO commitments.
  4. Describe your operator-side migration support if applicable including operator preparation guidance and migration timeline expectations.
  5. Provide reference brokers in operator’s archetype with deployment scale and operational characteristics.

Retail VPS partner dimensions (4 questions)

  1. (Retail VPS partner procurement, applicable for CFD-touching archetypes with client-facing VPS recommendations) List your broker integration list including specific brokers with native broker-server proximity (ForexVPS.net 40+ broker integrations is the chapter benchmark).
  2. Describe your broker partnership program including operator-side sponsorship structures, revenue-sharing arrangements, and operator-side procurement integration.
  3. Describe your operating entity geography including specific entity jurisdiction (ForexVPS.net Wyoming reseller, ChartVPS UK-registered, FXVM ThinkHuge Hong Kong) and GDPR Article 46 SCC implications for EU broker partnerships.
  4. Provide pricing structure for client-facing VPS tiers and operator-side partner program economics.

Phase 4 framework alignment (4 questions)

  1. How does your product address the multi-IBX procurement requirement for institutional Archetype H including cross-IBX consistency and operator-side multi-IBX management framework?
  2. How does your product align with per-jurisdiction data residency requirements across the operator’s specific regulatory framework set?
  3. How does your product support the DR and business continuity expectations under FCA SYSC operational resilience requirements and MiFID II Article 16?
  4. Describe your contract terms including pricing escalation methodology, contract length (3-7 year typical for colo), termination provisions, and data portability on termination.

Reference customer questions

The 16 reference customer questions structure operator-side diligence with hosting-specific emphasis on long-tenure operational reality:

Operational reality (6 questions)

  1. How long has your operation been using this hosting provider and at what deployment scale across which IBXs?
  2. What is your actual uptime in operational reality versus the provider’s SLA commitments? Specifically: unplanned downtime events including breakdown by DC and incident type.
  3. How responsive is the provider’s customer support to operational incidents? What is the typical resolution time for production issues?
  4. How frequently does the provider deliver planned maintenance? How operator-friendly is the planned maintenance scheduling?
  5. (Multi-IBX deployments) How consistent is the provider’s service across IBXs in operational reality? Have you encountered IBX-specific operational issues?
  6. How frequently do you encounter cross-connect issues including provisioning delays, capacity constraints, or performance degradation?

Procurement specifics (5 questions)

  1. How long did your procurement cycle actually take versus the provider’s pre-contract estimate?
  2. What contract terms did you actually achieve versus the provider’s positioning? Specifically: pricing escalation across renewal, termination flexibility, data portability provisions.
  3. (For colo procurement) How did the provider handle capacity expansion when your operational scale grew? Were expansion timelines met?
  4. Has the provider’s roadmap delivery matched the roadmap visibility provided during procurement?
  5. How transparent is the provider about their financial position and IBX expansion roadmap during ongoing operational relationship?

Operational quality (5 questions)

  1. (For institutional colo) How accurate is the provider’s ecosystem density positioning in operational reality? Specifically: counterparty proximity, cross-connect provisioning timing, ecosystem expansion.
  2. (For DR capability) How did the provider handle disaster recovery scenarios you encountered? Specifically: actual incident response versus framework documentation.
  3. (For multi-IBX deployments) How clean is the provider’s cross-IBX consistency in operational reality? Have you encountered IBX-specific configuration drift?
  4. How responsive is the provider to regulatory developments including FCA SYSC operational resilience requirements implementation, MiFID II Article 16 implementation, or jurisdiction-specific regulatory shifts?
  5. Would you procure this provider again given the same procurement decision context? Why or why not?

Demo evaluation rubric

Hosting procurement demos involve site visits to relevant IBXs, latency testing from operator’s expected counterparty positions, and reference deployment walkthroughs. The 12-test rubric structures operator-side demo evaluation:

Demo Test 1: IBX site visit at operator-specified location.

Pass criteria: provider arranges site visit to operator-specified IBX including physical security framework demonstration, cabinet area inspection, and operator-side question handling. Fail criteria: site visit not arranged; physical security framework opacity; cabinet area access limited.

Demo Test 2: Ecosystem density demonstration at relevant IBX.

Pass criteria: provider demonstrates ecosystem density at operator-relevant IBX including LP presence verification, ECN presence verification, and specific counterparty proximity validation. Fail criteria: ecosystem density opaque; counterparty proximity not verifiable; LP presence list shallow.

Demo Test 3: Latency testing from operator-specified positions.

Pass criteria: provider demonstrates latency characteristics from operator’s expected counterparty positions including cross-connect latency verification and end-to-end latency measurement. Fail criteria: latency testing not provided; cross-connect latency opacity; end-to-end measurement absent.

Demo Test 4: Cross-connect provisioning demonstration.

Pass criteria: provider demonstrates cross-connect provisioning workflow including specific provisioning timeline, fiber routing transparency, and operator-side coordination. Fail criteria: provisioning workflow opaque; timeline estimate absent; operator-side coordination not demonstrated.

Demo Test 5: Multi-IBX deployment walkthrough (institutional Archetype H).

Pass criteria: provider demonstrates multi-IBX deployment patterns including cross-IBX consistency, operator-side multi-IBX management, and consolidated operator-side reporting. Fail criteria: multi-IBX capability shallow; cross-IBX consistency absent; consolidated reporting limited.

Demo Test 6: Low-latency network demonstration.

Pass criteria: low-latency network provider demonstrates IBX-to-IBX latency, network redundancy, and operator-side incident response framework. Fail criteria: latency metrics opaque; redundancy framework absent; incident response shallow.

Demo Test 7: Disaster recovery walkthrough.

Pass criteria: provider demonstrates DR scenarios including secondary site activation, operator-side communication framework, and SLA credit framework. Fail criteria: DR framework opaque; secondary site activation undemonstrated; SLA credit framework absent.

Demo Test 8: SOC 2 Type II audit report walkthrough.

Pass criteria: provider walks through current SOC 2 Type II audit report including specific controls coverage, operator-side compliance support, and operator-side audit access framework. Fail criteria: SOC 2 audit not current; controls coverage limited; operator-side support shallow.

Demo Test 9: Broker platform managed hosting demonstration (broker platform managed hosting procurement).

Pass criteria: provider demonstrates MT4/MT5 server cluster hosting including platform tuning, plugin support, and operator-side migration framework. Fail criteria: platform support shallow; tuning capability absent; migration framework not demonstrated.

Demo Test 10: Retail VPS partner program demonstration.

Pass criteria: VPS partner demonstrates broker integration list, partnership program economics, and operator-side client-facing integration. Fail criteria: broker integration list shallow; partnership economics opaque; client-facing integration not demonstrated.

Demo Test 11: Reference deployment walkthrough.

Pass criteria: provider arranges reference deployment walkthrough with reference operator including operational reality verification, support experience verification, and ongoing relationship verification. Fail criteria: reference deployment not arranged; reference operator response shallow; ongoing relationship verification absent.

Demo Test 12: Incident response simulation.

Pass criteria: provider demonstrates incident response framework simulation including outage notification timing, operator-side communication, and SLA credit application. Fail criteria: incident response framework opaque; notification timing inadequate; SLA credit framework absent.

Integration testing protocol

Hosting integration testing follows a structured pre-go-live framework with explicit milestones across the 3-6 month colo procurement cycle:

  1. Cabinet handover and physical inspection. Operator infrastructure team performs cabinet handover including physical security verification, power verification, and cooling verification.
  2. Cross-connect provisioning testing. Test cross-connect provisioning across operator-required connections including LP cross-connects, ECN cross-connects, and inter-IBX connectivity if applicable.
  3. Latency testing across cross-connects. Verify latency characteristics across operator-required cross-connects with explicit measurement methodology.
  4. Power and cooling testing under expected load. Test power consumption and cooling characteristics at operator’s expected production load including peak load handling.
  5. Network connectivity testing. Test all required network connectivity including LP connectivity, internet connectivity, and operator-side management network connectivity.
  6. Disaster recovery testing. Test DR scenarios including secondary site activation if applicable, operator-side recovery procedures, and SLA credit framework.
  7. Security perimeter testing. Verify physical security perimeter including biometric access, mantrap functionality, and CCTV coverage.
  8. Compliance documentation review. Review provider’s compliance documentation including SOC 2 Type II audit report, ISO 27001 certification, and jurisdiction-specific certifications.
  9. Operational handover preparation. Prepare operational handover documentation including incident response procedures, escalation paths, and operator-side runbook.
  10. End-to-end production simulation. Simulate production trading scenarios from cabinet to LP including order routing latency, market data feed integration, and post-trade reconciliation.

Integration testing typically takes 6-12 weeks for institutional colo deployments including cabinet handover plus cross-connect provisioning plus operational testing. Multi-IBX deployments add 4-8 weeks per additional IBX. Operators should plan accordingly.

Decision documentation template

The decision documentation template structures the operator-side hosting procurement record:

Section 1: Procurement context

  • Operator regulatory positioning and archetype identification
  • Hosting procurement scope (colo + low-latency network + broker platform managed hosting + retail VPS as applicable)
  • Multi-IBX requirement (institutional Archetype H from Day 1; mid-market multi-IBX as scale requires)
  • Procurement timing and decision process
  • Procurement team and roles

Section 2: Provider shortlist per component

  • Colo provider shortlist including specific IBXs evaluated
  • Low-latency network provider shortlist if applicable
  • Broker platform managed hosting provider shortlist if applicable
  • Retail VPS partner shortlist if applicable
  • Initial screening criteria per component

Section 3: RFP evaluation per component

  • Universal dimensions scoring per provider per component
  • Component-specific dimensions scoring
  • Per-archetype customisation applied
  • Disqualification thresholds applied

Section 4: Reference customer diligence

  • Reference customer list per shortlisted provider per component
  • Reference responses summarised
  • Long-tenure operational reality documentation
  • Reference diligence-driven scoring adjustments

Section 5: Demo evaluation

  • Demo dates and IBX site visits per shortlisted provider
  • Demo evaluation rubric results across 12 tests
  • Latency testing documentation
  • Ecosystem density verification documentation
  • Demo-driven scoring adjustments

Section 6: Integration testing

  • Integration testing dates and milestones per component
  • Cabinet handover documentation if colo procurement
  • Cross-connect provisioning documentation
  • Multi-IBX deployment documentation if applicable
  • Capability gaps identified with provider remediation commitments

Section 7: Procurement decision per component

  • Provider selection per component with explicit decision rationale
  • Multi-IBX architecture decision documentation if applicable
  • Contract terms summary per component including 3-7 year colo terms specifically documented
  • Long-term contract risk mitigation framework

Section 8: Ongoing monitoring

  • Operator-side provider performance monitoring framework per component
  • KPI definitions including uptime, incident response, cross-connect performance
  • Provider relationship review cycle (quarterly business review, annual relationship review, 5-year contract review)
  • Procurement decision review triggers (provider M&A, regulatory shifts, capability gaps, IBX expansion limitations)

What comes next in Phase 4

This dispatch provides the sixth per-pillar evaluation toolkit. Future Phase 4 artefacts will extend coverage:

  • Additional per-pillar evaluation toolkits. Broker analytics, copy trading, IB management, trading platform, prop firm tech, alt-WL platforms, crypto exchange WL, risk management, turnkey suites toolkits.
  • Per-archetype RFP templates. Complete RFP templates customised per archetype.
  • Vendor evidence library.
  • Institutional procurement toolkit (Archetype H specific).

Phase 4 corpus state after this dispatch:

  • 25 Phase 3 synthesis dispatches
  • 7 Phase 4 operationally-actionable artefacts
  • TOTAL: 32 dispatches

If you operate a broker stack with active hosting procurement consideration and the toolkit above does not match your procurement process reality, that is the editorial signal we are looking for. The corpus improves through ground-truth from operators.