In financial services, time has always been money. Every millisecond matters on the trading floor, every redundant engineering cycle represents lost opportunity, and duplicated responses to regulatory requirements are costly, time consuming activities that could be shared.
When I joined the Fintech Open Source Foundation (FINOS) community in New York for the Open Source Finance Forum (OSFF), velocity and speed were the defining themes on the mainstage, and in many hallway conversations, and sessions. It was a theme very much supported by evidence from the 2026 State of Open Source in Financial Serivces report, a project I’ve been proud to be part of for the past six years.
This year’s study provides new data combined with first-hand practitioner reflections on this speed, and on a number of other value points relevant to organizational open source engagement within the sector. Together with Scott Logic, a long-standing research partner to FINOS and the Linux Foundation, and BrightQuery, our report sponsor, we have witnessed cautious participation evolving into an industry moving at full throttle. That trendline is among the most inspiring since we first began work on measuring trends at the intersection of open source and financial services.
The report also reveals that the financial sector has officially moved beyond passive consumption into an era of structural mutualization, pooling capital, code, and standards to achieve relevant cost savings and other examples of ROI.
For years, the primary narrative around open source in banking centered on cost reduction. While financial efficiency remains vital—with organizations reporting average annual cost savings of $4.1 million and 15% saving more than $10 million annually—the true story in 2026 is about speed and execution. The report reveals that 88% of respondents agree that open source software delivers faster development time to market and improved productivity, while 88% also agree that it’s valuable to the future of their organization.
This strategic recognition is translating directly into code. Financial services organizations are no longer standing on the sidelines; they are building the tracks as they run on them. Over the past year, GitHub commits by financial services users surged by 63% year over year, reaching more than 1.26 million commits across 67,479 unique public repositories. Furthermore, 93% of institutions now permit open source contribution in some form, and 58% have implemented an Open Source Program Office (OSPO) to formalize their engagement.
As development velocity accelerates, so too does the complexity of the software supply chain. In a sector governed by strict mandates like the Digital Operational Resilience Act (DORA), knowing what is inside your software estate is non-negotiable. The report shows that 78% of organizations are mostly or fully aware of the open source components running in their systems. Yet, visibility has exposed a massive operational drag: maintenance debt.
According to the report, 35% of respondents spend more than half of their engineering capacity simply maintaining, upgrading, or remediating existing open source dependencies. Even more telling, 71% of organizations maintain private internal forks of open source projects. When hundreds of banks independently patch the exact same vulnerabilities in isolation, they pay a massive single-firm premium for zero competitive differentiation.
With security vulnerabilities (46%) and supply chain attacks (42%) topping the list of industry concerns, institutions are realizing they cannot patch their way out of this challenge alone. Instead, they are turning to neutral foundations to share the load. Initiatives like the Open Source Enterprise Resiliency Alliance (OSERA) allow banks to pool resources and apply secure back-patches collectively at a fraction of the cost. By collaborating on shared infrastructure and industry standards—such as the Common Domain Model (CDM), FDC3, and multi-firm platforms like Fluxnova—institutions eliminate redundant engineering and free up talent to focus on true commercial differentiators.
Nowhere was the theme of speed more palpable at OSFF New York than in discussions around artificial intelligence. The report demonstrates that financial services has rapidly escaped the AI prototype trap: 64% of respondents work at organizations that have already deployed agentic AI in production, either internally (41%) or externally (23%). AI has become a standard fixture in the software development lifecycle, with 87% of respondents reporting productivity gains over the past year.
However, generating code at machine speed introduces new governance bottlenecks. While 65% of respondents use AI tools for code generation, concerns around AI-driven dependency sprawl and code quality are rising, cited by 34% of participants. More broadly, as organizations look to scale autonomous agents across business intelligence (40%) and compliance workflows (38%), the primary roadblocks are not technological—they are institutional.
Reflecting on six years of tracking this ecosystem, the story told by The 2026 State of Open Source in Financial Services is one of an industry coming of age. Financial institutions have proven that fierce competitors can collaborate safely on the foundational layers of technology. The organizations that will lead the next decade are those that treat open source not as a bottom-up developer preference, but as a measured, executive-level discipline.
To build on this momentum, technology leaders should focus on a few core priorities:
We extend our deepest gratitude to our research partners, sponsors, survey respondents, and the senior industry leaders who shared their candid insights to make this study possible.
To explore the complete data, benchmark your organization's open source maturity, and discover our full library of insights, download The 2026 State of Open Source in Financial Services and explore our broader collection of reports at https://www.linuxfoundation.org/research.