Licensing

ProAuth includes built-in license validation to ensure compliance with your software license agreement. The license system validates your deployment at runtime and provides clear feedback about your license status.

The commercial terms below summarize the ProAuth Software Licence Agreement, version 3.0-2026-09-28. Your accepted order, agreement and incorporated schedules determine your entitlements. The new agreement does not automatically replace an existing customer's contract.

Production and Non-Production Environments

One production license covers one installed ProAuth system, normally within one Kubernetes cluster. You can scale that installation with unlimited runtime instances and replicas. Each separate production installation needs its own license, including separate installations in the same cluster. Multiple tenants within one installation do not by themselves create additional deployments.

Each production license includes a development/test license with the same purchased features and unlimited associated non-production environments, including development, QA, staging and automated testing. Those environments must not serve live business operations.

Application-registration, user-store and federated-provider limits apply separately within each non-production environment. Test configurations do not consume production allowances. For example, an allowance of 10 application registrations provides 10 for production and 10 independently for each development/test environment. Replicas of one installation share its allowance; they do not create additional allowances. Your order specifies the actual limits and counting rules.

The contracting customer and its subsidiaries expressly named in the order may share the licensed installation. A separate production installation still requires another license.

Disaster Recovery and Migration

Backup copies and passive disaster-recovery installations are included. A recovery installation may replace an unavailable primary installation. Temporary overlap for failover, failback or migration is included for up to 30 days per event; request a documented extension if needed. Independent ongoing production installations require additional licenses.

Overview

When ProAuth starts, it validates the installed license file against several criteria:

• License validity: Ensures the license file is valid and properly signed
• Version compatibility: Verifies your ProAuth version is covered by the license
• Expiration status: Checks subscription and software upgrade expiration dates
• Feature entitlements: Validates access to licensed features and modules

License Types

ProAuth supports different license types, each with specific characteristics:

License Type	Description
Subscription	Time-limited license that expires on a specific date
Perpetual	Indefinite use of covered versions, subject to the agreement
Perpetual with Upgrades	Perpetual license with time-limited upgrade rights

Subscription Licenses

Subscription licenses permit use during the active term and include generally released updates for the purchased edition. On expiry without renewal, the right to use ProAuth ends, including associated development/test use. Arrange renewal or migration before expiry. Technical operation or warning messages do not grant an additional grace period or extend your contractual entitlement.

Perpetual Licenses

A fully paid perpetual license permits indefinite use of covered versions within the purchased deployment scope, subject to the agreement's termination provisions. The initial purchase includes 12 months of upgrade coverage unless the order provides a longer period.

Perpetual with Upgrade Rights

This license type combines perpetual usage rights with time-limited upgrade eligibility. Covered versions include the delivered version and generally released versions of the purchased edition made available during included or paid coverage. After coverage expires, you can continue using those covered versions, including in associated non-production environments.

Later ordinary fixes and feature releases require renewed upgrade coverage or a separate purchase. Expiry of upgrade coverage does not remove security remedies required by applicable law.

Renewal and Payment

Unless the order states otherwise, subscriptions have an initial 12-month term and renew for successive 12-month terms. Either party may decline renewal with at least 30 days' notice. Renewal price increases require at least 60 days' notice; a later notice does not increase the price of that renewal unless the customer expressly agrees.

Optional perpetual upgrade coverage and separate support renew automatically only if the order expressly selects that arrangement. Perpetual use rights do not require renewal. The standard invoice payment period is 30 days.

Support and Security Updates

Basic Support for supported versions is included during an active subscription or perpetual upgrade coverage. Additional support services depend on the purchased plan. Support response commitments are distinct from resolution times and do not guarantee availability of a self-hosted deployment.

After perpetual upgrade coverage ends, security maintenance continues only to the extent and for the period required by applicable mandatory law or expressly agreed in the order. Where the Cyber Resilience Act's support-period requirements apply to a perpetual supply, the agreement specifies five years from delivery of that supply, or longer where mandatory law requires. The order or lifecycle schedule records the applicable dates separately from commercial upgrade coverage.

Release-maintenance dates may follow .NET and other dependency lifecycles. You may need to move to a supported successor release to receive further fixes. Where legally permitted, a qualifying newer version can provide a required security remedy without an upgrade fee. For a perpetual license, that replacement retains perpetual use within the existing deployment scope. This does not promise maintenance of every historical version or entitlement to every optional new feature. See section 7 of the agreement and your lifecycle schedule for the conditions.

License Validation

ProAuth performs license validation:

• At startup: Initial validation when ProAuth starts
• Periodically: Background validation at configurable intervals (default: every 4 hours)

Validation Behavior

The license validation runs as a background job and checks the current license status. If issues are detected, ProAuth logs appropriate warnings or errors:

License status: Valid subscription license, expires on 2026-12-31

Or in case of issues:

License validation warning: License expires in 30 days

Monitoring License Status

API Endpoint

License and product information can be retrieved via the Management API:

GET /api/management/v2/productinformation

This endpoint returns:

• Product version information
• License status and expiration dates
• Licensed features and modules
• Allowed host configurations

Logs

License-related events are logged with the following categories:

• ProAuth.Common.Licensing.ProAuthLicenseManager - License validation events
• ProAuth.JobQueue - Background license check job execution

Configure your log aggregation to monitor these categories for license-related warnings.

Recommended Alerts

Consider setting up alerts for the following log patterns:

Pattern	Severity	Action
License expires in	Warning	Plan license renewal
License has expired	Error	Renew license immediately
License validation failed	Error	Check license file installation
No valid license found	Critical	Install valid license

Troubleshooting

Common Issues

License file not found

Ensure the license file is properly mounted in the container at the configured path. Check your Helm values or Docker configuration.

Version mismatch

If you see version compatibility warnings, verify that your license covers the installed ProAuth version. Ordinary upgrades may require active upgrade coverage. For a security replacement supplied under section 7 of the agreement, request any necessary replacement key; mandatory security remedies are not conditioned on purchasing optional upgrade coverage.

Expired license

For an expired subscription, contact your ProAuth representative about renewal and stop using the expired entitlement. There is no automatic contractual grace period. Expired upgrade coverage on a perpetual license does not terminate the right to use covered versions; if a key incorrectly restricts a covered version, contact support.

Verifying License Installation

Use the ProAuth CLI to verify your license installation:

proauth license verify --license-file <path-to-license>

This command displays detailed information about the license including:

• License holder information
• Valid versions
• Expiration dates
• Licensed features

See Also

• Prerequisites - Resource access and license credentials
• Monitoring - Setting up observability for license events
• Software License Agreement - License terms and conditions