References ▼
The primary intent of the "single application" limitation for a development license is to ensure a contract developer or consultant is not able to purchase a single copy of LEADTOOLS and perform multiple custom programming jobs for different clients. Therefore, LEAD’s policy is to construe the definition of single application quite broadly as described below.
A customer is developing a system for internal use. The system is composed of multiple software modules. Each module was developed with LEADTOOLS, but all modules are part of the same internal system. LEAD considers the system and all of its component modules to be one "application" for development licensing purposes.
A customer develops a "suite" of applications that are always sold as a suite. LEAD considers the suite to be a single application for development licensing purposes.
A customer develops an evaluation version or a "lite" version of its application. LEAD does not require a separate development license for the evaluation/lite version.
A customer develops a new version of or update to an existing application. LEAD does not consider the update or new version to require an additional development license.
A customer develops an application for Windows, and later develops a Linux version and an Android version of the same application. One development license covers all OS versions of the application, assuming each version is developed by the same developer.
A customer develops a software engine that is contained in two products that are sold separately. In this case, the customer must buy a development license for each product, even if the engine is basically the same in each of the separate products.
A customer who develops a custom application for a client with LEADTOOLS may not use the toolkit to develop an application for another client unless the customer purchases a second development license. For example, if a consultant develops an application for one customer, and then subsequently develops an application for another customer, a second development license would be required. The developer would build the cost of the development license into its quotation for each project. In addition, the developer would need to assign the LEADTOOLS development license to the customer if the developer delivers his source code to the customer.
A LEAD product version or platform upgrade does not count as a second toolkit for the above-described purposes. For example, if a customer originally licensed LEADTOOLS Version 20, then later ordered an upgrade to Version 21, the customer holds only one product license. If two programmers are using the LEAD product at the same time, or two applications have been developed using the LEAD product, a second toolkit development license must be purchased.
LEAD may offer an Enterprise License for organizations requiring an unlimited license. An Enterprise License allows the customer to use the LEADTOOLS SDK for the development of an unlimited number of end user applications. Please contact sales@leadtools.com if you are interested in obtaining an Enterprise License.
For more information, refer to:
LEADTOOLS Standard End-User Software License Agreement (EULA)