Start free trial

Moving from LicenseSpring to Carcha Seal

This guide maps LicenseSpring's concepts to Carcha Seal for vendors of desktop apps, says plainly what has no equivalent, and sets out a migration that keeps existing customers working while they move. It follows LicenseSpring's own documentation. LicenseSpring is a licensing system with no application wrapper, so unlike a Sentinel move there is nothing to unwrap: the work is the license records and the SDK call.

Reading time
4 min
Updated
11 November 2026
Sections
4
On this page
Concept mapWhat does not carry overA migration in stepsFree migration assessment

Concept map

LicenseSpringCarcha Seal
Product and product codeProduct; its code is what the SDK sends.
License policyPolicy: seats, expiry or perpetual, end of updates, features, check-in and offline grace.
Key-based licenseA license key, shown once when issued. Carcha Seal keeps no copy; a lost key is replaced.
User-based license (LicenseUser, email and password)No equivalent. Carcha Seal licenses are key plus device, with no end-user login.
activateLicense, checkLicense, deactivateactivate(), check() (offline from the saved lease) and deactivate().
Hardware ID (HardwareIdStrategy)A device fingerprint: a SHA-256 hash of the operating system's machine ID and the product code; the raw ID never leaves the computer.
License features (checkLicenseFeature)Features listed on the license; the app asks for one by name, for example Seal.hasFeature(state, "pro").
Offline activation (activateLicenseOffline, license file, air-gap deactivation)Offline request file and license file (offlineRequest, activateOffline); a deactivation file frees the seat.
Floating (register, release, floatingInUse)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.
Consumption / metered (increaseConsumption)No equivalent. Carcha Seal has no metered licensing yet.
Order and generated keys (Management API)A license created by the admin API, or by a connected Lemon Squeezy store on each sale.
End-user portal, reseller portalNo equivalent. Customers move a seat to a new computer from the app or the offline page; you manage licenses in the console.

What does not carry over

  • User-based licenses. LicenseSpring can tie a license to a user who signs in with an email and password. Carcha Seal binds a key to devices, not to a login; a floating policy counting by user limits concurrent users but is not a named-user list.
  • Metered and consumption-based licensing. Carcha Seal has no usage counters or overages.
  • A floating server at the customer's site, and borrowing. Carcha Seal's floating seats come from your server; an on-premises floating server and taking a seat offline for days are not in version 1.
  • The end-user and reseller portals. There is no white-label customer portal or distributor portal.
  • SDKs in other languages. LicenseSpring covers many languages; Carcha Seal's SDKs today are Electron and Node.js, C++, .NET and Python. If your app is in Java, Go, Swift or for mobile, there is no SDK yet.

A migration in steps

  1. List what you use. Products, license policies, whether licenses are key-based or user-based, features, whether any customers work offline or use floating, which language your app is in, and how orders create licenses.
  2. 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 LicenseSpring features.
  3. 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 LicenseSpring order or license id in a reference.
  4. Ship an app version that accepts both. Swap the LicenseSpring SDK for the Carcha Seal SDK where your language is covered, or run both and check Carcha Seal first and fall back to LicenseSpring's checkLicense, so customers move when they enter a new key.
  5. Re-issue keys for existing customers. Export your licenses, customers and orders from the LicenseSpring Management API, then create Carcha Seal licenses with the same features and dates through the admin API, each with its LicenseSpring id as a reference, and send each customer a key.
  6. Remove the LicenseSpring 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 LicenseSpring products, license policies and features;
  • whether your licenses are key-based or user-based, and whether any are metered or floating;
  • 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

LicenseSpring's pages were checked on 11 November 2026; what Carcha Seal does is 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.