Licensing (planned)

Planned. Self-hosted deployment is not available yet. This page describes how the licence will work.

Your deployment is licensed by a signed hourly exchange with Provantix. It is built so that a network problem on your side is visible early, a stolen answer is useless, and nothing Provantix sends can run anything on your machine.

How it works

Every hour the deployment sends a beacon, signed with the deployment's own key (created on your machine at install). Provantix checks the signature, the sequence number and the machine hash, and replies with a signed answer that repeats the beacon's one-time number. The deployment accepts the answer only if:

  1. the signature verifies against the Provantix licensing key built into the product;
  2. it answers the exact beacon just sent (a recorded answer cannot be replayed);
  3. its time is close to your clock (within ten minutes).

An answer carries your status (active, lapsed or revoked), what you bought, and the time it is valid until. It carries no commands.

What the beacon contains

Field Meaning
deployment id Which deployment this is
sequence A number that rises with every beacon, so a copied machine is noticed
nonce One-time value the answer must repeat
time, version Your clock and the product version
usage Active agents and record counts for the period (counts only)
machine A salted hash of a machine identifier; the identifier itself never leaves the machine

No records, no content and no names are in it.

States and what you see

An answer is good for six hours from the time it carries. The count of missed beacons is worked out from the answer's age, so a restart or a changed clock cannot reset it.

Age of last good answer Missed beacons What happens
under 3 hours 0 to 2 Nothing.
3 to 6 hours 3 to 5 Administrators see a warning: Unable to validate the licence. Please ensure this server can reach Provantix. Nothing is blocked.
6 hours or more 6 Nobody can sign in, and the sign-in screen shows the same message.
a good answer arrives The count clears, sign-in returns and the warning goes at once.

A deployment that has been installed but never received an answer is treated as blocked, so finish activation before you hand it to people.

What keeps working when the licence cannot be validated

  • Telemetry keeps being accepted. Only a lapsed or revoked licence stops it.
  • Verification works offline. Verifying an export or checking a root needs no sign-in and no contact with Provantix.
  • A command-line export works without sign-in (planned), so your evidence is never locked behind the licence check.

When the licence is lapsed or revoked

Ingest answers HTTP 402 to whoever is sending. The Node SDK treats 402 as "retry later" and keeps its batches queued, so evidence is delayed, not lost, as long as the sender's queue has room. Renewing returns an active answer on the next beacon, within the hour.

Using more than you bought

Billed, never refused. Provantix does not stop telemetry because of volume. If you want a hard limit, set it yourself in your own systems.

Checking the licence

curl -sS http://127.0.0.1:8787/api/licence
{"mode":"customer","status":"active","health":"ok","missed_beacons":0,"message":null,"answered_at":"2026-11-03T05:20:00.000Z"}

health is ok, warning, blocked or unactivated.

If you see the warning

Work down this list; most causes are the first two.

  1. Can the machine reach Provantix? curl -sS -o /dev/null -w "%{http_code}\n" https://app.provantix.tech/health should print 200. If you use a proxy, the service needs it too: set it in the settings file and restart.
  2. Is the clock right? timedatectl status. An answer more than ten minutes from your clock is refused, and the last reason (clock_skew, with how far off) is kept for the licence screen and the support bundle.
  3. Is TLS inspection in the way? Your inspection certificate must be trusted by the machine.
  4. What was the last reason? The deployment keeps the reason for its last failed beacon (planned: sudo provantix licence-status and the Licence panel show it). Reasons you may see: unreachable, refused (401) (the deployment is not recognised: see "moving a machine" below), bad_signature, nonce_mismatch, clock_skew.

Activation

Provantix gives you a one-time activation key for your deployment. The installer generates the deployment's key pair on your machine, sends only the public half with the activation key, and Provantix records the deployment. The key cannot be used again.

Moving or rebuilding the machine

A beacon carries a hash of the machine. If the same deployment id beacons from a different machine, Provantix answers revoked until the real one registers again. This is how a copied virtual machine is stopped, and it is deliberate: a legitimate move is handled by re-registering, not by a support exception.

  1. Tell us you are moving or rebuilding. We issue a new activation key for the same deployment.
  2. Install on the new machine, or run the activation step again on the rebuilt one.
  3. The old machine is no longer accepted.

Keep the data directory with its signing key when you move: losing the key means roots can no longer be extended under the same key. See Operations.

Who can change your licence

Only Provantix staff, in the operator console, and only the three statuses and the number of agents bought. Every change needs a reason and is written to an audit log. They can see what your beacon reported and nothing else.