Page History
Chariot V3 Licensing
Chariot supports several licensing options to match how and where you deploy.
For step-by-step activation instructions, see the Licensing Procedure page.
Quick Comparison
| License Type | Internet at Runtime | Multi-Instance | How to Purchase | Best For |
|---|---|---|---|---|
| Online | Yes | No (one server per license) | Chariot Self-Service Portal or Cirrus Link Support | Standard server installs with internet access |
| Offline | No | No (one server per license) | Contact Cirrus Link Support | Air-gapped or high-security environments |
| Floating (Customer-Hosted) | LAN access to your FLS only | Yes (concurrent seats) | Contact Cirrus Link Support | Multi-instance deployments inside a closed network |
| Floating (Cloud) | Yes | Yes (concurrent seats) | Contact Cirrus Link Support | Containerized or auto-scaling deployments |
| Marketplace (AWS / Azure) | N/A | N/A | Through cloud Marketplace | One-click cloud deployments |
...
Online
The standard Chariot license. Most customers use this option.
...
Important: If you terminate, delete, or destroy the Chariot server without first clicking Deactivate on the License page, that activation is permanently lost. Each license has a finite number of activations, so always deactivate before decommissioning a server.
...
Offline
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.
...
- Your Chariot host has no outbound internet access
- Your security policy prohibits the Chariot host from contacting external services
- You're running a single Chariot server
...
Floating (Customer-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 your network.
...
- You're running multiple Chariot instances inside a single closed network
- You want to enforce a concurrent seat count rather than buy per-server licenses
- License validation must remain inside your 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.
...
- Purchase your seat count to cover your peak number of concurrently running Chariot containers, including any temporary overlap during rolling deployments. If running containers exceed your seat count, additional containers will fail to activate.
...
Marketplace (AWS / Azure)
If you deploy Chariot through the AWS Marketplace or Azure Marketplace, your license is pre-installed and pre-activated as part of the Marketplace deployment. There are no activation steps to perform, and billing flows through your cloud provider.
...
- You want one-click deployment from a cloud marketplace
- You prefer consolidated cloud billing through AWS or Azure
- You don't want to manage license keys directly
...
A Note on Terminology
Chariot supports two different floating license options, and it's worth distinguishing them clearly:
- Customer-Hosted Floating — a License4J Floating License Server that you install and run on a physical host inside your 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
- Licensing Procedure — step-by-step activation, deactivation, and reactivation flows
...
Overview
Content Tools