Why this dispatch exists
This is the fifteenth Phase 3 dispatch and the ninth 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, and trading platform. This one covers Chapter XI broker analytics and market signals.
The broker analytics segment is the most genuinely fragmented procurement layer in the corpus. Phase 2 covered the chapter with the observation that most operators run 2-4 analytics products in parallel because no single vendor covers the full procurement surface. The vendor refresh dispatch covered the FXStreet acquisition by ATFX (completing early 2025) which reframed FXStreet from independent FX news and analytics provider to broker-affiliated content source. The CASP archetype dispatch noted that CASP analytics procurement is structurally different from CFD broker analytics because the FX and CFD signal generation in the Phase 2 chapter does not extend to crypto-asset analytics; CASPs procure entirely separate vendors (CoinGecko Terminal, Glassnode, Messari Pro).
This dispatch covers the broker analytics procurement landscape state in 2026, the three structurally distinct vendor layers (trader-facing widgets, institutional data feeds, CASP-specific analytics), the 2-4-parallel-products procurement pattern at action-stage detail, the localisation procurement filter, the segment consolidation activity through 2025-2026, and three procurement implications for 2026.
The broker analytics procurement landscape state in 2026
Three structural realities shape analytics procurement through 2026:
The 2-4-parallel-products pattern is the operational baseline rather than the exception. Phase 2 surfaced this pattern as the operational reality across CySEC and DMCC operators. Through 2025-2026 the pattern has not consolidated. Most mid-market operators run combinations like Trading Central plus Autochartist plus Solitics, or Trading Central plus FXStreet plus Myfxbook integration. The vendor segment has fragmented along distinct product types that do not substitute for each other: trader-facing widgets (Trading Central, Autochartist, FXStreet), engagement analytics (Solitics, Myfxbook integration), institutional data feeds (Acuity, Newsquawk, Refinitiv), and tier-1 institutional analytics (Bloomberg Terminal). Procurement therefore happens across multiple vendors with explicit category-by-category procurement decisions rather than a single primary analytics vendor.
FXStreet’s ATFX acquisition has crystallised the broker-affiliated content question. Through early 2025 the FXStreet acquisition closed; FXStreet now operates as a broker-affiliated content source rather than as the independent FX news provider it was before the acquisition. The 2026 procurement-relevant question for operators is whether the broker-affiliation framing affects the content’s value in the operator’s client-facing distribution. ATFX-affiliation does not automatically compromise FXStreet’s content value but does change the procurement framing for operators who selected FXStreet partially on independence grounds.
CASP analytics procurement runs an entirely separate vendor set. The CASP archetype dispatch flagged this. Through 2025-2026 the gap between CFD broker analytics vendors and CASP analytics vendors has not narrowed. CoinGecko Terminal, Glassnode, Messari Pro, Kaiko, Chainalysis Market Intel, and similar crypto-asset analytics vendors do not have meaningful overlap with the Phase 2 chapter vendor set. CASP operators procuring analytics in 2026 should not extend their CFD analytics vendor procurement to the crypto-asset analytics decision; the segments are structurally distinct.
The trader-facing widget layer
Trader-facing widgets are the most-procured analytics layer across CFD broker archetypes. The 2026 vendor positioning:
Trading Central continues as the chapter’s strongest trader-facing widget procurement option. The Phase 2 SOLID verdict held; through 2025-2026 the vendor has continued expanding broker-affiliated content distribution including platform integrations with cTrader, Match-Trader, Spotware Store, and Brokeree-anchored deployments. Procurement-appropriate across all three CFD-touching archetypes (CySEC, DMCC, hybrid). The procurement-relevant question for operators is bundling structure and per-seat pricing: Trading Central’s pricing is bundle-tier-driven rather than per-trader transparent.
Autochartist continues as a SOLID procurement option with broker-affiliated content distribution similar to Trading Central. The Phase 2 verdict held; through 2025-2026 the vendor has continued deeper Match-Trade and Brokeree integration. Procurement-appropriate as either primary or secondary trader-facing widget alongside Trading Central; many operators run both products in parallel because the content surfaces complement rather than substitute.
FXStreet (post-ATFX) continues as a procurement option with reframed positioning. The Phase 2 SOLID verdict held operationally but the procurement reasoning has changed. Operators using FXStreet should evaluate whether the editorial framing changes since the ATFX acquisition affect the content’s value in the operator’s client-facing distribution. The SOLID verdict still holds; the procurement framing is “broker-affiliated content source” rather than “independent FX news provider.”
Investing.com continues as a procurement option for operators wanting broader market data coverage beyond FX (single-stock CFD analytics, ETF coverage, broader macro context). The Phase 2 SOLID verdict held; the procurement-relevant question is licensing tier and content distribution rights.
Myfxbook integration continues as a SOLID option for operators wanting community-and-network engagement alongside pure widget content. The Phase 2 verdict held; through 2025-2026 the vendor has continued integration depth expansion with broker platforms.
The procurement-relevant implication for the trader-facing widget layer is that operators typically procure 2 vendors in parallel (Trading Central plus Autochartist is the most common combination; or Trading Central plus FXStreet for operators wanting broader news coverage) rather than 1 vendor for full coverage. Operators procuring only 1 trader-facing widget vendor typically discover the gap in Year 2 when client engagement metrics suggest insufficient content variety.
The institutional data feed layer
Institutional data feeds are procurement-relevant primarily for tier-1 operators and for mid-market operators with institutional client segments. The 2026 vendor positioning:
Acuity continues as the strongest institutional data feed for FX and CFD operators wanting institutional-grade economic calendar, news intelligence, and sentiment analytics. The Phase 2 SOLID verdict held; through 2025-2026 the vendor has continued expanding broker-affiliated distribution including mid-market operators looking to differentiate institutional client experience. Procurement-appropriate at mid-market and tier-1 scale for operators with institutional segments.
Newsquawk continues as the strongest news-intelligence focused institutional data feed. The Phase 2 SOLID verdict held; through 2025-2026 the vendor has continued growth. Procurement-appropriate at mid-market and tier-1 scale.
Refinitiv continues as the broader institutional data feed option with FX, CFD, fixed income, and broader market data coverage. The Phase 2 SOLID verdict held; through 2025-2026 the vendor’s positioning within the London Stock Exchange Group has continued integrating. Procurement-appropriate at tier-1 scale.
Bloomberg Terminal continues as the highest-priced institutional data feed with broad market coverage. The Phase 2 SOLID verdict held at tier-1 scale; the verdict at mid-market scale is PARTIAL FIT because the per-terminal pricing rarely justifies for mid-market broker operations. The procurement-relevant question is whether the operator has institutional client segments that genuinely require Bloomberg coverage or whether the procurement is brand-driven rather than function-driven. The CySEC archetype dispatch flagged this explicitly.
The procurement-relevant implication for the institutional data feed layer is that procurement is tier-driven: tier-1 operators procure 2-3 institutional feeds (Acuity plus Newsquawk plus optionally Refinitiv or Bloomberg); mid-market operators procure 1 institutional feed (typically Acuity); lean operators do not procure institutional feeds and rely on the trader-facing widget layer alone.
CASP-specific analytics vendor set
The CASP analytics vendor set is structurally distinct from the CFD broker analytics chapter. The 2026 procurement reality:
CoinGecko Terminal continues as the broadest crypto-asset market data terminal with FX-and-CFD-trader-familiar UX patterns. The procurement-relevant question for CASPs is whether CoinGecko Terminal’s depth matches the operator’s institutional client segment requirements or whether more specialised vendors are appropriate.
Glassnode continues as the strongest on-chain analytics provider for institutional crypto-asset analysis. The procurement-relevant question is whether the operator’s analytics requirements extend to on-chain data (relevant for institutional clients with crypto-asset allocation strategies) or remain at the venue-level market data layer.
Messari Pro continues as a procurement option for institutional signals coverage with research-and-fundamentals positioning. The procurement-relevant question is whether the research depth justifies the per-seat pricing for the operator’s institutional client segments.
Kaiko continues as a procurement option for institutional crypto market data including order book depth across multiple venues. The procurement-relevant question is whether the operator’s needs include cross-venue order book reconciliation (relevant for institutional traders running cross-venue arbitrage or execution quality measurement).
Chainalysis Market Intel continues as a procurement option for operators wanting integrated market intelligence alongside the chain analytics products that the RegTech post-MiCAR dispatch covered. The procurement-relevant question is whether the bundling delivers procurement value.
The procurement-relevant implication for CASP analytics is that the procurement is genuinely separate from CFD broker analytics procurement. CASPs should not extend their CFD analytics vendor relationships to crypto-asset analytics; the vendors do not have meaningful overlap and the procurement decision is structurally different.
Engagement analytics distinct from market signals
The engagement analytics sub-category is procurement-relevant across all archetypes:
Solitics continues as the strongest engagement analytics platform with broker-specific positioning. The Phase 2 SOLID verdict held; through 2025-2026 the vendor’s growth funding round late 2025 accelerated product development including expanded retention campaign analytics. Procurement-appropriate across all CFD-touching archetypes for operators wanting client behaviour and retention analytics.
Myfxbook integration continues as a SOLID option for community engagement alongside trader behaviour analytics. The Phase 2 verdict held.
The procurement-relevant implication is that engagement analytics is a distinct procurement category from market signals. Most mid-market operators procure 1 engagement analytics vendor (Solitics) plus 2-3 market signal vendors (Trading Central plus Autochartist plus Acuity), producing the 2-4 parallel products procurement pattern that defines this segment.
Localisation for multi-language client cabinets
Localisation is a procurement filter that varies materially by vendor. The 2026 procurement-relevant positioning:
Trading Central offers the broadest multi-language coverage across the trader-facing widget layer. The procurement-relevant question is whether the operator’s specific client geography languages are in the native-translation tier or the machine-translation tier.
Autochartist offers similar multi-language coverage with slightly different language depth profile. The procurement-relevant question is whether Autochartist or Trading Central handles the operator’s specific language set with greater native translation depth.
FXStreet has expanded multi-language coverage post-ATFX but the procurement-relevant question is whether the post-acquisition editorial framing translates consistently across non-English content.
Acuity and Newsquawk primarily focus on English-language institutional content with limited multi-language coverage. The procurement-relevant implication is that institutional data feed procurement is generally English-language with multi-language content sourced from the trader-facing widget layer.
Solitics localisation extends to the engagement analytics UI but not to client-facing content. Procurement-relevant for operators wanting multi-language analytics dashboards for the operator’s internal team rather than client-facing content delivery.
The procurement-relevant implication for localisation is that operators serving GCC plus Indian subcontinent plus Southeast Asian client segments should explicitly test localisation depth for the operator’s specific language set during the procurement RFP rather than accepting vendor positioning around “multi-language support.”
The 2-4-parallel-products procurement pattern
The Phase 2 chapter and the CySEC archetype dispatch surfaced the pattern that operators run 2-4 analytics products in parallel. The 2026 procurement-action-stage breakdown:
Lean operators (1-5,000 active accounts) typically procure 1 trader-facing widget (Trading Central or Autochartist) plus 0 institutional feeds plus 1 engagement analytics product (Solitics if budget allows). Total: 2 products.
Lower-mid-market operators (5,000-15,000 active accounts) typically procure 2 trader-facing widgets (Trading Central plus Autochartist) plus 0-1 institutional feeds (Acuity if institutional segment exists) plus 1 engagement analytics product (Solitics). Total: 3-4 products.
Upper-mid-market operators (15,000-25,000 active accounts) typically procure 2 trader-facing widgets plus 1-2 institutional feeds (Acuity plus optionally Newsquawk) plus 1 engagement analytics product. Total: 4-5 products.
Tier-1 operators (25,000+ active accounts) typically procure 2-3 trader-facing widgets plus 2-3 institutional feeds (Acuity plus Newsquawk plus optionally Refinitiv or Bloomberg) plus 1 engagement analytics product plus optionally specialised feeds for institutional client segments. Total: 5-8 products.
The procurement-relevant implication is that operators graduating between scale tiers should plan the analytics procurement expansion explicitly rather than reactively. The procurement decision is multi-quarter and the vendor onboarding costs accumulate; treating analytics procurement as 1-vendor decision at lean scale and then layering on additional vendors reactively at mid-market produces higher total procurement cost than planning the 4-product mid-market state from the start.
Three procurement implications for 2026 operators
The above produces three concrete procurement implications:
Implication 1: The 2-4-parallel-products procurement pattern is the operational baseline; plan for it rather than assuming single-vendor coverage. Operators procuring analytics in 2026 should plan their analytics architecture as a multi-vendor procurement from Year 1 rather than treating analytics as a single primary vendor decision with additional vendors layered reactively in later years. The vendor onboarding costs accumulate; the multi-quarter procurement reality favours planned multi-vendor procurement over reactive addition.
Implication 2: FXStreet procurement requires reframing post-ATFX acquisition. Operators using FXStreet or evaluating FXStreet should explicitly evaluate whether the editorial framing changes since the ATFX acquisition affect the content’s value in the operator’s client-facing distribution. The SOLID verdict still holds operationally; the procurement reasoning has changed from “independent FX news provider” to “broker-affiliated content source.” Operators who selected FXStreet partially on independence grounds may need to reassess; operators who selected FXStreet on content quality alone can continue procurement.
Implication 3: CASP analytics procurement is structurally separate from CFD broker analytics procurement. Operators running CASP operations should not extend CFD analytics vendor relationships to crypto-asset analytics. The vendor sets do not have meaningful overlap and the procurement decision is structurally different. CASPs should procure crypto-asset analytics from the dedicated vendor set (CoinGecko Terminal, Glassnode, Messari Pro, Kaiko, Chainalysis Market Intel) treating the procurement as a separate category from CFD broker analytics rather than extending existing vendor relationships.
What comes next in the per-pillar series
Nine per-pillar dispatches shipped (payments, RegTech, crypto exchange WL, LP procurement, risk management, broker CRM, IB management, trading platform, broker analytics). The remaining per-pillar candidates with built-up editorial signal:
- 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.
- 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.
- Turnkey suite procurement deep dive. The Phase 2 chapter covered turnkey suites as an alternative procurement path; the CySEC and DMCC archetype dispatches surfaced lean-stack procurement as the typical turnkey use case. A per-pillar dispatch would extend coverage of turnkey procurement including the lean-to-mid-market graduation question that the archetype dispatches flagged but did not detail.
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 analytics 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.