Pre-release Sign-up is not open yet. Platform verification and the signed client download are in development. See what is available
Features

What Obscurity does, and what is ready today.

Each capability below carries a status. "Available" means it is implemented and covered by automated tests in the current release. Nothing in development is sold as finished.

Developer console

Organizations, teams and roles

Create an organization, invite your team and assign one of six roles, including Support for player appeals; developers, analysts and support can be limited to some games. Permissions are enforced by the server on every request. Each member can turn on two-step sign-in with an authenticator app, with single-use recovery codes.

Available

Game registration, protection tier and versioned policy

Register each title and choose its protection tier. Every policy change is stored as a new numbered version so later evidence can cite the exact configuration in force. The tier is set by the studio and enforced by the server; a player cannot choose a weaker one.

Available

Per-game feature switches

Every feature of every tier is listed on the game's page. Within the game's tier you switch each one on or off; the server applies the setting to every session, including ones already running. Switching a feature off needs a confirmation and is recorded in the audit log.

Available

Game-scoped server keys

Issue secret keys scoped to a single game, rotate them with an overlap window and revoke them immediately. Secrets are shown once and stored only as hashes.

Available

Audit log

Sign-ins, role changes, key operations and policy edits are recorded with actor, time and source address.

Available

Subscriptions

Per-game monthly subscriptions

Checkout, invoices, tier changes and cancellation through Stripe. Entitlements change only from verified provider data, never from a browser reaching a success page. Exercised end to end against Stripe's test environment; paid checkout is not open yet.

In development

Grace period and suspension policy

A failed renewal never lowers a game's protection tier. Service continues for 3 days while the payment is retried, with one reminder email a day. Still unpaid after the third day, the subscription is cancelled and the game's protected sessions stop until the studio subscribes again. Billing state is never recorded as a decision about a player.

In development

Platform security verification (Advanced and Elite)

TPM 2.0 attestation

The PC's TPM answers a fresh server challenge with a quote of how the PC booted, and the server checks that the answer came from a TPM a manufacturer certified, instead of trusting values the client reports. Built and working end to end without administrator rights on the one PC it has been run on. Not released: the client is unsigned, and a TPM is only accepted once its manufacturer's certificate is installed on the service.

In development

Secure Boot, HVCI and IOMMU checks

Read from the TPM-backed boot record and reported one by one: satisfied, switched off, unsupported hardware, unsupported Windows, could not be verified or invalid evidence. Secure Boot has been confirmed on real hardware. Memory integrity and IOMMU have only been confirmed in the "off" state on real hardware; their "on" state is tested with constructed boot records.

In development

Admission policy at session start

A game that requires platform verification admits a session only after the evidence is verified. A player who does not meet a requirement is told which one and what to change. That is a compatibility result: it never becomes a detection, a restriction or an accusation, and the client changes nothing on the PC. Works today in development; not released.

In development

Game integration (all tiers)

Protected sessions with server-side admission

The server decides whether a session may run from the game's policy and entitlement; a client cannot choose its tier. Every later request is signed with a per-session key and sequenced, and your game server confirms a player with a single-use join token.

Available

Released-build check

Register the hash of each executable you ship; other copies are refused or flagged at session start. The hash is reported by the player's PC, so this stops stale and casually modified copies and is not proof that the running game is unmodified.

Available

Usage metering

Monthly active players and peak concurrent sessions per game, shown in the console and the API. Going over an included amount never adds a charge.

Available

Windows client SDK (C/C++)

A small library with a C interface that opens the session, keeps it alive and mints join tokens. It also gathers the TPM evidence for games that require platform verification, without administrator rights and without changing anything on the PC. It builds from source and passes the end-to-end sample; signed downloads are not published yet.

In development

Server-authoritative validation helpers

Movement-speed and action-rate checks that run on your game server with state only the server holds, and report what they rejected. A Python reference library exists, is tested and builds as a package (obscurity-gameserver) but is not published on PyPI yet; other languages use the HTTPS API directly.

In development

Launcher with startup progress

A launcher window that shows real startup progress from 0 to 100 percent over your game's artwork, asks the service whether the game and build will be admitted, and starts the game. It is unsigned and does not protect anything by itself.

In development

Unreal Engine and Unity plugins

Engine plugins that wrap the C SDK. Until they exist, integration uses the C API directly.

Planned

Detection and evidence (all tiers)

Event collection and versioned detectors

Your game server reports the moves and actions it rejected; the service adds the session misuse it observes. Four versioned detectors turn sustained patterns into findings, each with a reason, severity, evidence strength and the thresholds it used. Automatic detection can be paused per game. No detector has a measured false-positive rate yet. Nothing is read from the player's PC for this.

Available

Evidence review and reversible cases

A reviewer confirms or dismisses each finding with a written reason. An owner or admin can then open a case on a confirmed finding: session removal, a suspension or a ban covering the identifiers the game's level (Low or Normal) includes, plus network addresses when IP bans are on. A case ends the player's running sessions, can expire, can be reversed, and is fully audited.

Available

Automatic punishment (per game, on by default, can be switched off)

Applies your configured penalty to a fresh finding, capped by each detector's ceiling: today at most a temporary suspension, and only for the speed detector with strong evidence. No detector can ban automatically until it has a measured false-positive rate. Other findings go to review. Detectors can be paused per game, and every case one detector release opened can be reversed in one step.

Available

Identifier levels, IP bans and Anti-VPN

One setting per game decides what a suspension or ban covers. Low: the game account, the platform accounts your server verified and a TPM proven in platform verification. Normal: plus the installation and the hardware identifiers the SDK reports as hashes. IP bans are a separate switch (off by default, 1 to 30 days), and Anti-VPN refuses sessions from VPNs, proxies, Tor and hosting providers once switched on. Shared PCs go to review, shared networks are skipped, and reported hardware counts only when two kinds match. Values are stored as keyed hashes per game. Needs SDK 0.6, not a signed download yet.

In development

Global Ban Network (add-on, $20 per game per month)

Restrict access for players with an active, verified cheating ban from another participating Obscurity-protected game. On by default once the add-on is paid, and can be switched off per game or per ban. A participating game's bans and suspensions, manual or automatic, are submitted automatically, and apply elsewhere only after Obscurity staff validate them; unbanning the player removes them at once. Games are linked only by platform accounts their servers verified and TPMs proven in platform verification, never by hardware the PC reports or network addresses. A shared PC goes to the receiving studio's review, which can also exempt a ban for its game. Reversing the original case ends the network ban everywhere at once. Studios never see each other's names or evidence. Built and tested; not released.

In development

Client-side integrity signals

Signals about the game's own code and memory, from inside the game process and from the kernel driver. Not built: today's detections rest only on what servers observe.

Planned

Kernel driver (all tiers)

Kernel driver while the game runs

A narrowly scoped Windows driver of our own, loaded when a protected game starts and unloaded when it exits, so that client-side protection does not rest on user-mode code alone. Its first version is written and compiles: it removes memory read and write rights from other programs' handles to the game and reports driver and module loads. It has passed its test suite on a physical test PC with test signing, also under Windows Driver Verifier, including 20,000 malformed requests and unloading while in use. It still needs testing with memory integrity on and Microsoft's driver certification, and no driver is distributed today.

In development

Install, update, removal and recovery

Signed installation with clear prompts, staged rollout and rollback of updates, complete removal, and a documented recovery path if the driver fails. Ordinary use of the PC must never depend on it.

Planned

Boot-start protection (Elite)

Driver loaded at Windows startup

On Elite the same driver is loaded early in Windows startup instead of with the game, so it can report tampering that happens before the game launches. It starts with Windows, not before it. Its install file and a recovery counter are built: if Windows fails to start three times in a row, the driver switches itself off. The counter passed on a physical test PC; a real restart with it, the installer and Microsoft's certification are still ahead. Installing or updating it will need a restart.

In development
Engineering targets

How we will measure ourselves.

These are targets we are building toward, not results. We will publish measured numbers, with method, once there is a client to measure.

False positives

Automated enforcement only from detectors with a measured false-positive rate and human-reviewable evidence. Platform requirement failures never count as detections.

Client overhead

A fixed budget for CPU, memory and frame-time impact, measured on a published hardware matrix against a build without the SDK.

Admission reliability

A defined behaviour for every failure, including when our own verification service is unreachable, so an outage is never mistaken for a failed player.

Integration effort

A documented path from registration to a protected session in a sample game, timed with developers who did not write the SDK.

Diagnostics

Every refusal carries a specific, stable result code and a remediation path that support staff and players can act on.

Privacy

A published list of every telemetry field, why it is collected, who can see it and how long it is kept.

Sign-up opens with the first release.

Until then, read how it works and ask questions in our Discord server.