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

# Floating Server V1

{% hint style="danger" %}
**Floating Server V1 is deprecated.** It receives security patches only and will not receive new features. All new deployments should use [Floating Server V2](https://docs.licensespring.com/floating-server/floating-server-v2).
{% endhint %}

The Floating Server allows you to leverage LicenseSpring’s licensing features in an on-premise environment. It can operate both online and offline, supporting a variety of licensing models. This makes it ideal for organizations requiring flexible license management, especially in environments with limited internet access or when high control over license distribution is necessary.

## How It Works

The Floating Server facilitates the creation and management of multiple licenses, each with its own configuration. This allows you to tailor licensing to your product’s needs. The server supports various license types, including:

* **Floating License Registrations**: Dynamically allocate licenses across multiple users or devices.
* **License Consumptions**: Track and manage how licenses are consumed across your organization.
* **Feature Registrations**: Control feature-specific access by enabling or disabling certain features.
* **Feature Consumptions**: Monitor feature usage and consumption, enabling granular control over product functionality.

Each license and feature registration can be customized to meet the specific needs of your organization or product offering.

## Deployment

The Floating Server can be deployed in various environments to suit your needs. Choose from:

* [**Executable**](/floating-server/floating-server-v1/deployment-methods/executable.md): Download and run on Windows, macOS, or Linux.
* [**Docker**](/floating-server/floating-server-v1/deployment-methods/docker.md): Use a containerized environment for easy management.
* [**Kubernetes (Helm)**](/floating-server/floating-server-v1/deployment-methods/kubernetes-helm.md): Orchestrate and scale in a Kubernetes cluster.

For help picking a deployment type, see [**Deployment Methods**](/floating-server/floating-server-v1/deployment-methods.md).

## Configuration

Configure the Floating Server using the `config.yaml` file, where you can specify key settings such as the database type, API keys, and product licenses. For more information on how to configure your server, visit [**Configuration**](/floating-server/floating-server-v1/deployment-methods/configuration.md).

## API

The Floating Server offers an HTTP API for managing licenses, registrations, and consumptions programmatically. Configure your API and shared keys in the `config.yaml` file.

For full details on API usage, check the **API Reference** section.


---

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