Concept map
| Cryptolens | Carcha Seal |
|---|---|
| Product | Product; its code is what the SDK sends. |
| License key | A license key, shown once when issued. Carcha Seal keeps no copy; a lost key is replaced. |
Key.Activate with a machine code | The SDK's activate(); the machine code becomes a device fingerprint (a SHA-256 hash of the operating system's machine ID and the product code). |
| Offline: an RSA-signed license saved and re-checked locally | An Ed25519-signed lease the app verifies itself, and offline request and license files for computers that never go online. |
| Floating licenses (per machine or per instance) | Floating licenses: seats in use at the same time, counted per machine, running copy, user, or user per machine, taken with checkout and given back on quit. |
| Feature flags (f1–f8) and data objects | Features listed on the license; the app asks for one by name, for example Seal.hasFeature(state, "pro"). |
Trial keys (CreateTrialKey) | A per-machine trial policy: each computer gets one trial from a trial key. |
| User-based licensing (customers sign in) | No equivalent. Carcha Seal binds a key to devices, not to a login. |
| Usage-based (pay per use) | No equivalent. Carcha Seal has no usage counters. |
| License Server add-on (local cache / offline floating) | Floating seats come from your Carcha Seal server; a license server at the customer's site is not in version 1. |
Web API (CreateKey, Activate) | The admin API; a read-only API key for a dashboard. |
What does not carry over
- User-based licensing. Cryptolens can let customers sign in instead of entering a key; Carcha Seal binds a key to devices, not to a login.
- Usage-based (pay per use). Carcha Seal has no usage counters or overages.
- The License Server add-on. It serves floating licenses from a cache on the customer's network; Carcha Seal's on-premises floating is not in version 1.
- Arbitrary data objects. Carcha Seal has two reference fields per license and named features, not free-form key-value data.
- SDKs in other languages. Cryptolens covers many languages and add-in hosts; Carcha Seal's SDKs today are Electron and Node.js, C++, .NET and Python.
A migration in steps
- List what you use. Products, license keys, whether licenses are key-based or user-based, feature flags, whether any are floating or usage-based, whether any customers work offline, which language your app is in, and how orders create keys.
- Model products and policies. One Carcha Seal product per marketable product, one policy per kind of license term, and features in the catalog with names for your Cryptolens feature flags.
- 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 Cryptolens key or order id in a reference.
- Ship an app version that accepts both. Replace the Cryptolens SDK with 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. Loop your Cryptolens keys through the Web API, then create Carcha Seal licenses with the same features and dates through the admin API, each with its Cryptolens key in a reference, and send each customer a new key; keep a mapping so a repeat request returns the same new key.
- Remove the Cryptolens check in a later version, after the customers you care about have activated.
Add license keys to your software · .NET SDK · C++ 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 Cryptolens products, license templates and feature flags;
- whether your licenses are key-based or user-based, and whether any are floating or usage-based;
- 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
Cryptolens's pages were checked on 11 November 2026; what Carcha Seal does is from its server code and documentation.