The Open Source Program Office (OSPO) model of governance is used to manage use of, and contribution to, OSS projects. This model is becoming more common in public administration. As the use of OSS by public administrations grows, efficient governance models become more important. Awareness and planning of technical, legal, procedural and strategic dimensions can greatly increase the benefits that public administrations can get from of open source software. Public code faces a lot of expectations on quality, usability, privacy, transparency, and value to society at large. OSS can help reach these standards, and the OSPO governance model helps get the most out of OSS.
With this page, we want to help public administrators on setting up their own OSPOs and encourage them to share their experiences with the community. You can join the OSOR collection and publish your articles here, or send us an email to EU-OSOR[at]ec.europa.eu.
Jump to:
Key facts
WHAT ARE OSPOs?
OSPOs are dedicated teams or units that coordinate an organisation's open source strategy, governance, and engagement. They oversee processes like software selection, compliance, contributions, community, collaboration, and training.
EU COUNTRIES WITH AN OSPO
at the government level
OF FORTUNE 100 COMPANIES
have established an OSPO and their adoption is generally training upwards. While originating in the private sector, OSPOs are increasingly adopted in public institutions too.
OSPOs PROVIDE SUPPORT FOR
- Design and execution of open source strategies
- Use and adoption of open source software
- Development and release of open source software
- License selection and monitoring
- Developing key applications
- Analysis and following up on open source software adoption and evolution
- Communicating and managing relations with the open source ecosystem
- Training and education
KEY SUCCESS FACTORS
of establishing an OSPO:
- Alignment with organisational goals
- Understanding organisational culture
- Management support
- Formalisation of the OSPO
- Finding place in the ecosystem
THE EUROPEAN COMMISSION OSPO MISSION
- Removing legal barriers
- Promoting open source solutions
- Integrating open source into IT governance tools
- Managing of code.europa.eu, fostering code sharing
The EC OSPO was created in 2020 as the first concrete action of the Open Source Software Strategy for 2020-2023.
FAQ
If your organisation uses, develops, or relies on open source software, an OSPO can help coordinate strategy, ensure compliance, and foster sustainable collaboration with the open source ecosystem. Organisational needs vary, so it’s important to conduct a thorough assessment before making a decision.
The first step is to define clear objectives: what do you want the OSPO to achieve? These could include compliance, contribution to open source, community engagement, or internal capacity-building. Once objectives are set, conduct an internal assessment to identify who uses open source, how it is used, what policies exist, and which resources are available. Finally, define a clear mandate and secure management support.
Yes. Many governments and organisations have made their OSPO frameworks public, such as the European Commission, the City of Paris, and the German state of Schleswig-Holstein. Browse the OSOR country reports, OSPO case studies and FLOSS-PSO directory to see how others have approached it.
There is no standard size or structure. Some OSPOs start with a single coordinator who dedicates only part of their time to OSPO activities during the initial phase, while others are established as full departments. The right set-up depends on your organisation’s open source activities and ambitions.
OSOR plays a central role in supporting public administrations adopting open source solutions by providing resources, guidance, and a platform for community exchange. The FLOSS-PSO Network is an initiative listing and connecting public sector OSPOs, facilitating contact, visibility and opportunities for joint work. OSPO++ offers a global community connecting OSPOs in universities, governments, and civic institutions to support their strategic objectives and foster worldwide cooperation.
Event key takeaways: spotlight on OSPOs in the public sector
Join the OSOR Webinar : Exploring the role of OSPOs in transforming public services with open source
Trinidad and Tobago will open an Open Source Program Office
OSPO library
Think-tank publishes a blueprint for Cybersecurity OSPOs
Webinar for representatives of public services
Lero gets a European open science award for launching OSPO and Ope
Galician Region Publishes Good Practices for Releasing Open Source
The Open Source Observatory (OSOR) has developed an eLearning course on Open Source Software for EU Public Administrations, now available on the Interoperable Europe (IE) Academy.
Module 2 focuses on how public administrations can effectively manage open source software across its lifecycle. It introduces the key components of open source governance — from project structures and policies to collaboration models and community engagement. The module takes approximately 30 minutes to complete, and participants can obtain a certificate of achievement upon completion.
Module 2 is structured around three chapters:
- The open source project lifecycle: This chapter explains how open source projects evolve — from initial idea to maturity — and how public organisations can contribute throughout.
- Open Source Programme Offices (OSPOs): An OSPO serves as a strategic hub for open source within an organisation. This section explores how OSPOs manage licensing, security, compliance, and collaboration, and presents best practices for establishing and operating an OSPO.
- Open source communities: Open source thrives on collaboration. This chapter discusses how to build and sustain open source communities within the public sector, covering levels of openness, typical community roles, and approaches to fostering inclusivity and engagement.