> 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/use-cases/use-case-directory/dark-site-local-license-server-network-based-licensing.md).

# Dark Site Local License Server (Network-based licensing)

Deploy network-based licensing — concurrent, floating, or consumption-based — either directly against Zentitle Cloud or through a local license server for isolated, dark-site environments.

{% embed url="<https://www.youtube.com/watch?v=g7TNvc-YYU8>" %}

Many software vendors want to use network-based licensing models, such as concurrent or floating licenses, using our element pools, floating features, and consumption tokens. We support two flexible options for implementation.

The most straightforward approach is connecting your application to our Zentitle Cloud—a fully multi-tenant, highly available service with low latency worldwide. If you have customers in China, Japan, South America, North America, and beyond, and want to provide an easy-to-adopt, reliable cloud-based licensing service, Zentitle Cloud is perfect.

However, some customers—often large organizations—must work in completely isolated environments. This may be for security reasons (to prevent outside access) or for reliability and sovereignty concerns (eliminating dependencies on external cloud services for daily operations).

For these situations, we provide our local license server, which is deployed as a Docker container that works in any environment. You can delegate a license from Zentitle Cloud to this local license server, which remains locked in that dark LAN environment. Your applications can then connect directly to the local license server.

The beauty of this approach is that the protocol between your application and the local license server is identical to the one used with Zentitle Cloud. This means no additional changes to your application are needed.

This setup enables deployment in any environment with concurrent license models, including floating features, element pools, and consumption-based models. The local license server tracks seat and feature usage locally. That usage data doesn't flow back to the Zentitle Cloud, so the Zentitle2 interface doesn't show usage for entitlements hosted on a local license server.

{% embed url="<https://youtu.be/DbMPOfT-Iow>" %}

Many software vendors use what's called a floating or concurrent-use license model.

Instead of having individual "node-lock" licenses that are permanently tied to specific machines, floating licenses work differently.

Here's how: Let's say you have three users but a two-seat floating license. This allows any two of those users to access the application simultaneously. The licensing system ensures the two-seat limit is never exceeded. If the third user tries to access the application, they'll be denied and must wait until a seat becomes available.

This model allows companies to maintain a larger pool of potential users while only purchasing enough seats for their peak usage needs.

### Network configurations

<figure><img src="https://2412542193-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1tBhTGn5igyI6ECLHjpC%2Fuploads%2FPBeTfZwtCyuMxFSTvg8b%2FSlide6.png?alt=media&amp;token=39255cf1-8d77-47fe-9cf4-646597a18e25" alt=""><figcaption></figcaption></figure>

<figure><img src="https://2412542193-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1tBhTGn5igyI6ECLHjpC%2Fuploads%2FBjs0MRSFsFaTGGLP0giJ%2FSlide7.png?alt=media&amp;token=f0ec0894-e025-4acf-97df-b4f76cdda5aa" alt=""><figcaption></figcaption></figure>

<figure><img src="https://2412542193-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1tBhTGn5igyI6ECLHjpC%2Fuploads%2FZR08m47sJqSOcsYMWxCM%2FSlide8.png?alt=media&amp;token=e350aa35-f3b1-4e1b-adeb-1ac6b440413b" alt=""><figcaption></figcaption></figure>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.nalpeiron.com/zentitle2-docs/use-cases/use-case-directory/dark-site-local-license-server-network-based-licensing.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.