Decentralized Ecosystem Growth
The Decentralized Ecosystem Program ("DEG") program aims to aggregate, develop, and integrate tools that facilitate coordination of decentralized applications across disparate financial services firms and ecosystems. This is still a new and evolving landscape and the program aims to provide an open venue for everyone, both large firms and individual developers, to work together to accelerate delivery of tangible value.
The FDC3 is a standards group whose mission is to develop protocols and taxonomies for local communication between financial desktop apps
Hadouken is the open source core of the OpenFin OS, a secure user agent for running web apps with native experience and interoperability
Data Technologies
This program supports open collaboration for technology and tools supporting common uses of data across the full lifecycle of financial services - including but not limited to data acquisition, storage, governance, processing, and distribution.
Financial Objects
The Financial Objects program is focused on identifying standardized structured objects that support Financial Services industry workflows
Open Source Readiness
The Open Source Readiness (“OSR”) program helps address the unique obstacles financial services firms face with open source collaboration - legal & regulatory concerns, internal policies, cultural friction, and heavily restricted technology environments.
Data Analytics Visualization
Robust and flexible data visualization tools are essential to derive value from the vast amounts of complex data delivered at increasing speeds. This program supports open collaboration on technology and tooling focused on user driven data analytics & visualization to deliver that.
Financial Delivery Accelerator Program
The Financial Delivery Accelerator (“FDX”) program is focused on solving some of the unique challenges developers in financial services and fintech face due in part to the highly regulated and risk sensitive nature of the industry.
Plexus Interop
Plexus program aim is to enable development of extensible workflows connecting independent desktop apps developed by different organizations in different technologies (.NET, Web, Java, Python, etc.) by passing relevant context (structured data objects) between those apps.
The Symphony program is focused on interoperability of tools and applications built on top of the Symphony platform
FINOS' voice program fosters collaborative development related to voice technologies, voice metadata, and voice APIs


Programs are how the FINOS community organizes its nearly 100 working groups and projects. Programs help align efforts, address shared business problems, and build out common technical platforms. 

Some programs, such as FDC3, are focused on building new standards for interoperability. Others, like the Voice and Data Technologies programs, are organized around sets of use cases in a particular area of the financial services technology stack. Still other programs, such as the FINOS Symphony and Hadouken programs, house and govern open source projects built on a specific development or technical platform.  

It's through creating standards together in a program working group, or by writing code for a new platform or API in a program project, that industry participants typically first get engaged with FINOS. These initial forays into our community often lead to lasting cross-firm collaborations , deeper professional networks, and, quite often, new personal friendships. 


 Ready to get involved in the FINOS community? Here's how:

  • Check out the descriptions of the FINOS programs above. Find one that might be interesting to you or your firm.

  • Available via the "participate" buttons below, each program has its own program site or wiki where you can find all sorts of useful information about current activity within FINOS programs, including specific information about the programs' working respective groups and projects, meeting minutes, as well as meeting times and dial-in information. Joining, say, an upcoming working group call or program general meeting is a great way to experience FINOS and see our collaborations first hand. The wiki also is where you can also find recent meeting minutes.

  • Communication between scheduled meetings, and much of the overall collaboration within the community, occurs via Google Group mailing lists. A great way to get involved is to subscribe to the general mailing list for a program. Specific mailing lists used for projects and working groups within a program can be found on the respective program's wiki as well as in the directory of FINOS mailings lists.

    (If you encounter any issues getting access to FINOS Google Group mailing lists, send an email to and we'll get it sorted out).
  • Developers and other technologists eager to get their hands on code should look for the Github buttons below to check out the various code repositories associated with a program's projects (Note some new programs may not have Github repos set up yet).

NOTE: Commits and pull requests of code to FINOS repositories will only be accepted from those contributors with an active, executed Individual Contributor License Agreement (ICLA) with FINOS OR who are covered under an existing and active Corporate Contribution License Agreement (CCLA) executed with FINOS.

Commits from individuals not covered under an ICLA or CCLA will be flagged and blocked by the FINOS "CLA-bot" tool. Please note that some CCLAs require individuals/employees to be explicitly named on the CCLA.

Need an ICLA? Unsure if you are covered under an existing CCLA? Email



Programs are the community's mechanism through which business issues, market opportunities, and use cases are grouped together. It's through the program structure that FINOS members and contributors cooperate, specifically by creating and organizing themselves into projects and working groups

  • Projects produce shared solutions to business problems in the form of code made available though an Open Source license for any organization to use.
  • Working groups are focused efforts to creating common definitions, protocols, practices, processes and standards. However, they usually do not produce code. 

A program may have multiple projects and working groups.


Check out our contribution process if you have an idea or want to contribute to an existing program.

New programs are proposed by FINOS Members and approved by the Board of Directors.  Check out our wiki to suggest an idea for a program or contact us!


FINOS is committed to providing a welcoming, professional, and safe environment for every member of our community. Our Community Code of Conduct sets out clear, common-sense guidelines for respectful participation. If you learn of a violation, please report it to