Concept map
| Cryptlex | Carcha Seal |
|---|---|
| Product | Product; its code is what the SDK sends. |
| License key and license policy | A license key, shown once when issued, and a policy: seats, expiry or perpetual, end of updates, features, check-in and offline grace. |
LexActivator SetLicenseKey + ActivateLicense | The SDK's activate(); check() then verifies the signed lease, offline from the saved one. |
| Node-locked activation | A device seat on the license, bound to a device fingerprint; deactivate() frees it. |
| Offline activation (request and response files) | Offline request file and license file (offlineRequest, activateOffline); a deactivation file frees the seat. |
| Floating, and LexFloatClient / on-premise LexFloatServer | Floating licenses: seats in use at the same time, counted per machine, running copy, user, or user per machine, served by your Carcha Seal server. No server at the customer's site in version 1. |
| Feature flags and product metadata | Features listed on the license; the app asks for one by name, for example Seal.hasFeature(state, "pro"). |
Trial (ActivateTrial, keyless) | A per-machine trial policy: each computer gets one trial from a trial key. |
| Named-user and subscription licenses | Subscription = an expiry with renewal; named-user licenses have no equivalent (a floating policy counts concurrent users, not a named list). |
| Metered / usage-based (meter attributes) | No equivalent. Carcha Seal has no usage counters. |
| Users, organizations, resellers | The customer name and email on each license, and the Customers page. No reseller hierarchy or portal. |
| Web API | The admin API; a read-only API key for a dashboard. |
What does not carry over
- Named-user licenses. Carcha Seal binds a key to devices, not to a user login.
- Metered and usage-based licensing. Carcha Seal has no meter attributes, counters or overages.
- An on-premise floating server. LexFloatServer hands out floating licenses on the customer's network; Carcha Seal's on-premises floating is not in version 1.
- Product metadata and resellers. Carcha Seal has two reference fields per license, not arbitrary metadata, and no reseller or organization hierarchy.
- SDKs in other languages. LexActivator covers 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, license policies, whether licenses are node-locked, floating, named-user, subscription or metered, features, 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 Cryptlex 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 Cryptlex license id in a reference.
- Ship an app version that accepts both. Replace the LexActivator calls 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. Export your licenses and users from the Cryptlex Web API, then create Carcha Seal licenses with the same features and dates through the admin API, each with its Cryptlex id as a reference, and send each customer a key.
- Remove the LexActivator 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 Cryptlex products, license policies and feature flags;
- whether your licenses are node-locked, floating, named-user, subscription 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
Cryptlex's pages were checked on 11 November 2026; what Carcha Seal does is from its server code and documentation.