Inner source is the adoption of open-source development practices, tools and culture within the boundaries of a single organisation, allowing teams to discover, use and contribute to each other’s code as if it were open source internally. It promotes shared repositories, transparent collaboration, peer review and meritocratic contribution while keeping the code private to the company. The approach aims to reduce duplication, improve quality and spread knowledge across organisational silos.
- Inner source applies Open Source practices, tooling and culture inside one organisation, letting teams collaborate across boundaries as a form of Distributed Collaboration.
- It uses shared repositories and Version Control to enable Knowledge Sharing while keeping code private.
Overview
- Inner source borrows the transparency, peer review and meritocratic contribution of open source and applies them internally.
- Teams publish their code to an internal commons where others can read, reuse and submit improvements.
- The goal is to reduce duplicated effort, raise quality and break down silos without releasing code publicly.
Key aspects
- Internal shared repositories acting as a company-wide commons.
- Transparent, asynchronous collaboration across teams.
- Trusted maintainers reviewing and merging external contributions.
- Clear contribution guidelines and lightweight governance.
- Cultural shift toward openness within organisational limits.
Mechanisms
- Pull-request style contribution mirrors open-source workflows.
- Version Control platforms host the internal commons and history.
- Maintainer roles steward quality and direction of shared components.
- A Governance Model defines ownership, review and acceptance.
Applications
- Large enterprises reducing duplicated internal tooling.
- Shared platform and library components consumed across teams.
- Spreading engineering culture and best practices internally.
- Bridging toward eventual external open-sourcing of components.