Open source software imparts a number of benefits, including decreasing product development time, distributing development across a community and attracting developers to your organization. However, some organizations shy away from it due to perceived risks and disadvantages around intellectual property. Once you've incorporated open source into your products or open sourced your own code, it's common to worry that you've surrendered control over your most valuable assets, or even worse, left your organization vulnerable to litigation with no defensive weapons with which to protect yourself.

Good news: it is possible to simultaneously support an open source program while maintaining an active IP program. Smart organizations can avail themselves of the benefits of open source, identify the aspects of its software that are of interest to a broader development community—and thus good candidates for open sourcing—and protect those aspects of its software that are unique to the business or provide a competitive advantage through various IP protections.

The issues exist on a spectrum. There are 100 percent open sourced projects or products at one end, like the programming languages Python, Rust and Google's Go. In the middle are products that make use of a combination of open source and proprietary code. At the far end is proprietary software that is 100 percent closed. Most businesses today are somewhere in the middle. To strike an effective balance between open source and proprietary code, organizations have to think strategically about the value a piece of software provides to the company and whether it makes sense to develop it internally.