What the portal issues
- signed `license.json` material for the active entitlement
- a matching `cerb1:` string for copy/paste or automation workflows
- customer-visible entitlement metadata such as plan, limits, and expiry
Licensing docs
Understand how Nyalma issues Cerberus licenses without becoming a runtime control plane.
The portal handles entitlement visibility and license delivery. Cerberus remains responsible for local verification of issued `license.json` and `cerb1:` material after you import it into your environment.
What Cerberus verifies locally
- signature validity and the issued license payload
- named-user, team, deployment, and expiry limits expressed in the license
- continued operation of an already issued license without a live portal dependency
When to reissue
- after an entitlement change such as a commercial upgrade or support-backed fulfillment
- when you need a fresh artifact after administrative renewal or rollout planning
- when your internal release process requires re-approved license material for deployment
Commercial meaning by plan
- Community is a real Cerberus evaluation path with smaller limits.
- Professional raises named-user and team capacity for regular operational use.
- Enterprise allows tailored commercial packaging and negotiated rollout support.