Re: Updates to Our Licensing Terms
Posted: 27 Mar 2024, 21:05
This seems correct, yes. One license per server.Some people already told me they want to provide a third-party service where they create their own version of the project, offer cloud-hosted servers, and provide their clients with a compiled client for each platform (since it's a cross-platform project). In this case, would they need a license per client subscribing to their services, per server a client sets up, or would a single license be enough to offer their services? Of course, I understand that under the tiered pricing model, they would pay based on the revenue they generate. This means that after reaching a certain revenue threshold, they would need to upgrade to the next license tier. Am I right?
In general, these assumptions are correct. New binaries require a new license. And our license keys can't be transferred to other companies.Here is a few examples of commercial models that I think could happen with my project:
- They start offering cloud-hosted servers and provides specific binaries for each platform so they can connect to their servers, in this case based on my understanding the person who is offering the product would require a license but not the client.
- They sell a custom project license which includes only binaries so the buyer can setup as many servers as they want in their own hardware, in this case would be the same as the first scenario.
- They sell a modified client and server source code so they would need to compile by themselves, I guess in this third scenario each user who is going to compile it would require a license.
- I offer binaries compiled on the fly by some service that I create (with free and paid subscription) to make it easier for each user to compile the project for each platform, in this case I guess they would need to provide their NoesisGUI license which would be allocated temporarily in a docker instance to provide binaries.
Development files included in our SDKs (C++ headers, libraries) must be never redistributed to your clients. The same thing for the license key information. Your clients must download Noesis and get a license directly from us.Regarding the last scenario that would be my case, I want to be sure what kind of guidelines I would have to follow to avoid any kind of misunderstanding or breach of contract, I intend to buy a license soon, either just to continue development (like token of my gratitude) and also to offer this kind of service in the future.
Of course, this doesn't apply to runtime files like Noesis.dll, they are allowed to be distributed.