0 Get started
Photon is not a backend and does not claim to be. It is the networking layer: rooms, state synchronization, a relay or an authoritative host, with deep Unity integration. The kit has turn-based sessions and none of that. They overlap on one word — multiplayer — and mean quite different things by it.
Choose Photon
When frames matter.
Sixty-hertz state synchronization, client prediction, rollback in Quantum's deterministic engine, and rooms that just work in Unity. If your game has players moving in the same space at the same time, this is the category and Photon is the safe pick in it.
Choose Pithy
When turns matter, and the rest of the game needs a backend.
A Durable Object holds authoritative state no client can be trusted with, resolves a move and writes a durable result to your own D1 — alongside accounts, matchmaking, rating, leaderboards and a ledger. Photon would still be the answer for the frames; this is the answer for everything around them.
On this capability alone
| Feature | Photon | Pithy |
|---|---|---|
Multiplayer | ||
| Real-time state synchronization Photon: the entire product Pithy: not offered | Yes | No |
| Client prediction and rollback Photon: Quantum is deterministic and built for it Pithy: not offered | Yes | No |
| Turn-based authoritative sessions Photon: possible, but not what it is for Pithy: a Durable Object per session, with hidden per-player state and a deadline | Partial | Yes |
| Matchmaking Photon: rooms and lobbies Pithy: room codes, invites, a friend graph and a skill-bucketed queue | Yes | Yes |
| Durable result written to your database Photon: the room is transient Pithy: every finished session writes a row to your own D1 | No | Yes |
| Player accounts Photon: bring your own Pithy: passwordless auth as a capability | No | Yes |
| Leaderboards, rating, economy Photon: not offered Pithy: leaderboards, MMR per pool, and a ledger that cannot double-spend | No | Yes |
| No concurrent-user pricing Photon: CCU plans with bandwidth bundled per user Pithy: Cloudflare bills what your Worker runs; there is no CCU dimension | No | Yes |
| Deep Unity integration Photon: first-class, and the reason most people choose it 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 Photon 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 Photon wins
Photon exists because synchronizing a moving world is hard. If that is your game, nothing on this page competes and you should stop reading.
A deterministic engine with rollback, for games where fairness under latency decides everything. There is no equivalent anywhere in this kit.
The integration, the samples and the community are enormous. A documented HTTP contract is not that.
A flat allowance with bandwidth bundled in means you can forecast the bill from a player count, which usage-based pricing makes harder.
These are not alternatives. If your game is real-time, use Photon for the networking — and you will still need accounts, matchmaking by skill, leaderboards, an economy and receipts, none of which Photon does. That is the part this kit is, and the two sit together perfectly well.