# How Tilia Labs Licensing Works
All variations of Phoenix licenses are software based. In order to activate a license an internet connection is required. During activation Tilia Labs licensing server will be contacted over https. This connection is secure and safe.
Once a standalone license is activated on a computer it will be locked to that computer and cannot be activated simultaneously on another workstation. This also applies to virtual machines, which means a single license cannot be activated on a machine and then also activated on a VM running on that machine.
# Trial License
Tilia Labs can generate trial licenses with either a trial period or a fixed expiry date. In the case of a trial period, once the license has been activated the trial period will begin. This means that a customer does not need to activate their trial immediately. So as an example if a customer receives a 15 days trial license and they activate it 1 week after receiving it, it will be valid for 15 days from the time it was activated. Fixed expiry trial licenses do not have this flexibility, and will expiry on the specified expiry date regardless of the activation time. For all trial licenses, an internet connection is required during Phoenix start-up to verify it's authenticity.
# Partner License (NFR)
Partner licenses are essentially the same as trial licenses, with the exception that they do not require an internet connection at start-up to verify authenticity. This is particularly useful for resellers who perform on-site demos with a laptop and tradeshows.
# Perpetual License
Perpetual licenses are the licenses generated for purchased copies of Phoenix. During purchase an initial expiry is usually set while payment is collected. Once payment has been received this expiry is removed and the license can then be used indefinitely.
# Use with tilia Cloud
Tilia Cloud licenses allow you to manage, distribute, and set up licenses online. You can create an unlimited number of users for your organization and define exactly who can and can't have access to your licenses. Refer to How to setup Tilia Cloud for more details.
When licenses of products such as tilia Phoenix, tilia Griffin, etc., are used with tilia Cloud, an active MSA is required at all times.
Additionally an active tilia Cloud account is required at all times.
For Trial and Partner Licenses, upgrades are always valid. For perpetual licenses during start-up Phoenix will verify that the license is valid for the current version of Phoenix. If the license is not valid for the current version of Phoenix, Phoenix will attempt to update the license by contacting Tilia Labs servers. This process is automatic and requires no manual intervention by the user. If the license is covered under an MSA or the server has an updated copy of the license with support for a newer version of Phoenix, the upgrade will be successful. If the license cannot be updated for the current version of Phoenix, the user will be required to downgrade back to their previous version in order to continue using Phoenix.
In order to deactivate a license an Internet connection is required. Once a license has been deactivated on a given computer, Phoenix can no longer run on that workstation. This process unlocks the license from the computer it was activated on, and the user is then free to activate the license on a different workstation. Please note this feature is not intended as a method to allow users to periodically use Phoenix on different machines. There is a limit to the number of times Phoenix can be deactivated. If this limit is surpassed, the customer or reseller will need to contact Tilia Labs in order to allow the license to be deactivated.
# Computer Failure
In the event of computer failure please contact Tilia Labs to resolve the issue. We will manually deactivate the license on the broken workstation, at which point the customer will be able to use the same license on a new computer.
# Remote Desktop
Standalone licenses are not intended for use in perpetual with remote desktop access. This essentially allows customers to use a single standalone license as multiple licenses. We are not able to enforce this for all remote desktop systems on the market, but it is against our policy and will violate the EULA if customers utilize Phoenix in this way.