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. Unlike 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. In-depth guide: Floating Licensing

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. See: 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 license check-outs and syncs. The floating server can handle offline floating features, allowing operations in air-gapped or restricted environments. Offline licensing docs: Offline License Activation

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 locally, including offline floating features that allow the licenses to be borrowed or used without an active internet connection. More info: Floating Features

General floating features guide: Floating Features

License Borrowing

• Floating Cloud: Users can borrow licenses for a specified time to work offline. Initial borrowing requires an internet connection. Borrowing API: Borrow Floating License

• Floating Server: Offers more flexibility for offline environments; licenses can be borrowed locally without internet as long as the borrowing happens on the server.

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 info: Hardware Key Licensing

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. Setup docs: 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: Reporting capabilities are currently limited compared to the cloud:

  • Floating usage and consumption data are stored locally on the server.

  • When an internet connection is available, this data is sent to the cloud and used to generate reporting graphs.

  • If the server is offline, only CSV reports are available (no graphical reports).

  • For 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 to better align the floating server's reporting capabilities with the cloud. General analytics docs: 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, and roles/permissions can be customized similarly. Some advanced cloud-based features (like real-time updates) might be limited.

End-user portal docs: End User Portal

Consumption Syncing / Caching Mechanisms

• Floating Cloud: Data on license consumption is locally cached; it is necessary to sync consumptions (as with non-floating licenses) to accurately reflect consumption data on the LicenseSpring platform.

• Floating Server: Consumption data is tracked locally, with periodic syncs to LicenseSpring’s platform (every hour) when a connection is available. Syncing does not occur when running in offline mode.