Blazorise licensing
Understand the difference between a License Key and ProductToken before configuring an application.
License Key and ProductToken
A License Key identifies a purchased Blazorise license. Use it only for license and account management. Never embed a License Key in an application.
A ProductToken is generated for use by an application. Blazorise validates it to apply the licensed functionality, limits, and notices for that application. A valid commercial ProductToken removes licensing warnings and the limitations that apply without a valid token. Unlike a License Key, a ProductToken is not considered secret data. ProductTokens have limited validity and can change over time.
| License Key | ProductToken | |
|---|---|---|
| Purpose | Identifies the purchased Blazorise license | Enables licensed functionality in applications |
| Used in application | No | Yes |
| Should be committed to source control | No | Avoid when practical |
| Can be exposed to the browser in Blazor WebAssembly | No | Potentially yes |
| Recommended storage | Blazorise account and secure internal records | Server configuration; application code or build output for WebAssembly |
ProductToken or place a License Key in application code, configuration, deployment files, or client-side assets.See Protecting your ProductToken for storage, local development, production, CI/CD, and Blazor WebAssembly guidance.
License behavior
A valid commercial ProductToken removes licensing warnings and licensed component limits. A Community ProductToken applies the Community license and displays a compact Community License button in the bottom-right corner. Select the button to open the full license notice.
A missing or invalid ProductToken is treated as unlicensed and displays the applicable warning and component limits. An expired token displays the applicable expired-license notice.
Get a ProductToken
Follow the ProductToken configuration guide to get a ProductToken from your Blazorise account and configure your application.