Set Up Your License Key

Activate your Blazor Power Tools license to unlock all components and receive updates.

License Activation

After purchasing a Blazor Power Tools subscription, you'll receive a license key via email. This key unlocks the full component library.

1. Obtain Your License Key

Your license key is available in two places:

• The confirmation email sent after purchase
• Your account dashboard at My Account on isabyte.debiansrv.ddns.net

The key is a signed token — two Base64 segments joined by a dot, several hundred characters long. It looks like this (truncated):

eyJMaWNlbnNlSWQiOiJmNGE3….rV2sK9dQxM…

2. Create the License File

Create a file named pt-license.txt in the root of your Blazor project (next to your .csproj file). At start-up the package looks for it in the app's working directory and then in each parent directory, so a file in the project or solution folder is found when you run the app from there:

MyBlazorApp/
  MyBlazorApp.csproj
  pt-license.txt        <-- place it here
  Program.cs
  ...

The file should contain only your license key (the full token, one line):

eyJMaWNlbnNlSWQiOiJmNGE3….rV2sK9dQxM…

3. Alternative: Use an Environment Variable

If you prefer not to use a file (for example, in CI/CD environments), set the ISABYTE_PT_LICENSE environment variable instead:

# Linux / macOS
export ISABYTE_PT_LICENSE="eyJMaWNlbnNlSWQiOiJmNGE3….rV2sK9dQxM…"

# Windows PowerShell
$env:ISABYTE_PT_LICENSE = "eyJMaWNlbnNlSWQiOiJmNGE3….rV2sK9dQxM…"

# Windows CMD
set ISABYTE_PT_LICENSE=eyJMaWNlbnNlSWQiOiJmNGE3….rV2sK9dQxM…

The environment variable takes precedence over the license file.

4. Additional Configuration Options

Point to a license file via environment variable:

Set the ISABYTE_PT_LICENSE_PATH environment variable to the full path of your license file:

# Linux / macOS
export ISABYTE_PT_LICENSE_PATH="/etc/isabyte/pt-license.txt"

# Windows PowerShell
$env:ISABYTE_PT_LICENSE_PATH = "C:\keys\pt-license.txt"

User-level license file:

Place the license file at ~/.isabyte/pt-license.txt (Linux/macOS) or %USERPROFILE%\.isabyte\pt-license.txt (Windows) for a user-level default that applies to all projects.

Programmatic configuration:

You can also pass the key or file path directly in Program.cs:

// Pass key directly
builder.Services.AddBlazorPowerTools("your-license-key-here");

// Or configure via options
builder.Services.AddBlazorPowerTools(options =>
{
    options.LicenseKey = builder.Configuration["Isabyte.PowerTools.Blazor:LicenseKey"];
    // Or: options.LicenseFilePath = "/path/to/pt-license.txt";
});

Tip — The programmatic approach via AddBlazorPowerTools(options => ...) lets you integrate with any configuration source — appsettings.json, Azure Key Vault, AWS Secrets Manager, or environment variables — using standard ASP.NET Core configuration binding.

Security — Do not commit license keys to source control. Use User Secrets during development and environment variables or a secret manager in production.

5. Verify Activation

Run your app. AddBlazorPowerTools validates the key at start-up: if it is missing or invalid, it throws an InvalidOperationException that names the reason, and the app does not start. With a valid key, the package writes this line to the console output of the process that validated the key:

[Isabyte.PowerTools.Blazor] License activated — <edition> (<type>)

Where that output appears depends on the hosting model:

• Blazor Server or a Blazor Web App (AddBlazorPowerTools in the server's Program.cs): in the server's console output — the terminal running dotnet run, the Visual Studio output window, or your host's or container's logs. It never reaches the browser.
• Standalone Blazor WebAssembly (AddBlazorPowerToolsClient(licenseKey)): in the browser's developer console (F12), because the key is validated in the browser.

In a Web App with a WebAssembly client, the client's parameterless AddBlazorPowerToolsClient() validates nothing and logs a "host-trust mode" line in the browser instead; the activation line is in the server output.

License Types

Developer License — Licensed per developer. Each developer on your team needs their own license key. The key is tied to the developer, not the machine — use it on as many devices as you need.

CI/CD & Production — Your developer license includes rights to use BPT in CI/CD pipelines and production deployments. No separate server license is required. Set the license key as a CI secret.

Troubleshooting

"license key not found" at start-up — Make sure pt-license.txt is in the app's working directory or one of its parent directories (a published app runs from its publish folder), or that the ISABYTE_PT_LICENSE environment variable is set in the process running your app.

"License expired on …" — Your subscription may have lapsed. Renew at Pricing or contact Support if you believe this is an error.

"Invalid license key format" — The key must be the full signed token described in step 1. Check for leading/trailing whitespace or invisible characters that may have been copied from email.

Next

• Back to Getting Started — Continue with the full setup guide.
• Need Help? — Contact support if you have license issues.