Skip to main content
Environments are the top-level organization layer for routing configuration.
Organization
└── Environment
      └── Route Collection
            └── Routing Rule

User-visible environment types

Shared across the organization.Use production for shared or live traffic. Organization members can see and edit it.

Comparison

ProductionDevelopment
VisibilityShared with org membersCreator only
Typical useShared validation and live trafficPersonal iteration
Safe for experimentsUsually noYes
Can be copied intoProduction

Development

Build and test new collections and routing rules in isolation.

Production

Promote collections you want teammates or live traffic to use.

Environment creation constraints

A few limits are enforced in code:
  • Free-plan organizations can be blocked from creating additional environments for a domain once the domain-level free-tier cap is hit.
  • Visibility rules differ by type: production is organization-visible, development is creator-only.

Deletion behavior

Deleting an environment soft-deletes its collections and rules. Requests to those collection URLs stop resolving until the data is restored.