Centroid Solutions: bridge, risk, hosting and client operations

Centroid supplies technology linking a brokerage’s customers, trading systems and operational teams. Its portfolio includes execution connectivity, risk analytics, hosting, trading interfaces and client administration. The company describes independently usable modules that can also form a connected system for brokers, banks and financial platforms.[1]

This modular structure supports several buying patterns. A broker can add risk analysis around an existing platform, replace execution connectivity while retaining its portal, or implement a broader trading and operations stack. The important distinction is the function being delegated. A hosting contract concerns infrastructure availability; a risk engine consumes and interprets data; a bridge changes how orders and prices move. Buying all three does not make their responsibilities interchangeable.

CS 360 documents FIX 4.4, WebSocket and REST connectivity, alongside FIX drop copy and database access for downstream data. It allows configurable execution models, external-provider routing and internalization, with exposure-limit hedging and backup liquidity providers. These are tools for implementing a broker’s dealing policy. A configured route still needs a separately agreed relationship with the provider that supplies executable prices and accepts the trade.[2]

The CQG announcement is especially useful because it explicitly separates the source of a price from the route used to execute an order. That can let a broker choose data coverage and execution arrangements independently. The operational consequence is that symbol definitions, timestamps and permissions must still agree between the two flows. A data feed that displays a market does not itself establish an account entitled to trade there.[8]

TRAction’s own announcement confirms that the CS 360 connection sends trading data into its reporting systems. It describes extraction/conversion, submission to repositories or approved reporting mechanisms and interpretation of reporting requirements as TRAction services. This is a concrete operational interface: an integration can remove a manual transfer step while leaving responsibility for correcting rejected records, client identifiers and classifications to the agreed reporting arrangement.[9]

For GCC access, Arqaam independently confirms the integration. That corroborates the commercial connection without requiring an inference that the companies merged. The distinction is useful for a broker expanding from leveraged FX into regional equities: the same technical interface can reach an additional provider, but settlement, custody and investor eligibility still follow that provider’s arrangement.[11]

The reviewed product pages direct enquiries to sales without establishing a subscription-rate card, trading-volume fee or standard contract term. Pricing is recorded as not publicly disclosed; this does not imply free installation or unlimited use.[7]

A useful total-cost model separates the technology invoice from external execution, data and payment relationships. The same trading volume can create a bridge workload, an execution commission and a reporting workload. Those quantities need not be billed on the same basis. This is an architectural cost distinction, not a claim that Centroid charges a particular fee per connection or transaction. The public pages do not supply enough numbers to calculate a defensible all-in monthly price.

C 24 can combine multiple platforms, export through APIs and save customized dashboard views. Centroid handles custom-platform integration. Consistent identifiers and exposure units are therefore important when reconciling the resulting risk view with a trading ledger.[3]

CS Drive locates infrastructure in Equinix LD4, NY4, TY3 and SG3, with colocation and cross-connect arrangements close to execution engines and providers. Its published controls include VPN connectivity, DDoS protection, redundancy, monitoring and administrative access. Proximity explains the architecture; it is not a measured latency outcome for every client or proof that hosting solves an upstream liquidity outage.[4]

For migration, the five-product structure suggests an explicit sequence: establish the account and instrument mappings, reconcile source data, reproduce approved operating rules, and then hand over the relevant workflows. A working login is insufficient evidence that settlement, exposure and customer balances agree. This is an implementation inference from the architecture, rather than a proprietary Centroid deployment checklist or a claim that a migration was performed for this profile.

The C 24 FAQ specifies 24/5 normal support and 24/7 emergencies through dedicated Teams/Slack groups and tickets. It does not publish severity-specific response or resolution times.[3]

CS Maystro’s FAQ advertises an uptime SLA above 99.99%, without the full measurement window, exclusions, credits or recovery-point schedule. This is a published service-level description, not a record of achieved availability.[5]

Operational support ownership follows the failed component. A connectivity problem may need bridge and venue logs; a rejected payment may need the PSP’s record; a risk discrepancy may need the source trade and its mapping. An integrated vendor can simplify coordination, but the incident record still needs to identify the authoritative event and the party able to correct it. That is why direct communication and a durable ticket trail serve different purposes.

Centroid’s ecosystem material describes technology joining onboarding, KYC, payments, trading, risk and hosting, with integrations to banking-as-a-service and core-banking providers. This establishes the intended orchestration role. It does not establish that Centroid is itself a deposit-taking bank, investment counterparty or custodian, or that the purchaser can offer all connected services under one permission.[7]

C2C’s support for corporate actions, settlement and custody reporting describes software workflows for an operator’s investment service. Software can record and display an asset without being the legal custodian holding it. Equally, a client wallet in an operational platform is not by itself evidence of a protected bank account. The financial provider, account structure and customer agreement determine those relationships.[6]

The privacy policy describes processing of personal, business, technical and transaction information, with sharing involving service providers, affiliates and authorities where applicable. It also contemplates cross-border handling. Those disclosures are relevant to hosted broker operations, but they are not a deployment-specific processing agreement or a complete inventory of subcontractors and storage regions.[15]

Centroid is headquartered in Dubai, and its company page identifies Cristian Vlasceanu as chief executive. The current presentation emphasizes a broader capital-markets operating system rather than only bridge and risk tools. The public company material does not provide a complete shareholder register, so the profile distinguishes a documented group relationship from an independently reconstructed beneficial-ownership chain.[1]

180 Capital lists Centroid Solutions among its businesses alongside separate trading, systematic-investing and digital-asset activities. That supports the corporate-group affiliation. The page describes Centroid as a technology business based in Dubai with a Cyprus branch; it does not make the financial permissions of another 180 Capital business transferable to Centroid’s software contracts.[13]

Bloomberg’s LEI record identifies CENTROID SOLUTIONS DMCC, registration identifier DMCC90224, and the same Office 1705, The Dome, Jumeirah Lakes Towers address used by the company. It shows an issued LEI, an active entity and a March 2026 update, with validation marked partially corroborated. This is useful corporate identity corroboration, not a financial-services licence or a substitute for the contracting entity stated in a signed order.[14]

Operator

Centroid Solutions DMCC (LEI-matched entity; the signed agreement determines the contracting party)

Service scope

Modular broker technology spanning execution connectivity, risk analytics, hosting, trading interfaces and client lifecycle management. Financial access is supplied through separately contracted financial providers.

Customer types

Brokers and broker-dealers; Banks and financial institutions; Liquidity providers; Proprietary trading businesses; Fintech platforms and super apps

Delivery

SaaS; Hosted; On premises; API

Pricing publication

Not disclosed

Headquarters

Dubai, United Arab Emirates

Platforms

CS 360; C 24; CS Drive; C2C; CS Maystro

Integrations

CQG trading connectivity; TRAction reporting integration; Arqaam Capital regional-market connectivity; Financial Modeling Prep content

Implementation

Dedicated hosted bridge/risk instances; C2C and CS Maystro also offer customer-infrastructure deployment. Published setup windows describe initial deployment, with testing and training afterward.

Support

Product FAQs specify 24/5 standard support and 24/7 emergencies through dedicated communication groups and tickets. Public uptime statements are vendor SLA descriptions.

Permissions and regulatory scope

Technology-provider profile. Corporate identity and group affiliation are documented separately from customers’ financial permissions. No brokerage, bank or custody licence is attributed to Centroid from its product integrations.

Provider metadata checked 20 Oct 2026Source 14Source 1Source 7Source 2Source 3Source 6Source 5

CS Maystro supports multiple entities in one instance, configurable onboarding, partner rebates, API/event extensions and Tableau reporting. A group can centralize technology while preserving separate customer journeys. Legal-entity distinctions still belong in client records, ledger permissions and reports.[5]

Financial Modeling Prep integration adds another layer beyond order entry: historical pricing, issuer fundamentals and company/news content can be presented inside the trading experience. The underlying announcement is dated December 2024 and was republished by 180 Capital in January 2025. It documents a content integration, not a guarantee that every field is licensed for redistribution in every deployed front end or that the content is an executable quote.[12]

The risk model and the risk decision also have different roles. Value-at-risk summarizes a modelled loss distribution under chosen assumptions; stress tests examine specified shocks. Neither is a guarantee of the next loss or an instruction to retain a client’s exposure. A broker can use the analytical output to inform limits while keeping authorization, overrides and review of the underlying assumptions under its own governance.

The public evidence supports a modular technology supplier with several distinct integration paths. It does not establish a universal price, a completed deployment specification or a consolidated financial-service permission. The substantive comparison is therefore which operating functions the buyer can consolidate, how data moves between them and which separately contracted providers still supply execution, payments and asset services.