frameDockDocumentation

Handoffs, runners and studio controls

Add collaboration while keeping builds and credentials under your control.

Signed artifact handoffs

Indie adds identifiable artifact handoffs and Discord delivery notifications. Verify the received record and files before using the build; a signature does not replace gameplay or compatibility checks.

Runners on computers you control

Pro adds managed runners on your own computers. Match the receiving machine’s editor, modules, target and toolchain. Pairing does not establish that every project can build there.

Roles and release approvals

Teams adds roles, approvals, single sign-on and audit retention. Local project permissions and release policy remain separate from account billing roles. A plan ending does not erase an approval policy as a shortcut around it.

People seats and device access

Teams pricing counts people, including the owner, with two active computers per member. Removing a person frees that member seat; signing out a computer does not change the subscription quantity.

Current evidence boundary

Paid sales remain closed. A complete team/runner demonstration is not recorded here. This guide explains the capability policy and prerequisites, not a newly verified studio deployment.