llms.txt
Compare with other sites' llms.txt files →# LicenseManager
> License keys for desktop apps, sold with Stripe. Every Stripe purchase or subscription creates a license key and emails it to the customer. The app validates the key with one HTTPS request that needs no secret, then verifies a signed token offline. SDKs for Electron, Tauri, native macOS apps (Swift), TypeScript, Go, Python, Ruby, Java, C# and PHP. Free up to 100 active licenses, no cut of sales.
- Sign up: https://app.licensemanager.dev/signup
- Pricing: https://licensemanager.dev/pricing
- REST API reference (OpenAPI): https://api.licensemanager.dev/docs
- Electron: https://licensemanager.dev/electron
- Tauri: https://licensemanager.dev/tauri
- macOS (Swift): https://licensemanager.dev/macos
## Docs
- [Plans and billing](https://licensemanager.dev/docs/account/billing): The plans, what each limit counts, how plan changes are billed, and what happens when you go over a limit.
- [Organization and team](https://licensemanager.dev/docs/account/team): Invite your team to your organization, and choose what each member can do with roles.
- [Cancellations](https://licensemanager.dev/docs/analytics/cancellations): How many customers cancel their licenses during their money back guarantee, when, and why.
- [Analytics](https://licensemanager.dev/docs/analytics): How your licenses are used, which versions and platforms your customers run, what you sold, your MRR, and why customers cancel, from the product's dashboard, its releases and each license.
- [Platforms](https://licensemanager.dev/docs/analytics/platforms): The operating systems your customers run your application on, from the platform each machine sends.
- [Release adoption](https://licensemanager.dev/docs/analytics/releases): Which versions of your application your customers run, on the Releases page, the product's dashboard and each license.
- [Revenue](https://licensemanager.dev/docs/analytics/revenue): What you sold, per currency, this month and over time, from the price recorded on each license and the payments of subscriptions.
- [Subscription analytics](https://licensemanager.dev/docs/analytics/subscriptions): Your MRR, active subscriptions, churn and failed renewals, from the Stripe subscriptions of the product's licenses.
- [Usage](https://licensemanager.dev/docs/analytics/usage): How many licenses you have, how many are used, on how many machines, and how often they're activated, for the product and for each license.
- [Authentication](https://licensemanager.dev/docs/api/authentication): Authenticate requests to the LicenseManager API with organization API keys.
- [Errors](https://licensemanager.dev/docs/api/errors): The format of API errors, and every error code with what to do about it.
- [Using the API](https://licensemanager.dev/docs/api): Automate LicenseManager from your backend with its REST API, and the conventions every endpoint follows.
- [Rate limits and quotas](https://licensemanager.dev/docs/api/limits): What counts as an API request, how the quota of your plan works, and what happens when you go over it.
- [Pagination](https://licensemanager.dev/docs/api/pagination): How list endpoints return their items one page at a time, sorted and filtered.
- [Scoped tokens](https://licensemanager.dev/docs/api/scoped-tokens): Short-lived tokens limited to one customer, license or machine, that your backend creates and hands to your customers' browser or app.
- [Customers](https://licensemanager.dev/docs/concepts/customers): A customer is a person or company holding licenses of a product, identified by their email.
- [Events](https://licensemanager.dev/docs/concepts/events): Events are the history of policies, licenses and machines, recording what happened, when, and who did it.
- [Concepts](https://licensemanager.dev/docs/concepts): The building blocks of LicenseManager, what each one represents, and how they fit together.
- [Licenses](https://licensemanager.dev/docs/concepts/licenses): A license is the right of a customer to use a product, unlocked by its key, with its own expiration and limits.
- [Machines](https://licensemanager.dev/docs/concepts/machines): A machine is a device a license is used on, identified by its fingerprint, and counted toward the license's max machines while active.
- [Policies](https://licensemanager.dev/docs/concepts/policies): A policy is an offer of a product. It sets how long its licenses last, on how many machines, offline for how long, which versions they unlock, and how long customers can cancel them for a refund.
- [Products](https://licensemanager.dev/docs/concepts/products): A product is an application you license. It holds its policies, customers, licenses and releases.
- [Releases and version locks](https://licensemanager.dev/docs/concepts/releases): Releases are the versions of a product you ship. Version locks decide which of them each license unlocks.
- [Test mode](https://licensemanager.dev/docs/concepts/test-mode): Test products are sandboxes of your live products, to build and test your integration without touching real customers and licenses.
- [Customizing the portal](https://licensemanager.dev/docs/customer-portal/customizing): Make the customer portal look like your brand, and link it back to your website.
- [Customer portal](https://licensemanager.dev/docs/customer-portal): A page where your customers find their license keys, free their machines, cancel their licenses and manage their subscriptions, without contacting you.
- [Portal links](https://licensemanager.dev/docs/customer-portal/portal-links): Links that sign a customer in to the customer portal, without entering their email, until they expire.
- [Activating a license in Electron](https://licensemanager.dev/docs/electron/activation): Activate the key the customer enters with setLicenseKey, and show the right message for each error.
- [Clock tampering protection in Electron](https://licensemanager.dev/docs/electron/clock-tampering): How the Electron SDK detects a system clock set back to keep using an expired token offline, and what it does about it.
- [Machine fingerprint in Electron](https://licensemanager.dev/docs/electron/fingerprint): How the Electron SDK identifies the computer, why it survives reinstalls, and how to override it.
- [Electron SDK](https://licensemanager.dev/docs/electron): License your Electron app with @licenseman/electron, which validates keys, works offline, renews tokens and detects clock tampering for you.
- [License states in Electron](https://licensemanager.dev/docs/electron/license-states): The nine states of the Electron SDK, what each one means, how it changes, and what your app should show.
- [Working offline in Electron](https://licensemanager.dev/docs/electron/offline): How the Electron SDK falls back on the stored token when LicenseManager can't be reached, retries, and checks versions offline.
- [Electron SDK API reference](https://licensemanager.dev/docs/electron/reference): Every class, method, option and type of @licenseman/electron.
- [Renderer and IPC](https://licensemanager.dev/docs/electron/renderer): Expose the license state and activation to your Electron windows through a preload script and IPC.
- [Installation and setup of the Electron SDK](https://licensemanager.dev/docs/electron/setup): Install @licenseman/electron, create the LicenseManager in the main process, and configure it.
- [Where the Electron SDK stores data](https://licensemanager.dev/docs/electron/storage): What the Electron SDK stores on the customer's computer, where, and how to reset it during development.
- [License validation and renewal in Electron](https://licensemanager.dev/docs/electron/validation): When the Electron SDK validates the key, what it sends and checks, how it renews tokens, and how to tune it.
- [Licensing a desktop app](https://licensemanager.dev/docs/guides/desktop-app): Add license activation to a Mac, Windows or Linux app, from the product setup to offline use, updates and moving to a new computer.
- [Migrating from another license manager](https://licensemanager.dev/docs/guides/migrating): Import your existing customers and license keys with the API, so your customers keep their keys.
- [Selling licenses with Stripe](https://licensemanager.dev/docs/guides/selling-with-stripe): Set up Stripe products and prices, a checkout, the Stripe integration, a money back guarantee and a subscription, to sell licenses end to end.
- [Trial licenses](https://licensemanager.dev/docs/guides/trial-licenses): Offer time-limited trials of your app with a trial policy, and turn them into paid licenses.
- [Introduction](https://licensemanager.dev/docs/): Issue, track and validate software licenses with LicenseManager.
- [Handling validation errors](https://licensemanager.dev/docs/integrate/error-handling): What each error of the key validation means, and what your application should show and do.
- [Machine fingerprints](https://licensemanager.dev/docs/integrate/fingerprinting): Identify each device a license is used on with a stable fingerprint, computed by your application.
- [Integrate in your app](https://licensemanager.dev/docs/integrate): How your application validates license keys, runs offline, and reacts when a license isn't valid.
- [Offline validation](https://licensemanager.dev/docs/integrate/offline-validation): Verify the signed license token in your application, without reaching LicenseManager, and renew it before it expires.
- [Validating license keys](https://licensemanager.dev/docs/integrate/validating-keys): Check a license key from your application, activate the machine, and get a signed license token.
- [Activating a license on macOS](https://licensemanager.dev/docs/macos/activation): Activate the key the customer enters in your Mac app with setLicenseKey, and show the right message for each error.
- [Clock tampering protection on macOS](https://licensemanager.dev/docs/macos/clock-tampering): How the macOS SDK detects a system clock set back to keep using an expired token offline, and what it does about it.
- [App Sandbox, notarization and the Mac App Store](https://licensemanager.dev/docs/macos/distribution): Use the macOS SDK in sandboxed, hardened and notarized apps, and how license keys fit with the Mac App Store.
- [Machine fingerprint on macOS](https://licensemanager.dev/docs/macos/fingerprint): How the macOS SDK identifies the computer, why it survives reinstalls, and how to override it.
- [macOS SDK (Swift)](https://licensemanager.dev/docs/macos): License your native Mac app with the LicenseManager Swift package, which validates keys, works offline, renews tokens and detects clock tampering for you.
- [License states on macOS](https://licensemanager.dev/docs/macos/license-states): The nine states of the macOS SDK, what each one means, how it changes, and what your app should show.
- [Migrating from Electron or Tauri to Swift](https://licensemanager.dev/docs/macos/migrating-from-electron): Move your Mac app from Electron or Tauri to Swift without your customers activating again.
- [Working offline on macOS](https://licensemanager.dev/docs/macos/offline): How the macOS SDK falls back on the stored token when LicenseManager can't be reached, retries, and checks versions offline.
- [macOS SDK API reference](https://licensemanager.dev/docs/macos/reference): Every type, property and method of the LicenseManager Swift package for macOS.
- [Installation and setup of the macOS SDK](https://licensemanager.dev/docs/macos/setup): Add the LicenseManager Swift package to your Mac app, create the LicenseManager, and configure it.
- [Where the macOS SDK stores data](https://licensemanager.dev/docs/macos/storage): What the macOS SDK stores on the customer's computer, where, and how to reset it during development.
- [SwiftUI and AppKit](https://licensemanager.dev/docs/macos/swiftui): Show the license in SwiftUI with LicenseObserver, gate paid features in code, and use the macOS SDK from AppKit apps.
- [License validation and renewal on macOS](https://licensemanager.dev/docs/macos/validation): When the macOS SDK validates the key, what it sends and checks, how it renews tokens, and how to tune it.
- [C# SDK](https://licensemanager.dev/docs/sdks/csharp): Call the LicenseManager API from C# and .NET with the official SDK.
- [Go SDK](https://licensemanager.dev/docs/sdks/go): Call the LicenseManager API from Go with the official SDK.
- [SDKs](https://licensemanager.dev/docs/sdks): Official LicenseManager SDKs for TypeScript, Go, Python, Ruby, Java, C# and PHP, generated from the API's OpenAPI document.
- [Java SDK](https://licensemanager.dev/docs/sdks/java): Call the LicenseManager API from Java, Kotlin or any JVM language with the official SDK.
- [PHP SDK](https://licensemanager.dev/docs/sdks/php): Call the LicenseManager API from PHP with the official SDK.
- [Python SDK](https://licensemanager.dev/docs/sdks/python): Call the LicenseManager API from Python with the official SDK.
- [Ruby SDK](https://licensemanager.dev/docs/sdks/ruby): Call the LicenseManager API from Ruby with the official SDK.
- [TypeScript SDK](https://licensemanager.dev/docs/sdks/typescript): Call the LicenseManager API from TypeScript with the official SDK.
- [Connecting Stripe](https://licensemanager.dev/docs/stripe/connecting): Connect your Stripe account with a restricted API key, and what each permission is for.
- [Stripe integration](https://licensemanager.dev/docs/stripe): Create licenses automatically when customers pay with Stripe Checkout or a Payment Link, once or with a subscription.
- [Payments, renewals and refunds](https://licensemanager.dev/docs/stripe/lifecycle): What happens when a customer pays, how canceled licenses are refunded, and what to do on renewals, refunds made in Stripe and disputes.
- [Mapping prices to policies](https://licensemanager.dev/docs/stripe/price-mappings): Choose which Stripe prices create licenses, of which product, and with which policy.
- [Stripe subscriptions](https://licensemanager.dev/docs/stripe/subscriptions): Sell licenses with Stripe subscriptions, monthly, yearly or any period, valid while the customer pays, with every update included.
- [Activating a license in Tauri](https://licensemanager.dev/docs/tauri/activation): Activate the key the customer enters in your Tauri app with setLicenseKey, and show the right message for each error.
- [Clock tampering protection in Tauri](https://licensemanager.dev/docs/tauri/clock-tampering): How the Tauri SDK detects a system clock set back to keep using an expired token offline, and what it does about it.
- [Machine fingerprint in Tauri](https://licensemanager.dev/docs/tauri/fingerprint): How the Tauri SDK identifies the computer, why it survives reinstalls, and how to override it.
- [Frontend and permissions](https://licensemanager.dev/docs/tauri/frontend): Render the license in your Tauri windows with @licenseman/tauri, and choose what they're allowed to call.
- [Tauri SDK](https://licensemanager.dev/docs/tauri): License your Tauri app with tauri-plugin-licensemanager, which validates keys, works offline, renews tokens and detects clock tampering for you.
- [License states in Tauri](https://licensemanager.dev/docs/tauri/license-states): The nine states of the Tauri SDK, what each one means, how it changes, and what your app should show.
- [Migrating from Electron](https://licensemanager.dev/docs/tauri/migrating-from-electron): Move your app from @licenseman/electron to the Tauri SDK without asking your customers to activate again.
- [Working offline in Tauri](https://licensemanager.dev/docs/tauri/offline): How the Tauri SDK falls back on the stored token when LicenseManager can't be reached, retries, and checks versions offline.
- [Tauri SDK API reference](https://licensemanager.dev/docs/tauri/reference): Every function, command, permission, option and type of tauri-plugin-licensemanager and @licenseman/tauri.
- [Using it from Rust](https://licensemanager.dev/docs/tauri/rust): Reach the LicenseManager from Rust with app.license(), gate your commands, and react to state changes.
- [Installation and setup of the Tauri SDK](https://licensemanager.dev/docs/tauri/setup): Install tauri-plugin-licensemanager and @licenseman/tauri, register the plugin, allow it in your capability, and configure it.
- [Where the Tauri SDK stores data](https://licensemanager.dev/docs/tauri/storage): What the Tauri SDK stores on the customer's computer, where, and how to reset it during development.
- [License validation and renewal in Tauri](https://licensemanager.dev/docs/tauri/validation): When the Tauri SDK validates the key, what it sends and checks, how it renews tokens, and how to tune it.
## Articles
- [Activation licensing service: how software activation works](https://licensemanager.dev/blog/activation-licensing-service): What an activation licensing service does, what happens when a customer activates a key, how limits, deactivation and offline activation work, and how to choose one.
- [How to add license keys to a Tauri app](https://licensemanager.dev/blog/add-license-keys-to-tauri-app): Add license keys to a Tauri 2 app, checked in the Rust core where the webview can't bypass them. Plugin, capability, activation screen and offline checks.
- [How RabbitGUI sells its Electron app with license keys](https://licensemanager.dev/blog/how-rabbitgui-sells-its-electron-app): How RabbitGUI, a desktop client for RabbitMQ, replaced its in-house license server with LicenseManager.dev, migrated existing keys silently and kept offline use, refunds and free updates.
- [Entitlement management system: what your licenses unlock](https://licensemanager.dev/blog/entitlement-management-system): What an entitlement management system is for software vendors, which entitlements to track, and how to keep them in sync with sales and enforce them in your app.
- [Self-service licensing: let customers manage their own licenses](https://licensemanager.dev/blog/self-service-licensing): What self-service licensing is, what a self-service license portal should let customers do, where to stop, and how to cut licensing support emails to almost zero.
- [The best Electron boilerplates](https://licensemanager.dev/blog/best-electron-boilerplate): Electron AppStack, electron-shadcn, Electron React Boilerplate, Electron Forge, electron-vite, Angular Electron, Vutron, Nextron and more. What each Electron starter does well, and who it's for.
- [How to add license keys to an Electron app](https://licensemanager.dev/blog/add-license-keys-to-electron-app): Add license key activation to your Electron app, from the activation window to offline checks. Includes main process, preload and renderer code.
- [How to sell an Electron app](https://licensemanager.dev/blog/how-to-sell-an-electron-app): Everything you need to start selling an Electron app - app stores vs direct sales, payment providers, pricing models, license keys, code signing and updates.
- [How to code sign and notarize an Electron app](https://licensemanager.dev/blog/electron-code-signing): Sign and notarize your Electron app for macOS, and code sign it for Windows, with electron-builder or Electron Forge. Certificates, entitlements, CI and common errors.
- [Electron auto update, explained](https://licensemanager.dev/blog/electron-auto-update): How auto updates work in Electron, how Electron's autoUpdater compares with electron-updater, where to host updates, and how to roll them out safely.
- [electron-builder vs Electron Forge](https://licensemanager.dev/blog/electron-builder-vs-electron-forge): A practical comparison of electron-builder and Electron Forge - installers, auto updates, code signing, bundlers, configuration and which one fits your app.
- [How to protect your Electron app's source code](https://licensemanager.dev/blog/protect-electron-app-source-code): Anyone can extract an Electron app's asar archive. Here's what actually protects your source code and your license checks - obfuscation, V8 bytecode, fuses and integrity checks