By Buğra Ömer Aydemir · Updated 16 October 2026
Guides
How to license a desktop app with Carcha Seal, how it compares, and the terms it uses.
How-to guides
- How to add license keys to an Electron app that keep working offline. Install the SDK, activate a key once, then verify a signed lease locally at every start, gate features by name and let a customer move to a new machine.
- Offline license verification with signed leases (JWS and Ed25519). What a lease contains, the order in which the app checks it, how signing keys rotate through a JWKS, and what happens when the device clock moves back.
- Moving from Thales Sentinel LDK to Carcha Seal. A concept map from Vendor Code, Feature, Entitlement and C2V/V2C files to Carcha Seal, the Sentinel features that have no equivalent, and a migration in steps.
Comparisons
Each comparison uses the other vendor's own published pages, links them, and says on which date they were checked. Where Carcha Seal does less, the table says so.
- Keygen alternative: Carcha Seal compared with Keygen. Hosting, pricing model, license models, offline use, floating licenses and SDKs side by side.
- Cryptlex alternative: Carcha Seal compared with Cryptlex. The same questions for Cryptlex, with the points where each one fits better.
- LicenseSpring alternative: Carcha Seal compared with LicenseSpring. The same questions for LicenseSpring, with the points where each one fits better.
Reference
- Software licensing glossary. License key, policy, seat, node-locked and floating licenses, lease, device fingerprint, check-in, offline grace, feature keys, offline activation and JWKS, defined as Carcha Seal uses them.
- Documentation. Concepts, the SDK reference, the client and admin APIs and the order webhook.