LEAD deployment licensing requirements and prices vary depending upon the type of deployment. The following are some of the typical types of deployments of End User Software developed with LEAD SDKs.
A “Commercial Deployment” is any distribution and other disposition of End User Software by our customer to third-party end-users, either directly or through distribution channels. Commercial Deployments are typical when our customer is acting as an ISV, OEM, or solution provider that offers End User Software to the public for license, lease, subscription, or other form of disposition.
An “Internal Deployment” is any distribution and other disposition of End User Software, including Single User Deployments, Concurrent Deployments, Server Deployments, Multi-user Deployments and/or some other deployment model approved by LEAD, by our customer to hardware devices owned or controlled by our customer for internal business use limited to our customer’s employees and contractors. If customer uses a third party cloud provider to host the End User Software and the End User Software is for use/consumption only by LEAD’s customer’s employees and contractors, this would also be considered an “internal deployment”.
“Hosted Service Deployment” is a type of Deployment where our customer is hosting End User Software on customer’s machines for consumption or commercial use by its customers, vendors, and other third parties. Examples of a “Hosted Service Deployment” include End User Software operated by a service bureau, application service provider, software offered as a service (SaaS), outsource facility, and any public facing End User Software hosted by our customer accessible by third parties via the internet or other network. If customer uses a third-party cloud provider to host the End User Software and the End User Software is for use/consumption by LEAD’s customer’s vendors, customer subscribers, the general public and other third parties, this would also be considered a “Hosted Service Deployment".
“Single User Deployment” is installation of End User Software by our customer and/or its customer on a stand-alone PC, work station, mobile device or other hardware for use by a single named user. End User Software that is deployed as Single User is intended for interactive use by the named end user, and has a GUI requiring the user to control the application by mouse, keyboard, touch-screen or similar means. A Single User Deployment also is applicable where End User Software is distributed to client machines through a deployment server or other network device via a CAB file or similar mechanism and installed on the client machine. Single User Deployments are commonly referred to as desk top licenses, client licenses, stand-alone licenses, app licenses and user licenses.
“Concurrent Deployment” is where our customer has built a reasonable method of concurrency into the End User Software so that, although installed on multiple PCs for single user uses, only a limited number of users are technically permitted to use the End User Software at the same time. For example, if the End User Software is installed on one hundred (100) PCs, but only ten (10) users may be logged in to use the End User Software at the same time, licensing for ten (10) Concurrent Deployments would be required instead of 100 Single User Deployment licenses. The fact that a server application is “queuing” jobs sent to it, and processing one job at a time, is not considered concurrency for purposes hereof. This type of deployment would be a Server Deployment. A Concurrent Deployment also occurs if our customer issues client licenses on a subscription type model and wishes to recapture client licenses that are no longer subscribed and assign such licenses to another user. Concurrent licenses are also commonly referred to as floating licenses.
“Server Deployment” includes the following: (i) End User Software installed on a networked device accessible by one or more persons who can independently operate the End User Software from another machine; (ii) End User Software installed on a networked device running as a service that accepts connections from other machines or applications (for example, a "headless" process to watch a folder or other data source for work originating from other machines), and (iii) End User Software deployed to a browser from a webserver, such as an HTML5 based application, where the End User Software is not installed on the client machine but is in use by the client machine while the user is connected to the webserver. Server deployments are typically priced based on the number of core processors that are available to the End User Software. Therefore, a server may run multiple instances of the End User Software and/or multiple VMs on a physical server machine with a specified number of core processors and only be required to purchase one (1) server license.
A cloud deployment of End User Software means that the End User Software is deployed on machines owned or controlled by a third-party cloud provider (e. g. Microsoft Azure, AWS, GoogleCloud). Cloud deployments can be licensed in a number of ways with pricing models available based on several factors including: (i) minimum number of dedicated physical server machines hosting the End User Application, (ii) maximum number of processors available, (iii) whether additional processors are available on demand (burstable) (iv) whether the architecture is single tenant or multi-tenant, (v) number of “transactions” processed and (vi) number of your customers/end users that are subscribed to the service.
“Multi-User Deployment” is a computer installation designed to service the public or multiple un-named users, and not a single named user or set of concurrent named users, such as a kiosk or a scan station.
A "modular deployment" means our customer has different LEADTOOLS features enabled in an "application", with some modules being installed and enabled on one or more machines and other modules being installed and enabled on other machines. For example, a Document Management system may be comprised of some scan stations for OCR and Barcode recognition operations as well as some annotation/markup stations for image markup and editing operations. The deployment licenses for OCR, Barcode and image markup features are priced separately. The applicable deployment licenses only need to be purchased where the technology is enabled. Thus, OCR- and Barcode-enabled licenses will need to be purchased for the scan stations, while the lower priced Document Imaging licenses will need to be purchased for the image markup stations.
If none of these deployment licenses fit your licensing model, LEAD can tailor a licensing program to meet your specific needs and circumstances. We offer fully paid up licenses, site licenses, and percentage of revenue licenses in certain cases. Please contact firstname.lastname@example.org to initiate a dialog regarding your unique license requirements.
For more information, refer to: