Skip to main content

License management

Every Qry installation runs under a license from IXEN: how many users and datasources it may have, which features are on, and until when. It is pasted in Admin › System Settings › License and shown, with current usage, in Admin › License.

The license file​

A license is one line of text that starts with QRYLIC1. It carries the customer, the limits, the features, the support level and the expiry date, signed by IXEN. Qry checks the signature with a public key built into its image, so a license cannot be edited (a changed limit breaks the signature) and checking it calls no one.

There are two kinds:

OnlineOffline
ForInstallations that can reach the internetInstallations with no route out
ChecksThe signature, and every 6 hours whether IXEN has withdrawn it, at https://get.qry.dev/licenses/revocationsThe signature only
LengthThe contract'sShort (quarterly), renewed
NetworkOutbound HTTPS to get.qry.devNone

An online license that cannot read the list keeps working for 7 days, so an outage on either side does not stop anyone. After that it stops until the list is reachable again or an offline license is pasted. The list is signed too: a copy that is altered, or older than one already read, is refused, so it cannot be used to undo a withdrawal.

When a license stops​

  • Expired: past its date.
  • Withdrawn: an online license IXEN has put on the list. Installations stop at their next check, within about 6 hours.
  • Not confirmed: an online license that could not read the list for 7 days.

Qry then answers every request with the reason, except the ones an administrator needs to put a new license in place: signing in, Admin › System Settings and Admin › License. Paste the new license there; it takes effect at once, without a restart.

Qry checks the license at startup, every 6 hours, and whenever an administrator saves configuration. Administrators get a notice 30 days before it expires.

What the limits do​

  • Users: adding a person beyond the limit is refused, whether an administrator creates them, they register, or they sign in with Entra ID or Google for the first time; so is turning a deactivated user back on. People already active are never locked out, so an installation over its limit only stops adding people. IXEN's own support accounts, when the license names them, are outside the limit and shown in Admin › License.
  • Datasources: creating a datasource beyond the limit is refused; the count is of active datasources.
  • Features: an endpoint of a feature the license does not include answers 403.

qry doctor reports an expired, expiring (45 days) or stopped license.

Pulling Qry's images with the license​

The license is also the password for Qry's registry, registry.qry.dev, with the user name license. It serves the images and the Helm chart of the releases the license covers, and refuses an expired or withdrawn license.

helm install qry oci://registry.qry.dev/qry/qry-platform --version <version> -n <namespace> \
--username license --password "$(cat <license file>)" \
--set image.registry=registry.qry.dev --set image.project=qry --set image.repository= \
--set runtimeImages.registry=registry.qry.dev/qry \
--set imagePullSecret.dockerServer=registry.qry.dev \
--set imagePullSecret.dockerUsername=license \
--set-file imagePullSecret.dockerPassword=<license file> \
-f <your values>

The chart writes the pull secret into Qry's namespace and the one where people's Python runs, and runtimeImages.registry sends the images Qry starts itself (Python, notebooks, storage sidecars) to the same registry, each at the version its release ships.

After installing, the registry password follows Admin › License. When a new license is pasted there, Qry writes it into the pull secret too, so a renewal needs nothing else; the chart then keeps that secret on later upgrades instead of putting the install-time license back, so --set-file imagePullSecret.dockerPassword no longer changes it. To force a password with Helm, remove the mark first (kubectl annotate secret <pull secret> qry.dev/registry-license- in both namespaces) and upgrade. qry doctor reports a pull secret that does not carry the license in force.

The older license: a service-account key​

Installations licensed before the license file was introduced carry a Google service-account JSON key instead, in the same settings page. Qry reads the limits from Google's IAM API at startup and every 6 hours; when Google cannot be reached it keeps the last result for 24 hours. The key has to be rotated every 180 days, and that route needs outbound HTTPS to *.googleapis.com.

These installations move to a license file at their next renewal: paste the file, and it is used instead of the key, which can then be removed.

Common issues​

"License file not valid: signed with an unknown key". The license was signed with a newer IXEN key than this version of Qry knows. Upgrade Qry, or ask IXEN for a license signed with the current key.

"The signature does not match". The text was changed or cut when it was copied. Paste it again exactly as received, as one line.

"Qry could not confirm this license for N days". The installation cannot reach get.qry.dev. Allow outbound HTTPS to it (through the proxy if there is one), or ask IXEN for an offline license.

See also​