Make cracking and tampering harder
No protection is unbreakable, but every check that runs on the server is one a cracker can’t simply patch out. Vaultix puts them there.
Only your builds get in
Upload your released executable, or its SHA-256, to the app’s approved-build list. Before credentials are accepted the SDK hashes the running program; in enforce mode a modified client is refused. Start in monitoring mode and switch to enforce once customers have updated.
Every request is signed
- Each sign-in creates a new key pair, certified for that session only
- Requests are signed with a timestamp and a fresh nonce; replays are refused
- Responses are signed too, so a fake server can’t answer for Vaultix
- A randomized integrity heartbeat re-checks the running executable
And the basics, done well
- HWID lock: one license, one PC
- Session control: see who is signed in and end any session
- An audit log of every change, with the values before and after
Questions
- Does this stop every crack?
- No system can promise that. It moves the important checks to the server, where they can’t be patched out of your program.
- Will it lock out customers on old versions?
- Not in monitoring mode. Switch to enforce once your active customers use an approved build.
Client security · Security best practices · HWID binding
Vaultix · Features · Pricing · Documentation · Changelog · llms.txt