Two things you can fetch without an account: the Readiness Check tool players run to see whether their PC meets the Layer 1 and Layer 3 requirements, and the SDK evaluation build studios use to integrate before a partner key is issued. Everything else — the signed kernel driver and the production library — ships through the partner portal only.
Both packages are plain zips: a PowerShell script and a C/C++ source tree. Nothing in them phones home. File names, sizes and hashes below are read from the signed release manifest, not typed by hand.
A read-only PowerShell script that checks the fourteen things the driver needs on a player's PC — OS build, Secure Boot, TPM, VBS/HVCI, DMA protection, test-signing, VM markers — and prints a verdict plus a short readiness code you can decode at /readiness/. It makes no network calls and writes nothing outside the folder you run it from.
—
The public header, an evaluation runtime stub that compiles and links in place of the real library, the C# binding, C++ / Unreal-style / Unity-style examples and a CMake project. It lets you wire up init, sessions and callbacks before you have a partner key. It does not include the kernel driver, the production library, or any API connectivity — detections are simulated.
—
The parts that actually enforce anything are tied to a partner key and a manual review. We don't publish them as static files — not because they're secret, but because a driver that installs on any machine that finds the URL is a liability for us and for you.
Delivered through the partner portal after key issuance. The signed driver and the production .lib are never published here. Each package is built for a specific partner and title, so the file name, size and hash differ per studio and are shown in the dashboard, not on this page.
Delivery: partner portal. Provisioning is reviewed manually, typically 2–5 business days after a key is issued.
Both checks run in your browser with WebCrypto. Nothing you drop here is uploaded — the file is hashed locally and compared against the manifest above. If you'd rather not trust a web page for this, the equivalent command-line steps are shown alongside.
Drop a zip (or choose one) to compute its SHA-256 locally and match it against the published artifacts.
certutil -hashfile <file> SHA256 on Windows, sha256sum <file> elsewhere.The checksum list is signed with our Ed25519 release key. This fetches SHA256SUMS.txt, its .sig and the public key and verifies them in the browser. Some browsers don't expose Ed25519 in WebCrypto yet — in that case use the openssl command below.
Read from the manifest so it can't drift from what the build script actually did. Engine builds ship to players through the runtime updater and are not re-cut into SDK releases; the SDK tracks the engine minor.
Loading manifest…
—
Manifest generated — by —. Schema v—.
Archived SDK builds are not served from this site. Partners who need one for a migration can ask support and we'll provide it from the release archive.
| Artifact | Version | Released | Status |
|---|---|---|---|
| Loading manifest… | |||