TradingHub: market-abuse surveillance, analytics and service terms

TradingHub works with institutions that need to examine orders, trades and positions for possible misconduct. Its audience includes banks, asset managers, hedge funds, commodity businesses and brokerage firms. For a multi-asset broker, the relevant use is supervision of trading activity across products and desks, with analysts investigating the resulting alerts. Nordic Capital’s current company profile places the business in institutional surveillance software.[10]

The linked MAST brochure describes assigning a dollar value to alert severity, helping analysts prioritise the economically significant cases. It also describes automatic recalibration as market conditions change. These features affect how the investigation queue is organised: an alert count alone says little about the size of the suspected benefit or the exposure involved. The customer still needs to understand the model, its thresholds and the cases selected for review.[19]

The cross-product approach becomes useful when a desk manages one exposure with several instruments. TradingHub’s methodology converts positions into comparable risk sensitivities and models how a move in one part of a curve can affect others. A bond, futures contract and swap may offset risk or collectively benefit from manipulation. Reviewing only each instrument’s trade count can miss that relationship. The provider’s examples illustrate its analytical approach; they do not establish the detection rate for a particular customer.[16]

The August 2026 security schedule describes separate customer environments on third-party cloud infrastructure. SFTP credentials are issued during onboarding, and the customer is responsible for securing them. Single sign-on can delegate additional access requirements to the customer’s identity provider. Corporate IP ranges must be supplied for access restrictions. These arrangements require coordinated work by the surveillance, data and identity-management teams.[5]

Order Book Surveillance was launched in November 2025. Its announcement describes activating replay on an existing MAST instance or alert, with browser-based processing and granular playback. The investigation can connect listed-market activity with OTC exposure and reference-price concerns. This is a documented workflow capability; the announcement supplies no universal processing-latency commitment.[4]

A general public price list, minimum annual commitment and renewal schedule were not established in the reviewed materials. The website terms govern use of the public site and do not substitute for the production-service contract. A usable commercial offer should identify the covered business, purchased modules and contractual schedules, so their applicability can be assessed together.[12]

TradingHub’s 2026/27 Code of Conduct requires relevant staff to complete customer due diligence and approval before signing contracts, enabling services or granting access. That is a customer-acceptance condition. It does not publish a fixed deployment duration or promise that every applicant can obtain the service.[17]

These governance measures are drawn from TradingHub’s published methodology. They describe the work an institution should organise around surveillance; they are not a promise that every proposed check is automatically configured in every subscription.[14]

The publicly available SLA is dated 12 May 2023. It applies only when expressly incorporated into the contract and covers production MAST, excluding UAT and onboarding. Its support arrangements depend on consent to Global Support, which involves personal-data transfers to group offices and sub-processors.[6]

TradingHub is a technology supplier to institutions supervising their trading activity. The Companies House record establishes the company’s identity and software-development activity. It does not establish a dealer permission, and security certifications should be assessed against their technical scope rather than treated as approval of the customer’s surveillance programme.[9]

The Trust Centre states ISO 27001:2022 certification and SOC 2 Type II assurance, and lists a 2026 SOC 2 report. The underlying report and certificate were not inspected. It also labels an ISO 42001 audit as forthcoming in Q4 2026, so that item is a planned assurance activity. The public statements provide a route for supplier due diligence, with detailed evidence available through the Trust Centre’s access process.[8]

The June 2025 platform privacy policy identifies the customer as controller and TradingHub as processor for user and trader information. It describes analysing usage, alert amendments and parameter changes to improve the platform. AWS and conditionally Swisscom appear among its sub-processors, alongside group companies. International transfers may use contractual safeguards. The dated policy should be matched to the current processing agreement and deployment.[7]

TradingHub Group Limited is an active English company, number 07382307, incorporated on 21 September 2010. Its registered office is 2nd Floor, 5 Aldermanbury Square, London EC2V 7HR. Earlier names were Financial Acquisitions Limited, Trading Hub Limited and Financial Skills Limited. Those historical names refer to the same company identity.[9]

Nordic Capital currently lists TradingHub in Fund XI, with a 2026 investment. TradingHub appointed Phil Snow as chairman on 13 October 2026. That announcement describes the Nordic investment as having taken place, following the agreement announced in March. Mike Coats is the current chief executive on TradingHub’s company page.[11][1][10]

The contact directory lists London, Toronto, Singapore, Sydney and Manchester. Its London address agrees with Companies House. The public website terms still show an older Broadgate Tower address; the current company record and contact page are the more useful address references.[13][9][12]

Operator

TradingHub Group Limited

Service scope

Institutional market-abuse surveillance, custom controls and operational analytics.

Customer types

Banks; Asset managers; Hedge funds; Commodity houses; Brokerage firms

Delivery

SaaS

Pricing publication

Quote only

Headquarters

London, United Kingdom

Platforms

MAST; CaaS; Order Book Surveillance

Integrations

SFTP trade-data delivery; Single sign-on through the customer identity provider; Custom reporting and data extracts

Pricing scope

No general numerical tariff was established; modules, covered entities, data and support require an agreed offer.

Implementation

Hosted environments with trade-data integration, customer access controls and surveillance-model governance.

Support

Contract-dependent MAST support windows; customer support by email.

Permissions and regulatory scope

Surveillance technology for institutional customers; company registration and security assurance are distinct from financial-services authorisation.

Provider metadata checked 20 Oct 2026Source 1Source 9Source 13Source 10Source 5Source 12Source 6Source 2Source 3Source 4

Real-time surveillance needs a defined operating purpose. TradingHub’s June 2026 discussion distinguishes controls for immediate market disorder from investigations that need a fuller record of trading patterns and context. This matters when commissioning the service: the customer should specify which activity requires an intraday response and who can act on the alert. A browser replay feature and a post-trade analysis process do not, by themselves, establish an order-blocking or emergency kill-switch service.[15]

CaaSbot is presented as a way to describe reports and controls in ordinary language. The published product page positions it as an aid to authoring these outputs.[3]

TradingHub’s separate AI series discusses both analytical improvements and workflow changes, and describes agentic dispositioning as a gradual development. The public material does not establish unrestricted autonomous case closure, a particular foundation model or a universal release entitlement. An implementation needs a clear account of what the assistant can propose, what it can execute and which decisions require approval.[18]

The staff Code of Conduct provides a related governance boundary: AI tools require internal approval, sensitive customer information needs authorisation, and human oversight must address inaccurate or biased output. These are published staff obligations. They are not evidence that a particular customer configuration has already passed model validation or that customer data can be sent to an external model.[17]

The security schedule requires contractual incorporation, describes encryption during transfer and storage, and provides for annual continuity testing. Customer penetration testing has restrictions, including prior permission for application tests. Retention follows the contract or TradingHub’s retention policy; the schedule does not supply a universal number of years. An exit arrangement therefore needs explicit export formats, retrieval time and deletion treatment.[5]

The platform privacy policy permits retention for necessary purposes and describes possible indefinite use after anonymisation. That should be distinguished from a guaranteed customer archive or a post-termination retrieval window. No general public exit-assistance tariff or complete production offboarding procedure was established in this review.[7]

For FX and rates desks, TradingHub’s pre-hedging discussion adds a specific use case: private transactions can depend on a price observed in another market. Investigators may therefore need to connect trading ahead of a fixing with the exposure that benefits from that price. The practical question is whether the relevant RFQ, customer order, hedges and fixing context are present in the surveillance data. The article explains a monitoring problem; it does not grant permission for pre-hedging or decide whether a particular trade is lawful.[20]