Clarification on Bryntum Scheduler License Usage Across Projects

[divyanshkumarbohz26]

Hello Bryntum Community,

I’d like to clarify how the Bryntum Scheduler license applies when working across different repositories and projects. Specifically, I have a few concerns:

1. Can a single license be used for multiple projects, or is it restricted to one?

2. If we purchase a license, does that mean we can’t use it in any other GitHub repository, even for testing purposes?

3. If the license does restrict usage to a single project, how can we test different setups before final implementation?

Understanding these restrictions will help ensure compliance while maintaining workflow flexibility. If anyone has insights or official guidance, please share your experiences.

Looking forward to your input!

[marcio]

Hey divyanshkumarbohz26,

Thanks for reaching out.

1. A single Bryntum Scheduler license can typically be used across multiple projects within the same organization, as long as it adheres to the terms specified in the license agreement. It's not restricted to just one project.

2. You can use the license in different repositories, including for testing purposes, as long as it is within the scope of your organization and complies with the license terms.

3. The license does not restrict usage to a single project, so you should be able to test different setups before final implementation without any issues.

For detailed information, it's always best to refer to the official license agreement or contact Bryntum directly for clarification.

[marcio]

Just adding more info here

There are no restrictions regarding being used by many applications if the client has an EUL license (internal software).

An OEM license is required for commercial software, and other conditions apply according to the agreement.