How Open Source Enables Collaboration in Creating a Platform

2026-07-09 · Source: InfoQ · Field: Technology & Digital — Software Development & Engineering, Cloud Computing & IT Infrastructure, Platform Engineering · Depth: Intermediate, extended

Summary

A KubeCon & CloudNativeCon Europe talk by Marcy Paramonova and Stéphane Cusin detailed how Pictet, a private Swiss bank, leveraged open source to build a collaborative internal developer platform. Despite a highly regulated environment, Pictet transitioned from a traditional enterprise stack to a cloud-native approach, now managing over 1,700 Kubernetes clusters on-premises and 200 on AWS. This transformation was driven by open source providing shared standards and a common language, fostering trust through predictable platform behavior, and a cultural shift towards community-driven practices. Key initiatives included "Genius Bar" support sessions, technical exchanges, super user rewards, and a technology adoption framework based on active use, open ecosystems, auditability, skill availability, and documentation.

Key takeaway

For DevOps Engineers or IT Professionals building internal platforms in regulated environments, prioritize open source as a "compass" for technology adoption. Focus on building trust through predictable operations and explicit responsibilities, rather than just features. You should actively design a collaborative culture with mechanisms like "Genius Bar" sessions and super user rewards to ensure platform success and scalability, as tools alone won't drive cultural change.

Key insights

Open source fosters platform trust and collaboration by establishing shared standards and a community-driven engineering culture.

Principles

• Trust is built through consistent, predictable platform operation.
• Open source acts as a compass for technology adoption.
• Culture must be designed, not left to emerge.

Method

Adopt new technology using a 5-question framework: Is it actively used? Open or vendor-controlled? Has an ecosystem? Auditable? Well-documented?

In practice

• Implement "Genius Bar" sessions for direct user support.
• Reward "super users" who contribute feedback.
• Define explicit platform responsibilities and service levels.

Topics

• Open-Source
• Platform Engineering
• Kubernetes
• DevOps Culture
• Banking Technology
• Digital Transformation

Best for: CTO, VP of Engineering/Data, DevOps Engineer, Software Engineer, IT Professional

Related on AIssential

• How a Culture of Data-Driven Conversations Can Support Platform Engineering — Platform engineering success hinges on data-driven conversations, continuous architectural simplification, and embedding sovereignty from design.
• How to contribute to Open Source - 7 EASY steps 🤗 — A structured, seven-step process simplifies contributing to open-source projects, from identifying issues to submitting pull requests.
• AI in Reality Fireside Chat: Enterprise AI & Open-Source Innovation — Enterprise AI success hinges on open-source adoption, human-centric strategies, and balancing innovation with regulatory realities.
• The Platform Engineer’s Handbook • Ajay Chankramath & Kaspar von Grünberg • GOTO 2026 — Platform engineering, viewed as a product, is crucial for building robust, vendor-agnostic foundations essential for effective AI integration.
• Building and Scaling a Platform with Project-as-a-Service — Shifting from full developer autonomy to a "paved road" with Project-as-a-Service reduces cognitive load and increases standardization for platform adoption.
• [D] Self-Promotion Thread — The community is actively developing diverse open-source tools and frameworks for ML education, research, and practical applications.

Open in AIssential →

Editorial summary, takeaway, and curation by AIssential. Original article published by InfoQ.