Publishing a game

Available for local testing. Public hosting and automatic GitHub builds are not configured.

Your game, from project to playable listing.

View full-size diagram ↗

1. Create. Add a game, choose its entry type and give your coding agent the setup prompt.
2. Preview. Try its browser build privately. Native games may need an agreed browser port.
3. Approve. Confirm the finished preview. Spawn manually reviews new games before listing them.
4. Publish. Players can discover and launch the approved game.

Find your private workspaces under Creations on your profile. Visitors see your published games, never your drafts or publishing keys.

Updates stay in your hands

Upload a new browser build to prepare a private preview. Automatic previews from GitHub pushes are planned. Publish the version you approve; a failed update leaves the working game live. Routine updates do not need another manual review unless held for investigation. Spawn administrators can pause a listing or restore a previously published build.

Who hosts what?

Spawn's direction covers browser-build distribution, accounts and limited game data. Creators run their own multiplayer servers and protect their game rules. Upload checks reject malformed files and unsafe paths; a human still checks playability. These checks do not certify honest gameplay.

Spawn-owned reference games are intended to be open source. Other creators choose their own licences.