Well. Uhm. We don&#x27;t know us well. I guess this needs some clarification.<p>We&#x27;re a &quot;15 year old startup&quot; and we&#x27;re very active with serveral open source projects. Our decision to not open source the project at the early stages is a decision that serves certain goals for us and the project.<p>First of all, we see some interest in the technical foundation of eZing. We admit it, we don&#x27;t want to see a lot of forks and other people making profits based on our work while our initial investments are not covered. Yes, we&#x27;re selfish like that.<p>The second goal is that we want eZing to stay. Forever if possible. When we look at successful open source projects, we noticed that quite some of them have had a proprietary or at least a protected &quot;childhood&quot;. If open sourced at the right moment, a development community can take the momentum and relevance of the software and lead it to heights a single company is not able to. 
There are two things that can go wrong: Open source it too early, before the technology is relevant or open source it too late, when the horse is already dead. The approach we choose is of course not a guarantee, but we believe in this approach.<p>Regarding the review and transparency: We are not willing to limit disclosure of the source code only to security companies or entities like that. We know that trust is not easily earned. If you allow us to dream, then we would - under NDA, see our first goal - disclose the code on a permanent basis to a group of developers that have earned the trust of the community until we finally release it as open source.<p>We&#x27;re thankful for your thoughts on this and we would be glad to further discuss solutions so we get eZing off the ground.