Obscurity developer documentation
How to set up your organization, register a game and authenticate your backend today, and how the parts still in development are designed.
Read this first. Obscurity is pre-release. These docs separate what you can use now from what is being built. Pages about unreleased parts describe the design and are marked as such; details can change.
Delivery status
| Area | Stage | Status |
|---|---|---|
| Website, accounts, organizations and console | Stage 2 | Available |
| Three protection tiers, per-game billing and entitlements | Stage 3 | In development |
| Core: sessions, server validation, sample game (client SDK not yet a signed download) | Stage 4 | Available |
| Core: event collection, detections, review and reversible restrictions | Stage 5 | Available |
| Advanced: platform attestation and admission | Stage 6 | In development |
| Release signing, update distribution and deployment | Stage 7 | In development |
| Kernel driver for every tier, boot-start on Elite | Stage 8 | In development |
Guides
| Console quickstart | Create an organization, register a game, issue a server key and make your first API call. | Available |
| Server API reference | Authentication, endpoints, errors and rate limits. | Available |
| Roles and permissions | What each of the six roles can do, and limiting a member to some games. | Available |
| Integration model | Client, server and service responsibilities and the trust boundaries between them. | In development |
| Platform security requirements | How TPM 2.0, Secure Boot, HVCI and IOMMU are verified, and what each check proves. | In development |
| Data collection and privacy | What is collected today and the rules for what will be. | Available |