Skip to content

Licensing

Ruslan Konviser edited this page Nov 25, 2020 · 14 revisions

Official Information

Please make sure you read our official information about the licenses here: https://github.com/ever-co/ever/blob/develop/LICENSE.md

IMPORTANT: below is not legal advice. Please consult your lawyer about licensing & usage of open-source software!

Our Open-Source Licenses

One of the main requirements for usage of the AGPLv3 open-source software is to keep changes in the source code under the same license and make them public. For example, make a public fork on Github of our repositories and do changes there. Do not modify or remove the AGPL v3 license from your fork!

We decided to go with the AGPLv3 license for the same reasons many other companies who build true open-source software make the same choice. For example, see the recent move of Plausible described here: https://plausible.io/blog/open-source-licenses (some text below adapted from that blog post)

Benefits of the AGPLv3

AGPL is designed to ensure corporations contribute back to the open-source community, e.g. when running the software as a service in the cloud. If you used AGPL-licensed code in your web service in the cloud, you are required to open source it. It basically prevents corporations that never had any intention to contribute to open source from profiting from the open-source work.

Some restrictions with the AGPLv3

GPL license helps minimize the possibility that corporations can take advantage and profit from open-source software without contributing back to the project and the open-source. It basically says that as we open-sourced our code so should you too and everyone can benefit from it.

A corporation needs to be clear and provide a prominent mention and link to the original project so people that are considering using their version of the software can be aware of the original source. If a corporation modifies the original software, they need to open source and publish their modifications by for instance contributing back to the original project.

So how can a corporation commercialize a FOSS project without open-sourcing their modified code? They can purchase our commercial license(s) to remove the copyleft restrictions and in that way support the original project.

Our Commercial Licenses

Our commercial licenses are required, for example, if you don't want to release your code changes as open-source (e.g. you want to keep code private). We encourage everyone to use our open-source versions to benefit the community (and as a result make our platform better).

You can check more information about our Commercial Licenses and they cost at https://ever.co/pricing

FAQ

Q: Can I use the same brand name or Logo, i.e. "Ever" or "Gauzy"? A: No, we hold a registered trademark Ever® and we have used Gauzy™ trademark and you can't use any of our trademarks without written permission. You need to replace our logo and brand name with your own in all apps of the platform!

Q: Can I use Ever Platform or Gauzy Platform software for free?
A: Yes, as long as you can comply with AGPLv3 license requirements, you can use our software for free!