Murex: MX.3 trading, treasury, risk and post-trade infrastructure

The core proposition is a consistent record across positions, valuations, lifecycle events, risk calculations and operational processing. MX.3 can be deployed broadly or by module. Instrument coverage therefore needs to be considered together with the functions and business entities that will use the platform.[1]

The API framework uses REST, JSON and published OpenAPI specifications. Murex describes TLS encryption, OAuth 2.0 authentication and permission checks aligned with the core application’s entitlements. This supports controlled integration with existing trading and operational data: credentials do not automatically grant unrestricted access to every platform function.[2]

Published use cases include custom pricing tools, consolidated risk dashboards, client-facing channels and operational data flows. The practical design questions include which application is allowed to read or modify a record, how errors are handled, and whether downstream systems use the correct interface version. The use cases describe capabilities rather than a tested integration for a particular institution.[2]

MXSaaS documents interfaces to market-data providers, trading and affirmation platforms and in-house systems. Its examples include Bloomberg, LSEG, SWIFT, CLS, Acadia and DTCC, alongside bespoke interface routes. The selected services and commercial data entitlements still need to match the implementation.[3]

No universal public price for an MX.3 implementation was established in the reviewed product materials. Software modules, delivery model and project scope determine what must be priced. Replacing a risk engine, introducing a broad operating platform and moving an existing MX.3 estate to managed delivery are materially different projects.[1][3]

A comparison should specify the licensed functions, environments, interfaces, migration work, operating responsibilities and upgrade arrangements. These are project boundaries visible in the offering, not asserted line-item fees. A SaaS label alone supplies too little information to infer the total cost or which operational tasks the institution retains.[6][7]

MXSaaS is described as a dedicated, single-tenant MX.3 instance with managed services from Murex. Hosting and infrastructure are supplied through third parties on public or private clouds. Published responsibilities include infrastructure, networking, operating systems, database administration and MX.3 technical configuration. The page also describes monitoring and managed upgrades.[3]

For an established estate, migration must preserve opening positions, transaction histories, valuation inputs, interfaces and downstream reporting. For a new implementation, model validation and operational acceptance are separate from confirming that the application runs. These are analytical consequences of placing several stages of the transaction lifecycle on a shared platform.[1][5]

Murex’s public contact page links to Community Zone and the Customer Portal. These authenticated resources are useful starting points for an existing customer’s product support. The managed-service page describes 24/7 platform monitoring, which is a detection and operating arrangement; incident response and restoration obligations require the actual service agreement.[4][3]

The enterprise-risk offering supports calculations and controls associated with regulatory frameworks, including market-risk and counterparty-credit methodologies. The institution must still establish its applicable method, inputs, validation and governance. A software capability is separate from approval of an internal model, a capital treatment or permission to conduct a regulated business.[5]

Murex’s official site identifies MUREX S.A.S. and traces its origins to Paris in 1986. MX.3 is the product identity within that business. The agreement remains the authority for the customer’s contracting company and service perimeter.[4]

Operator

MUREX S.A.S.; the customer agreement identifies the contracting supplier

Service scope

Integrated capital-markets, treasury, risk and processing software, with institutional APIs and managed delivery options.

Customer types

Banks; Investment managers; Clearing houses; Corporates; Public agencies; Energy and commodities businesses

Delivery

SaaS; On premises; API; Managed service; Hybrid

Pricing publication

Not disclosed

Headquarters

Paris, France

Platforms

MX.3; MXSaaS; MX.3 APIs

Pricing scope

No universal public MX.3 implementation tariff was established in the material reviewed.

Implementation

Modular or broader MX.3 implementation. MXSaaS uses a dedicated single-tenant application with Murex managed services and third-party hosting on public or private cloud.

Support

Public company contact, Community Zone and Customer Portal. MXSaaS describes 24/7 monitoring; restoration commitments remain agreement-specific.

Permissions and regulatory scope

Technology and calculation support for institutional workflows. No financial-services authorisation, internal-model approval or customer regulatory compliance is asserted from the purchase of software.

Provider metadata checked 20 Oct 2026Source 1Source 2Source 3Source 4Source 5Source 6Source 7Source 8Source 9

The investment-management offering combines portfolio management, trading, compliance, performance and accounting around a cross-asset book of record. It also describes bringing in preferred data sources and adapting the data model. That breadth can reduce reconciliation boundaries, while making configuration changes consequential across several outputs instead of just one application screen.[6]