Licensing & Activation
eXLib uses the aescripts licensing system. A distributable build does not use a local preference or a hidden development flag as proof of entitlement: the launch gate waits for the licensing service and opens the product only when it reports a valid license or configured trial.
First launch
If no valid entitlement is available, eXLib shows its License gate instead of the editor. Choose Activate / Check license to open the aescripts licensing flow. The gate remains in place when the service is unavailable or the package is missing its authentic eXLib product identity; those states are errors, not an offline bypass.
A development build can carry an explicit development bypass. It is labeled DEVELOPMENT LICENSING BYPASS — this build cannot be distributed, and the release package verifier refuses customer artifacts containing that mode.
Settings → License
The License section shows the current state—Licensed, Trial, Activation required, or Unavailable—and the registration label returned by aescripts. When a trial is active, the configured product trial policy is shown on the same card.
The available actions are:
- Activate / Check license — run the interactive aescripts license check.
- Refresh registration — re-read the current registration details.
- Automatic update checks — change the aescripts product-update preference.
- Check now — ask aescripts to check for an eXLib product update; this is separate from validating the current license.
- Open aescripts support ticket — open the licensing support flow.
- Deactivate license — available for a licensed installation and guarded by a confirmation that explains eXLib will be blocked until another valid license is activated.
Failure behavior
If an activation, refresh, update, support, or deactivation request cannot be completed safely, the section reports the failure and does not manufacture a successful state. Deactivation also requires explicit confirmation; reclaiming or changing an entitlement is never inferred from closing the panel.