Skip to main content

License Tiers

Each Releval deployment runs under a license that defines a tier and a set of resource limits. The tier is selected at license issuance time. Three tiers are defined.

How limits are enforced​

Resource limits are checked when you create new resources. If you're at the cap for a given resource type, the API returns 403 Forbidden with a problem-detail body explaining which limit was reached. Existing resources are not affected.

For example, attempting to invite an 11th member on a Team tier returns:

{
  "type": "https://tools.ietf.org/html/rfc7231#section-6.5.3",
  "title": "Limit reached",
  "status": 403,
  "detail": "Member limit (10) reached on Team tier."
}

Viewing current tier and usage​

The license endpoint returns the active tier, expiration, and licensee details:

curl "https://${RELEVAL_HOST}/api/v1/license" \
  -H "Authorization: Bearer ${TOKEN}"

The limits endpoint returns the per-resource cap and your current usage:

curl "https://${RELEVAL_HOST}/api/v1/license/limits" \
  -H "Authorization: Bearer ${TOKEN}"

The response uses null to indicate "unlimited" for that resource.

Upgrading​

To change tiers, contact your license provider for a new license file. Once issued:

  1. Place the new license file at the path specified by License__Path (see Licensing configuration).
  2. Restart Releval.
  3. Verify the new tier with GET /api/v1/license.