gbandit documentation

gbandit hosts web games and web apps. You bring the code and the Dockerfiles, and the platform builds and runs them, with managed databases, shared player accounts and separate dev and prod environments.

Getting started

• Use the template: scaffold a working game and deploy it.
• Deploy an existing app: bring a repo you already have and make it fit the platform.

Reference

• Deploy contract: everything needed to go from a repo to a deployed app.
• Authentication: getting a game token for the player and verifying it in your backend.
• The gbandit runtime: the script your frontend loads for the player's token, player counting and frontend logs.
• Player activity: how your game's players are counted for the games.gbandit.com catalog.
• Frontend logs: what reaches gbandit logs frontend from your players' browsers.
• Errors: the error responses every gbandit API sends, and what each type means.

For agents and tools

• /llms.txt: index of these docs as a link list.
• /llms-full.txt: all documentation in a single file.
• Every page is also served as raw markdown: /deploy.md, /auth.md, /runtime.md, /heartbeat.md, /frontend-logs.md, /errors.md.
• The CLI prints any page: gbandit docs deploy.

Agents porting an app should start from the deploy contract: most failed ports come from an assumption about the runtime that it spells out.