0 Get started
Colyseus is the closest thing in spirit to how the kit's multiplayer capability is built: an authoritative server holding state clients cannot be trusted with. The difference is that Colyseus is a framework you deploy and scale, and Pithy's version is a Durable Object Cloudflare instantiates — and that Colyseus stops at the room while the kit carries on into accounts, economy and leaderboards.
Choose Colyseus
When you want rooms in Node, with state sync done for you.
Define the state on the server and it is synchronized to every client automatically, with matchmaking, horizontal scaling across processes and SDKs for TypeScript, Unity, Defold and Haxe. Self-host it or take Colyseus Cloud. For real-time rooms in a Node codebase it is an excellent, focused tool.
Choose Pithy
When the session is turn-based and the game needs a backend around it.
A Durable Object per session with hidden per-player state, an alarm-driven deadline and a durable result in your own D1 — plus accounts, matchmaking by skill, leaderboards and a ledger. No processes to scale, and the rest of the product comes with it.
On this capability alone
| Feature | Colyseus | Pithy |
|---|---|---|
Multiplayer | ||
| Automatic state synchronization Colyseus: define state on the server and it syncs Pithy: the session holds state and resolves moves; there is no automatic diffing to clients | Yes | Partial |
| Real-time rooms Colyseus: the core of the framework Pithy: not offered; the kit is turn-based | Yes | No |
| Turn-based authoritative sessions Colyseus: a room can be turn-based Pithy: a Durable Object, with hidden per-player state and a deadline | Yes | Yes |
| Matchmaking Colyseus: built into the framework Pithy: room codes, invites, a friend graph and a skill-bucketed queue | Yes | Yes |
| No servers to run or scale Colyseus: processes you deploy, scaled horizontally Pithy: a Durable Object is instantiated on demand | No | Yes |
| Durable result in your own database Colyseus: the room ends and its state goes with it Pithy: every finished session writes a row to your own D1 | No | Yes |
| Player accounts Colyseus: bring your own Pithy: passwordless auth as a capability | No | Yes |
| Leaderboards, rating, economy Colyseus: out of scope by design Pithy: leaderboards, MMR per pool, and an overdraft-safe ledger | No | Yes |
| Engine SDKs Colyseus: TypeScript, Unity, Defold, Haxe Pithy: documented HTTP; the Unity path is written up, not packaged | Yes | Partial |
The saffron tick marks where Pithy leads — not that the other column is absent. Every claim about Colyseus was checked against their own documentation on 2026-08-25; both products change, and this page is a snapshot rather than a maintained contract.
Where Colyseus wins
Declare the schema, mutate it on the server, and every client sees it. The kit asks you to model moves and resolution yourself, which is more code.
Sockets, tick rates and presence. Durable Objects can hold a socket, but the framework around it is Colyseus's and not the kit's.
If your team is a Node team, running game logic in the same language and process as the state is simple in a way a distributed object is not.
Colyseus does one thing. A kit of capabilities is more to learn on day one, and for a game jam that matters.
Your own hardware or Colyseus Cloud. A Worker runs where Cloudflare runs.
For real-time rooms in Node, Colyseus is a better tool than anything here and the two are not really competing. Where they do meet is turn-based play, and there the argument is operational: a Durable Object needs no process to deploy or scale, and the session it holds is surrounded by the accounts, ratings, boards and currency the game also needs.