Offline licensing allows applications to validate licenses without requiring a continuous internet connection. Instead of contacting a licensing service during every validation, applications verify signed license data locally while continuing to enforce licensing rules.

If you want to learn more about offline software licensing, common implementation approaches, and when each approach is appropriate, please read our guide to offline software licensing.

Related Resources

• Licensing Models Overview
• Offline Software Licensing Guide
• Documentation on Offline Licensing
• Video Walkthrough

How Devolens Implements Offline Licensing

Devolens uses digitally signed license files that applications can validate locally using an embedded RSA public key.

When a license is retrieved from Devolens, the SDK verifies the digital signature before accepting the license as valid. Once stored locally, the same license can continue to be validated without contacting Devolens again.

Because the application performs the validation itself, licenses remain protected against modification while continuing to function in offline environments.

‍

Offline Activation Files

Offline deployments use signed activation files that contain the license information required by the application.

These files can be generated on a connected machine and transferred to the target environment using approved methods such as USB drives or other secure media. Once installed, the application validates the activation file locally without requiring network connectivity.

This approach is well suited to desktop applications, engineering software, plugins, and other products deployed in environments where manual license updates are acceptable.

‍

Supporting Different Offline Strategies

The same implementation supports several deployment models depending on operational requirements.

Common approaches include:

• One-time online activation followed by offline validation
• Periodic license refresh using signed activation files
• Fully air-gapped deployments using manually distributed license files

The expiration period of offline licenses can be configured to match your operational requirements, allowing organizations to balance administrative effort with how frequently licenses should be refreshed.

‍

When a License Server Becomes Useful

Signed license files provide a straightforward solution for many offline deployments, but larger environments often introduce additional operational requirements.

As the number of machines grows, organizations may need to manage license renewals, updates, revocations, and floating licenses without manually distributing activation files to every device.

For these environments, the Devolens License Server provides centralized license management while allowing client applications to remain disconnected from the internet.

‍

Implementation

Offline licensing is implemented using signed license files validated by the Devolens SDKs.

The Devolens documentation on offline licensing includes code examples and guides for:

• Validating signed license files
• Creating offline activation workflows
• Configuring offline license expiration
• Refreshing offline licenses
• Deploying fully air-gapped licensing solutions