The server that keeps your players in sync

What Colyseus is

Colyseus is an open-source multiplayer framework for Node.js, MIT licensed, widely used across the indie game world. It is authoritative by design: the server owns the state, clients send intent, and the framework handles the parts everyone gets wrong on their own — room lifecycle, delta-compressed state synchronisation, and reconnection after a dropped connection.

Stock Colyseus, not a fork

What we run is Colyseus 0.18 as published, with a quota layer bolted on top and nothing else changed. The Engine talks to it with the official Colyseus client. Nothing about the wire protocol, the room API or the state schema is aukimi-specific, which has a concrete consequence: the upstream documentation applies to your game as written, and what you learn building here is not knowledge you can only use here.

A free shared server, already switched on

You do not need a subscription, or even a decision, to see your game go multiplayer. A shared test server runs permanently, and a scene that has never been configured already points at it. It is deliberately small and deliberately forgetful — 8 players to a room, 16 connected and 2 rooms per room code, nothing stored between sessions. It is where you find out your game works; a server of your own is where you let players in.

• 8 players per room · 16 connected · 2 rooms, counted per room code
• No account, no persistence, no uptime guarantee
• Quotas are enforced per room code, so one busy game cannot starve the others

A server of your own, started from the member zone

When the test room is too small, servers get their own page: create, start, stop, restart or delete one, watch it move through provisioning, copy its address — or open it straight in the Engine. Each runs in its own isolated container with published limits. No terminal, no container to babysit, and the plan grid says what every tier does.

Reconnection is part of the deal

Players lose connections — a tunnel, a lift, a laptop lid. Colyseus keeps a seat reserved for a disconnected client and lets it return to the same session with the same identity rather than restarting as a stranger. That path is the one we broke, found and fixed while bringing the host up, and it is verified with a real client rather than a health check.