This page aims to answer commonly asked questions about the licensing system for our products – including technical aspects as well as legal ones (i.e. what is enforced vs. the spirit of the license agreement).
All our products are licensed per named developer, with the obvious exception of site licenses, covered below.
This means that a single named user may install and use the product on as many computers (real or virtual) as they need, provided they are the only person using the product. If more than one person uses the product, a separate license is required for each user. This applies even if the software is not used by both users at the same time, and/or is used the same machine).
The simple rule is that if X people work at your company and use the product, you need X licenses.
Licenses owned by a company can be transferred to a different user, if the current user leaves the company or permanently transitions to no longer working with the product (e.g. switches departments or roles).
This is of course not to bypass the previous rule; i.e. a license cannot be transferred back and forth between two developers on a daily or regular basis – two separate licenses would be needed in that scenario.
A separate license is not needed to install and use the product on build machines, providing each user directly working with the product is covered by a license, and the build machine is not used to enable unlicensed users to use the product.
For example, it would not be permissible to have a developer use a trial license of a product, but commit code that then gets built with or against against the licensed product on a build machine, circumventing the need of said user to have a proper license.
Our products use no activation system or otherwise enforce licensing limits on a technical level. We trust our users, and we want our licensing system to not get in the way of users installing or re-installing the software in as many places as they need to.