Protection is integrated, not bolted on.
Obscurity cannot protect a game it is not part of. Integration has a client half, a server half and a console where you configure policy and review evidence.
Who trusts whom.
The game client runs on a machine the player controls, so everything it sends is treated as potentially manipulated. Decisions are made by components the player cannot modify.
Game client + SDK
Collects attestation evidence from the TPM and signals about its own integrity. Never decides anything.
Untrusted inputObscurity services
Verify evidence against a fresh challenge, apply your policy, issue a short-lived session result.
Makes admission decisionsYour game server
Confirms the session with a secret key and enforces gameplay rules it is authoritative for.
Authoritative for gameplayThe integration path.
-
Register the game and create a server key Available
Create your organization in the console, register the title, choose its protection tier and issue a game-scoped secret key for your backend. The protection policy is versioned from the first save.
-
Link the client SDK into your Windows build In development
The SDK is a library with a C API, shipped with a small launcher that shows real startup progress and then your game's splash image. It opens an authenticated session and reports the hash of the game's executable, which the server compares with the builds you released. On Advanced and Elite it will also gather the TPM quote and measured-boot log and return an explicit result for each platform requirement, so your game can show the player an accurate message; that part is not built yet.
-
Confirm sessions from your game server Available
Before a player joins a protected match, your server redeems the single-use join token the client presented, using its secret key. Admission is decided server to server; the client cannot grant itself access.
-
Apply server-authoritative checks In development
Validate movement, timing and cooldowns against your game's rules using state your server already holds. Tolerances are explicit so that lag, packet loss and reconciliation are not mistaken for cheating.
-
Review evidence, then decide Available
Detections arrive in the console with the evidence, rule version and policy version that produced them. Enforcement is a separate, audited step that can be reversed.
What integration needs from your game.
- A Windows x64 client build you can link a native library into.
- A game server or backend that is authoritative for the state you want protected. Purely peer-to-peer games get platform verification but little gameplay validation.
- The ability to gate matchmaking or session start on a server-side check.
- For Advanced and Elite, players on PCs that meet the platform requirements. Core adds none.
See supported integrations for engines and platforms.