Murex has certified its MX.3 capital-markets platform for Google Cloud, giving banks and other financial institutions another public-cloud option for infrastructure supporting trading, treasury, risk, and post-trade operations. Those workloads sit among the more sensitive parts of the financial technology estate, so changing the underlying infrastructure alters operational dependencies even when the application used by employees remains recognisably the same.

The Paris-headquartered software company says multiple clients are already examining deployments of MX.3 on Google Cloud. The agreement adds another environment for workloads including market-risk calculations, counterparty risk, intraday analytics, trading operations, and treasury systems, where demand for computing capacity can change sharply around volatile markets or reporting cycles.

For Murex, adding Google Cloud broadens the infrastructure choices available to customers as financial institutions pursue multi-cloud strategies and modernise systems that have often been operated for many years. For Google, certification provides another route into regulated financial workloads where migration has generally proceeded more cautiously than in less critical parts of enterprise IT.

Neither side can reduce the decision to raw computing capacity, however, because a capital-markets platform has to remain available through disruption, protect sensitive data, integrate with numerous surrounding systems, and recover predictably. Moving it onto hyperscale infrastructure changes the failure domains, supplier relationships, and operational model beneath the application.

Cloud economics meet resilience requirements

Risk calculation provides an obvious case for elastic infrastructure because demand can rise quickly and temporarily. Murex says Google Cloud can provide compute across regions for data-intensive work including market risk, counterparty risk, and intraday analysis, allowing institutions to scale processing without maintaining equivalent peak capacity entirely in their own facilities.

Yet the attraction of elasticity sits alongside demanding resilience requirements. Trading and risk platforms connect to market data, order systems, collateral processes, payments, reporting, and numerous downstream controls, meaning a cloud architecture has to be judged by recovery, observability, security, and integration as much as by cost per unit of compute.

Murex is accordingly presenting cloud choice alongside operational resilience, security, and automation rather than simply as a hosting decision. Customers gain another option when designing environments around regional requirements, continuity plans, or internal multi-cloud policies, while Google’s automation and infrastructure services can be used beneath MX.3 deployments.

The word “choice” carries particular weight in financial services because supplier concentration has become part of the regulatory discussion around cloud adoption. A relatively small number of hyperscale providers operates much of the global public-cloud market, while financial institutions are moving increasingly important workloads onto external infrastructure.

European rules change the cloud conversation

The EU’s Digital Operational Resilience Act has applied since January 2025, creating common requirements around ICT risk management, resilience testing, incident reporting, and oversight of third-party technology dependencies. Financial entities must maintain more detailed information about those relationships, giving supervisors greater visibility into which suppliers sit beneath important operations.

That framework does not prevent cloud adoption, but it changes how institutions have to approach it. A decision to run a core market system on public cloud brings questions about provider dependencies, subcontractors, monitoring, access to data, recovery arrangements, and the practical ability to move or restore the service when something fails.

Multi-cloud strategies are sometimes presented as a straightforward answer to concentration, although capital-markets software exposes the trade-off. Operating complex systems consistently across several providers can increase engineering and operational overhead, while depending deeply on one provider can improve integration at the cost of a larger dependency.

Additional certified environments therefore create options without removing the architecture work required to make those options credible. An institution still has to know which parts of the stack are portable, which depend on provider-specific services, and how much time and expense an exit would actually require.

Financial software keeps changing underneath

MX.3 is used across trading, risk management, treasury, and post-trade processing, while Murex has continued expanding the ways customers can operate the platform. That allows institutions to modernise infrastructure without attempting to replace every business process and application at the same time, which can be attractive in capital markets where systems accumulate integrations over many years.

The Google Cloud certification extends that approach by separating application choice from infrastructure choice. Customers can retain specialised market software while changing where compute, resilience, and operational tooling are delivered, rather than treating cloud migration as synonymous with application replacement.

Established enterprise-software vendors are increasingly adopting that model as hyperscale infrastructure becomes standard beneath long-lived business platforms. Cloud providers gain demanding workloads, software vendors preserve existing customer investment, and users can modernise in stages rather than through a wholesale rebuild.

Financial services remains a demanding test because regulators and internal risk functions are interested in dependencies several layers below the user-facing software. An MX.3 deployment may still look like Murex to a trader, but its operational model can now extend through Google Cloud infrastructure, identity systems, monitoring, network architecture, data controls, and supplier relationships.

Murex’s certification consequently adds another infrastructure path rather than settling the financial sector’s cloud debate. As capital-markets platforms consume more data and compute, institutions have stronger reasons to use hyperscale infrastructure, while the regulatory environment requires them to understand exactly what those decisions introduce into the risk model.