Environment types
Production
Where your application lives and operates after launch. All final work is deployed here for your customers to access.
Staging
An identical replica of the production environment (not publicly accessible) used for user-acceptance testing (UAT) with real data volumes and user behavior simulation.
Testing
Where the QA team runs compatibility, integration, regression, and performance tests on code from the development environment.
Development
Configured for developer productivity with smaller resources and developer-specific tools. Constantly changing as new functionality is added.
Production environment
The production environment is where your application operates after launch. Before deploying code from development to production, two key activities must occur:- Testing — A separate testing environment enables QA teams to execute tests and verify system components in different scenarios.
- User-acceptance testing (UAT) — This is done on a staging environment that mirrors production, including live data volumes, data types, and user behavior.
Staging environment
A staging environment is an identical replica of the customer’s production environment, typically containing sanitized real production data. It is hosted identically to production servers and uses the same setup and update operations. Testing on a staging environment provides the most reliable way to check code quality before production deployment. This is considered a must for enterprise applications.Testing environment
The testing environment enables QA engineers to run complex and time-consuming tests — compatibility, integration, regression, and performance — without disrupting the development process.Development environment
The development environment features smaller resources than production and developer-specific tooling. It is constantly changing as new functionality is added, making it unsuitable for time-consuming QA tests.Environment plans
Not all OroCommerce Enterprise Edition licenses include staging and testing environments. However, customers can always add development and testing environments for an additional cost. The table below outlines features available in different OroCloud environment types:| Feature | Production | Staging | Testing | Development |
|---|---|---|---|---|
| Support | 24x7 | 5x8 | 5x8 | 5x8 |
| Secure access | Yes | Yes | Yes | Yes |
| Base monitoring | Yes | Yes | Yes | Yes |
| Logs access | Yes | Yes | Yes | Yes |
| SMTP relay | Yes | Yes | Yes | — |
| Email sending restrictions | — | Yes | Yes | — |
| Redundancy | Yes | Yes | — | — |
| CDN | Yes | Yes | — | — |
| Custom domain | Yes | Yes | — | — |
| Advanced monitoring | Yes | Yes | — | — |
| Backups | 1 year | 2 weeks | 1 week | — |
| Disaster recovery | Yes | — | — | — |
| SLA | Yes | — | — | — |
| App dev mode | — | — | Yes | Yes |
| Live data | Yes | — | — | — |
To use different default configurations based on the application environment, see the Configuration Environments in Symfony documentation.