Static hosting stops at the page
Hosts for websites serve files. Your game also needs a server that runs all the time and holds a live connection to every player.
For developers building with AI
Your AI coding agent can write a multiplayer game. MultiPlayground runs it: upload the zip, and its Node.js server goes live in its own container, with a link to send your friends.
Works with Claude Code, Cursor, Codex, or anything that writes Node.js. Players need nothing but the link.
The hard part
A multiplayer game is two programs: the page people see, and a server that stays up and keeps every player connected. That second one needs a home.
Hosts for websites serve files. Your game also needs a server that runs all the time and holds a live connection to every player.
Renting a machine means ports, HTTPS certificates, restarts after a crash, updates and security. None of that is your game.
A game running on your laptop can't be opened by your friends. They need a link that works on their phone and their computer.
How it works
Start from the sample game with your AI, or follow the few rules in the guide with a game of your own. Try it in two browser tabs on your computer.
Zip the folder and drop it in the console. We install your packages and start your server in its own container, in about half a minute.
Your game is live at your-name.multiplayground.io/your-game/. Send the link. It's on the games page too, with how many are playing.
Running on MultiPlayground now
Agar.io is a Node.js and Socket.IO server like yours, in its own container. The server runs the world and sends it to every player 20 times a second.
What we run for you
Each game runs in its own Docker container, with its own memory and processor limits, kept apart from every other game.
WebSockets and Socket.IO work through our proxy, over HTTPS. Your server talks to every player live.
Leave node_modules out of the zip. We run npm install from your package.json.
Every game at your-name.multiplayground.io/game/, and all of them together on your page.
If your server stops, we start it again on its own, waiting a little longer each time.
Upload again under the same name. The link your players have keeps working.
After 15 minutes without players a game is paused, and it wakes as soon as someone opens it.
See in the console whether it's running, how many are playing, and what your server printed.
Publish with your AI agent
A small working multiplayer game that already runs here. It carries only what MultiPlayground needs: what you build on it is up to you.
In Claude Code, Cursor, Codex or your favourite tool, paste this and fill in your idea:
I'm making a multiplayer browser game for multiplayground.io. This folder has a compatible sample game: it's here only so my game runs on multiplayground. Read AGENTS.md and keep that compatibility, but the game itself can be completely different: [describe your game]. Then tell me how to try it with two players on my computer.
The sample's AGENTS.md tells your agent what keeps a game compatible.
Run it, then open http://localhost:3000 in two browser tabs. Both players should see each other move.
$ npm install
$ npm start
Zip the game's folder (without node_modules), sign in to the console, drop the zip and choose a name. The name becomes the address.
The whole contract, in code
package.json
{
"scripts": { "start": "node server.js" },
"dependencies": { "express": "^4", "socket.io": "^4" }
}
server.js
// the port we give you, on every network interface
server.listen(process.env.PORT || 3000, "0.0.0.0");
public/client.js
// your game lives at /your-game/: connect below it
const socket = io({
path: location.pathname.replace(/[^/]*$/, "") + "socket.io",
});
That's all a game needs to run here. The sample already does it. The rules in full
Already here
Multiplayer browser games with a Node.js server: Express and Socket.IO like the sample, or any Node server that listens on the port we give it. The page and the server are served together, from your zip.
No. It shows the few things a game needs to run here, and your game can be completely different. Those things are package.json at the top of the zip, npm start starting the server, and listening on process.env.PORT on 0.0.0.0.
No. Players open the link and play, on a phone or a computer. Only developers sign in, with a username and a password.
Upload again under the same name. The link stays the same. The game restarts with the new version, so players in it at that moment are disconnected and join again.
Not yet. Game state lives in your server's memory and starts fresh whenever the game restarts. There is no database or lasting disk storage.
A zip of up to 100 MB. Each game gets up to 512 MB of memory. One version runs at a time, and there is no rollback: a new upload replaces the old one.
Open its Logs in the console. Most often the server listens on localhost or a fixed port instead of process.env.PORT on 0.0.0.0, or package.json isn't at the top of the zip. The guide lists the usual causes.
Not yet. Your games live at your-username.multiplayground.io.
Sign up with a username and a password, upload your zip, and send the link.