Compare
The usual suspects, honestly.
PlayFab, Photon, Nakama, and Playroom are good at what they are for. The distinction that matters: if you want to build a game, use a game backend. If you want your app to have games, with real opponents in them, use Parlor.
| Parlor | PlayFab | Photon | Nakama | Playroom | |
|---|---|---|---|---|---|
| Ships with a playable game | Yes. Live chess, today. | No | No | No | No |
| Opponents included, shared cross-app pool | Yes. Every app feeds one pool. | No, you match your own users | No, you match your own users | No, you match your own users | No, you match your own users |
| Server-authoritative rules built in | Yes, for its games. Moves, clocks, ratings. | You write them | You write them | You write them | No, largely client-side |
| Custom game logic | No. They win here. | Yes | Yes | Yes | Yes |
| Engine SDKs, Unity and Unreal | No. They win here. REST and WebSocket, plus Swift in early access. | Yes | Yes | Yes | Web-first, with Unity support |
| Self-hostable | No | No | Partly, via Photon Server | Yes, open source. Nakama wins here. | No |
| Scale track record | New and focused. They win here, plainly. | Mature, proven at scale | Mature, proven at scale | Mature, proven at scale | Established |
| Time to a live match in your app | Three REST calls and a socket | After you build the game | After you build the game | After you build the game | After you build the game |
Comparisons reflect our reading of public documentation as of July 2026. If we have something wrong, tell us and we will fix it.
The honest ending
Use both.
Parlor is not trying to replace a game backend. If you are building your own game, build it on PlayFab or Nakama and be happy. Parlor sits beside them: it gives the rest of your app, the alarm screen, the loading screen, the waiting room, a live game with a real opponent in it. The two do not compete for the same line in your architecture.