Join the waitlist
Start on the public landing. If pilot access opens for your profile, the platform contacts you through the submitted email.
Pilot access
This is a closed pilot. Access is staged so email verification, approval, VPN onboarding and lab reachability can be validated safely before scale increases.
The process is intentionally explicit. Each step exists to keep public access separate from restricted runtime access.
Start on the public landing. If pilot access opens for your profile, the platform contacts you through the submitted email.
Registration requires anti-bot verification. Email verification must be completed before any platform access is expected.
Verified accounts still remain blocked until an operator explicitly approves access. That is part of the pilot safety model.
Approved users generate a WireGuard config from their profile. The private key is only returned in the downloaded file and new issuance invalidates the previous profile.
After tunnel activation, the player plane exposes DNS, HTTPS and the assigned lab path only. It does not become a broad host-access network.
The public explanation should make scope and non-scope obvious before a participant touches the runtime plane.
Restricted DNS, HTTPS and event-assigned lab reachability only.
Keep the instructions short and operational. The goal is to reduce onboarding mistakes, not to decorate the page.
Install the official WireGuard app, import the downloaded `.conf` and activate the tunnel before opening a lab target.
Install WireGuard for Windows, choose `Import tunnel(s) from file`, select the downloaded `.conf` and connect before using lab endpoints.
Use the WireGuard app from the App Store, import the `.conf` from Files or a secure transfer and enable the tunnel only when needed.
Use the WireGuard app from Play Store, import the `.conf` from local storage and activate the tunnel while working on assigned labs.