In the browser
Your software opens your website, the customer signs in there and the license goes back to the app. Nothing to copy or paste.
Licensing for plugins and desktop apps
Activate in your app, in the browser or offline. SDKs for JUCE, C++, .NET and Rust, with device self-service for customers.
Three ways to activate
In the browser, inside your plugin, or offline with a file. Offer one, or let customers pick the one that suits the machine they are on.
In your app
Customers activate without leaving your plugin or app, using the screens from the SDK or your own.
Offline
The offline machine makes a device token. The customer uploads it in their account on your website and gets a license token back to load into your software.
SDKs
SDKs for the frameworks audio software is built with
The SDKs carry framework-specific utilities, so most of the work is already done. The JUCE module ships with screens for welcome, trial and license, ready to theme. If you want full control, call the licensing API directly.
Frameworks, with activation screens
JUCEA JUCE 8 module with activation, trial and license screens, ready to theme.
Gorilla EngineAn activation overlay that keeps MIDI and audio off until the plugin is licensed.
ElectronActivation in its own window, or locking the app until it is licensed.
TauriA Tauri 2 plugin with a built-in activation screen.
Languages, with the interface left to you
Trials and self-service
Trials and device management
- Time-limited trials.
- Offer customers a taste of your app by allowing time-limited licenses on demand.
- Trials that never expire.
- Turn on "Trials never expire" for a product and a trial has no end date until you change your mind.
- Extend trials.
- Give one customer more time, or extend every running trial at once.
- Device self-service.
- Customers see which devices are activated and free a seat themselves, in their account on your website.
Signed licenses that work offline
License tokens are RSA-signed, and your software checks them on the machine, so an activated device keeps working without a connection.
Signed license tokens
License tokens your software can verify on its own.
- RSA-signed JWT license tokens
- New accounts get a 3072-bit signing key
- Every SDK verifies 2048 and 3072-bit keys
- Revoke a license or a single device
Working offline
For studios, stages and machines that never go online.
- Offline activations with device and license tokens
- If a store closes, activated devices get offline licenses
- Perpetual licenses keep working for good
- Revoked and expired licenses are still refused
Bring your existing licensing
Sell through Moonbase while licenses come from the system you already run.
- Provision licenses in external systems
- Pre-upload lists of key codes
- Connect your licensing over an HTTP API
- Convert legacy licenses when you switch SDKs
“Integration is straightforward, the platform is reliable, and the team is incredibly responsive. It's become our preferred solution for licensing and ecommerce.”
Joshua Hodge
The Audio Programmer
Frequently asked questions
Browser-based activations, in-app activations and offline file-based activations. You can offer one or several, and the SDKs and API support all three.
Yes. The offline device makes a device token file, the customer uploads it in their account on your website or in your customer portal, and they download a license token to load into your software.
No. You can configure products to provision licenses in an external system, from pre-uploaded lists of key codes to HTTP API integrations.
A license validation on a device already activated returns an offline license for that device, signed with your account's key, so the app keeps working there. Perpetual licenses keep working for good, and subscription licenses until their period ends.
10,000 validations a month free
Try it with your own plugin
Add a product to a free account and activate it from your own build before you sell anything.