Describe the game you want to play. It gets built on a real machine, runs in front of you, and ships.
Free to start. No card.
How it works
“A low-poly racer through an autumn forest.” “A first-person puzzle game in a lighthouse.” “Skim a ringed planet, dodge the debris.” One sentence, the way you would say it to a person.
It builds on a real machine and serves itself on port 8000, and you are playing it while it is still being written. Keep talking until it plays the way you want.
Push the folder to GitHub, or put it on your own Vercel with one button. It is plain HTML and JavaScript, so it runs anywhere that serves files.
What you actually get back
Everything below is the real component, running the real code — the same preview, file view and package check you get inside the builder.
One — a working game
Flip the switch. That is the rule that ships, running.
Nothing gets into your browser on trust. You watch the thing you asked to disappear actually disappear, and if it takes the wrong rows with it you say so — the same way you would tell a person who built it for you.
Files
Two — every file it is made of
Not another round of asking. Open the file and change the line.
The site changed its layout and one selector is stale. With most generators that means describing the problem and hoping. Here you open content.js, fix the selector, and the preview updates — because the file you are reading is the file that ships.
Files
Three — what it is allowed to do
Every file open, with nothing compiled in between.
A generated game you cannot read is a generated game you cannot fix. The scene, the player, the world and the shaders are each their own file, in plain JavaScript with no bundler, so the thing you read is the thing that runs — and changing a number means changing that number.
Files
Four — somewhere to put it
One button each, both to accounts you own.
A static game is already what a static host wants, so there is nothing to configure and nothing to build. Deploy puts the folder on your Vercel at a URL you can send to someone; push puts it in a repository you own. Or take the zip and host it yourself — it is a folder of files.
Files
Every panel above is the real component. Click anything.
Build your ownNothing is hidden
A generated game you cannot read is a generated game you cannot fix. Every file is open in the editor — the scene, the player, the shaders — and it is plain JavaScript with no build step, so what you read is what runs.
Change a number by hand and the game reloads with it. Nothing is generated that you cannot change yourself.
This game asks for
No network access requested. Nothing leaves your browser.
Surfaces
One chat that holds the whole game — the scene, the player, the world — and changes it in place rather than starting over.
It builds on a real machine and serves itself, so you are playing the actual thing while it is still being written.
No black box. Open any file, change a number by hand, and the game reloads with it.
Every build is kept. Go back to the one that worked without asking for it again.
One button puts it on your own Vercel, at a URL you can send to anyone.
Tell it the one thing that has annoyed you for years. It will be fixed in about a minute.
Get started