The right tools. Room to grow.

We license on a per-developer basis. All members of a development team using Blazorise need a license. We do not charge runtime, royalty, server, or deployment fees.

Companies, non-profit organizations, government entities, agencies, and other organizations need a commercial license when Blazorise is used for work, internal systems, client work, or commercial products.

Individual developers can use the Community License when they meet the Community License eligibility requirements.

The number of licenses purchased must match the maximum number of concurrent developers contributing changes to the front-end code of projects that use Blazorise.

Example 1. A team has 5 front-end developers and 10 back-end developers on an app that uses Blazorise. Only the front-end developers work on Blazorise-related UI code, so the company purchases 5 licenses.

Example 2. A UI platform team with 2 front-end developers builds an internal component library with Blazorise. Two product teams with 5 and 3 front-end developers use it. The company purchases 10 licenses.

Yes. Freelancers and contractors using Blazorise for client work need a commercial license. Whether the freelancer or client purchases it depends on the project agreement.

No. Customers who only use or receive an application built with Blazorise do not need to purchase a Blazorise license.

An active commercial subscription includes updates, access to licensed packages and private repositories available for your plan, and support during the subscription period.

Yes. You may continue to use the last version available to you in production after the subscription expires. An active subscription is required to keep developing with new versions, receive updates, access support, or access private repositories.

To renew your license, please contact sales.

Renewal is automatic if the license was purchased through our website and paid by credit card. You can cancel your subscription at any time.

Yes. Blazorise Professional and Blazorise Enterprise include dedicated support via our support forum during the subscription period. Response-time targets depend on the selected plan.

A License Key identifies a commercial purchase and is used for license and account management. Never embed it in an application. A ProductToken is generated for application use and applies the functionality, limits, and notices for that license level. It is not considered secret data in the same way as a License Key and may be embedded in Blazor WebAssembly application code.

See the licensing guide for the comparison and ProductToken security guidance.

Yes. Some advanced components have record, row, item, node, or point limits when used without a commercial license. Licensed and trial versions remove those limits.

The full limits are shown in the plan comparison table above.

No. Blazorise Themes and Blazorise Blocks are commercial resources available on the plans shown in the comparison table. Choose Enterprise or Enterprise Plus when your team needs those assets.

To offer a Community License at no cost, we confirm eligibility using LinkedIn. We verify your profile in read-only mode; LinkedIn does not receive information about your Blazorise activity.

Prices are shown in EUR. Charges are made in your local currency when available; otherwise, they are charged in EUR. Local taxes may apply depending on your location.

Yes. You can request a purchase order or contact our sales team for volume pricing.

You can request a refund within 30 days of purchase. Because Professional and Enterprise include source-code access, refunds for these licenses are 60% within 30 days. Renewals and subsequent license purchases are non-refundable.

You can download the latest software license agreement from our license page.