> 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.md).

# License Options

The Floating Server supports a variety of license types, each tailored to different deployment environments and usage scenarios. Understanding these options will help you choose the most appropriate licensing method for your needs, ensuring optimal compliance and functionality.

Explore the following license types:

* **Online**:\
  Requires an active internet connection to validate the licenses frequently. This option is suitable for environments where real-time license validation is feasible and necessary. Additional information can be found on the [**Online**](/floating-server/floating-server-v1/license-options/online.md) page.
* **Offline**:\
  Designed for environments with no or limited internet connectivity. Offline licenses can be activated once and used without needing to connect to the internet, providing flexibility for remote or secure settings. More details are available on the [**Offline**](/floating-server/floating-server-v1/license-options/offline.md) page.
* **Air-Gapped**:\
  Specifically for environments that are completely isolated from the internet. These licenses are similar to offline licenses but tailored for setups where security and isolation are paramount. Visit [**Air Gapped**](/floating-server/floating-server-v1/license-options/air-gapped.md) for details.
* **Hardware Key**:\
  Utilizes physical devices (dongles) to manage license activation and validation. Hardware keys are highly secure and ideal for environments where software must be tightly controlled. Learn more on the [**Hardware Key**](/floating-server/floating-server-v1/license-options/hardware-key.md) page.
* **Which to Use?**:\
  Not sure which license type is right for you? This section provides guidance based on your specific requirements and constraints, helping you make an informed decision. Check out [**Which to Use?**](/floating-server/floating-server-v1/license-options/which-to-use.md) for help deciding.

Choosing the correct license type is crucial for ensuring your software’s integrity and compliance with licensing terms. Each type offers different benefits and is suited to particular scenarios, from tight security requirements to ease of use in various operational contexts.


---

# 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.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.