Environments

Environments are a first-class entity in uRun — prod, staging, dev, or whatever you name them. They isolate apps and sessions so a deploy to staging never touches prod's deployment or traffic. Secrets and capacity are scoped to the org/app, not per-environment — a secret or capacity pool set for an app applies across all of that app's environments.

Where they live

• The header org / environment switcher changes your active environment; the whole console re-scopes to it.
• Settings → Environments lists your environments.
• Create a new one from the switcher's Create Environment modal.

How environments flow through the product

• CLI — most urun app commands take --environment / --env (default main). See Manage apps.
• Deploys — an app deploys into an environment; the same app can exist in prod and staging with separate releases. Capacity pools are shared across an app's environments (see the callout above).

When to use it

• Stage a new app version in staging and exercise it in the Playground before promoting to prod.
• Keep a dev environment for experimentation that's fully isolated from production traffic.