Open Source in Production: Why Your Company Needs an OSPO (Before It's Too Late)

Today, 87% of code in production contains open source components, yet most companies lack a clear strategy to manage them. The result? Unpatched vulnerabilities, license violations, abandoned critical dependencies, and development teams reinventing the wheel.

An Open Source Program Office (OSPO) isn't a luxury for Big Tech: it's a strategic necessity for any company that develops software. But what exactly does an OSPO do? And why should you convince your C-level to invest in one?

In this talk we'll explore:
- The hidden cost of "wild west" open source: compliance, security, and technical debt
- The 4 pillars of an effective OSPO: governance, security, contribution, and culture
- Measurable ROI: from avoided costs to concrete competitive advantages
- Where to start: practical roadmap to begin even with limited resources

Through real cases (successes and failures), you'll discover why companies that excel at open source don't do it by chance, but through dedicated processes, competencies, and ownership.

Whether you're a CTO looking to reduce risks, an engineering manager seeking efficiency, or a developer advocate wanting to contribute better: this talk will give you the arguments to take the first step.