Yes, it's a completely new product. Everything has been rewritten using the latest and some of the best technologies available.
- Completely API driven
- Brand new dashboard
- Customer portal for your customers
- New beautiful documentation
- New client libraries
- New hosting providers (Heroku and AWS)
- Code samples have been moved to Github
- Updated pricing plans
{% hint style="info" %} Cryptlex v3.x is not backward compatible with Cryptlex v2.x. {% endhint %}
No, you need to create a new account for using Cryptlex v3.x. You can signup for free, no credit card required.
We are planning to support it for one year (upto May 10, 2019), after which you won't be allowed to create more products and product versions.
Don't worry updates in existing product keys, activations and deactivations will still work after one year. The tentative date for completely turning off Cryptlex v2.x API is May 10, 2021.
Do our customers need to reactivate when we integrate LexActivator v3.x or upgrade to LexFloatServer v3.x?
Yes, a reactivation will be required. You can do an auto-activation if you store the key in your application settings and after upgrade check whether key exists and do an auto-activation.
No, when you subscribe to any paid plan on Cryptlex v3.x your Cryptlex v2.x account subscription will get discounted by the amount you pay for your subscription. Please notify us when you do so.
A lot has changed and many new features have been added. Most of the feature requests by our customers have made into Cryptlex v3.x, we thank you for your valuable feedback.
Everything is now API driven in Cryptlex. You can even skip using LexActivator (though not recommended) and directly use web API to license your products.
We now support identity management for your customers. Along with creating licenses you can also create users and link them with the licenses. Basic features like login, password reset, profile management are supported out of the box. Your customers can also log into the dashboard to manage their license keys.
A license policy helps you create different types of license profiles. It acts as a blueprint for the licenses you create for your customers and helps you implement different types of licensing models.
Now you can simply use LexActivator for implementing floating licenses where Cryptlex server acts as your floating license server. So you get to see activation log in real time for your floating licenses.
Every action is logged and you can easily view the event log in the dashboard. Logs are retained for 30 days.
{% hint style="info" %} Additionally, activation log of your licenses is also available which can be used to audit license usage. {% endhint %}
You can now easily integrate Cryptlex with third party apps and take actions when some event occurs in your Cryptlex account. You can even use Zapier and integrate Cryptlex with thousands of cloud apps.
Cryptlex v2.x allowed for storing custom fields with your licenses. This has been replaced with metadata which can be stored along with your products, licenses, users, activations and trial activations.
{% hint style="info" %} You can use product metadata to easily detect software updates (if not using Release API) in your app by storing your release version. After trial or license activation product metadata can be accessed in your app. {% endhint %}
Analytics have been improved and we are adding more metrics to further give you detailed insight of your products.
LexActivator has gone through major upgrade and now supports a lot many new features. You can checkout the changelog.
To keep it short we won't be discussing all the features, if you have any queries drop us an email and our team will reach out to you.
You can easily export the license keys in csv format from the Cryptlex v2.x dashboard. The exported csv data needs to be processed a bit before it can be imported into Cryptlex v3.x. It looks as follows:
"Key ID", "Product Key", "Email", "Status", "Expires On", "Total Activations", "Used Activations", "Total Deactivations", "Used Deactivations", "Validity", "Creation Date", "Custom Fields", "Activation Location","Activation Date","Activation Extra Data","Activation OS"
Remove the fields which can't be imported so it will become:
"Product Key", "Email", "Total Activations", "Total Deactivations", "Validity", "Creation Date", "Custom Fields"
Rename the fields as per the new schema:
"key", "email", "allowedActivations", "allowedDeactivations", "validity", "createdAt", "Custom Fields"
Multiply each entry in validity column by 86500 to convert it to seconds.
Each custom field should be added as a separate field, assuming you had stored order_id, first_name, last_name:
"key", "email", "allowedActivations", "allowedDeactivations", "validity", "createdAt", "order_id", "first_name", "last_name"
We have created a sample project on Github to help you with the import. It's a Node.js script which you can modify as per your requirements.
You need to decide whether you want to store the user data as separate user resource or simply store it as part of license metadata. The script uses user data to create a new user and links the user with the license. You can modify the script as per your requirements.
The script invokes Cryptlex v3.x Web API, so you will need an access token to use the script. Go the "Personal Access Tokens" section in dashboard and create an access token with following four permissions:
license:read, license:write, user:read, user:write
In case you need more help, we'll be glad to help you make the transition. You can either post your questions on our support forum or can contact us through email.
{% hint style="info" %} You can also share your exported CSV file with us, in case you want us to handle the transition. {% endhint %}