< BLOG HOME

Why Mirantis Has Joined FINOS

William Rizzo - November 04, 2026
image

Mirantis joins the Fintech Open Source Foundation as a Silver member, to work with the other members on the open standards the industry is building for AI workloads.

In August of this year, Mirantis has joined the Fintech Open Source Foundation as a Silver member, with a very focused purpose: to work alongside the other members, respond to their requirements, and contribute to the standardized, open technologies the industry is building for AI workloads, in particular Common Cloud Controls and the AI Governance Framework.

What regulated infrastructure asks for

Mirantis has spent 15 years providing open source software, expertise and training to financial institutions. The durable lesson is that regulated infrastructure rarely asks for a feature. A capital markets platform team is not short of Kubernetes distributions; it is short of ways to answer a supervisor's question with evidence. Which image was that node booted from on a given date? Who approved the change to that cluster's admission policy?

Regulations such as SOX, PCI-DSS and Basel III translate into engineering requirements: auditability, drift prevention, independently-validated cryptography, and network segmentation that can be demonstrated rather than asserted. In Europe, DORA adds expectations around information and communications technology resilience and third-party dependencies. The consequence for platform design is that "everything as code" stops being a DevOps preference and becomes the cheapest available compliance posture. If every node is an immutable image with a digest, every cluster a reviewed manifest in Git, and every policy a versioned resource, then the change history is the audit trail. Regulated customers pushed us toward that model early, and it shapes the projects we contribute to today.

From consuming open source to contributing it

Financial services have consumed open source for decades. What is changing is the institutions' willingness to give code back, and how far that willingness has to travel through legal, risk and procurement to reach a public repository. The FINOS 2025 State of Open Source in Financial Services report puts numbers on the gap: 87 percent of respondents recognize the business value of open source, yet contribution is growing only modestly, held back in roughly half of organizations by unclear return on investment and legal or licensing concerns. FINOS exists to close that gap: a neutral place for competing institutions to mutualize engineering effort, and a way for vendors to bring code to problems the industry has already articulated, on the industry's terms.

RBC Capital Markets, and in particular Erick Bourgeois, Distinguished Technologist, were design partners in the early development of k0rdent, the open source cluster lifecycle project to which Mirantis is the leading contributor. Their requirements arrived as production constraints, and the project is different for it. Bourgeois has described RBC's platform philosophy on the CNCF blog; the organizing principle, in his words, is "everything is code, reconciled continuously, with no manual state."

RBC has also done what the FINOS report says is still hard. It took 5-Spot, a controller it built to lend physical machines to Cluster API clusters on a time schedule and drain them gracefully when the window closes, and contributed it to FINOS as an incubating project under its own maintainership. 5-Spot is RBC's work, governed under FINOS and led by the engineers who run it in production. Our company’s role there, as in any FINOS project, is the one a vendor should have: contribute where maintainers want help, and leave the leadership where it belongs.

Erick Bourgeois, RBC Capital Markets. Suggested angle: what changes when a regulated institution moves from consuming open source to maintaining a project under a neutral foundation. To be sourced from and approved by RBC.

Why now

The problem the industry is mutualizing effort on today is AI. In June 2026, FINOS launched an AI Fund, anchored by DTCC, Morgan Stanley, RBC and NatWest, to fund governance, standards and reference implementations for agentic AI in regulated finance. The building blocks FINOS names are the AI Governance Framework, now at version 2.0 with an agentic risk catalogue of 46 risks and mitigations cross-referenced to OWASP, MITRE and the EU AI Act, and Common Cloud Controls, an open standard for machine-readable security, resiliency and compliance controls. Together they describe governance as code: controls written once, validated automatically, evidenced at runtime.

Most of that evidence has to be produced by infrastructure. Tenancy isolation, GPU partitioning, the provenance of a model artifact, the trail an inference request leaves behind: these are properties of the platform, not the model. Much of the AIGF and CCC work so far has, understandably, been written from the perspective of consuming cloud services, while institutions are now also building private AI capacity on bare metal and GPUs, and on sovereign infrastructure with no hyperscaler involved. The control semantics should not change when the substrate does, and that is where on-premises and air-gapped deployment experience is most useful.

Responding to members' requirements

Mirantis is making two commitments (for right now), both as a contributor.

Common Cloud Controls. We will work in the CCC working groups to help extend the catalogue to Kubernetes, bare-metal and accelerator capabilities, so that the same controls apply whether the service boundary is a hyperscaler API or a rack in the institution's data center. Where members find it useful, we will offer our open source projects as a reference against which CCC assessment requirements can be executed and reproduced.

AI Governance Framework. The AIGF's mitigations are strongest today at the model and application layers. We will contribute infrastructure-layer mitigations and reference implementations: how isolation, artifact provenance, admission policy and observability satisfy specific AIGF controls, expressed declaratively so they can be validated rather than attested.

Beyond those two, the stance is the one in our FINOS announcement: listen to what members need, and bring code where it is wanted.

In the open

Our 2022 announcement said that collaboration is the fastest path to innovation. The clearest lesson of the years since came from watching a bank's platform team solve a problem for itself and place the solution in a neutral foundation for others to use. Rejoining FINOS is how we hold up our end. If you work on infrastructure inside a regulated institution, find us in the Common Cloud Controls and AI Governance Framework working groups, or at the Open Source in Finance Forum. Bring the difficult questions.


Choose your cloud native journey.

Whatever your role, we’re here to help with open source tools and world-class support.

GET STARTED
contact-us