Current Version Licensing

We utilize the Zentitle2 licensing platform from Nalpeiron. General platform and security information can be found directly from their documentation here.

Tiers

A detailed breakdown of the tiers can be found here: https://www.datacor.com/solutions/flow-simulation/tiers

  1. Core: The base application with no additional advanced features.

  2. Pro: Adds the Goal Seeking, Extended Transients, Slurries, and Pulsation advanced features to the applicable apps.

  3. Enterprise: Adds the capability to use the Local License Server (LLS) for air-gapped secure sites and metered API functionality.

Duration Terms

  • 2 Week Trial: Approved by our Sales Team when you need to test the software before purchase.

  • 1 Year: Simple subscription that lasts one year.

  • 3 Year: For locking in specified rates year to year.

Entitlements

When you purchase licenses from us we will combine a Tier + Term + Number of Seats to create an Entitlement. An Entitlement is the actual license set up in the Zentitle2 platform. You may have multiple entitlements based on which products and tiers you have. If you change the seat count this will be modified directly on the entitlement. We will appoint one or more employees of your company as the License Admin(s) for your account. They are in charge of managing the users who have access to your company's entitlements. License Admins can add or remove users by email address and grant them access to specific entitlements. For example, they can grant you access to Fathom but block access to Arrow. The Datacor Flow Simulation Support team will not assign you to different entitlements because this is the role of your company's License Admin(s), and we will not bypass their intended setup unless directly authorized in writing.

End-users log in to the applications using their email + password, so long as they have been granted permission to access the given entitlement.

Technical Details of Activation

The entitlements act as a pool of seats. A seat is checked out upon successful login and opening of the software application. The seat is then returned to the pool when closing the application.

Online Activation:

The standard online activation will use the internet to reach out to the licensing server hosted by our provider Nalpeiron. This will verify if a seat is available and check it out. For IT Admins who need to white-list the connection in a firewall the specific hostname is https://datacor.license.nalpeiron.io.

Temporary Offline Activation:

Temporarily locks a seat to the computer for 1 week where the application can be used offline without internet. Suitable for short-term business travel where internet will not be available. Not intended for fully air-gapped system setup (in which case use the Local License Server option instead). This option requires prior approval from your company's License Admin(s) who must provide you with a special activation code. See our guide on Temporary Offline Activation.

Local License Server (LLS):

This method is for air-gapped networks that are completely isolated from the internet. The LLS is a Docker application that can be hosted on a server machine in your network. In this case, the end-user machines are configured to pull and release seats from the LLS instance on their internal network. The LLS must be activated originally through a process that transfers certificates in and out of the environment. It's then loaded with the entitlements which are valid for a certain subscription duration. See our guide on LLS Setup.

Stuck/Orphaned Seat Activations:

If the software crashes or is forcefully closed via Task Manager the seat will not release in the normal way. Usually, re-opening the app from the same user account on the same machine and closing it normally (gracefully) will release the seat back to the pool as expected, otherwise there is a 2 hour checkout interval as a safety measure to automatically release the seat server-side. During the intermediate time the seat is still considered to be consumed. After the checkout period elapses the seat is considered orphaned. An orphaned seat will still show the last-known checkout information, but if all other seats from the pool are occupied then the next user will reset the orphaned seat (which will check it out with updated information).