Environment definitions
When a customer is onboarded, four specific environments are provisioned and dedicated for you. Each environment has a specific purpose and role in the overall development and deployment lifecyle of experiences, content, assets and applications built on the platform.
The environments are summarized below:
| Label | Type | Purpose | High-Avail | Monitoring |
|---|---|---|---|---|
| dev | Development | Development of customer-owned experiences & applications | No | Basic |
| qa | QA | Integration testing of customer-owned experiences & applications | No | Basic |
| auth | Authoring | Authoring and validation of content and digital assets | Yes | Full |
| prod | Production | Delivery of content, applications & experiences to both internal & external audiences | Yes | Full |
This enables distinct environments in which your development and delivery lifecycle activities can be focused and managed, with a clear path for promotion from development through production release.
Depending on the specific offerings purchased by each customer, your environments will all contain the same combination of the requisite component applications and services, in an integrated deployment and security model.