Not translated yet — showing English.
Creating a New Project
A project is one game's backend on PlayServ. It holds the game's data, functions, players and keys, split into isolated environments. Projects belong to a studio, and everyone on the studio's team sees the ones they have access to. This page covers getting a studio and its first project going, and looking after projects afterwards.
Your first sign-in
The first time you sign in, PlayServ walks you through two steps.
Name your studio
The studio is what your team sees in headers. Give it a name of up to 60 characters; its slug is shown under it and can be edited.
Create your first project
Pick Start with example to get a fully loaded demo game in about five seconds, or Start blank to name a project and choose its icon and region. Skip for now takes you straight in.
Start blank asks for the same name, icon and region as creating any other project.
You then land on Projects with the new project selected. Its API keys panel stays empty until you create a key, which is the next thing your game needs.
If someone has already invited you to a studio, the first screen asks instead whether to accept the invite or create your own organization. Creating your own keeps the invitation; you can accept it later from Organizations in the profile menu.
Create a project
On Projects, click Create project, or use Create project at the bottom of the project switcher in the top-left corner.
| Field | Rules |
|---|---|
| Name | Up to 48 characters. Letters and digits, with spaces or punctuation; it can't be only digits, and must be unique in the studio, ignoring case. |
| Icon | The project's initials on one of six colours. |
| Region | Where the project's data and services run. Frankfurt (eu-west-1) is available today; Virginia, Singapore and São Paulo are coming soon. |
The region can't be changed later
A project stays in the region it was created in. Choose the one closest to most of your players.
The new project becomes the active one, with a dev and a prod environment ready.
The slug is the project's identifier in addresses and the CLI. It is built from the name, and PlayServ adds a random five-character suffix to keep it unique: a project named Sky Arena gets a slug like sky-arena-a1b2c. The preview in the dialog shows the part made from the name.
The example project
Try example creates a complete demo game called Tank Wars, with catalog items, storefronts, three cloud functions, 30 days of simulated activity and over a thousand events. It takes about five seconds and is the fastest way to see every part of the Backoffice with real-looking data. A studio can have more than one example, and an example can be deleted like any other project.
The Projects page
Every project in the studio has a card showing its name, region, monthly active users and 24-hour revenue (example projects show sample data), and when it was last used.
| On a card | What it does |
|---|---|
| Click the card | Makes it the active project. |
| Gear | Opens project settings. |
| Chart | Opens the project's Analytics. |
| API Keys | Shows the project's keys in the panel below the cards, see API Key Management. |
| Trash | Deletes the project. |
The History tab lists what happened to projects and keys, newest first: who created, renamed, deleted, restored or opened a project, and who created, rotated or revoked a key. Key events are shown for the selected project in the current environment.
Project settings
The gear on a card, or on a project in the switcher, opens the project's settings. The tabs are General, Environments, Deployment, Notifications and Danger zone.
| Setting on General | What you can do |
|---|---|
| Name | Rename the project, up to 48 characters. Renaming doesn't change the slug. |
| Slug | Read-only; the owner can regenerate it. |
| Icon | Pick another colour. |
| Region | Shown for reference; it can't be changed. |
| Description | Up to 280 characters. |
Changes are kept when you click Save changes.
Regenerate the slug only when you must. It changes the address every integration uses. Regenerate slug keeps the part made from the name and replaces the random suffix. The old slug can keep redirecting for 0 to 180 days (60 by default) so storefront links, webhook targets and bookmarks have time to move; with 0 it stops working at once. You confirm by typing the current slug. Only the studio owner can do this, once every 30 days and five times in a project's life.
Delete and restore a project
Delete a project from the trash icon on its card or from Danger zone in its settings, and confirm by typing its name. Its catalog, storefronts, functions, analytics, events and keys go with it.
You have ten seconds to change your mind
After deleting, Undo appears on the card and in the notification for ten seconds. After that, the project moves to Deleted projects.
A deleted project serves nothing, but its data is kept. Under Deleted projects:
| Action | Who | What happens |
|---|---|---|
| Restore | Owner or org admin | The project comes back as it was. |
| Erase | Owner only | The data is deleted for good. There is no way back. |
A project marked Held can't be erased while a PlayServ operator hold is on it.
Next steps
- Environments —
dev,prodand any others, and copying one into another - API Key Management — the keys your game and servers use
- Team & Access — invite people and decide which projects they see
Last updated on 15 Oct 2026