TABLE OF CONTENTS
Separate Cryptlex Products
There are separate Cryptlex "products" for the Preview and Beta:

That way we prevent any licensing interactions between Preview and Beta. Specifically, the fact that a Preview trial exists/existed on a computer won't interfere with our ability to activate Beta as a trial.
Trial-Based Licensing
The Preview and Beta licensing will be based on Cryptlex activatable ("verified") trials. We have:
- "Preview Trial Policy" that's attached to the "Sensitivity Explorer Beta" product
- "Beta Trial Policy" that's attached to the "Sensitivity Explorer Preview" product

The trial policies are User-Locked; that's the setting we'll always use for Cryptlex licensing. We allow VMs for testing; this is not a licensing loophole: we mean to eventually delete these products from Cryptlex, so nobody will be able to use the software after that date.
We'd like to specify a fixed expiration date for all these trials, like April 30th; however, Cryptlex trials do not support this. We'll have a workaround for this. Let's say we release the preview on April 1st; we'll start out with a trial policy that allows 30 days. 30 days is fine for users who start their trials on April 1st. However, we don't want to give 30 days to users who start their trials on April 2nd. Well, on June 2nd we just need to change the "Preview Trial Policy" to allow 29 days. We could do this daily, but probably weekly will be good enough. The worst case scenario here is that a user gets to run the Preview for a week after our intended Preview expiration date.
Changing Trial Expiration Date
We can change the trial expiration date on the server:
- individually for a specific user
- all trials via API
This will be reflected on the end-user machine automatically, if they have an Internet connection. That's because with Preview and Beta licensing every time SV boots a call to "activate trial" is made to Cryptlex:
- this call will start the trial period the first time the software is launched
- it will also pull a new expiration date from the server, if it has been updated
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article