License
QALITA Platform is a proprietary software developed by QALITA.
How license validation works​
A license is delivered as a set of registry credentials (a username and a key). The platform validates the license by authenticating against the QALITA license registry rather than by decoding an offline token.
At every backend start (and when a new partner is created), the backend performs an authenticated request to the registry:
GET https://registry.qalita.io/v2/ (HTTP Basic auth)
The result determines the license state:
| Registry response | License state | Effect |
|---|---|---|
200 (credentials accepted) | Valid | The validity window is refreshed to a fixed 90 days from now. |
401 / 403 (refused) | Invalid | Not renewed. The platform stays usable until the stored expiration date, then expires. |
Network error / 5xx | Unreachable | Treated as a transient outage — not an expiration. The stored license is kept. |
The validity window acts as a sliding grace period: as long as the backend successfully re-authenticates at least once within the 90-day window, the platform keeps working — including across short registry outages. Beyond that window without a successful check, the license expires.
When no credentials are configured (e.g. local development), the platform runs in Free Trial mode and never contacts the registry.
Configuration​
| Variable | Default | Description |
|---|---|---|
QALITA_LICENSE_USER | none | Registry username (license holder) |
QALITA_LICENSE_KEY | none | Registry password (license key) |
QALITA_LICENSE_REGISTRY_URL | https://registry.qalita.io | License registry used for validation |
You can check the current status from the user interface under Settings >
License. To renew, update QALITA_LICENSE_USER / QALITA_LICENSE_KEY and
restart the backend.