Change to licensing model
The licensing model for Katalon Studio Enterprise (KSE) and Katalon Runtime Engine (KRE) is changing. KSE node-locked and floating license types as well as KRE node-locked license types are being deprecated. The licensing model for both products is transitioning to the following:
- KSE node-locked and floating license → KSE per-User license
- KRE node-locked and floating license → KRE floating license
- To learn more about per-User and other license types, refer to Types of licenses.
What is node-locked and floating license?
|Node-locked license||Floating license|
|One license is assigned to one machine ID.||One license is assigned to one execution session and can be shared between 3 machines.|
|Licenses are transferable.||Licenses need to be assigned.|
|Applies to local desktops or workstations with fixed hardware specifications.||Applies to all types of execution environments.|
|Online subscription available.||Online subscription available.|
|Offline licenses can be generated from online node-locked licenses.||Offline licenses are available for on-premises licensing server only. For more information, contact sales.|
This license type is applied to local desktops or workstations with fixed hardware specifications (machine-blocked license), such as:
- A virtual machine with a fixed machine ID
- A physical machine
With node-locked licenses, one machine running tests = one license.
- A license is tied to a single machine ID and only for one execution session at a time.
- A machine can be mapped to multiple licenses if needed.
- For machines connected to the internet, the licenses can be transferred to other machines at no cost and as many times as needed.
- For annual licenses only: Licenses can be converted to be used in an offline environment. Once converted, the license cannot be transferred to another machine until it is expired.
- Licenses purchased on a monthly basis cannot be converted for use in an offline environment.
For scaling teams with dynamic usage, floating licenses reduce the management cost and optimize your workflow.
This license type is applied to all types of execution environments, including cloud or virtual machines with dynamic hardware specifications (to execute tests in Docker, Azure, AWS).
- One floating license can be shared across a maximum of 3 machines.
- One floating license is assigned to one execution session at a time.
For instance, you have 1 floating Katalon Studio Enterprise license attached to the email email@example.com.
You can use firstname.lastname@example.org to log in to Katalon Studio on up to 3 different machines, but not at the same time. This is because email@example.com represents only 1 floating Katalon Studio Enterprise license. Therefore, you can only be active on 1 of those 3 machines at a time.
Technical support for annual or multi-year contract
If you currently have an annual or multi-year contract, deprecating license types will continue to function as expected until the end of your current contract. Once that contract ends, only new license types will be available for use.
- For KSE, floating and node-locked licenses cannot co-exist with per-User licenses. You cannot directly purchase per-User licenses until your contract expires or you decide to transition to the new license model. You can contact the Success team at firstname.lastname@example.org, if you want to immediately convert to the per-User licensing model.
Migration mapping of KSE floating/node-locked to KSE per-User licenses
Case 1: Automatic transition to KSE per-User licenses
This case applies to those of you whose license renewal date is due, and happens automatically.
Consider a scenario where you are a group of 5 users. You have the following licenses at your disposal:
- 1 generated Offline floating license.
- 3 floating licenses.
As you can see above, the number of people in your group (5 users) is more than the number of licenses itself (3 floating licenses). Thus, when the license renewal date approaches, 3 KSE per-User licenses are issued to your group, based on the following order of priority:
- 1 user who has an Offline floating license.
- 2 unique users who are last seen active.
Thus, you can say:
N Offline licenses + O unique last active users = P licenses
In general, if you have 1,3,4,5……n KSE floating licenses, an equivalent number of last active users receive corresponding per-User licenses.
Case 2: Manual transition to KSE per-User licenses
This case applies to those who wish to upgrade Katalon licenses or switch to the KSE per-User licenses while the license renewal date is not due.
Consider a scenario where you are a group of 5 users and wish to transition to per-User licenses. To do this:
Go to the Katalon Pricing page, select Katalon Studio, on the KSE per-User plan, click Buy now.
Alternatively, you can sign in to Katalon TestOps, then go to Settings > Subscription Management, select Katalon Studio, and click Subscribe on the KSE per-User plan.
By doing so, you are prompted to confirm whether you wish to merge your existing floating/node-locked licenses to new per-User licenses.
Once you confirm your interest for the transition to per-User licenses, the licenses are assigned to you on order of priority, as it was during automatic renewal.
Migration mapping of KRE floating/node-locked to KRE floating licenses
Depending on the KRE licenses you currently have, the following cases apply.
Case 1: Users with monthly KRE node-locked licenses only
You can still use your existing KRE node-locked licenses until their renewal date, but you cannot purchase more. If the renewal date is after June 7th, KRE node-locked licenses will be converted into KRE floating licenses.
- Make sure you cancel KRE node-locked subscriptions before subscribing to the new KRE floating licenses to avoid additional charges.
Case 2: Users with KRE node-locked and KRE floating licenses
You can still use the current KRE node-locked licenses until their renewal date, but you cannot purchase more.
If you do not cancel the KRE node-locked licenses, they are automatically renewed and converted into KRE floating licenses after June 7th. For example, you have 2 KRE node-locked and 3 KRE floating licenses. If you do not cancel the KRE node-locked subscription, your KRE node-locked licenses will be renewed automatically after June 7th and become KRE floating licenses. You then have a total of 5 KRE floating licenses from June 8th.
You can upgrade KRE floating licenses normally.
Case 3: Users with KRE floating licenses only
You can upgrade KRE floating licenses normally.