Not translated yet — showing English.
Architecture
PlayServ is the backend your game talks to, run for you. Your game connects through the SDK; your game servers, if you have them, register their rooms; your team shapes everything in the Backoffice and ships code with the CLI. Each project is split into environments, and the key a caller uses decides which project and environment it reaches.
The parts
| Part | What it is |
|---|---|
| Your game | Your Unity project with the PlayServ SDK. It signs players in, reads and writes data, gets live updates, receives events and calls functions. |
| Your game servers | Optional dedicated servers. They register the rooms players join, and talk to the platform with a server key. See Game Server Hosting. |
| Backoffice | The web console where your team manages projects, keys, players, the schema and data, functions, servers and rooms. |
| CLI | The playserv command line, for deploying functions and game servers. See Command Line Interface. |
| Players | Player accounts, sign-in providers and sessions. See Managing Players. |
| Data | Your schema and its records, with live updates to the game. See Building a Game Schema. |
| Cloud functions | Your server-side code, run by the platform. See Functions. |
| Game rooms | The rooms your game servers run, and the players in them. See Game Rooms. |
How the game connects
The game keeps one live connection to PlayServ. PlayServ.Connect() signs the player in and opens it; the SDK keeps it alive and reconnects after a drop.
| Over | What travels |
|---|---|
| The live connection | Live data updates, events from your servers, RPC calls. |
| Separate requests | Most reads and writes of records, calling cloud functions, signing in. |
You don't choose between them: the SDK picks the right path for each call. The connection's states, reconnects and session handling are in Connection & Session.
Keys, environments and players
| Term | What it is |
|---|---|
| Project | One game's backend. See Create a Project. |
| Environment | A separate copy of the project's data, functions and players, such as dev and prod. See Environments. |
Client key (pk_…) | Built into the game. It decides the project and environment the game reaches. Safe to ship. |
Server key (sk_…) | For your servers, tools and CI. Never ship it in a game build. See API Key Management. |
| Player | Every connected game signs in as a player, anonymous at first. The player comes from their session, not from a setting. See User Login. |
One key, one environment
A build with a dev client key always talks to dev. To release, build with a key of the environment players should use.
SDK modules
The SDK is one package, com.playserv.sdk, with modules for each area, plus optional companion packages.
| Module | What it does | Guide |
|---|---|---|
PlayServ | Connects, configures and disconnects. | Connection & Session |
PlayServAuth | Signs players in, links providers, ends sessions. | User Login |
PlayServData | Reads, writes and subscribes to records. | Reading Records |
PlayServCode | Calls cloud functions. | Functions |
PlayServEvents · PlayServRpc | Receives events from your servers; calls RPCs. | Server Events |
PlayServMatchmaking | Browses and joins game rooms. | Browse, Host & Join Rooms |
Companion packages add sign-in providers, a dedicated game server, and other optional features. They're installed from Tools ▸ PlayServ ▸ Settings, see Connect Your Game.
Next steps
- Connect Your Game — install the SDK and connect
- Create a Project — the project and its first environment
- Connection & Session — what happens while the game is connected
Last updated on 19 Oct 2026