License Key Setup — Blazor Power Tools

License Activation

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

Obtain Your License Key

Your license key is available in two places:

The confirmation email sent after purchase
Your account dashboard at My Account

The key is a string in the format: BPT-XXXX-XXXX-XXXX-XXXX

Create the License File

Create a file named bpt-license.txt in the root of your Blazor project (next to your .csproj file):

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

The file should contain only your license key:

BPT-XXXX-XXXX-XXXX-XXXX

Alternative: Use an Environment Variable

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

# Linux / macOS
export BPT_LICENSE="BPT-XXXX-XXXX-XXXX-XXXX"

# Windows PowerShell
$env:BPT_LICENSE = "BPT-XXXX-XXXX-XXXX-XXXX"

# Windows CMD
set BPT_LICENSE=BPT-XXXX-XXXX-XXXX-XXXX

The environment variable takes precedence over the license file.

Additional Configuration Options

Point to a license file via environment variable:

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

# Linux / macOS
export BPT_LICENSE_PATH="/etc/bpt/bpt-license.txt"

# Windows PowerShell
$env:BPT_LICENSE_PATH = "C:\keys\bpt-license.txt"

User-level license file:

Place the license file at ~/.bpt/bpt-license.txt (Linux/macOS) or %USERPROFILE%\.bpt\bpt-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["BlazorPowerTools:LicenseKey"];
    // Or: options.LicenseFilePath = "/path/to/bpt-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.

Verify Activation

Run your app. If the license is valid, BPT components will render without watermarks or limitations. You can verify activation in the developer console — look for:

[BPT] License activated. All components unlocked.

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 not found" at runtime Make sure the bpt-license.txt file is in the project root and included in the build output, or that the BPT_LICENSE environment variable is set in the process running your app.

"License expired" 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 in the format BPT-XXXX-XXXX-XXXX-XXXX. Check for leading/trailing whitespace or invisible characters that may have been copied from email.

Back to Getting Started

Continue with the full setup guide.

Need Help?

Contact support if you have license issues.

Set Up Your License Key