Floating Server V1

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 docid\ nuigsodmruiadqa mtje1 download and run on windows, macos, or linux docker docid\ f6 e9q0dteogfahmr997 use a containerized environment for easy management kubernetes (helm) docid\ pf5ciozrnmrcqlxtlaejd orchestrate and scale in a kubernetes cluster for assistance with selecting a deployment type, refer to the deployment methods docid\ nxbg06l5tvr1lsvdmi2tb section 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 the configuration docid\ ai5mhs20r rcj9f8ey26c section 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