Device reputation as a service. One API call at your login keeps hardware you already banned on the outside — new account, new IP, new email, doesn't matter.
Product deck · 2026
The cheater loses an account and makes another one — same chair, same PC. Banning costs you the investigation, the moderation time, the judgment call. Coming back costs them nothing. Any control where the defender pays more than the attacker loses that fight over time.
A disposable email and thirty seconds at your signup form. You banned a row in a table, not a person.
A VPN is free and changes in one click. It still punishes shared connections — and misses the actual abuser.
Accounts are infinite, IPs are rentable. The physical hardware in front of the abuser isn't: buying another one costs real money. It's the first barrier whose cost of re-entry isn't zero — and that's what makes a ban stick.
Clean device. Let it through — no friction for the players who did nothing wrong.
Matches your banlist. Blocked — and the ban holds even inside a virtual machine.
Enough signal to flag, not enough to block outright. The call stays yours.
The SDK never blocks on its own — it collects and reports. Your server is the door, holding the verdict. That's deliberate: a patched client can't skip a check that lives where the attacker can't reach.
The SDK reads hardware signals and hashes them locally.
One request: POST /v1/check, with your key.
The composite is scored on our server, never trusted from the client.
Got a BAN? You refuse before the login completes.
The moat isn't the algorithm — it's that you're live this afternoon instead of building a fingerprint stack from scratch.
Seven SDKs — or none at all: the gateway sits in front of your app as a reverse proxy and you write no code.
In monitor mode everything runs and nothing is blocked. You see in your own logs who would have been caught, on your real player base, before you block a single login. You learn your false-positive rate from your data — not from our promise.
Verdicts land in your logs. Nobody is blocked. You compare them against the abusers you already know.
Happy with what you saw? Flip the switch and start enforcing. On your schedule, on your evidence.
"Ban the device" means something different in each business. Weighting the right signal for the case is the product — same API, the signal that actually fits.
The client never votes on its own trust. Claiming "I'm native" or "I have a TPM" earns nothing — only cryptographic proof gets precedence, and a guess always cedes to real evidence.
No single signal decides. Someone who swapped a hard drive isn't banned by accident — what triggers a ban is a threshold of real hardware evidence.
Spinning up a virtual machine to reset hardware trips detection — a disposable device shouldn't count as a fresh, legitimate one.
Our decision paths are attacked by an independent, different-model reviewer that tries to break them — and what it finds, we close.
No — by design. This is not a runtime anti-cheat living inside your app: no resident process, no hooks, no kernel driver, no continuous scanning.
The collector reads a handful of identifiers, hashes them locally and sends a few KB. That's it, once.
Scoring, banlist and analysis run on our server — not on your player's machine.
You set the limit. If our API is ever unreachable, your players still get in.
Anyone promising you infallibility is selling something. We'd rather state exactly where the signal is strong and where it's weak: that's what makes it trustworthy in the cases that matter.
A system that reads hardware identifiers should make a thoughtful engineer nervous. So: the raw serial never travels and is never stored readable — what exists is a composite of opaque hashes.
We compare "does this hash match a banned hash". We don't keep a catalogue of your players.
You decide how long data lives, per your use case and your law — and no longer.
A blocked user gets a path to contest it; the operator decides with the evidence in hand.
Early-access pricing — the first studios help shape the plans. If your volume doesn't fit, we'll fit it to you.
No card, no contract, no catch. "First 10" is real — it's all one person can integrate properly.
Create an app, generate a key, run your first check in five minutes. Monitor mode means you risk nothing to see it work.
Talk about a pilotHWID-Guard — device reputation as a service. Detection is weighted evidence, honestly — not a guarantee.