# Environments

An Environment is a named release lane under one App, for example `staging` or `production`.

Names are 1–50 characters, start with lowercase alphanumeric and otherwise use lowercase alphanumeric, `.`, `_` or `-`. Environment names are unique within an App.

Environments may be archived. New uploads require an active Environment; historical Builds remain readable according to access rules. A Build belongs to exactly one Environment and re-signed derivatives remain in the source Environment.

## Related

- [Hierarchy](/concepts/hierarchy)
- [Upload](/cli/upload)

## Plan limits

Free supports **2 Environments per Workspace**; Team supports **10 across all Apps**. Archived Environments still count, because they preserve historical Build classification. Deleting an unused Environment frees a slot; an Environment referenced by a historical Build cannot be deleted. A `409 quota_exceeded` response means the Workspace is full. Request an upgrade through support.

**Enterprise policy target:** Unlimited Environments. AppBarn does not yet offer an active Enterprise entitlement.
