Component licenses

All license plans contains free updates and bug fixes for a year and support a one year (free updates and bug fixing) and consulting based on contract.

The consulting cannot be used for development tasks, or for average tasks, only consulting for the given component itself.


Machine based license

The component needs a license for every machine it is installed on. It doesn't depend on number of users, only number of PCs. If a given hardware of the PC is changing, it needs a new license file. This is free of charge of course.

If you want to use the component on 10 machines then you need 10 licenses. These 10 machines can be used by any number of user. The machine based license cannot be used on machines where the users can work in paralel, like remote desktop, terminal server, or such.

Machine based license cannot be used on servers only on workstations. The machine based license does not allow the customer to build it in any kind of server side application like Windows Service, Web Service, webpage, or such.

Machine based license should be able to access WMI.


Company based license

This license plan is based on the network of a company. Any machine connected to the given network can use the component. The number of users nor the number of machines are not limited in any way.

Machine based licensed component can be built in to server side application like Windows Service, Web Service, webpage, or such, given that the goal of the application is not to extend the company's network to other networks.

Company based license should be able to access WMI.


Code based license

Code based license means that the customer can get the whole source code of the component (except licensing and crypting functions). The code can be used by the customer in any way except selling, presenting or renting the component or a component based on this component nor in code nor in compiled form. The client also cannot create similair component based on the techniques used in the source code.

If the client changes the code, then the merge with new versions is his responsibility. The customer also takes full responsibility of the protection of it's own application which uses the component code.