Releasing a library that uses Syncfusion controls under MIT license

Hi. Would it be OK to release a library that uses syncfusion controls from nuget.org as long as the license keys or any syncfusion files are not distributed / included in the source code?

What should we explicitly say in our documentation? Is there any page that has details about this matter?


1 Reply

JV Jaclyn Vidusic Syncfusion Team December 1, 2023 04:46 PM UTC

In order to allow Syncfusion to be used in an open-source project, we would need to put a Master License Agreement (MLA) in place. The Master License Agreement would have certain limitations.   

These limitations include, but are not limited to:  

  • You  are required to make it clear, in a license, to anyone obtaining your code, that they need to independently obtain dependencies (our product) from us whether under a community, commercial, or other license.  
  • You will not be able to license our binaries as part of the open-source project. 
  • The project can only be licensed under MIT, Apache, or BSD licenses. The project cannot be licensed under GPL or similar licenses.

A full list of limitations will be set forth in the Master License Agreement. If this works for you and your team, please let me know and I will start drafting the Agreement.  

Best Regards,

Syncfusion Legal Team.


Loader.
Up arrow icon