MahiMarkets: pricing, execution, flow classification and broker risk technology

MahiMarkets supplies dealer-side technology to brokers and prop firms. MFXCompass sits between trading platforms and liquidity providers, combining pricing, execution and risk management within an existing technology stack. The current homepage describes a modular deployment and simulation of proposed changes against a customer’s anonymized trading data.[1]

Compass is more than a distributor of aggregated liquidity. The supplier describes customer-specific price models, predictive signals used in price formation and hedging, and automated decisions about allocating flow. Its dashboard can show VaR, profit and loss, traded volume and book yield. Simulation allows changes to pricing or risk controls to be examined before they are put into production.[5]

The documented risk workflow separates classification from the decision about where a trade is held. The firm can apply different hedging speeds and holding periods to different flow types, and choose which flow to internalise or broker externally. Automated classification then ties those trading behaviours to the selected policy. Changing a classification can therefore alter execution and hedge behaviour, rather than merely change a dashboard label.[8]

A published EA example illustrates that relationship: Mahi says Echo identified accounts acting together, while Compass prevented their trades entering the broker’s internal B-book. This is a supplier-described use of analytics coupled to an active risk rule. It should not be read as a guarantee that every coordinated strategy will be detected, or that each customer has the same configured response.[9]

That card concerns TradeHaven. Mahi’s published website material describes pricing for its wider offering as tailored to the client. A bespoke Compass quotation should identify the selected modules, infrastructure, implementation and ongoing services; the TradeHaven starting figure cannot price every configuration.[2]

Mahi’s own scaling guide identifies transaction-linked vendor costs, server capacity and the price feed used to fill orders as operational cost questions. It does not establish a Mahi per-million tariff. For comparison of proposals, the useful distinction is between the subscription, any volume-sensitive component, infrastructure and separately specified services.[13]

The current homepage says most implementations take two to four weeks, including API integration, native connectivity and training. This is a supplier estimate for its described workflow, rather than a contractual delivery commitment. Its pre-commitment simulation uses anonymized customer trading data to model the effect on that particular book.[1]

A bespoke risk design can vary exposure limits, the time risk is held, the speed of hedging and the flow selected for internalisation. Those choices define the economics and behaviour of the deployment. The published B-book discussion treats them as distinct controls, so a migration should preserve the intended classifications and policy mapping as well as connectivity.[8]

The development team’s historical account describes configuration flexibility, work on the configuration interface and automated regression coverage. It also notes continuity with parts of the original 2010–11 system. This gives context for the configurable product architecture; it supplies neither a current release-support matrix nor a tested migration or recovery result for a new customer.[15]

TradeHaven lists Zendesk for monitoring and issues, with monthly meetings after onboarding. Incident hours, severity levels and response deadlines require a customer service schedule.[4]

Mahi also describes configurable real-time alerts, B2B onboarding assessments, alternative risk and pricing analysis, and trading consultancy. These services give the software engagement a continuing analytical component. Their inclusion and cadence should be distinguished from the narrower TradeHaven package specification.[12]

Mahi’s prop-firm article describes classification, predictive price filters, liquidity reduction and trade premiums, with objectives that include changing challenge pass rates and access to a graduate pool. These functions can affect client prices, fills and outcomes. They are dealer-side controls, and the article’s claims about fairness or profitability are not independent assessments of a firm’s operating policy.[11]

A privacy notice dated 1 March 2023, retained in the site’s public assets, identifies Mahi Services (UK) Ltd as website controller within a group also comprising New Zealand and Antigua entities. Its general personal-data handling language does not specify production-trading-data retention, model-training permissions or a contractual deletion timetable. Those need the customer’s processing terms.[2]

The current homepage describes network-wide flow learning and confidential simulation on anonymized customer data. A deployment specification therefore needs to distinguish local trading records, information used across clients and the outputs retained after analysis. The public descriptions are insufficient to establish a customer’s rights to retrieve model inputs, configurations and historical records when the service ends.[1]

Susan and David Cooney founded the business after leaving Barclays in 2010. The official company account links their earlier electronic-trading experience to the development of pricing and risk technology for other firms. The group’s origins predate the current UK company’s incorporation.[14]

Companies House lists Mahi Services (UK) Limited, number 11737484, as active and incorporated on 20 December 2018. Its registered office is Beaumont Midtown, 322 High Holborn, London WC1V 7PB, and its stated activity is software development. The exact group entity supplying a customer deployment belongs in the contract.[17]

The UK company’s active control record identifies David Laurence Cooney with at least 75% of shares and voting rights and the right to appoint or remove directors. This establishes control of that registered entity; it is not a consolidated register of every group business.[18]

The March 2021 MahiFX-to-MahiMarkets rebrand accompanied an announced expansion into commodities, CFDs, crypto, single stocks and options. A contemporary developer interview describes the wider transition from a retail platform to supplying technology. That history helps distinguish the present B2B product business from historical retail-brand references.[16][15]

Operator

Mahi group; UK website controller Mahi Services (UK) Ltd

Service scope

B2B price formation, execution, flow classification, risk management and analytics.

Customer types

Brokers; Prop firms

Delivery

Managed service; Hosted

Pricing publication

Public and quoted pricing

Platforms

MFXCompass; MFX Echo; MFX Pulse; MFX TradeHaven

Integrations

MFXConnect optional upgrade; Existing trading infrastructure

Pricing scope

TradeHaven starts at $15k monthly as printed; bespoke configurations require a proposal.

Implementation

Questionnaire-led managed configuration; current homepage gives a typical two-to-four-week implementation estimate.

Support

TradeHaven: Zendesk and monthly meetings; incident terms require agreement.

Permissions and regulatory scope

Technology and managed trading workflows; customer contracts define the supplying entity and operating authority.

Provider metadata checked 20 Oct 2026Source 1Source 2Source 17Source 5Source 4Source 6Source 3

These swap-free tools are risk analytics for the broker. The documented service is monitoring exposure and trading behaviour; it is not a certification of the religious or contractual terms of any client account. The distinction is relevant because the broker may still incur financing costs when hedging externally.[10]

Echo’s published rationale begins with a practical dealing-desk problem: explaining slippage and determining what happened to an order. Its analytical perspective connects pricing, liquidity providers and counterparties instead of treating a poor outcome as a single aggregate metric. Mahi describes assistance in resolving the issues diagnosed, alongside the software’s simulations and reporting.[7]