License keys
How keys are generated, where customers find them, and what to do when one leaks.
Every subscription carries exactly one license key, generated when the subscription is created. The key is unique across the whole install and never changes for the life of the subscription.
Format#
A key is a configurable prefix followed by random characters. Both are set in Settings → License keys:
| Setting | Default | Range |
|---|---|---|
| Prefix | MP |
Up to 10 characters |
| Total length | 32 | 8 to 64 |
A prefix is worth setting to something recognisable. When a customer pastes a key into a support ticket, you can tell at a glance whether it is one of yours.
Changing either setting affects only keys generated afterwards. Existing keys keep working unchanged.
Where customers find their key#
In the customer panel, on the subscription’s page, with a copy button. It is also included in the welcome email.
Where you find a key#
Admin → Subscriptions is searchable by key, by customer, and by product — enough to answer “is this key real and what is it entitled to?” from a support ticket in one lookup.
A leaked key#
There is no reissue button, and that is deliberate: rotating a key breaks every legitimate installation using it. Deal with a leak by acting on the subscription instead.
- Look at the activated domains. A key being used far beyond its limit shows up there immediately.
- Deactivate the domains that should not be there. The slots free up at once.
- If the abuse continues, suspend the subscription. Verification then fails everywhere the key is used.
What a key does not do#
A key does not encrypt or protect your code. It answers one question over HTTP — is this installation entitled? — and gives you a place to see where your software is running and to cut off abuse. Treat it as accounting and access control, not as copy protection.