How-to guide

Activate your license

License activation is operator-initiated and online here: you upload the activated license file Elevarq provided, and Workbench verifies its embedded signature against its public key ring. Air-gapped sites use the offline flow instead.

Before you start

You need an admin session (see Create the first admin) and the license.json file Elevarq sent you. The examples re-use the cookie jar from login.

Upload the license

WORKBENCH=http://127.0.0.1:8080

curl -fsS -X POST "$WORKBENCH/api/license" \
  -b /tmp/wb.cookies \
  -H 'Content-Type: application/json' \
  -H "X-Arq-CSRF: $(grep arq_workbench_csrf /tmp/wb.cookies | awk '{print $7}')" \
  --data-binary @license.json

A successful activation returns 200 OK with the parsed license summary — plan tier, valid-until, and the configured limits. The artefact is persisted to the data volume (default /var/lib/arq-workbench/license.json), and Workbench refreshes its entitlement cache immediately.

The CSRF token is set as a cookie at login; the example pulls it from the cookie jar. Clients that handle CSRF automatically can skip the header.

Verify

curl -fsS "$WORKBENCH/api/licenses" -b /tmp/wb.cookies
# {"plan": "...", "status": "LICENSE_VALID", ...}

# /healthz now reports the licensing cache as "fresh" (was "empty"):
curl -fsS "$WORKBENCH/healthz"

Air-gapped or outbound-restricted? Use Activate offline instead — you export an activation request, upload it to the Elevarq portal, and import the counter-signed activation file you download back.