> 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/ui-local-license-server/local-license-server-lls.md). # Local License Server (LLS) {% embed url="" %} The Zentitle2 Local License Server (LLS) allows the vendor to deploy a Docker container-based server to an end customer who does not want to (or cannot) allow an ongoing connection with the Zentitle2 cloud-based license server. These "dark sites" are common in Enterprise software where the end-user customer has a secure network environment. Traditionally, they have been very hard environments to deploy and maintain. With the local license server, we aim to simplify deployment. {% hint style="info" %} LLS provides a compatible replacement for the cloud-based Licensing API, so your application can use [almost all](https://docs.zentitle.io/account-settings/local-license-server-lls/entitlements-to-be-used-on-lls-instances#current-limitations) licensing features with LLS without any changes to its implementation logic. {% endhint %} Once your Local License Server (LLS) is running and activated, you can export entitlements from the LLS and use the LLS Licensing API to activate seats and manage features. This simplifies everything: one API and one product that can run both in dark and internet-connected environments. {% hint style="info" %} LLS is a standalone Zentitle product that can be activated like any other product on the platform using the entitlement's activation code. Ask the Zentitle support team to configure an LLS license for you. {% endhint %} {% hint style="warning" %} LLS is licensed to our customers and controlled accordingly in the field. It is set up as a perpetual license, eliminating the need to constantly re-activate it. However, the LLS will still need to renew its internal lease period under the agreement you have with Nalpeiron; i.e., this is deployed to your customers and remains active as long as you remain a Nalpeiron customer. {% endhint %} ### What are the differences between legacy and low-cost solutions and the Nalpeiron Growth Platform? Many organizations only realize the hidden costs and limitations of cheaper or legacy licensing solutions after deployment, when support, flexibility, and security truly matter. Zentitle's premium approach ensures you avoid these pitfalls, providing a future-proof, enterprise-ready foundation for all your licensing needs. ### **Summary Table: Zentitle2 for Secure, Offline, and Dark Sites** | Feature/Benefit | Zentitle2 Delivers | Cheap/Legacy Solutions | | -------------------------------- | ------------------------------ | ---------------------- | | Easy Docker-based Deployment | Yes | Rare/No | | Full Business Model Support | Yes (all models, even offline) | Limited | | Advanced VM & Security Controls | Yes | No/Weak | | Remote Management & Automation | Yes | No | | Unified Cloud & Offline Platform | Yes | No | | Lower Total Cost of Ownership | Yes | No | | Premium Support & Partnership | Yes | No | Zentitle is the only choice for organizations that demand robust, flexible, and secure offline software licensing, delivering operational efficiency, business model agility, and peace of mind that cheaper solutions simply cannot match. See this article for more details: *** ### How is LLS different from an old-fashioned concurrent server? Unlike old-fashioned network-oriented concurrent servers like FlexLM/FlexNet Publisher), LLS can support all the same business models within an Intranet as it can outside it. Why is this important? Now, both concurrent and node-locked type deployments can be managed on a customer site, allowing total freedom just like when they use the Internet or the Public web. In addition, LLS can run without extra security, unlike FlexLM, which has traditionally required a dongle—this is very cumbersome, slow, and prone to issues. LLS can be activated quickly and easily on the customer site and managed effectively via Zentitle2. This is a significant change in options available to end-user customers. Now, more options are available within secure (dark/offline) environments. *** ### How is this different from offline license "files" In offline or air-gapped environments, software vendors typically choose between static license files and a local license server (LLS). While both enable offline operation, they differ fundamentally in control, security, and revenue protection. ### Key Difference * License Files: Fixed, pre-issued artifacts with no live control * Local License Server: A live entitlement system enforcing policy in real time (even offline) ### Risk & Revenue Impact #### License Files (High Risk) * No real-time enforcement or revocation * Easy to copy or misuse → piracy risk * No visibility into usage or over-deployment * Manual updates → errors and missed renewals * Limited to simple models (node-locked, expiry-based) 👉 Result: Significant revenue leakage and compliance risk #### Local License Server (Low Risk / High Control) * Continuous enforcement of entitlements locally * Strong anti-piracy controls (binding, concurrency, policy) * Full usage tracking and auditability * Dynamic updates without reinstalling software * Supports modern models (usage-based, concurrent, hybrid) 👉 Result: Controlled monetization and minimized leakage ### Strategic Takeaway * License files solve a technical problem: offline access * A local license server solves a business problem: revenue control, flexibility, and scalability ### Bottom Line If your software: * has enterprise customers * needs a single "live" auditable control plane across deployments * has issues with revenue leakage * wants to remove manual errors and manual processes * uses (or plans to use) usage-based / hybrid pricing * operates in complex or offline environments **→ A local license server is not optional — it’s critical infrastructure for protecting and growing revenue.** *** ## How to deploy LLS to your Customers: * Ensure your Zentitle2 subscription has LLS enabled and that you have activation details in your dashboard. * Download and test the LLS and Zentitle2 interworking as explained below. * Install the LLS container at an end-user site and activate it securely via the "offline" process described in the following pages. * Transfer any rights for that end-user (entitlements) to the LLS instance. * Manage the LLS deployment over time using "refresh" and "deactivation" options. ### LLS Testing Quick Start Follow the steps below to test the LLS functionality: 1. [Run the LLS on your local environment ->](/zentitle2-docs/ui-local-license-server/local-license-server-lls/local-license-server-installation.md#running-the-demo-application) 2. [Activate the LLS license ->](/zentitle2-docs/ui-local-license-server/local-license-server-lls/lls-license-end-user-management.md#license-activation) 3. [Export an entitlement from Z2 into LLS ->](/zentitle2-docs/ui-local-license-server/local-license-server-lls/entitlements-to-be-used-on-lls-instances.md#entitlement-export) 4. [Use the LLS Licensing API ->](/zentitle2-docs/ui-local-license-server/local-license-server-lls/lls-licensing-api.md) {% 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, and the optional `goal` query parameter: ``` GET https://docs.nalpeiron.com/zentitle2-docs/ui-local-license-server/local-license-server-lls.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.