Use case
Licence keys for desktop apps and CLI tools
For software that runs on a buyer’s computer rather than a website: licences are counted per machine, and updates are signed so your app can verify them offline before installing.
How it fits
-
Counted per machine
Choose machine-ID counting on the product and send a stable device ID in the
domainfield. -
Works offline
If the server can’t be reached, the app keeps working. Only update checks wait.
-
Verified updates
The public key is built into your app. It checks the SHA-256 and the Ed25519 signature of each download before installing.
-
Any language
Ready clients for Node.js (18+, no packages) and Python (3.8+). Anything that can make an HTTPS POST works.
The code
From the copy-paste client files. Never switch features off: show the licence message and hold back updates.
import { DevEntitleClient } from './deventitle-client.mjs';
const client = new DevEntitleClient({ server: 'https://terminal.deventitle.com', product: 'acme-crm', publicKey: ACME_RELEASE_PUBLIC_KEY });
const result = await client.activate(key, machineId, '1.4.2'); // { valid: true, message: … }
const latest = await client.checkForUpdate(key, machineId, '1.4.2'); // null when up to date
if (latest?.download_url) await client.downloadVerified(latest, `/tmp/acme-${latest.version}.zip`); Getting started
Questions
What should the device ID be?
Any stable identifier your app can generate for the machine. DevEntitle stores it like a domain and counts it against the licence limit.
Does the app need to be online?
Only to activate and to check for updates. If the server can’t be reached, the app must keep working and simply try later.
How often should the app check?
On demand or once a day. The protocol allows 60 checks a minute per IP address and 20 per key.
Other use cases
Add your first product today
Free for software companies. No fees on sales. Your buyers pay you directly.