InnerSource Adoption Trends #268
Replies: 8 comments 7 replies
|
In 2023 StackOverview Survey, the percentage went down to 14.13% - but that corresponded to a higher number of respondents than 2022 saying they practiced InnerSoruce (5.9K vs 5.5K).
|
|
Copying references for InnerSource -> Open Source examples from Slack discussion here: 9 replies mainec @Carsten Hoffmann Clare Dillon 3:47 russ apache/fory dirkriehle gilyehuda Guilherme Dellagustin Tom Sadler |
|
Reference 2024 Gartner Hype Cycle for Software Engineering - taken from here: https://www.harness.io/blog/platform-engineering-beyond-the-trough-of-disillusionment |
|
Gartner Blog Post in Sep 2024 Maximize Platform Development Velocity Using InnerSource Summary |
|
Reference to Gartner's 2024 Hype cycle for Software Engineering. InnerSource is also on the 2025 Gartner Hype Cycle (as confirmed to us by email from Gartner on 4th Nov 2025) - moving into the trough of disillusionment. |








Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
The purpose of this thread is to keep track of reports of InnerSource adoption, emphasizing the growth in InnerSource momentum in previous years. It's intended for use by anyone creating resources regarding InnerSource and includes ISC and external references. If you come across something that could be of use, please do add it as a comment. Thanks!
InnerSource Trends
Although the term was coined by Tim O’Reilly in the early 2000s, InnerSource began to gain momentum in 2015, coinciding with the foundation of InnerSource Commons.
Since 2020, there has been another positive shift in momentum around InnerSource. In recent years, many industry research reports and opinion pieces have noted InnerSource as an important emerging software developer trends:
All reactions