License Management

License activation requires the computer to be connected to the internet. One license can be activated on one (and only one) machine at the time. After a license is activated, the machine no longer needs to be connected to the internet for a certain amount of time (depends on license level, typically 4 weeks). A warning is displayed both on licenses that are soon expiring and on licenses that soon need to be activated online again.

The activation of a license will transfer data uniquely identifying the PC that the software is installed on to Voysys.

Licenses are handled in the Help menu. See Activate licenses for the step-by-step activation flow.

To transfer a license to another computer first use Help  Revoke current license. Then use Help  Enter new license key on another computer.

Session-based license activation

Use --session-license <key> to activate a license for a single application session:

oden_ui --session-license 11111111-1111-4111-8111-111111111111
oden_streamer --session-license 22222222-2222-4222-8222-222222222222

Replace the example keys with your license keys. Each process gets a unique license identity, so several processes on the same PC can use different licenses as if they were running on different machines. Each concurrent session needs its own available license key. --session-license also enables --multiple-streamers, allowing multiple Streamers to run simultaneously.

The application activates the supplied key during startup and attempts to deactivate it during normal shutdown. The PC’s saved machine license is not changed. If activation fails, the application exits with a nonzero status. To change the session key, close the application and start it again with the new key. The option cannot be combined with --activate, --revoke, or --force.

An internet connection to the license server is required at startup and shutdown. Use an ordinary license that allows deactivation. Bulk licenses are not supported. Licenses locked for their full duration cannot be deactivated, and the existing server protocol does not let the application identify them before activation. Do not use those licenses with --session-license. An existing machine activation must be released before its key can be used for a session.

Before contacting the server, the application saves a session-license-<UUID>.conf recovery file alongside its other license files. The UUID identifies this session to the server. The file contains the license key hash and server address, and is locked while the session is running. Successful deactivation removes the recovery file.

After a crash, forced exit, power loss, or failed network request, the recovery file remains. On the next startup of the same application, files that are no longer locked are used to retry cleanup. Recovery can reactivate the same session identity to obtain a new deactivation credential if the previous response was lost. Files for running sessions are left alone, and failed cleanup is retried on a later startup. Recovery requires the files to remain on disk and the license server to be reachable; no cleanup runs while the application is stopped. If an activation cannot be released automatically, release it in the license portal before reusing the key.