Environments

An environment is an isolated instance of a project's services, configuration, domains, databases, and release state.

Environment types

Switch environments

Use the environment selector in the project breadcrumb. The canvas and service panel update to the selected environment. Check the breadcrumb before changing variables, creating a database, stopping services, or publishing a domain.

Create an environment

1. Open the environment selector.
2. Choose New environment.
3. Enter a name and select a supported persistent type.
4. Confirm the base environment when offered.

The new environment receives its own canonical identity. Copying topology does not imply copying production secrets, database contents, or persistent volumes.

Preview environments

Eligible pull requests can create a stable preview identity that updates when the pull request changes and is removed after close or expiry.

By default:

• fork pull requests are denied;
• production secrets and data are not copied;
• artifacts are pinned by digest;
• generated domains are separate from production; and
• cleanup is retried by the platform if a workflow close job does not run.

Environment-aware changes

These values are scoped to the selected environment:

• service instances and current releases;
• service and shared variables;
• managed databases;
• generated and custom domains;
• private network endpoints;
• deployments, logs, and metrics; and
• stop/redeploy state.

Project members and outbound-webhook definitions are project-wide, though delivered events identify the environment involved.

Production checklist

Before deploying production:

1. Confirm the production environment in the breadcrumb.
2. Verify required secrets exist.
3. Confirm the resource quote and active plan.
4. Use immutable artifacts from the reviewed source revision.
5. Check health and generated-domain behavior before switching custom traffic.