The Devolens License Server allows applications running in restricted, on-premises, and air-gapped environments to use Devolens without requiring every client machine to communicate directly with the internet.

If you want to learn when a license server is the right architectural choice and how it compares to other offline licensing approaches, read our guide to software license servers.

‍

Related Resources

• Offline Licensing Guide
• Software License Server Guide
• Documentation on the Devolens License Server

How the Devolens License Server Works

The License Server acts as a gateway between your applications and Devolens.

Instead of every client application communicating directly with Devolens, applications communicate with a single License Server running within your network. The License Server synchronizes licensing information with Devolens whenever connectivity is available and serves license requests to client applications over the local network.

This architecture allows organizations to maintain existing network security policies while providing centralized license validation for all connected applications.

‍

Supporting Restricted and Air-Gapped Environments

The License Server supports a range of deployment scenarios, including enterprise networks with strict firewall policies, customer-managed on-premises installations, and fully air-gapped environments.

When internet connectivity is available, the License Server synchronizes license information with Devolens automatically. For environments that operate without internet access, the server can use pre-loaded activation files to continue validating licenses locally.

This allows organizations to maintain a consistent licensing workflow across connected, restricted, and fully offline deployments.

‍

Centralized License Management

Because applications communicate with a single License Server rather than directly with Devolens, license management becomes centralized.

Administrators can manage license changes, entitlement updates, renewals, and revocations through Devolens without distributing updated license files to every client machine. As the License Server synchronizes with Devolens, those changes become available to connected applications automatically.

This reduces the operational effort associated with managing large offline deployments.

‍

Operational Visibility

Centralizing license validation also provides a single point for managing licensing activity across restricted environments.

Rather than tracking activation files across individual machines, organizations can manage licensing through one service while continuing to synchronize license data with Devolens whenever connectivity is available.

This approach simplifies administration without requiring changes to existing network architecture.

‍

Implementation

The documentation on the Devolens License Server includes code examples and guides for:

• Deploying the License Server
• Configuring client applications
• Enabling cached and offline operation
• Configuring floating licensing
• Running fully air-gapped deployments
• Integrating the License Server with the Devolens SDKs