> For the complete documentation index, see [llms.txt](https://docs.nalpeiron.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nalpeiron.com/zentitle2-docs/premium-features/network-licensing.md). # Network Licensing {% embed url="" %} Here’s a refined overview of concurrent (floating) network licensing with Zentitle2 from Nalpeiron Inc., using only references from the official Zentitle2 documentation. *** ### What is concurrent or network-based licensing? In Zentitle2, a concurrent (floating) license allows a pool of users/devices to share seats, enabling up to N users to use the software simultaneously. **The platform explicitly supports concurrent/floating models.** Examples: * A customer purchases a “50-seat concurrent license,” which allows any 50 users/devices to run the application simultaneously under that license. * If a 51st tries to run, they are blocked until one of the active seats is freed. (Described in the “Dark Site Local License Server (Network-based licensing)” use case). #### Key characteristics: * The license is not permanently tied to specific named users or machines (unlike node-locked). Instead, it’s about how many are active at once. * Once a user stops using the software — via application exit, logout, or license return — the seat becomes available for use. If a client crashes/leaves orphaned, the system can reclaim via the local license server mechanism. * Zentitle2 supports this model through both cloud services and on-premises/local license server deployments (for restricted or “dark site” customers). *** ### How it works in Zentitle2 #### Setup/configuration * Within the Zentitle2 product/entitlement setup, you’ll define the license code/profile with a Concurrency Mode (e.g., “concurrent”). The documentation refers to network/floating models in the “Network Licensing” / use-case sections. * Set the parameter for “Max number of active clients allowed” (i.e., how many concurrent seats) in the license/profile configuration. * If using the local license server (LLS) scenario, you deploy the Docker container at the customer site, delegate the license from the Zentitle Cloud, and the same protocol applies as in the cloud mode. * No changes needed in your application. #### Runtime/usage * Upon application start, the client requests checkout of a seat. Zentitle2 checks if seats are available; if yes, it allows, else denies (or queues) the request pending seat availability. The client then holds that seat until it returns it. * On application exit or when the user logs out, the seat is returned, freeing it for someone else. * In case of orphaned activations (client crash or no return), particularly in the local license server model, the system can detect expired leases and free up seats to prevent blocking legitimate users. * **Analytics**: Zentitle2 tracks seat usage (high/low water marks, etc) to help you monitor usage. #### Monitoring & analytics * Through the Zentitle platform, you can monitor the number of currently active seats, the number of allocated seats, and usage trends over time. * This allows you to plan seat counts, upsell additional seats, and understand actual usage. (Implicit in the platform capability of supporting floating/floating-feature/element-pool licensing) *** ### Key advantages * **Flexibility for customers:** They purchase a pool of seats, not tied individually, so if usage fluctuates, they only need enough seats for peak usage rather than for every user. * **Vendor/hands-off control:** You still enforce the seat limit, handle orphan returns via lease logic, and monitor usage. * **Deployment options:** Whether cloud or local/air-gapped (the “dark site” local license server), you have full concurrent licensing support. * **Monetization leverage:** You can offer “concurrent seat” tiers, upsell extra seats, monitor actual utilization, and refine pricing accordingly. *** ### Key considerations * **Seat-count planning:** You must understand usage patterns to avoid under-seating (which blocks users) or over-seating (which wastes unused capacity). * **Return/lease logic:** Ensure your application gracefully returns the seat upon exit or logout. Similarly, ensure the local license server lease logic is robust to release orphaned seats. * **Connectivity/deployment constraints:** For cloud mode, clients typically require internet access. For restricted environments, you must deploy the local license server (LLS) to ensure seamless operation. The docs emphasize this for network-based/floating licensing. * **Application integration:** Your software must integrate with the Zentitle2 SDK/API to check out the seat, return the seat, handle “no seats available” cases, and handle lease expiry. * **Mixing models:** You may decide to offer a hybrid portfolio, where node-locked licenses are provided for some users and floating/concurrent licenses are offered for others. Zentitle2 supports mixing. * **Dark site/on-prem variant:** For customers who cannot allow internet connections, the local license server is essential. That imposes some operational burden (deployment, network, local server). The docs cover this case in the “Dark Site Local License Server (Network-based licensing)” section. *** **Network deployments can be complex. Talk to us to learn more.** {% hint style="success" %} Let's jump on a call and discuss how we can help, get in touch with your account manager today → [Setup a 1:1 discussion](https://www.nalpeiron.com/get-a-11-demo.html) {% endhint %} --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.nalpeiron.com/zentitle2-docs/premium-features/network-licensing.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.