> For the complete documentation index, see [llms.txt](https://docs.licensespring.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.licensespring.com/floating-server/floating-server-v1/license-options/which-to-use.md).

# Which to Use?

Selecting the correct license type is crucial for maximizing the functionality and security of your software. This section provides guidance on choosing the appropriate license type based on your operational environment and needs.

## [Online](/floating-server/floating-server-v1/license-options/online.md) Licenses

* Ideal For: Environments with reliable internet connectivity.
* Advantages: Allows real-time validation and management of licenses, suitable for dynamic or cloud-based settings.
* Use Case: Best for organizations that can handle online checks and need flexibility in managing and reallocating licenses on-the-fly.

## [Offline](/floating-server/floating-server-v1/license-options/offline.md) Licenses

* Ideal For: Settings with limited or unreliable internet access.
* Advantages: Works without the need for continuous internet connectivity, ensuring functionality in remote or mobile scenarios.
* Use Case: Suitable for applications used in remote locations where internet access is intermittent or unavailable.

## [Air-Gapped](/floating-server/floating-server-v1/license-options/air-gapped.md) Licenses

* Ideal For: High-security environments that must operate completely isolated from the internet.
* Advantages: Provides the highest level of security by operating without any external network connections.
* Use Case: Optimal for highly sensitive or secure installations such as governmental or military applications where no external communication is permitted.

## [Hardware Key](/floating-server/floating-server-v1/license-options/hardware-key.md) Licenses

* Ideal For: Environments where physical security and anti-piracy measures are paramount.
* Advantages: Offers a physical element to the licensing process, which can be more secure against certain types of tampering.
* Use Case: Effective for small-scale deployments where software needs to be tightly controlled and bound to specific hardware.

## Deciding Factors to Consider

* Security Requirements: Choose **Air-Gapped** or **Hardware Key** licenses for maximum security. **Online** licenses offer secure real-time validation.
* Connectivity: Opt for **Online** licenses if connectivity is consistent; choose **Offline** or **Air-Gapped** licenses for environments with limited or no internet access.
* Flexibility and Management: **Online** licenses provide the most flexibility in management and reallocation, whereas **Hardware Key** licenses add a layer of physical security.
* Regulatory Compliance: Ensure your licensing strategy complies with any industry regulations, which might favor one type over another based on data security standards.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.licensespring.com/floating-server/floating-server-v1/license-options/which-to-use.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.