Ship your game to players in one command.
Build your game with anything that runs in a browser. Deploy it with one command, and Arcadible publishes it.
Bring your
own agent
Whichever agent writes your code can build, check, and publish your game too. Arcadible tells it what it needs, in words it can act on.
Working with agents in the docs →Works with Claude, ChatGPT, Gemini, Grok, and Meta AI.
llms.txt lists every page, llms-full.txt has them all in one file, and any page is Markdown with .md on its address.--json, every failure has a code that never changes, and a link to what fixes it.A home for games. Keep your engine, your repository, and your README. Arcadible adds the store page, the link to play, and the desktop app.
Everything after
the deploy
Where your games live once they're out: every release, the repository it ships from, and the store page.
Open Studio →Release from
GitHub
Connect a repository and release with a tag. Anyone who can push one can ship.
Deploying from GitHub →Bring
any engine
Start from a starter, or deploy a game you already have. If it runs in a browser, it runs here.
Game engines in the docs →Starters for Phaser, Three.js, PixiJS, and Babylon.js.
Your README is
your store page
Write your title, tagline, and description in your README, and put your art in .arcadible/. Each release turns them into the store page.
Your store page →Where your
game lands
Players find games in the store, on the web and in the Arcadible app, and play them right there.
Browse the store →