Sandbox preview · Payments are simulated. This Windows pilot is for testing.

Create account

Add collaboration when your workflow needs it.

Keep the local build foundation. Add a clearer handoff, a dedicated build computer or studio controls as the people involved change.

  1. Share the checked build.

    Indie

    Signed artifact handoffs keep the result identifiable for testers and collaborators. Discord notifications can tell them a build is ready without replacing the artifact or its evidence.

    Understand a signed handoff

  2. Build on your own dedicated computer.

    Pro

    Managed runners use computers you control. Keep their engine, target and environment ready rather than assuming a different machine can build the same project.

    Read runner prerequisites

  3. Make release responsibility explicit.

    Teams

    Roles, approvals, single sign-on and audit retention support a studio’s release policy. People seats belong to account licensing; project roles govern the local workflow.

    Read roles and approvals

A handoff carries a result—not a promise.

  1. Build and play the game
  2. Inspect its artifact and manifest
  3. Create the signed handoff
  4. Verify before using it on another machine

Store credentials are not included in an artifact handoff. A signature does not replace the receiving computer’s compatibility or gameplay checks.