Concept map
| Keygen | Carcha Seal |
|---|---|
| Product | Product; its code is what the SDK sends. |
| Policy | Policy: seats, expiry or perpetual, end of updates, features, check-in and offline grace. Node-locked or floating. |
| License (key) | A license key, shown once when issued. Carcha Seal keeps no copy; a lost key is replaced. |
| Machine (activate / deactivate) | A device seat on the license: activate() binds it to one computer, deactivate() frees the seat. |
| Machine heartbeat (ping) | The check-in for a node-locked license, or the seat heartbeat for a floating one. |
| Entitlements | Features listed on the license; the app asks for one by name, for example Seal.hasFeature(state, "pro"). |
| Cryptographic (signed) license files, offline licensing | Offline request file and license file (offlineRequest, activateOffline), plus the Ed25519-signed lease the app verifies itself. |
| Floating, concurrency (processes) | Floating licenses: seats in use at the same time, counted per machine, running copy, user, or user per machine. |
| Users, user-locked licenses | No equivalent. Carcha Seal binds a key to devices, not to a user login. |
| Metered licenses | No equivalent. Carcha Seal has no usage counters. |
| Keygen Relay (local license pool) | Floating seats come from your Carcha Seal server; a license server at the customer's site is not in version 1. |
| Releases and artifacts (distribution) | No equivalent. Carcha Seal licenses software; it does not host release downloads or updates. |
| List licenses / machines / users (API) | The admin API and the console; a read-only API key for a dashboard. |
What does not carry over
- User-locked licenses. Keygen can bind a license to a user; Carcha Seal binds a key to devices, not to a login.
- Metered licensing. Carcha Seal has no usage counters or overages.
- Release distribution. Keygen hosts release artifacts and auto-updates; Carcha Seal only licenses the software, so you keep your own distribution.
- A license server at the customer's site. Keygen Relay hands out licenses from a local pool offline; Carcha Seal's on-premises floating server is not in version 1.
- Environments, groups and the fine-grained token model. Carcha Seal has one account per vendor, with full and read-only API keys.
- SDKs in other languages. Keygen ships a Go SDK and example code in many languages; Carcha Seal's SDKs today are Electron and Node.js, C++, .NET and Python.
A migration in steps
- List what you use. Products, policies, whether licenses are node-locked, floating, user-locked or metered, entitlements, whether any customers work offline, which language your app is in, and how orders create licenses.
- Model products and policies. One Carcha Seal product per marketable product, one policy per kind of license term, and features in the catalog with the same names as your Keygen entitlements.
- Connect the order system. Point your store or backend at a Lemon Squeezy connection or the admin API, so a new order creates a Carcha Seal license, with the Keygen license id in a reference.
- Ship an app version that accepts both. Swap the Keygen SDK or your validation code for the Carcha Seal SDK where your language is covered, or run both and check Carcha Seal first, so customers move when they enter a new key.
- Re-issue keys for existing customers. Export your licenses, machines and users from the Keygen API, then create Carcha Seal licenses with the same features and dates through the admin API, each with its Keygen id as a reference, and send each customer a key.
- Remove the Keygen check in a later version, after the customers you care about have activated.
Add license keys to your software · C++ SDK · .NET SDK · Glossary
Free migration assessment
Write with your current setup and get an answer from engineering, not a sales queue, within 2 business days. Useful to include:
- your Keygen products, policies and entitlements;
- whether your licenses are node-locked, floating, user-locked or metered;
- the language and platforms of your app;
- whether any customers run offline or air-gapped.
Leave out your customers' names and emails. The answer maps each product and license model to Carcha Seal, lists what would not carry over, and sets out the steps for your case. It does not oblige you to anything.
Sources
Keygen's pages were checked on 11 November 2026; what Carcha Seal does is from its server code and documentation.