When a compile succeeds, the result is a playable web build hosted for you — no exporting, uploading, or wiring up a server. You can play it in the workspace the moment it's ready, then hand it to testers as a link.
Generate a share link for any build and send it to external testers. Links can carry an optional password, so you decide whether a build is open to anyone with the URL or gated to the people you choose. Testers don't need an account to play and respond.
External testers can leave feedback against a build, and the game emits telemetry as they play — events, sessions, and completion signals are captured and summarized on your dashboard. You get a real picture of how a build performs in the wild instead of guessing.
After a successful deploy, Vision QA opens the hosted build in a headless browser, screenshots it, and asks a vision model whether the game actually rendered. It captures two frames to catch frozen games, marks the result PASS or FAIL in the build log, and on a pass stores the screenshot as your project thumbnail. A fail can trigger one credit-checked self-heal.
The Architect builds, the compiler produces a web export, Vision QA verifies it, and Playtest hands it to your testers. Their feedback and telemetry flow back into the workspace, where you describe the next change and run the loop again.