Single Application

Dynamic .NET TWAIN SDK is primarily licensed on a per application per named programmer basis, and Dynamic Web TWAIN is primarily licensed on a per application per server basis. Dynamsoft Barcode Reader SDK also limits its license use to one application only. This brings the question, what is counted as a single application?

A summary of Dynamsoft's licensing:

Your Application Type Dynamic .NET TWAIN Dynamic Web TWAIN Dynamsoft Barcode Reader
Web Application
development license See note (3) See note (1) Development License
testing, staging and production server license See note (3) Server License Server Runtime License
Desktop Application  
development license Developer License See note (2) Development License
deployment license Royalty free to desktops See note (2) Desktop Runtime License


  • 1. If developers work on local machines for development, they can either use an Evaluation License key or a Server License key (after purchase).
  • 2. Although Dynamic Web TWAIN is optimized for use in web applications, its ActiveX Edition can be used to develop a desktop application.
  • 3. Although Dynamic .NET TWAIN is optimized for use in desktop applications, its solution can be accessed by multiple users as a service, or as a background service running as an automated process. This way, it's licensed per server per application basis.

In the following, we are listing several common scenarios. If none of these fits your situation, please feel free to contact for inquiry.

  • 1. Same Software Engine, Multiple Products

    If you develop a software engine that is contained in two products sold separately, you need a License for each product, even if the engine is basically the same in each of the separate products.

  • 2. Same Software, Multiple Domains

    (for Dynamic Web TWAIN; Dynamsoft Barcode Reader)

    If you deploy the same web application to multiple domains which reside on one server, it is still considered one application. However, if each domain is hosted on a separate server, being physical or virtual, you need multiple Server Licenses, based on the per application per server rule.

  • 3. Consultants and Works Made for Hire

    For example, if you develop an application for one customer, and then subsequently develops an application for another customer, a second development license would be required.

  • 4. Modular Application

    A customer is developing a system for internal use or commercial use. The system is composed of multiple software modules. Each module is developed with Dynamsoft SDKs, but all modules are part of the same system. Dynamsoft considers the system and all of its component modules to be one "application" for licensing purposes.

  • 5. Application Suite for External Sale

    A customer develops a "suite" of applications that are always sold as a suite. Dynamsoft considers the suite to be a single application for licensing purposes.

  • 6. Evaluation and "Light" Application Versions

    A customer develops an evaluation version or a light version of its application. Dynamsoft does not require a separate development license for the evaluation/lite version.

  • 7. New Versions and Updates of Existing Applications

    A customer develops a new version of or update to an existing application. Dynamsoft does not consider the update or new version to require an additional development license.

  • 8. Site License

    A Site License allows an unlimited number of programmers (working for the same branch in an organization) to use the Dynamsoft SDKs for the development of one single end user application.

  • 9. Unlimited Development License

    An Unlimited Development License allows an unlimited number of programmers (working for the same organization) to use the Dynamsoft SDKs for the development of an unlimited number of end user applications. Please contact if you are interested in obtaining an Unlimited Development License.