Skip to main content

​
License Management

​
Lifecycle

​
HWID binding

Keys lock to the hardware that first activates them. key/check compares the client-sent hwid against the key’s bound hardware IDs and returns FINGERPRINT_MISMATCH when they differ.
  • hwid_binding (project setting) — master switch.
  • max_hwid_per_key — how many hardware IDs one key may bind (1–10). Forced to 1 when binding is off.
  • FFA — free-for-all keys skip binding entirely. Forced on when project binding is disabled.
  • HWID is passthrough: the client computes its own hwid string; Vampauth only compares what it receives.

​
Usage stats

Every successful key/check increments executions, refreshes last_used, and seeds first_used. The executor label from the request (when the client sends one) feeds a per-project executor breakdown. These persist on the license in real time. HWID resets are deliberately not script-facing: release a key’s hardware binding from the dashboard, or let end users self-serve on the public flow page.