> ## Documentation Index
> Fetch the complete documentation index at: https://docs.godizzy.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Environments

> GoDizzy's self-serve workflow uses shared production and private development environments to isolate routing configs.

Environments are the top-level organization layer for routing configuration.

```text theme={null}
Organization
└── Environment
      └── Route Collection
            └── Routing Rule
```

## User-visible environment types

<Tabs>
  <Tab title="Production">
    **Shared across the organization.**

    Use production for shared or live traffic. Organization members can see and edit it.
  </Tab>

  <Tab title="Development">
    **Private to the creator.**

    Use development for experimentation, new rule authoring, and risky changes before you move a collection into production.
  </Tab>
</Tabs>

## Comparison

|                      | Production                         | Development        |
| -------------------- | ---------------------------------- | ------------------ |
| Visibility           | Shared with org members            | Creator only       |
| Typical use          | Shared validation and live traffic | Personal iteration |
| Safe for experiments | Usually no                         | Yes                |
| Can be copied into   | —                                  | Production         |

## Recommended usage

<CardGroup cols={2}>
  <Card title="Development" icon="flask">
    Build and test new collections and routing rules in isolation.
  </Card>

  <Card title="Production" icon="bolt">
    Promote collections you want teammates or live traffic to use.
  </Card>
</CardGroup>

## 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.