Start free trial

Software license types: the legal kinds and the commercial models

“Software license type” answers two different questions. The legal type says what people may do with the code: copy it, change it, ship it in their own product. The commercial model says what a customer pays for and how the software checks it: forever or for a term, on one computer or any computer, with which features. A product you sell needs an answer to both. This guide covers each, and states which models Carcha Seal enforces today.

Reading time
6 min
Updated
15 November 2026
Sections
5
On this page
Legal license typesCommercial licensing modelsModels combine in one policyChoosing a model by where the software runsWhat a licensing model does not decide

Commercial licensing models

A licensing model is the shape of what you sell. The models below are the ones vendors of desktop and on-premises software use most. The last column says what Carcha Seal enforces in the version that runs today, not what is planned.

ModelWhat the customer getsIn Carcha Seal
PerpetualThe right to use the version bought with no end date, often with paid updates for a year that can be renewed.Yes: a license with no expiry. The policy's maintenance days put the end of updates in the lease, so the app can refuse versions released after it.
Subscription or termUse until a date. Paying again extends it.Yes: an expiry date, a check-in interval and offline grace. A connected Lemon Squeezy store updates the license on renewal, cancellation and refund.
TrialA free period before buying.Yes: a per-machine trial policy. One key serves every trial customer, and each computer gets one trial that lasts the policy's days from its first activation.
Node-lockedUse on a fixed number of named computers.Yes: each activation is bound to a device fingerprint, and the seat count limits how many computers. Virtual machines can be allowed or refused per policy.
Floating or concurrentA pool of seats any computer can take while the app runs, given back when it closes.Yes: seats counted per machine, running copy, user, or user per machine. The app needs your server while it runs. Borrowing a seat to take offline and a license server at the customer's site are not in version 1.
Feature-based or editionsModules or tiers (Standard, Pro) unlocked by the license.Yes: the lease lists the licensed features. Code or data encrypted for a feature opens only with a license that includes it.
Named userSeats assigned to particular people, wherever they sign in.No. A floating policy counting by user limits users at the same time, not a fixed list of people.
Usage-based or meteredPay per use: runs, documents, hours, tokens.No. The Python SDK counts MCP tool calls into signed usage reports the console checks, but no license is limited by them; billing on them stays in the contract.
Site or enterpriseUse across an organisation, often without counting computers.Partly: a license can allow unlimited devices, and a site license file covers containers and servers bound to no machine. Where those copies run stays in the contract.

Terms such as seat, lease, grace and maintenance are defined in the glossary; check-ins and grace are in the documentation.

Models combine in one policy

Few products sell a single model. A common offer for desktop software is a perpetual license for three computers, with the Pro features and a year of updates. In Carcha Seal that offer is one policy, created in the console or with the admin API:

POST /api/policies
{
  "productId": "<your product id>",
  "code": "pro-perpetual",
  "name": "Pro, perpetual, 3 computers",
  "maxActivations": 3,
  "durationDays": null,
  "maintenanceDays": 365,
  "features": ["pro"]
}

durationDays: null makes it perpetual, maxActivations is the node-locked seat count, and maintenanceDays is the year of updates. Licenses created from the policy take these values, and each license can override its seats, expiry and features. A floating policy sets licenseModel to floating instead, and takes no check-in, grace, offline days or per-machine trial. The full list is in the admin API reference.

Choosing a model by where the software runs

The environment often decides before pricing does, because each model needs a different amount of contact with your server.

  • One user, one computer, usually online: subscription or perpetual, node-locked. The app checks in now and then and works offline between check-ins.
  • Shared workstations, labs and classrooms: floating, so a seat follows whoever is using the software. It needs a network path to the license server.
  • Networks with no internet: perpetual or an annual term, activated by file. Floating and metered pricing need a connection or a local server, so they move into the contract. See air-gapped software monetization.
  • Several tiers of the same product: one product with features, rather than separate products, so an upgrade changes the license and not the installation.

What a licensing model does not decide

  • The legal terms. A license key enforces a model; the EULA still states what the customer may and may not do.
  • Whether a determined user can bypass the check. The check runs on the customer's computer, so someone who controls it can patch the app. Seal states its limits on the home page.
  • Instant revocation offline. An app that is offline learns of a revoked license only at its next check-in, after its grace period.

Add license keys to an Electron app · Offline license verification · Entitlement management · Try the live demo

Sources

Each page was checked on 11 November 2026. What Carcha Seal supports 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.