SOOS began as a side project, born out of my own experience as a Software Architect helping out with an organizational compliance exercise. There was a moment during the due diligence process where it became apparent that security and licensing in open source software were things we needed to worry about. While attempting to manually identify all the licenses and potential compliance issues within the various branches of code, I felt there had to be an easier way. So I did some research… 

What I found was frustration. Of the available tools, there was a great deal of confusion around features, pricing, and user seats. Nothing was straightforward, and after spending a ton of time reading through websites and talking to sales representatives, I still didn’t feel any closer to the solution I was looking for. This motivated me to begin building a tool myself.

As an architect, I also wanted SOOS to be something I would want to use, and something developers everywhere would be excited about. As security breaches become more commonplace, it is critical that companies are aware of each and every dependency within their code. I’m proud to say SOOS is available to help the development community stay secure.