SigChain Guard is hardware-backed anti-cheat for Unity VR. The headset’s secure hardware attests the session, our server runs it through eight gates, and SCG.Validate() hands your game a result it can act on. One Unity package. One call.
using SigChainGuard;using UnityEngine; public class GameManager : MonoBehaviour{ async void Start() { SCGResult result = await SCG.Validate(); if (result == SCGResult.PASSED) { LoadGame(); // verified; forward the token } else if (result == SCGResult.FAILED) { // your call: kick, ban, or flag } else if (result == SCGResult.NO_CONNECTION) { // offline; not a failure } }}Register your game in the dashboard by uploading your signed APK. SCG extracts the certificate fingerprint and package name itself, and your API key is bound to that certificate — a re-signed or repackaged build presents a different certificate and is turned away.
Download the .unitypackage from the dashboard, import it, then open Window → SigChain Guard → Setup and paste the key. The setup window’s Fix All checks your project settings and resolves the common integration problems for you.
.unitypackageC# API · Java bridge · native arm64-v8a libraryValidate() at startOne async call in your start logic. The native bridge collects the hardware attestation, seals the payload, and sends it to SCG’s server; your game has the result before any gameplay code runs.
Re-validation is not automatic. When you want a fresh verdict mid-session — after a suspicious event, before a ranked match — call ReValidate(). It runs the same full pipeline and the bridge limits it to once every two minutes per player.
| Method | Returns | What it does |
|---|---|---|
| SCG.Validate() | Task<SCGResult> | Full validation. Run it at start; it also tracks the player’s HWID. |
| SCG.ReValidate() | async | The same eight gates, mid-session, when you ask. Bridge-limited to once per 2 minutes per player. |
| SCG.ValidatePS() | async | Checks your configured Photon endpoint. Returns PHOTON_ONLINE or NO_CONNECTION_NOPS. |
| SCG.HWIDPlayer() | async | Registers the player’s hashed device ID against your game. |
The client never grades itself. The sealed payload goes to SCG’s server, which runs eight gates in order. Any failure stops the pipeline — the game gets an error code or FAILED, never a token. Before gate two it also checks bans: yours, the network blacklist, and the cross-game threshold you configure.
One of these is hardware-proven. Gate 6 rests on a certificate chain signed inside the headset’s secure hardware; gates 1–5 and 7 are checks the server makes against its own records. Gate 8’s software signals are collected by the SDK on the device and sealed for transit — evidence you weight, not proof.
SCG_INVALID_PAYLOADSDK_OUTDATED/SDK_FAILEDTIMESTAMP_INVALIDNONCE_INVALIDSDK_OUTDATEDTEE_FAILED + reasonBASELINE_MISMATCHFAILEDGates 1–7 answer with an error and no verdict. From the ban checks onward, anything that is a judgement about a real, identified device — a ban, gate 8, the network fail-rate — comes back as a 200 with result: FAILED. A 200 is not a pass; read the result.
PASSED arrives with a signed token — a JWT your own server can verify, valid for five minutes, or sixty seconds when Photon custom auth is on. FAILED arrives with nothing.
SCG reports; you decide. A failure can be a kick, a ban or a quiet flag, you can whitelist specific device IDs, and you choose which of gate 8’s signals count. Ban a device in your game with cross-game banning on and it is flagged across every SCG-protected game — the newest game inherits every ban before it.
Using Photon? Pass the token as a custom-auth parameter before ConnectUsingSettings(). SCG verifies it server-side on every room join, so a bypassed client still cannot walk into a lobby.
| SCGResult | Kind | Meaning |
|---|---|---|
| PASSED | pass | All eight gates passed. Token issued. |
| FAILED | fail | A check failed, or the device is banned here or on the network. Reason is in your dashboard, not on the client. |
| NO_CONNECTION | warn | No internet. Not a security failure; your game decides. |
| SDK_OUTDATED | fail | The integrated SDK is below the minimum version. Update from the dashboard. |
| RATE_LIMITED | warn | ReValidate() called inside its two-minute window, or the game hit its per-minute ceiling. |
| QUOTA_EXCEEDED | warn | The plan’s monthly active users are past the grace allowance. |
| AUTH_PAUSED | warn | You paused validation from the dashboard toggle. |
| CHECK_DASHBOARD | fail | Subscription lapsed, key inactive, or game registration incomplete. |
| BACKEND_TIMEOUT | warn | The server did not answer in time. Retry. |
A security tool that oversells itself is one you should not trust. These are the edges of what SCG does.
ReValidate() when a fresh one matters, at most every two minutes per player.NO_CONNECTION is a distinct result. Your game decides what limited play looks like; validate again on reconnect.Straight answers. Where a figure has not been measured yet, the answer says so instead of guessing.
All pricing questionsDecompiling exposes the SDK’s logic, but the security does not depend on that logic staying secret. Validation is gated on an attestation certificate signed inside the headset’s secure hardware, and the server verifies that it chains to the manufacturer’s hardware root. Full APK access still does not let an attacker produce a passing certificate without compromising that hardware — which, on a locked, non-rooted headset, we have no known method for. Root or an unlocked bootloader changes the calculus, which is exactly why device-integrity and root signals are surfaced to you.
SCG never bans on its own: it reports signals and you choose the action, which is the real defence against false positives. You can whitelist specific device IDs, tune which checks count as a failure, and decide whether a failure is a soft warning or a hard block. We are early on a young platform, so expect edge cases — OS updates, unusual hardware, reprovisioned devices. Treat the result as input to moderation, not a verdict.
Each device gets a hashed ID built from hardware-backed values a normal app can read. Ban that ID with cross-game banning on and the device is flagged across SCG-protected games. The honest limit: those values can change after a factory reset or certain OS updates, so device identity is treated as strong but not absolute, and we are moving toward a multi-signal model. We will not pretend a non-privileged app can read an unchangeable hardware serial.
Yes. Distribution does not matter — Meta Store, AppLab, sideloaded or a dev build — on Meta Quest and Android VR headsets with a hardware TEE. There is no dependency on Google Play Services or Meta’s platform SDK.
Validate() returns NO_CONNECTION, which is not a failure. Your game decides what an offline session may do; we recommend allowing limited offline play and validating again on reconnect.
It is one async call in your start logic, awaited before gameplay code runs, and there is no background loop afterwards — re-validation runs only when you call ReValidate(). We have not published a verdict time or a build-size figure; those wait for measurements on real headsets.
Hardware identity signals — hashed device fingerprints, APK certificate data, attestation results — and the security-scan results. No personally identifiable information. Device data is hashed before it leaves the headset and is never stored in plaintext. Full details are in the privacy policy.
Meta Quest 2, Quest 3 and Quest Pro. Pico and other Android VR headsets with a hardware TEE are on the roadmap — we plan to expand to them where the hardware allows — but they are not supported today: our focus is getting Meta Quest right first. A headset is listed as supported only once it has passed hardware testing. PC VR is planned for a later release.
Unity 6 (6000.x) and Unity 2022.3 LTS — tested on Unity 6.4 and 2022.3. Android API level 29 (Android 10) or higher is required, because that is where hardware TEE attestation becomes available to an app.
SCG.Validate() more than once?It runs once per session and returns the cached verdict after that, so calling it again is free and harmless. When you need a fresh verdict — after a long session, or when a player returns from offline — call SCG.ReValidate(); the bridge limits how often it can actually re-run.
CHECK_DASHBOARD?Your API key is not verified yet, or the account is paused. An API key only starts returning real verdicts once BTKV — the step that proves you own the app you are registering — is complete, and the account is active. Finish that in the dashboard and the same key starts working without a rebuild.
Rotate it from the dashboard. Rotation asks for your password again, mints a new key for the same game, and keeps the old one working for seven days so a build already in store review is not stranded. After that the old key answers SCG_API_KEY_RETIRED so you can tell a stale build from a forgery. Only rotate if the key has leaked — changing plan never needs a new key.
Yes. JWT verification for your own game server is on every plan including Starter — you should never need a higher tier just to check a verdict server-side.
One device that validated at least once in the calendar month. Once or five hundred times, it counts once. Devices that fail hardware attestation are never counted, so you are not charged for cheaters or for attack traffic.
Nothing breaks straight away. Up to 110% of your limit everything runs normally, with a warning in your dashboard. Between 110% and 125% it keeps running and we tell you clearly — a dashboard banner and a Discord alert. Only sustained overage beyond 125% is enforced, after a three-day grace period from when you first cross it. Your players should never be locked out because your game did well.
No. Your quota is metered on successful, hardware-attested validations. Anyone hitting the endpoint with an extracted API key fails attestation, so their requests are rejected without touching your limit — and they land in a separate abuse bucket that cannot starve your real players.
It is the throughput ceiling for your game: how many players can be verified per minute at peak. Starter’s 120 a minute comfortably covers a few thousand monthly players; a game with tens of thousands of concurrent sessions needs Growth or Studio. Your dashboard tells you if you actually hit it, and suggests an upgrade only when one would genuinely help.
Yes. Upgrades take effect immediately and are prorated. Downgrades apply at the end of the current billing period, so you keep what you paid for.
You pay for ten months and get twelve — about 17% off. Billed once a year, same features, cancel before renewal at any time.
Genuinely unlimited games and players under normal commercial use; there is no hidden counter. If a single title reaches a scale where a flat fee stops making sense for either of us, we come to you and work out a custom plan — no quiet throttling, no surprise invoice.
After the private beta. Right now accounts are invite-only and nothing is charged — no card, no billing. The prices are published early so you can plan, and they may still change before public launch.
Shown for transparency during the private beta. Paid plans open after beta — no card, no charge yet — and prices may change before launch. You pay for players we actually verify: not seats, not requests, not attacks.
For solo devs shipping their first game
$29/ month
or $290 / year — two months free
≈ $14.50 per 1,000 players · 2,000 MAU
Paid plans aren’t open yet
For games that are taking off
$89/ month
or $890 / year — two months free
≈ $3.56 per 1,000 players — 4× cheaper than Starter
Paid plans aren’t open yet
For teams running multiple titles
$229/ month
or $2,290 / year — two months free
Flat rate · unlimited players — cost per player keeps falling as you scale
Paid plans aren’t open yet
“Works really well out of the box. If you know basic C# the docs walk you through everything clearly. The dashboard is the standout — toggling custom auth on and off without touching code is genuinely useful. Would recommend it to anyone building a VR multiplayer game.”
Every gate, every result code and every limit above is in the documentation in more detail than a homepage should carry. Start there.