Why We Built a Browser-Native AI Game Studio

Game generation does not have to begin with a remote desktop or an always-on Docker container. For browser games, the useful unit of work is smaller: a validated design specification, a versioned set of source files, and a safe place to preview the result.

The production path

SXY Game Studio converts a request into a structured GameSpec, generates a PixiJS v8 project, and stores every file in a virtual workspace. The browser can then preview the game, edit source, validate asset bindings, and export a normal Vite project.

This architecture keeps the default workflow inexpensive and portable:

• AI providers are called from the server, so API keys never reach the browser.
• Project files and versions persist independently of a compute session.
• The preview runs a constrained game renderer rather than arbitrary server commands.
• Exported source can be deployed to Cloudflare or any static web host.

Where isolated workers still fit

Containers remain valuable for untrusted package installation, native compilers, Cocos editor automation, and long-running build jobs. They are an optional execution tier, not the storage model or the baseline cost for every active user.

That separation lets the studio begin with a low-cost web-native path and introduce isolated workers only when a project actually needs them.