Skip to main content
Environments are the top-level organizational layer in GoDizzy. Every route collection belongs to an environment, and the environment determines who can see it and how it’s meant to be used. The hierarchy looks like this: 
Organization
└── Environments
      └── Route Collections
            └── Routing Rules

​
Environment types

One per organization. Visible to everyone on the team.The production environment holds your live routing configuration — the rules that govern real traffic from your agents and integrations. All organization members can view and edit it.Use production when you’re ready to route live requests. Collections in production count against your plan’s collection limit.
Production collections count toward your plan’s collection limit. Keep an eye on this when copying collections from other environments.

​
Comparison

ProductionStagingDevelopment
Quantity1 per org1 per org1 per user
VisibilityAll team membersAll team membersCreator only
Counts toward collection limitYesNoNo
Typical useLive trafficPre-production validationPersonal experimentation

​
When to use each environment

Development

Use your dev environment to build and test new routing rules. Point your agent at the collection URL and iterate freely — your changes are invisible to the rest of the team.

Staging

Promote configurations to staging once you’re confident in them. Run integration tests, simulate failure modes, and let the team review before production.

Production

Use production for live agent traffic. Flip individual rules between mock and proxy without changing your agent’s URL or code.

​
Soft deletion

When you delete an environment, GoDizzy performs a soft delete: the environment and all of its collections and rules are hidden from your dashboard and excluded from routing, but not permanently removed. This means accidental deletions are recoverable — contact support if you need to restore something.
Deleting an environment soft-deletes all of its route collections and routing rules as well. Requests to those collection subdomains will return a 404 after deletion.