You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Customer-Hosted Floating Licenses

For closed-network environments running multiple Chariot instances that share a pool of concurrent license seats. License validation stays entirely inside your network.

What is a Floating License Server?

A Floating License Server (FLS) is a small server application that holds your Chariot license and tracks how many Chariot instances are using it at any given time. Instead of binding a license to one specific Chariot server, the FLS lets multiple Chariot instances share a pool of concurrent license seats.

When a Chariot instance starts, it asks the FLS for a seat. When the Chariot instance shuts down, it releases the seat back to the pool. As long as you have available seats, additional Chariot instances can activate against the same FLS.

The FLS runs entirely inside your network.  Your Chariot instances communicate with it over your LAN, and neither the Chariot instances nor the FLS itself need outbound internet access for license validation.

The FLS is provided by License4J as free software. For installation, configuration, and administration, see License4J's Floating License Server page.

Once your FLS is running, see Purchasing a new license to purchase and activate a Customer-Hosted Floating license against it.

Activating Floating Licenses

Prerequisites

Before requesting a Customer-Hosted Floating license, you should already have:

  • A running License4J Floating License Server inside your network. See Hosting a Floating License Server above for setup.
  • Network connectivity from each Chariot host to the FLS on the FLS's listening port (default 16090).
  • Have purchased licenses with Chariot Support that are ready to deploy to your FLS. 


Make sure to purchase the number of licenses that your system requires under its highest load

Request a License Usage

You'll send Cirrus Link two pieces of information from your FLS so we can issue a license keyed to your specific server.

Log in to your FLS admin UI (default is port 16090http://<fls-host>:16090)


Open the Actions dropdown.



Select View Server Info.



Note the Hostname and Fingerprint values.


Send Cirrus Link the FLS hostname, fingerprint, and your seat count.

Cirrus Link will generate your license and email you a usage hash. This can take up to 24 hours.

Install the License on Your FLS

Log in to your FLS admin UI (default is port 16090http://<fls-host>:16090)

Navigate to License Management → New License.


Paste in the usage hash provided by Cirrus Link and save.


The license appears in the FLS license grid, and the FLS is ready to serve seats to Chariot instances.


Activate Chariot Against the FLS

In the Chariot UI, navigate to the License page.

Select I have a license key and want to activate.


Select Floating and click Next.

Fill in the activation details:

    • Floating license server URL — your FLS host plus port and the /fls path. Example: http://10.0.0.10:16090/fls
    • License Features — the feature set this Chariot instance will use. This must match the features on the license issued to your FLS:
      • MQTT Server
      • IoT Bridge for Snowflake
      • Full product

Click Next, then Finished on the Complete step.

Chariot will contact your FLS, lease a seat, and display a success screen.

Important: The /fls path on the URL is required. The single most common activation failure for Customer-Hosted Floating is forgetting it.

Important: The License Features you select in Chariot must match the features on the license installed on your FLS. Mismatched features will cause activation to fail.


Repeat for each Chariot instance you want to license against the FLS.

Add More Chariot Instances

Each running Chariot instance leases one seat from the FLS. As long as you have available seats on the installed license, additional Chariot servers configured with the same FLS URL and matching License Features will activate automatically.

Upgrade a Customer-Hosted Floating License

When upgrading a Customer-Hosted Floating license — for example, changing feature flags or adding seats — you must uninstall the previous license from your FLS before installing the new one. If both are installed at once, your FLS will count seats twice.

  1. Contact Cirrus Link Support to request the upgrade. Provide your existing license key and the changes you need.
  2. Cirrus Link will issue a new usage hash for your existing FLS hostname and fingerprint.
  3. Once you receive the new usage hash:
    1. Log in to your FLS admin UI.
    2. Uninstall the previous license from the license grid.
    3. Install the new license using the usage hash from Cirrus Link.
  4. On each Chariot instance, click Reactivate on the License page to pick up the updated features without restarting Chariot.


  • No labels