Page History
...
| License Type | Internet at Runtime | Multi-Instance | How to Purchase | Best For |
|---|---|---|---|---|
| Online - Node-locked | Yes | No (one server per license) | Chariot UI or Contact Cirrus Link Support | Standard server installs with internet access |
| Offline - Node-locked | No | No (one server per license) | Contact Cirrus Link Support | Air-gapped or high-security environments |
| Online - Floating | Yes | Yes (concurrent seats) | Contact Cirrus Link Support | Containerized or auto-scaling deployments |
| Offline - Floating (CustomerSelf-hosted FLS) | LAN access to the FLS only | Yes (concurrent seats) | Contact Cirrus Link Support | Multi-instance deployments inside a closed network |
| Marketplace | N/A | N/A | Through Cloud Marketplace: | Cloud deployments |
...
- Chariot host has no outbound internet access
- Security policies prohibit the Chariot host from contacting external services
- Running a single Chariot server
...
Floating (
...
Self-Hosted)
For air-gapped and closed-network environments running multiple Chariot instances that share a pool of concurrent license seats. License validation stays entirely inside the deployed network.
Install the License4J Floating License Server (FLS) on a host inside a network, send Cirrus Link the FLS hostname and fingerprint, and receive a license keyed to the Floating License Server. Each Chariot instance is configured with the FLS URL and leases a seat from the FLS at startup.
Use CustomerSelf-Hosted Floating when:
- Running multiple Chariot instances inside a single closed network
- Using short-lived deployments based on concurrent seat count rather than per-server licenses
- License validation must remain inside a secure network perimeter (no outbound internet from Chariot or the FLS)
...
Overview
Content Tools