Call For Proposals (CFP)

The Open Source in Finance Forum (OSFF) is the premier event connecting the leaders in financial services, technology, and open-source innovation – a unique combination of business decision-makers and developers at one conference. This conference is uniquely designed to foster partnerships, advance talent development, and accelerate technological advancements across the finance industry, building faster, trusted, and secure solutions.

Open source is fundamental to the financial services industry, and OSFF provides companies with the tools and insights to maximize value through open source collaboration. By strategically contributing to open projects, organizations benefit from reduced development costs, heightened security, top talent, and rapid innovation. OSFF 2026 will spotlight groundbreaking advancements, deliver insights on best practices, and offer exclusive access to the leaders shaping open source in finance.

Please be aware that the Linux Foundation will now utilize Sessionize for CFP submissions. Sessionize is a cloud-based event content management software designed to be intuitive and user-friendly. If you need guidance, please review how to submit your session for an event to see step-by-step instructions and helpful screenshots.

• CFP Opens: Wednesday, June 10
• CFP Closes: Sunday, July 26 at 11:59 PM EDT / 8:59 PM PDT
• CFP Notifications: Monday, August 17
• Schedule Announced: Wednesday, August 19
• Slides due date: Tuesday, November 3
• Event Date: Wednesday, November 4 – Thursday, November 5

Reminder: This is a community event, so no product and/or vendor sales pitches.

We welcome talks on a wide range of topics relevant to open source in financial services. Our talk themes this year center around our strategic initiatives. 

Please Note:

Below are potential / suggested topics that speakers may use as guidelines within the conference themes above. PRODUCT / SALES PITCHES WILL NOT BE ACCEPTED. 

Please do not submit a general talk. We are very interested in talks built around our financial services decision-maker and technologist audience. Regulated industries like finance have a different set of rules that our community has to negotiate daily – so make your talk impact this community, not just open source communities in general.

Track Name: Financial Services Process Orchestration with Fluxnova

Note: Note: Day 1 (November 4) will focus on Fluxnova and how it crosses over to many, if not all of our FINOS open source projects. There will be about 20-30 talks total that day. Please choose “Fluxnova” in the drop-down menu to be featured on Day 1: Fluxnova Con.

Suggested Topics to Submit

• Agentic AI based workflows (using standard patterns such as MCP or A2A)
• Pre-trade, trade, post-trade process automation
• Using Fluxnova in conjunction with other open source projects (FDC3, CDM)
• Securing Agentic AI based workflows

Track Name: Agentic AI, GenAI, and AI Governance

Suggested Topics to Submit

• AI Readiness for Financial Services – Build Safe & Responsible AI through Open Source.
• FINOS AIGF (AI Governance Framework) – building a collection of risks and mitigations that support on-boarding, development of, and running Generative AI solutions within FSI environments
• The Rise of AI Agents and Digital Workforce in Financial Services: Enhancing Productivity, Automation, and Customer Experience.
• Moving from experimentation to production: Open Source for deploying Agentic AI workflows and Large Language Model (LLM) orchestration in financial environments.
• Practical applications of open source for AI agents for operational efficiency, customer service, and automating complex financial tasks.
• The role of emerging technologies, such as quantum computing and IoT, in shaping the future of finance.
• Practical applications of AI for operational efficiency, customer service, and risk management.
• Case studies on successful implementation of AI-driven financial models.
• Methods for complying with governance, regulations, & internal policies around emerging technology. 

Track Name: OSERA & Open Source Security and Supply Chain Risk Management

Suggested Topics to Submit

• OSERA – FINOS Open Source Enterprise Resilience Alliance – regulated institutions close patch coverage gaps and operationalize remediation at scale. We help participants prioritize vulnerabilities, sponsor open back-patches, define shared consumption standards, and apply patches from upstream, vendors, and elsewhere – with greater consistency and evidence
• Implementing secure open source practices in highly regulated industries.
• Tooling and methodologies for identifying and mitigating security vulnerabilities in the open source supply chain.
• Securing the open source software (OSS) supply chain: challenges, strategies, and innovations.
• Collaboration models that enhance the security of OSS projects through community oversight.

Track Name: HPC – High Performance Computing

Suggested Topics to Submit

• Scaling Financial Workloads in HPC environments
• Deployment of distributed workloads
• Hybrid Cloud and On-Premise HPC
• The Future of HPC in Finance

Track Name: Evolution @ Scale

Suggested Topics to Submit

• Reducing technical debt through shared infrastructure projects and community-driven architectural patterns.
• Essential developer tools and modernization techniques to tackle technical debt in large financial institutions.
• Addressing common financial institutions’ legacy modernization and ongoing maintenance challenges with AI.

Track Name: The Business of Open Source: ROI and Strategy

Suggested Topics to Submit

• From Promise to Proof: Defining and measuring the Return on Investment (ROI) of open source contributions and usage.
• Case studies showcasing open source as a driver of measurable business value, cost reduction, and technical agility. Bonus points if leveraging FINOS projects. 
• Strategies for making the business case to executive leadership and shifting organizational culture from “consumer” to “contributor.”
• Real-world success stories of financial institutions leveraging open source to accelerate speed to market.
• Gaining control of your own destiny: following the Fluxnova example, highlighting projects where financial institutions can and should come together to strategically maintain openly governed projects and reduce vendor lock-in.

Track Name: Open Source Security and Automated Compliance

Suggested Topics to Submit

• Featuring CALM: Leveraging “Compliance-as-Code” to automate regulatory adherence and control frameworks.
• Securing the software supply chain through Software Bill of Materials (SBOM) adoption and automated vulnerability management.
• Meeting the requirements of the Digital Operational Resilience Act (DORA) and other global cyber resilience regulations through open collaboration.
• Collaboration models and example projects for identifying and mitigating systemic risks in critical financial infrastructure.
• Featuring any FINOS projects in the tech risk space, like Common Cloud Controls, SDLC Controls, AI Governance Framework.
• OSS Supply Chain Security in a Post-Mythos world.

Track Name: FDC3, Identity, and Next-Gen Interoperability

Suggested Topics to Submit

• The evolution of the connected desktop: Integrating Voice, Natural Language Interfaces (NLI), and AI agents with FDC3 standards.
• Case studies in leveraging FDC3 to create seamless user experiences across desktop, web, and mobile applications.
• Innovations in cross-application identity management and secure data passing between financial workflows.
• Standards and best practices for unifying the financial workstation and improving trader productivity.
• FDC3 in the world of agents: the crossroads of MCP and FDC3.
• Fluxnova Tasks list feature in a FDC3-compliant mode.

Track Name: CDM (Common Domain Model), Regulatory Technology (RegTech), and Compliance

Suggested Topics to Submit

Track Name: Open Source Regulatory Technology (Open RegTech) and Data Standards

Suggested Topics to Submit

• Digital regulatory reporting: Open source approaches to transparent and automated reporting pipelines.
• Handling complex data and improving interoperability through industry-wide data standards.
• Collaboration among financial institutions to drive standardization in non-differentiating regulatory functions. 

Track Name: OSPO Strategy, Governance, and Licensing

Suggested Topics to Submit

• Best practices for establishing and scaling Open Source Program Offices (OSPOs) within highly regulated institutions.
• Navigating the legal and regulatory landscape of open source licensing, contribution policies, and IP management.
• Guidelines and tools for assessing organizational maturity and enhancing open source readiness.
• Strategies for managing vendor relationships and commercial open source software (COSS) procurement.

Track Name: Developer Experience, InnerSource, and Talent

Suggested Topics to Submit

• InnerSource Strategies: Fostering collaboration, code reuse, and transparency across internal engineering teams.
• Talent retention and upskilling: Using open source contribution to attract top developers and build internal expertise.
• Building internal talent pipelines and mentorship programs through involvement in OSS projects.

Track Name: Hot Topics in Open Finance

Suggested Topics to Submit

• Streamlining cross-industry workflows through open source and open standards: collateral management, payments, and settlement.
• Digital Assets: Stablecoins, Institutional adoption of blockchain, tokenization, and interoperability between TradFi and DeFi protocols.
• Physical risk and Sustainability-aligned investing: Open source data standards for ESG reporting, climate risk modeling (OS-Climate), and net-zero transition planning.
• Lightning talks on emerging trends: Quantum computing, Post-quantum cryptography, Open Banking, edge computing, and novel industry collaborations.

• Session Presentation (typically 30 minutes)
• Panel Discussion (typically 30 minutes)
• Workshop/Tutorial (typically 60 minutes)
• Lightning Talk (typically 15 minutes – ideal for first-time speakers)

• All speakers are required to adhere to our Code of Conduct. We also highly recommend that speakers take our online Inclusive Speaker Orientation Course.
• Panel submissions should include the names of all participants. In addition, The Linux Foundation does not accept submissions with all-male panels as part of an ongoing effort to ensure a range of perspectives and representation among speakers. If you need help in finding panelists, please reach out to [email protected].
• Avoid sales or marketing pitches and discussing unlicensed or potentially closed-source technologies when preparing your proposal; these talks are almost always rejected due to the fact that they take away from the integrity of our events, and are rarely well-received by conference attendees.
• Reviewers must be able to confidently assess a speaker’s subject-matter expertise from the proposal. Submissions that rely heavily on AI-generated or templated content often lack the specificity needed to evaluate technical depth and may be harder to advance. Please ensure your proposal clearly reflects your own experience and understanding of the topic you intend to present.
• All accepted speakers are required to submit their slides prior to the event.

While it is not our intention to provide you with strict instructions on how to prepare your proposal, we hope you will take a moment to review the following guidelines that we have put together to help you prepare the best submission possible. To get started, here are three things that you should consider before submitting your proposal:

1. What are you hoping to get from your presentation?
2. What do you expect the audience to gain from your presentation?
3. How will your presentation help better the ecosystem?

There are plenty of ways to give a presentation about projects and technologies without focusing on company-specific efforts. Remember the things to consider that we mentioned above when writing your proposal and think of ways to make it interesting for attendees while still letting you share your experiences, educate the community about an issue, or generate interest in a project.

How to Give a Great Talk

We want to make sure submitters receive resources to help put together a great submission and if accepted, give the best presentation possible. To help do this, we recommend viewing seasoned speaker Dawn Foster’s in-depth session titled Overcoming Imposter Syndrome to Become a Conference Speaker!.

Have More Questions? First Time Submitting? Don’t Feel Intimidated

Linux Foundation events are an excellent way to get to know the community and share your ideas and the work you are doing, and we strongly encourage first-time speakers to submit talks for our events. If you aren’t sure about your abstract, reach out to us, and we will be more than happy to work with you on your proposal.

The Linux Foundation is dedicated to providing a harassment-free experience for participants at all of our events. We encourage all submitters to review our complete Code of Conduct.