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 | ||||||
| Online - Leased | Yes | Yes (concurrent seats) | Contact Cirrus Link Support | Containerized or auto-scaling deployments | ||||||
| Offline - Node-locked | No | No (one server per license) | Contact Cirrus Link Support | Air-gapped or high-security environments | ||||||
| Online Self- Floating | Yes | Yes (concurrent seats) | Contact Cirrus Link Support | Containerized or auto-scaling deployments | Hosted Floating License Server | Offline - Floating (Self-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 |
...
| Warning |
|---|
| If the Chariot server is terminated without first being Deactivated on the License page, that activation is permanently lost. |
...
Online - Leased
For containerized or auto-scaling Chariot deployments where instances are ephemeral. Containers automatically lease a license seat from Cirrus Link's license server at startup and release it at shutdown with no manual deactivation between deployments.
Leased Cloud license activation looks identical to Online: Paste a license key into the Online activation tab in Chariot. The difference is in how the license is configured behind the scenes where seats are pooled across all running containers rather than node-locked to a specific instance.
Use Cloud Leased Licenses when:
- Deploying Chariot in Kubernetes, ECS, or another container orchestrator
- Using auto-scaling groups where Chariot instance lifecycles follow load
- Using ephemeral containers where there is a risk of losing Online activations when a container is replaced
| Note |
|---|
| Purchase seat count to cover the peak number of concurrently running Chariot containers, including any temporary overlap during rolling deployments. If running containers exceed seat count, additional containers will fail to activate. |
...
Offline - Node-locked
For environments where the Chariot host has no internet access — for example, air-gapped industrial networks or high-security deployments where outbound internet is prohibited.
...
- Chariot host has no outbound internet access
- Security policies prohibit the Chariot host from contacting external services
- Running a single Chariot server
...
...
Self-Hosted
...
Floating License Server
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.
...
- 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)
Floating (Cloud)
For containerized or auto-scaling Chariot deployments where instances are ephemeral. Containers automatically lease a license seat from Cirrus Link's license server at startup and release it at shutdown with no manual deactivation between deployments.
Floating Cloud license activation looks identical to Online: Paste a license key into the Online activation tab in Chariot. The difference is in how the license is configured behind the scenes where seats are pooled across all running containers rather than node-locked to a specific instance.
Use Cloud Floating when:
- Deploying Chariot in Kubernetes, ECS, or another container orchestrator
- Using auto-scaling groups where Chariot instance lifecycles follow load
- Using ephemeral containers where there is a risk of losing Online activations every time a container is replaced
| Note |
|---|
| Purchase seat count to cover the peak number of concurrently running Chariot containers, including any temporary overlap during rolling deployments. If running containers exceed seat count, additional containers will fail to activate. |
...
Marketplace (AWS / Azure)
...
- Need one-click deployment from a cloud marketplace
- Prefer consolidated cloud billing through AWS or Azure
- Do not want to manage license keys directly
A Note on Terminology
Chariot supports two different floating license options, and it's worth distinguishing them clearly:
- Self-Hosted Floating — a License4J Floating License Server installed and run on a physical host inside a network. Best for closed-network multi-instance deployments. In the Chariot UI, this uses the Floating activation tab.
- Cloud Floating — a license configured against Cirrus Link's cloud license server, designed for containerized deployments. In the Chariot UI, this uses the Online activation tab.
...
Related Pages
- Purchasing and Activation — step-by-step activation, deactivation, and reactivation flows
...
Overview
Content Tools