How can one software have both open source and commercial versions? [closed]

Question

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.

---

This question does not appear to be about programming within the scope defined in the help center.

Closed 6 years ago.

Improve this question

I happen to know there is a routing software which has one GPL open source version, Zebra project and a commercial version, Zebos. This is against my understanding of open source. If the 2 software are based on the same code base, isn't it right that the GPL version automatically mandates all other variants including the commercial one open source?

Answer 1

I am not a lawyer, but:

The GPL mandates all variants of the GPLed code be GPLed, however, nothing stops the original author from offering the original code in both GPLed and non-GPLed variants.

For instance, I could write a library, and release it under the GPL and also separately release it under a proprietary license requiring a fee. Since I did not modify the GPL licensed version, this is fine. Anyone who acquired the GPL would be bound by the GPL. Anyone who paid me and acquired it under the terms of the proprietary licensee would be bound by the terms of that license.

When a company decides to open source something under the terms of the GPL, there is nothing that stops it from doing whatever it wants to the original codebase, including making modifications without releasing them. The GPL binds people who agree to the license, but not the original author.

Answer 2

If the core is open source and shared its one case , but consider the following:

2 versions, one that relies on an open source component, and one that isn't , for example:

A software company who specializes in C# / WPF development , developed version A with Component X written in C#. they wanted a version that does the same , but in a web environment, they couldn't use their core code and it had to be re-written, but they used an open source substitution for component X, for whatever reason you choose (manpower, time to market etc.):

Result:

• version A will be commercial.

• version B will be open source.

No code sharing between versions, although they are basically the same product.

Additional Note

I believe (worth looking into) you can have code sharing between version and still not share the same license definition in some cases. for example :

Version A and Version B are both client applications, no code sharing per say , but the same server application is used.

Answer 3

Some companies have open source versions of products, but offer additional services for fees, such as support.

Answer 4

Zebos is commercial and zebra is open source. The code base for both software are different. Zebos is from IPInfusion and zebra is open source.