Environments

Environments are isolated deployment targets within a project. Run multiple versions of your application simultaneously—production, staging, development—without them interfering with each other. Each environment maintains its own deployment history with full audit trails and rollback capability.

​

What is an Environment?

An environment is an isolated namespace where you deploy your application:

• Isolated Infrastructure - Each environment has its own services, volumes, and configuration
• Separate Secrets - Environment variables don’t leak between environments
• Independent Scaling - Production can have 5 replicas while dev has 1
• Version Control - Full deployment history with rollback to any previous state

Every project starts with a default production environment. Create additional environments as needed.

​

Common Environment Types

​

Creating an Environment

From the environment dropdown:

1. Click “Create New Environment”
2. Choose to fork an existing environment or start blank
3. Enter environment name
4. Deploy when ready

​

Environment Isolation

Each environment is completely isolated: Separate Namespaces:

• Services in “production” cannot communicate with services in “staging”
• Private networking only works within the same environment

Independent Configuration:

• Different environment variables per environment
• Different secrets (database passwords, API keys)
• Different resource allocations (CPU, memory, replicas)

Separate Deployments:

• Deploy to production without affecting staging
• Each environment has its own deployment history
• Rollback independently per environment

​

Environment Forking

Forking creates a complete, isolated copy of your infrastructure. All services, configuration, and volume definitions are duplicated to a new environment where you can experiment safely.

​

What Gets Forked

Copied:

• All services (containers and functions) with their images
• Resource allocations (CPU, memory, replicas)
• Networking configuration (HTTPS endpoints, TCP proxies)
• Volume definitions and mount paths
• Service connections and dependencies

Not Copied (for security/freshness):

• Environment variable values (keys are copied, values must be set)
• Volume data (volumes are created empty)
• Deployment history (starts fresh)
• Logs and metrics

​

After Forking

1. Set Environment Variables - Keys are copied but values are empty for security. Set passwords, API keys, and secrets.
2. Deploy - The forked environment starts undeployed. Deploy to provision infrastructure.
3. Populate Data - Volumes are empty. Load data from backups or seed manually if needed.

​

Fork vs. Create Blank

Fork when:

• Testing changes to existing infrastructure
• Need environment parity (staging matching production)
• Debugging issues requiring exact replication

Create blank when:

• Starting a new architecture from scratch
• Existing environments don’t match what you need
• Experimenting with a completely different setup

​

Switching Environments

1. Click the environment dropdown in the top-right
2. Select the environment
3. The canvas updates to show that environment’s infrastructure

​

Deleting Environments

​

Common Questions