License Key¶

The 3LC Enterprise On-Prem deployment uses license keys to authenticate 3LC usage. Enterprise license keys are provided directly from 3LC. License checks are done on initial import tlc when integrating the 3LC Python Package with your ML code, as well as on startup of the Object Service.

License Types¶

All license keys are configured and recognized in the same way, but 3LC supports two different licensing schemes.

A Hosted-Floating License allows multiple users to share a pool of licenses located on a central license server. The license server will manage the allocation and deallocation of licenses to connected users.

Note

If the Object Service is not shut down normally, it will hold the floating license for an hour. In case of abrupt termination, you can release the license by starting and stopping the Object Service again on the same machine.

A Node-Locked License is restricted to a specific machine. The Object Service will verify the license with a central license server on startup.

Local License Server¶

For deployments where machines cannot reach the central license server at all — isolated networks and air-gapped facilities — 3LC supports a license server running inside your own network. 3LC processes lease a floating license from it over your LAN, and no licensing traffic leaves your network.

Instead of a license key, point 3LC at the server with the TLC_LICENSE_SERVER environment variable:

export TLC_LICENSE_SERVER=http://license-server.internal:8090

The server URL is a regular configuration option (license-server), so it can also be set in the 3LC configuration file or with the --license-server command-line argument.

A lease is released automatically when it expires. 3lc license status shows the current license status, and 3lc license deactivate releases the lease immediately.

The license server itself is activated once at commissioning — for air-gapped installations this is done with an offline request/response file exchange, so the machine never needs a network connection. The server software, deployment instructions, and your license are provided directly by 3LC.

Note

The local license server requires 3lc version 3.3 or later and an agreement that includes on-premise floating licenses. Contact support@3lc.ai for details.

Providing Your License Key¶

A license key may be provided by setting the TLC_LICENSE environment variable to the value of the license key or to the path of a file containing the license key.

# To set the environment variable to a file
export TLC_LICENSE=/path/to/license/file

# To set the environment variable to a string
export TLC_LICENSE=<license key>

# To set the environment variable to a file
set TLC_LICENSE=C:/path/to/license/file

# To set the environment variable to a string
set TLC_LICENSE=<license key>