Environments

Create and manage isolated environments for staging, production, and feature testing.

An environment is an isolated runtime context within a project. Each environment has its own set of services, deployments, and variables. Common examples are production and staging.

Switching environments

Use the environment selector at the top of the project canvas to switch the active environment. The canvas re-renders to reflect the services and statuses in the selected environment.

Viewing all environments

Go to Project Settings → Environments to see all environments in the project. Each row shows the environment name, creation date, and available actions.

Creating an environment

Go to Project Settings → Environments.
Click New Environment.
Enter a name (e.g. staging) and click Create.

The new environment starts empty. Add services from the canvas just as you would in any other environment.

Environments within the same project share the same service definitions. Variables, however, are scoped per-environment — allowing you to use different database credentials in staging vs production.

Renaming an environment

Go to Project Settings → Environments.
Click the three-dot menu next to the environment you want to rename.
Choose Rename, enter the new name, and confirm.

Deleting an environment

Deleting an environment permanently removes all its deployments and variables. This cannot be undone.

Go to Project Settings → Environments.
Click the three-dot menu next to the environment.
Choose Delete and confirm.

You cannot delete the last remaining environment in a project.

PR / ephemeral environments

Ephemeral environments are short-lived environments tied to pull requests or feature branches. They are created automatically when a PR is opened and deleted when it is closed.

Ephemeral environments are useful for testing changes in isolation before merging to the main branch.