How do I get, extend, or apply a Hub or runtime license?

Q: How do I get, extend, or apply a Hub or runtime license?

Hub licenses are per tenant and SKU. Apply SaaS, Light, or Enterprise keys in the right portal, and treat expired runtime keys as the cause of license 500s.

Licenses are issued per tenant / product SKU, not as a generic file you invent locally. OL Hub SaaS and deployment is the control plane for tenant licensing.

Where to apply it

Hub SaaS — the tenant is licensed in the SaaS license portal. Runtime HTTP 500s with “license exceeded” or “time limit” usually mean the runtime key expired or does not match that environment.
Hub Light / Enterprise (on-prem) — apply the license in the Hub UI (or the documented Light license path). “Can’t update license” in the UI usually needs an admin role on that Hub.
CLI — CLI operations that talk to Hub need a valid Hub session or API key and a licensed Hub. A valid CLI install is not a substitute for a Hub license.
NFR / trial / partner renewals — request an extension from OpenLegacy. Do not reuse last year’s key.

If generation of a production license looks wrong (wrong SKU, Hub Light vs full), stop and have the license re-issued rather than pasting it into production.