​
Project

The top-level container. Builds, servers, queues, lobbies, and keys all belong to a project. Create a separate project for each game or environment you run.

​
Build

A deployable game server artifact. Upload a ZIP containing your server binary and a simpl-server.sh startup script. Simpl wraps it in a container and stores it in a private registry. Reference builds by their version tag when booting servers or configuring queues.

​
Server

A running instance of a build. Every server boots with /simpl/its_simpl.json on disk, containing match context, connection details, and player data. See its_simpl.json for the full schema.

​
Queue

A matchmaking configuration. A queue defines which build to run, which region and tier to use, how many players are needed, and how to group them. See Setting Up Matchmaking.

​
Lobby

A room where players gather before a match. Players create lobbies at runtime through your game client. When the host enters a queue, Simpl finds compatible lobbies, boots a server, and delivers connection details to every player over SSE.

​
Keys

Every project has two key types. Use sk_live_ keys on your backend to create builds, servers, and queues. Use ck_live_ keys inside your game binary — they’re safe to ship to players.