Getting a Radiator License

Getting a Radiator License

Radiator requires a valid license for its server services and RadiatorDB. Radiator Software offers evaluation licenses for testing and subscription or perpetual licenses for production use.

License types

Radiator supports these license types:

• Time-limited evaluation: Intended for testing during a fixed period and valid until its runtime end date.
• Request-limited evaluation: Intended for testing with a fixed allowance of counted requests per protocol during each Radiator process boot.
• Subscription: Valid until its runtime end date and for Radiator software built on or before its end-of-support build date.
• Perpetual: Has no runtime end date and is valid for Radiator software built on or before its end-of-support build date.

The end-of-support build date is both the end of support and the newest Radiator software build that can use the license. Software built after that date requires a newer license.

Licensed services

A license states which Radiator servers are available (RADIUS, TACACS+, etc.) and whether RadiatorDB is included. RadiatorDB operations do not add to the server request count.

The Licenses page in the Management UI shows the effective status of each service across all active licenses. It also shows expiration and per-boot request usage when a request limit applies.

Server service flags apply to incoming servers. They do not restrict backend connections. For example, the RADIUS service flag controls incoming RADIUS servers, not RADIUS backends used for proxying.

Request-limited evaluation licenses

The Requests value sets the maximum number of counted incoming requests for each licensed protocol during one Radiator process boot. All configured servers for the same protocol share that protocol's allowance.

When multiple active licenses include the same protocol, Radiator uses the highest request allowance for that protocol. If any active license permits unlimited requests for the protocol, the effective allowance is unlimited. Licenses that do not include the protocol do not affect its allowance.

The count starts at zero when Radiator starts. Reloading or replacing a license does not reset it. Management UI and Management API requests, RadiatorDB operations, backend requests, and RADIUS Status-Server traffic do not count. A TACACS+ continuation belonging to an already-counted request does not count again.

When a protocol's allowance is exhausted, Radiator rejects further counted requests for that protocol and logs Request rejected because licensed maximum request count was reached.

Obtain, renew, or replace a license

Send an email to sales@radiatorsoftware.com to obtain or renew a license, or to request a replacement for a missing license.

For a new license, include whether you need a testing or production license, which server services and RadiatorDB access you need, and the required requests per protocol per Radiator process boot for a request-limited evaluation. See the Radiator product page for an overview of the product. For a replacement license, include your organization name and any order reference you have.

Install a license

Once you receive the license file, upload it using the Licenses page in the Management UI (click Licenses in the left sidebar).

You can also install license files through configuration. See the license configuration reference for directory and single-file configuration behavior.

See Also

• license configuration reference
• request limit rejection log message