Commercial licensing

The licence is noncommercial; this is what a company needs instead.

keycloak-doctor is released under the PolyForm Noncommercial License 1.0.0. That license lets you use, modify, and distribute the software for any noncommercial purpose at no cost. Any commercial use needs a separate commercial license from the author — this page explains how to get one.

You do NOT need a commercial license for#

Noncommercial use is already granted by the PolyForm Noncommercial License, including:

• Personal use, hobby projects, learning, and experimentation.
• Research and teaching at educational institutions.
• Use by charities, nonprofits, public research, public safety/health, environmental, or government organizations — regardless of funding.
• Evaluating keycloak-doctor before deciding whether to buy a commercial license.

If you are unsure whether your use is covered, ask (see below) — asking is free.

You DO need a commercial license for#

The short version: if a for-profit company benefits from keycloak-doctor running, that is commercial use — including when it only ever audits your own realms and no customer ever sees the report. "Commercial" here is about the purpose the software serves, not about whether you redistribute it, so "we only use it internally" does not make it noncommercial. That is the single point most people get wrong, so it is stated plainly rather than left to be inferred.

Roughly, any use "with an anticipated commercial application", such as:

• Auditing the Keycloak realms of a for-profit company's own products or operations, including in its CI.
• Offering keycloak-doctor (or a service built on it) to customers — a hosted product, a managed service, or a security assessment you invoice.
• Bundling or redistributing keycloak-doctor inside a commercial product, appliance, or consultancy deliverable.

This list is illustrative, not exhaustive. The authoritative terms are in LICENSE.

What a commercial license gives you#

A commercial license removes the noncommercial restriction for the agreed scope. Terms are tailored per agreement and typically cover:

• The organization and use case in scope.
• The versions covered and how long.
• Support and update expectations, if any.

How to request one#

Open the conversation by email or a GitHub issue — whichever you prefer:

• Email: allannava95@gmail.com (subject: keycloak-doctor commercial license)
• GitHub: open an issue at https://github.com/Allan-Nava/keycloak-doctor/issues titled Commercial license request (no confidential details in a public issue — just ask to be contacted).

To speed things up, include:

1. Your company / organization name and country.
2. A short description of how you intend to use keycloak-doctor.
3. Rough scale (e.g. how many realms and environments are audited, or whether it is embedded in a product or service you sell).
4. Which version(s) you plan to run.

You will get a reply with scope and pricing. Pricing is quoted per request; there is no public price list yet.

Notes#

• This document is a summary for convenience. If anything here seems to conflict with LICENSE, the LICENSE text governs.
• This is not legal advice. For a binding interpretation of how the license applies to your situation, consult your own counsel.