Skip to content

License FAQ

Answers to common questions about licensing, grace periods, 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.

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 when the license is expiring within 30 days. The expiration date turns red as a visual reminder to start the renewal process.

What if I don't create any datastores?

No license is required. The grace period only begins when the first datastore is created. A deployment with no datastores can run indefinitely without a license.

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 with the message "Dataplane operations are restricted until a valid license is applied." You must apply a valid license to restore full functionality.

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 — 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 (e.g., "15 days remaining") along with the message "A license is required after 31 days of datastore connectivity."

Expiration

What happens when the license expires?

Dataplane operations are restricted. You can still access the platform, manage configurations, users, teams, and quality checks — but Sync, Profile, Scan, External Scan, Export, and Materialize operations will not run until a valid 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 (except dataplane operations)

Do running operations stop when the license expires?

No. Operations that are already running will complete normally. The license is only checked when the dataplane initializes — not on each individual operation. Scheduled operations that trigger after expiration will not execute.

Renewal

How do I renew my license?

  1. Use the Generate License Request action to create a request code.
  2. Send the code to the Qualytics support team.
  3. Once you receive the new key, apply it 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 license keys over time. The platform always uses the license 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 key and try again. Possible errors:

Error Meaning
Invalid license signature The key is corrupted or tampered with.
License has expired The key you received has already passed its expiration date.
Fingerprint mismatch The key was generated for a different deployment.
Invalid license format The key is not in the expected format (e.g., incomplete paste).

Can I use a license from a different deployment?

No. Each license is tied to a specific deployment fingerprint — a cryptographic snapshot that includes the number of datastores, quality checks, users, and operations created in your deployment. Applying a license generated for a different deployment returns a fingerprint mismatch error.

What is a deployment fingerprint?

A fingerprint is a unique identifier generated from your deployment's history — including counts of datastores, quality checks, users, and operations created. It is embedded in the license request code and used to verify that a license key was issued for your specific deployment.

What is the license request code?

The license request code is an encoded string that contains your deployment's fingerprint. You generate it from the platform and send it to the Qualytics support team, who use it to create a signed license key bound to your deployment.