Start free trial

Entitlement management software for desktop and on-premises apps

An entitlement is what a customer bought: which product, which features, on how many computers, until when. Entitlement management software keeps that record for every customer and makes the application respect it. Carcha Seal does this for software that runs on your customers' computers and servers. The record lives on a license server, hosted by us or run by you, and the app checks it with a signed lease it verifies itself, with no network call at each start.

Reading time
5 min
Updated
11 November 2026
Sections
6
On this page
Three things called entitlement managementWhat an entitlement holds in Carcha SealHow the app enforces itKeeping entitlements in step with salesHosted or on your own serverQuestions

Three things called entitlement management

The same words name three kinds of product. Only one of them is about software you sell and your customers install.

KindWho it is forWhat it manages
Identity governance (for example Microsoft Entra)IT departmentsWhich employees and guests can reach which internal groups, applications and sites, and for how long.
Usage and plan limits for web SaaS (for example Schematic, Stigg)Teams selling a hosted web or AI productPlans, credits and usage limits enforced inside an application that runs on the vendor's own servers.
Software entitlement management (Carcha Seal)Vendors of installed softwareWhat each customer may run, on which computers, with which features and until when, enforced inside the app, including where it has no connection.

If your product only runs on your servers, a plan and usage tool is the closer fit. If it is installed on your customers' machines or servers, the rest of this page is for you.

What an entitlement holds in Carcha Seal

  • Product and policy. A policy is a reusable set of terms: how many seats, how long a license lasts, how long updates are included, how often the app checks in, how long it keeps working when it cannot, whether virtual machines and offline activation are allowed.
  • Licensing model. Node-locked, where each seat is one computer, or floating, where seats are in use at the same time and counted per machine, running copy, user, or user per machine. See software license types.
  • Features. Each license lists the features it unlocks. A feature can have its own encryption key, so the code or data behind it opens only on a computer whose license includes it.
  • Time. An expiry date, or none for a perpetual license, and separately the end of updates: the versions the license may run.
  • Seats on computers. Each activation is bound to one device. A user can move a seat to a new computer three times in 12 months; you can free a seat from the console at any time.
  • Status. Active, suspended or revoked, changed from the console or the API.
  • Trials. A trial policy gives each computer one trial. Reinstalling or using another trial key does not start it again.
  • Your references. Two fields of your own on each license, such as an order number and a CRM id.

How the app enforces it

  1. The app activates once with the customer's license key.
  2. The server returns a lease: the entitlement, bound to that computer and signed with your account's Ed25519 key.
  3. The app verifies the lease locally at each start. It does not need the network to do so.
  4. The app checks in on a schedule to pick up changes: a renewal, a new feature, a suspension. If it cannot reach the server, it keeps working for the grace period you set.

Computers with no network at all are activated and renewed by exchanging a file. A floating license is different: the app takes a seat from your server while it runs and gives it back when it closes, so it needs the connection. The steps in code are in offline license verification.

Keeping entitlements in step with sales

  • A payment connection. With a Lemon Squeezy store connected, a purchase creates the license and emails the key; renewals, cancellations and refunds update it.
  • The admin API. Create, change and revoke licenses from your own systems. A read-only API key serves a dashboard or a report and can change nothing.
  • The console. Issue a license by hand, change its terms, replace a lost key, free a seat.

Hosted or on your own server

The hosted service runs on Amazon Web Services in Frankfurt, and each account signs with its own key. Or run the Carcha Seal server yourself under a written agreement: it needs no connection to Carcha Labs, because its own license is renewed by file. After 12 consecutive months of subscription it keeps a perpetual fallback, so it goes on issuing licenses on the version it runs even if the subscription ends. See self-hosted servers.

SDKs: Electron and Node.js, C++, and .NET. All three verify leases offline and take floating seats.

Questions

What is software entitlement management?

Keeping a record of what each customer bought (products, features, seats and dates) and making the software enforce it.

How is it different from license key management?

A license key identifies the customer. The entitlement is what that key grants, and it changes after the sale: more seats, a new feature, a renewal, a suspension.

Does the app need to be online?

Not for a node-locked license. The app verifies its lease locally and checks in when it can; computers that never go online use activation files. A floating license needs the server while the app runs.

Can it run on our own servers?

Yes, under a self-hosting agreement, with no connection back to Carcha Labs.

Software license types · Moving from Sentinel LDK · Try the live demo

Sources

Each page was checked on 11 November 2026. What Carcha Seal does is taken from its server code and documentation.

License your app in an afternoon.

14-day trial, no card. Your own server address and signing key from the first minute.