Audio plugins (VST3, AU, AAX)
A signed key for every order, checked inside the plugin at launch with no connection needed. Seats are bound to a machine, and the JUCE kit ships the activation screen and a free demo period.
Use cases
Every paid order gets a signed, device-locked key. What your software does with it depends on what you sell. These are the shapes we see most, and you can mix them.
Offline checks the signed key on the customer's machine, no connection needed. Online asks the API on each use, so revocation is instant.
Where licensing started, and where the offline machinery matters most.
A signed key for every order, checked inside the plugin at launch with no connection needed. Seats are bound to a machine, and the JUCE kit ships the activation screen and a free demo period.
Sell instruments, loops and presets with a key that unlocks the installer or library loader. Cap the devices per customer, and let buyers move to a new computer without a support email.
Editors, DJ tools and notation apps activate once, run without internet, and renew quietly in the background while the customer is online.
Offer a free demo period or a time-limited trial, then let a paid key take over. Revoke a beta key the day the beta ends.
One signed token, verified with whatever your platform already ships.
Electron, native macOS and Windows .NET apps verify the same token with the platform's own crypto. The same check has been run from Swift, C#, Kotlin, Rust, Go, Python and PHP clients.
Per-seat keys for command-line tools, IDE extensions and build plugins. Validate online in CI, or offline on a laptop on a plane.
Online games check on login and can limit concurrent sessions. Offline games verify a signed file. Works from C# and any language with an HTTP client.
Extensions for hosts that run Python or JavaScript can verify the token in a few lines. The format is open and documented.
Checked on your server, so a canceled customer is cut off at the next request.
A premium plugin asks the API whether a key is valid. Count each site as a seat, so one key cannot run on an unlimited number of sites. Keys are issued when a WooCommerce order is paid.
Your backend checks the license on every use. Revocation is instant, and you can limit concurrent sessions and set usage quotas per plan.
Issue a key per customer, check it at your gateway, and decide what each plan may call. Pro adds a merchant API and signed webhooks for your own systems.
Monthly or yearly licenses that renew with each payment and stop when a subscription is canceled or a charge is refunded.
Keep private downloads, member areas and early-access builds behind a key that your server checks, so a refund closes the door.
The commercial shapes your catalog actually has.
One purchase unlocks several products. The customer gets one key and every product in the bundle activates with it.
Sell a license with several seats, and let your support team release a seat or grant another activation in one click.
Keep the keys your customers already hold. Existing licenses can be adopted or imported, so nobody has to re-buy or re-activate.
If you can make an HTTP request, you can check a license. The REST API works from any language, and the token format is open, so a verifier is a short piece of code.
Not sure which fits?
Tell us what you sell. We can integrate the license manager into your product for you, and harden it against cracking and abuse.