HWID lock: one license, one PC
Turn on the HWID check and every account is bound to the PC it first signs in from. A key that is shared or sold on does not get anyone else in.
How it works
- The C++ SDK builds a hardware ID from several identifiers of the computer and hashes them
- The first sign-in stores it with the account
- Every later sign-in must come from the same hardware, or it is refused
- Nothing to code: the SDK sends the hardware ID by itself
When a customer gets a new PC
Reset the hardware ID in the dashboard and the next sign-in binds the new machine. Customers can also ask in a Discord support ticket, and your team resets it from the ticket.
Spot sharing
Resets are logged in the audit log, and the Sessions page shows who is signed in and from which device, so frequent resets stand out.
Questions
- What changes the hardware ID?
- Mostly a new motherboard or CPU, sometimes a reinstalled operating system. A reset in the dashboard fixes it.
- Is the HWID check on for every app?
- It is a setting per app. Existing users are bound at their next sign-in after you turn it on.
HWID binding · Support tickets
Vaultix · Features · Pricing · Documentation · Changelog · llms.txt