Not translated yet — showing English.
Environments
An environment is a fully separate copy of your project's backend. Each one has its own data, schema, catalog, functions, secrets, players and API keys, so work in dev never touches prod. Every project starts with dev and prod; add more, such as staging, whenever you need another stage.
Environments are also how PlayServ versions your data: there is no separate versioning feature. To keep a version of your data and content, copy the environment; to try a change safely, make it in a copy first.
Switching environments
The environment selector in the top bar decides what most of the Backoffice shows: Data, Functions, Servers, Game Rooms, API keys and so on all follow it. Environments are listed with their state, and only a Ready one can be selected.
The same separation applies outside the Backoffice: an API key belongs to one environment, and the CLI works in the environment of the key it signed in with.
Create an environment
Open New environment from the environment menu in the top bar, or from the Environments tab in project settings.
| Field | Rules |
|---|---|
| Name | 2–16 characters: lowercase letters, digits and single dashes, starting with a letter. Unique in the project. |
| Copy from another environment | Leave it off for an empty environment, or pick a Ready source to start from a copy. |
An empty environment is ready almost at once. A copy is made in the background, and its state shows how far it has got.
| State | Meaning |
|---|---|
| Creating… · Copying… | Being set up. It can't be selected or deleted yet. |
| Ready | In use. |
| Error | The copy failed; what it had copied is cleaned up. |
| Deleting… · Deleted | On its way out, see below. |
What a copy includes
A copy carries the project's content, not its people or history.
| Copied | Not copied |
|---|---|
| Data records | Players and their sessions |
| Schema | Analytics event history |
| Catalog and storefronts | Revoked keys |
| Secrets | The link that lets new code be deployed (see below) |
| Active API keys, with new secrets | |
| Functions, redeployed from their current builds |
Copied keys get new secrets nobody has seen
Each active key arrives with its name and type, but a fresh secret that is never shown. To use one in the new environment, rotate it to get a secret you can save.
A copy is read from the live source one part at a time, so changes made to the source while it is being copied may or may not be included. Copy from a quiet moment if you need an exact match. Functions that were never deployed in the source are skipped, and secrets bound without a value are left unmounted; the environment's row lists both.
Re-link deploys before shipping code to a copy. A copied environment starts with deploys of new code blocked. Its row is marked Deploys unlinked, and deploys fail with env_not_linked until you click Re-link deploys on the Environments tab. Functions copied from the source keep running in the meantime.
This is deliberate: the copy doesn't take over the source's branch bindings, and it can't be bound to a branch until you re-link it, so code meant for the source can never land in the copy by accident.
Delete and restore an environment
Delete an environment from its row on the Environments tab and confirm by typing its name. Its keys stop authenticating, its functions stop running, and its data, schema and catalog become unreachable.
You have ten seconds to undo. After that, the environment moves to Deleted environments, where its data is kept until someone acts:
| Action | Who | What happens |
|---|---|---|
| Restore | Owner or org admin | The environment comes back as it was. |
| Erase | Owner only | The data is deleted for good. |
An environment can't be deleted while it is still being created, while another environment is being copied from it, or when it is the project's last one.
Next steps
- API Key Management — keys for each environment
- Deploying with the CLI — ship functions and game servers to an environment
- Create a Project — project settings, slugs and deleting a project
Last updated on 15 Oct 2026