One hub that issues and checks every licence
What the Hub controls
Everything a licence can do, and a record of each time it did it.
Issuing on payment
A completed order issues a key tied to the seat count of the site pack bought. Nobody on your team has to do a thing.
Remote validation
Installed sites check in and the Hub answers. Each request is signed, and it is refused if the signature or the timestamp does not match.
Seat enforcement
Each activation counts against the site pack. Deactivating a site frees the seat at once, so it is ready for another domain.
Block and revoke
A chargeback or a breach can suspend a key without deleting the record you need to explain why it happened.
Upgrades without downtime
Moving up to more sites issues a new key. The old key keeps working for seven more days, so customers have time to switch over.
Rotatable signing secret
The shared secret signs every request and no endpoint ever sends it back. You can rotate it from the Hub settings whenever you need to.
How the Master Hub signs every request
Every Hub request is signed with an HMAC-SHA256 signature over the method, the route, a timestamp and a hash of the body. A replayed or changed request fails the check. The shared secret never travels in the request.
Built to fail open
If the Hub cannot be reached, installed sites keep working. Licensing should never take a customer's site offline just because one check timed out. Your buyers keep their sites running while the Hub comes back.
Seats that follow your customers
Each activation counts against the site pack. When a customer deactivates a site, the seat is free at once for another domain. Moving a site is a quick deactivate and activate, not a support request.
A chargeback or a breach can block a key without deleting its record. The history stays, so you can still explain what happened and when.
An audit trail that answers questions
Create, block, revoke and sync are all logged with the person and the time. When a customer asks why a key stopped working, the history gives the answer. That is how you keep a clear licence history for every key.
Your own code can do the same work through the signed licenses API. It is the API the dashboard itself calls.
Upgrades and the signing secret
When a customer moves up to a larger site pack, the Master Hub issues a new key. The old key keeps working for seven more days, so there is time to switch every site over without downtime.
The shared secret that signs each request can be rotated from the Hub settings whenever you need to. No endpoint ever sends it back, so it never shows up in an answer from the Hub.
Key takeaways
- The Master Hub issues a key as soon as an order is paid.
- Signed requests stop replayed or changed calls.
- Sites keep working if the Hub cannot be reached.
- Every action on a key is logged with who and when.
Frequently asked questions
What happens if the Hub is down?
Installed sites keep running. Validation fails open, so the master hub never switches off a working site.
Can a customer move a licence between domains?
Yes. Deactivating the licence on the old domain frees the seat at once for the new one.
Is the licence secret ever exposed?
No. It is used to sign requests and is never included in any answer the Hub sends.
Is the master hub included in all tiers?
Yes. The Master Hub is part of the platform, not a paid add-on. Every site pack includes it.
Licensing included on every tier
The Master Hub is part of the platform, not a paid add-on.