Comparison of Floating Cloud and Floating Server Licenses

activation & registration floating cloud activation is managed via licensespring’s cloud platform, meaning the client communicates with the cloud for license issuance and revocation this requires internet access in contrast to a floating server setup, a floating cloud license demands individual activation on every device aiming to utilize the license since the license is bound to the client device an in depth guide for activating on the floating cloud can be found on our floating cloud guide https //docs licensespring com/sdks/tutorials/licensing scenarios/floating? gl=1 gipckn up mq ga mtu1mdk4njmwoc4xnzi5mjy4ndu3 ga wp8x5pq7n7 mtcyoti2odq1ni4xljaumtcyoti2odq1ni4wljauma #sputq with a floating cloud license, you must first activate any client that will be allowed to register a license floating server license activation happens locally, on premise, using a self hosted floating server internet connection is not required for clients to check in/out licenses since all interactions between the floating server and client application happen over the local network the license is bound to the floating server for floating server licenses licenses can be activated online, offline, air gapped or by using a hardware key on the floating server with guides for each being found in our floating server registration documentation https //docs licensespring com/license options with a floating server, you first activate the floating server, then any clients on the private network may register to it online/offline access floating cloud requires constant internet access to check out licenses and perform license checks floating server clients can operate completely offline as long as they can communicate with the on premise server internet connection is required only for online licenses check outs and syncs the floating server can handle offline floating features, allowing operations in air gapped or restricted environments offline licensing on the floating server can be done by following the steps in our offline activation documentation https //docs licensespring com/offline floating features floating cloud provides concurrent licensing features, allowing users to check in/out licenses dynamically, with cloud based management of license usage floating server supports similar features but locally, including offline floating features that allow the licenses to be borrowed or used without an active internet connection more information about floating features on the floating server can be found in our floating server floating features documentation https //docs licensespring com/fcsu floating features more general information about how to use floating features in your code can be found at floating features documentation https //docs licensespring com/sdks/tutorials/licensing scenarios/floating features license borrowing floating cloud users can borrow licenses for a specified time, allowing them to work offline this feature still requires an internet connection for the initial borrowing process a license can be borrowed over the floating cloud with license borrow https //docs licensespring com/license api/floating/license/borrow floating server offers more flexibility with offline environments, allowing licenses to be borrowed without any internet connection, as long as the borrowing happens locally on the server a license can be borrowed on the floating server with floating server license borrow https //docs licensespring com/floating server/api/registration/borrow hardware keys floating cloud not typically used for cloud licenses floating server hardware keys can be used to secure the floating server setup, preventing unauthorized copying or misuse of the server installation more information at floating server hardware keys https //docs licensespring com/floating server/hardware keys setting up the sdk floating cloud easier setup as there is no need for local server configuration; the client sdk interacts directly with the cloud floating server more involved, requiring setup and configuration of the local server path and network settings more information at floating server setup https //docs licensespring com/floating server analytics and reporting floating cloud reports can be generated via the licensespring platform, providing real time insights into license usage and status floating server the floating server's reporting capabilities are currently limited compared to the cloud reporting at present, floating usage and consumption data are stored locally on the server when an internet connection is available, this data is sent to the cloud, from where it is later used to generate reporting graphs however, if the server is offline, only csv reports are available, with no graphical reports for other metrics, such as api calls and activation/deactivation events, users must rely on cloud based analytics and reporting this setup is expected to change in version 2, where the goal is to align the floating server's reporting capabilities more closely with those of the cloud for now, though, the reporting remains as described general information about analytics and reporting at licensespring can be found within our analytics documentation https //docs licensespring com/vendor platform/analytics user portal and license manager permissions floating cloud permissions for users and administrators can be managed via licensespring’s web portal, providing easy access to manage licenses remotely floating server user management is handled locally, but roles and permissions can be customized in a similar way however, some advanced cloud based features (like real time updates) might be limited find information about our end user portal in our end user portal documentation https //docs licensespring com/portals/end user consumption syncing/caching mechanisms floating cloud data on license consumption is locally cached, it is necessary to sync consumptions (just like with non floating licenses) to accurately reflect consumption data on the licensespring platform floating server consumption data is tracked locally, and syncing with licensespring’s platform (if necessary) is performed via periodic updates every hour this syncing does not occur when running in offline mode