Offline software licenses for on-premise installations
Issues signed license files and checks them offline in the customer's installation, with a warning before renewal and a switch to read-only when the license expires.
If you license software that runs on the customer's own infrastructure, you need to control how long each license is valid without depending on an activation server, above all on networks with no internet access. This offline software licensing module issues a signed license file and checks it inside the installation itself, with no external calls. When the license expires, the application switches to read-only: the customer can view and export its data, but not change it.
Who it is for
Software companies that offer on-premise installations, integrators that distribute software to customers with isolated networks and product teams moving from SaaS to self-hosted installations.
What offline software licensing solves
- Renewals without a connection. Validity is controlled even if the installation has no internet access.
- Tampered licenses. Any change to the file breaks the signature.
- Expiry that locks the customer out. When the license runs out, the data stays accessible in read-only mode.
What it does
- Issues signed licenses with the customer's details, the issue date and the renewal date, in a single-line file that is easy to send.
- Gives each signing key an identifier, so it can be replaced later on.
- Checks the license in the installation with the public key, read from the configuration or from a file.
- Distinguishes three states: active, expiring soon (from 30 days before) and expired.
- On expiry, rejects changes made by users and keeps sign-in, password changes and system logs working.
- If the installation requires a license and the file is missing or altered, or there is no public key, it also switches to read-only.
- Shows a warning in the interface before and after expiry.
- Includes a console to issue, record and check licenses.
Benefits
- You can offer installations on isolated networks without losing control of renewals.
- Your customers do not lose access to their data because a renewal is pending.
- You skip designing a delicate part of your product.
What you get with each license
Price upon request, depending on license type and scope. Integration support and maintenance are contracted separately.
- The code for the issuing and checking module, ready to add to your application.
- The warning component and the issuing console.
- Integration examples and documentation.
- A warranty against defects for the agreed period.
- Everything above, with the right to adapt and maintain it inside your product.
- The right to embed the asset in a commercial product of your own, identified in the contract.
- The right to distribute it to your customers as part of that product, without asking for authorization for each installation and with no limit on end customers, unless otherwise agreed.
- It does not include reselling or sublicensing it on its own.
- It is not exclusive, unless otherwise agreed.
- Maintenance, support and adaptations are contracted separately.
Technical specifications
Language and runtime: TypeScript 5.9 on Node.js 22 (the version it ships with).
Frameworks: It does not depend on a framework. The write lock plugs in as a Prisma Client 7 extension, and the interface warning into Next.js 16 applications.
Database: No database needed to check the license.
Operating systems: A server with Node.js.
Interface languages: Spanish (interface warning).
Required infrastructure:
- Nothing extra: the customer's installation only needs the public key and the license file.
Private deployment: Runs fully on its own, offline: the license is checked locally.
Main libraries: It uses the standard Node.js crypto library. The optional integrations rely on these libraries in the host application:
| Library | Version | License |
|---|---|---|
| @prisma/client | 7.10.1 | Apache-2.0 |
| next | 16.4.2 | MIT |
Dependencies with specific license terms: None.
Compatibility and integrations: Prisma Client (query extension) and Next.js (App Router).
Redistribution terms
The asset's own code can be embedded in the licensee's commercial products under the embeddable module, source code and OEM licenses, on the terms of the contract. None of the module's production dependencies has a copyleft license or specific commercial terms.
Installation requirements
A Node.js application. Signing and checking work in any application of this kind. The write lock is ready for applications that use Prisma, and the warning for Next.js applications; in other cases they need adapting. The private signing key always stays on your side, and the customer's installation only needs the public key and the license file.
Frequently asked questions
Does it need a connection to validate the license?
No. The signature is checked locally with the public key.
What happens to the data when the license expires?
It can be viewed and exported. Only changes are blocked.
Can a license be copied to another installation?
The license is not tied to a specific machine. It protects the validity period and the integrity of the file; if you need to bind it to a machine, that has to be added during adaptation. If you hand the source code to your customer, they could disable the check.
Is maintenance included?
No. Maintenance and support are contracted separately. Keeping the private key safe is the responsibility of whoever issues the licenses.
Request
Request information on M-SEG-01
Fill in the form with the asset reference and the license type you're considering. I reply in writing. If you need to review code, tick the NDA box and we'll sign one before anything is shared.