A Practical Guide to Inner Sourcing Your IDP
Strategies for treating internal developer platforms as open source projects to bridge developer-platform team gaps.
Abstract
Bridging the gap between developers and platform teams is hard.
Scattered documentation, domain-specific language and hidden knowledge leave developers frustrated, while platform teams struggle to understand what devs really need. Treating platforms as products is a start, but treating them like open source projects, allowing developers to contribute and maintain features, is where real collaboration starts.
In my roles as Developer Advocate and Platform Engineer, I have years of experience working with highly bureaucratic organisations, helping to improve developer experience and adoption.
In this talk, I’ll share concrete steps to identify contribution opportunities, set up maintainable processes, and measure engagement. You’ll leave inspired with ideas to boost adoption, reduce friction, and turn your platform into a collaborative, thriving ecosystem.
Scattered documentation, domain-specific language and hidden knowledge leave developers frustrated, while platform teams struggle to understand what devs really need. Treating platforms as products is a start, but treating them like open source projects, allowing developers to contribute and maintain features, is where real collaboration starts.
In my roles as Developer Advocate and Platform Engineer, I have years of experience working with highly bureaucratic organisations, helping to improve developer experience and adoption.
In this talk, I’ll share concrete steps to identify contribution opportunities, set up maintainable processes, and measure engagement. You’ll leave inspired with ideas to boost adoption, reduce friction, and turn your platform into a collaborative, thriving ecosystem.
Recording
KubeCon+CloudNativeCon EU (2026)