Products - LICENSE Features

Protection Methods

LICENSE prevents your protected application from being started on several systems. One or several hardware codes are encoded in a license file. Other additional user-defined codes such as a password can also be filed.

Hardware linking

MAC address

  • The MAC address (Media Access Control) is the hardware address of the network card. This method is recommended and is the safest.

Volume ID

  • Enables the application to be protected using a specific hard-drive volume ID.


  • The name of a computer within a network is unambiguous and can be used for copy-protection purposes.

Selfmade ID

  • Using a self-made ID your own module can transmit any hardware ID to LICENSE - such as an EPROM ID for example. LICENSE then uses this ID as the basis for checking licenses.

Combi Mode

  • This mode makes it possible to combine the previous methods. A set of commands is then used to define which and how many IDs can be missing before LICENSE prevents your application from being executed. As well as offering maximum protection, this system is also extremely customer friendly because it enables users to exchange different hardware components without having to apply for a new license.
  • While it is possible for the user to copy the application from PC 1 to PC 2, it can only be used on the PC containing the licensed hardware. Users must upload an installation code, which is integrated into the license file or the activation ticket.
  • All copy-protection schemata work on a server (floating license) or a local workstation (computer tied). When the license file is located on a server, the hardware (volume ID, Mac address or host name, etc.) of the server is used. When the license file is located on a local workstation, the hardware of the local workstation is used.

Application linking

User-defined ID

  • The advantage of using a user-defined ID for checking purposes is that while the user is able to copy the application on to another hard drive, it will only run with the special license file, unless, that is, the license has been linked to the hardware. If the license has been linked to the hardware, the application can only be run on the licensed computer after the user-defined ID (i.e. password) has been entered.

Available Licensing Types

LICENSE offers a large number of licensing options. You can use an unlimited number of licensing options and combine them in any way you want. In addition to simply checking whether an option is available, there are also plenty of other options.

LICENSE supports two general licensing method types

Computer tied (per seat)

  • Licensing takes place on the computer on which the application will be used. One or several of the computer's hardware codes are used for checking purposes. This type of licensing is known as "per seat licensing". The license is allocated to the computer when the application is installed.

Floating license

  • The licence is engaged while the application is running. Once the application is ended, the licence is released again. The licenses are tied to the computer which is running the license server. This type of licensing is also known as "concurrent user". Using the floating license method it is possible to set the maximum number of users allowed to access the application at any one time. It is also possible to make a distinction between whether the number of applications actually started is used as the criteria or the number of different users using the application. The users of an application can be identified, for example, using their log-in names.

Software-protection licensing types


  • Licensing is product-related. An individual licensing method can be used for each product. Both the product code and the product version are taken into account.


  • Options make it possible to enable software modules selectively within an application. This makes it possible to deliver applications complete with all functions and then to enable only the components that have been licensed. A check is carried out to determine whether a particular option is enabled or not.

User-defined ID

  • It is possible to use a user-defined ID, which is used for checking licensed applications when they are started. It is also possible to forgo hardware linking in this case.

Optional additional limitations

Time limitation

  • It is possible to set a maximum number of days during which the product and the options can be used before a license is required.

Purge date

  • It is possible to specify a date before which the product and options can be used before a license is required.


  • Code for a demo version of the product or options that need to be licensed.


  • The counter makes it possible to restrict the use of the product or one of its options by a maximum set number. Each time the product is used, a counter is incremented automatically and the number compared to the maximum set number.
[ english ] [ deutsch ]