License FAQ
- Self-hosted
Answers to common questions about licensing, grace periods, initial setup, and renewal for self-hosted deployments.
General
Do I need a license?
Only self-hosted deployments require a license. Managed deployments do not require a license.
How are the registry token, deployment identifier, license request, and signed license different?
| Value | Source | Purpose |
|---|---|---|
| Container registry token | Provided by Qualytics before installation | Allows the cluster to pull Qualytics container images. |
| Deployment identifier | Provided by Qualytics before installation | Identifies one deployment in the Helm configuration. Add it exactly as provided, do not encode it, and keep the same value for upgrades. Never reuse it for another deployment. |
| License request | Generated by an Admin from the running deployment | Captures the information Qualytics needs to issue an initial or renewed signed license. |
| Signed license | Returned by Qualytics after processing a license request | Activates or renews the deployment license when an Admin applies it in the platform. |
An API token used to call License API endpoints is also separate from these values. It authenticates a Qualytics user with the Admin role.
Where do I find the license information?
Go to Settings > Status tab. The License section is at the bottom of the page. It is only visible to users with the Admin role and only on self-hosted deployments.
What does the warning icon next to the expiration date mean?
A warning icon appears and the expiration date turns orange when the license expires within 30 days. After expiration, the date turns red.
What if I don't create any datastores?
A signed license is not required while no datastores exist. The grace period only begins when the first datastore is created. The deployment identifier is still required to install the platform.
Grace Period
What is the grace period?
New self-hosted deployments without a license have a 31-day grace period. The grace period starts when the first datastore is created (not when the platform is installed). During this period, all features are fully available.
What happens when the grace period expires?
The platform displays a "Grace period expired" error alert. New data operations do not start until you apply a valid signed license.
Does the grace period reset if I delete all datastores?
No. The grace period is based on the first datastore creation date in the deployment's history. Deleting datastores does not reset the counter because the platform tracks the original creation timestamp.
How many days do I have left in the grace period?
The License section displays a countdown showing the remaining days (for example, "15 days remaining") along with the message "A license is required after 31 days of datastore connectivity."
Expiration
What happens when the license expires?
New data operations are restricted. You can still access the platform and manage configurations, users, teams, and quality checks. Sync, Profile, Scan, External Scan, Export, and Materialize operations do not start until a valid signed license is applied.
What is NOT affected by license expiration?
The following remain fully functional with an expired license:
- User management and authentication
- Team and permission management
- Datastore and container configuration
- Quality check creation and editing
- Flow and schedule configuration
- Integrations (notifications, data catalogs)
- API access unrelated to data operations
Do running operations stop when the license expires?
No. Operations that are already running complete normally. New scheduled or manually started data operations do not begin after expiration.
Renewal
How do I get my initial license?
Use the same request and update process described below. The running deployment generates the request after installation, and Qualytics returns the signed license.
How do I renew my license?
- Use the Generate License Request action to create a request code.
- Contact your Qualytics account team or support team to arrange an approved secure transfer method.
- Share the request through that channel, not through ordinary email.
- Apply the signed license returned by Qualytics using the Update License action.
Can I renew via API?
Yes. Use GET /api/license/request to generate a request code and POST /api/license/assign to apply the new key. See the License API page for details.
Can I have multiple licenses?
Yes. You can apply multiple signed licenses over time. The platform always uses the one with the latest expiration date. Old licenses are not deleted.
Validation
What happens if I apply an invalid license key?
The platform displays an error message and the modal stays open so you can correct the signed license and try again. Possible errors:
| Error | Meaning |
|---|---|
| Invalid license signature | The signed license is corrupted or was changed. |
| License has expired | The signed license has already passed its expiration date. |
| Fingerprint mismatch | The signed license does not match this deployment's fingerprint. |
| Invalid license format | The signed license is incomplete or not in the expected format. |
Can I use a license from a different deployment?
No. Each signed license is tied to the deployment fingerprint included in its license request. A signed license that does not match the current deployment returns a fingerprint mismatch error.
What is a deployment fingerprint?
A deployment fingerprint is a snapshot derived from deployment history, including counts of datastores, quality checks, users, and operations. It is embedded in the license request and used to verify the returned signed license. It is not the deployment identifier supplied by Qualytics for Helm configuration.
What is the license request code?
The license request code is an encoded string that contains your deployment's fingerprint. An Admin generates it from the running platform for an initial or renewed signed license. Share it with Qualytics through the approved secure transfer method.