Overview
Cryptlex lets you distribute your software applications securely to licensed users, protecting your software from unlicensed distribution. You host your release files on our servers (bandwidth is free, even if you distribute a million copies), and Cryptlex gates every download of these hosted files behind a valid license key or access token. You can also add external files hosted on your own server, whose URLs Cryptlex passes through as-is without gating.
How releases work
A release represents one version of your product. Each release has:
- Version, dot-separated digits in one of three forms:
$MAJOR.$MINOR,$MAJOR.$MINOR.$PATCH, or$MAJOR.$MINOR.$PATCH.$BUILD(for example,1.2,1.2.3, or1.2.3.4), used for ordering releases and detecting updates. - Platforms, such as
windows,macos, orlinux, so each operating system gets the right files. You create the platforms you need; none exist by default. - Channel, such as
stableorbeta, so you can ship pre-release versions to a subset of users. Onlystableexists by default; create any others you need. - Files, either uploaded to Cryptlex hosting or added as external files hosted on your own server.
Release lifecycle
- Create the release and upload its files. See Creating Releases.
- Publish it to freeze it; published releases are read-only and become visible to your users.
- Archive it when you want to retire it; archived releases disappear from the customer portal and update checks, though previously shared direct download URLs keep working.
Secure delivery
Download URLs for hosted release files require the customer's license key or an access token, so only licensed users can download your software. Customers can download releases from the customer portal, or your website can fetch them through the Web API. See Distributing Releases.
Automatic updates
Your app can check whether a newer release is available, using either the Web API or the LexActivator CheckReleaseUpdate() function, and then download and install it. See Auto-Updates.