Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Provision Environments-OLD

Updated on July 18, 2019

Typically, a project would use at least the following environments:

  • Development – primary application development and DCO environment
  • Test – environment to support the system test process
  • Staging – environment to support performance and scale testing; it also serves as the staging region for production
  • Production
  • (optional) Dedicated User Acceptance Environment (UAT)


You may need more depending on your application size and/or testing requirements. It is important to have at least a development environment ready for day 1 of the project with the remaining environments established over a period of time that suits the project and the business.

Under Pega’s Cloud Choice capability, Pega software can run where you want – Pega Cloud – a Client’s own Cloud – or a partner’s Cloud – or a hybrid blend of public and private, or a Clients on premise instance. You can separate application development from your production environments and migrate applications between them. This Cloud-based approach supports continuous deployment and integration, built in a DevOps pipeline.

No matter the type of hosting architecture or the number of environments used, it is imperative that the various environments stay in sync. Pega has the capability to logically segment the rules that a user sees, which means a test user can execute a stable set of rules in a development environment. This is a good way to do early testing without needing to migrate rules between environments. For more information, talk to your Lead System Architect.



The environments should include at least Development to start and will eventually include Test, Staging, Production, and others as needed.



Pega offers Cloud options and Cloud instances, sized to suit the number of end users and the number of virtual environments. Some or all of the following environments will typically be provided:

  • Standard sandbox – development, testing and User Acceptance Testing (UAT) (not for production).
  • Large sandbox – pre-production, staging and performance testing.
  • Production – a scaled environment that supports the production deployment of licensed Pega Platform, applications, and transactional use cases.
  • Production mirror – separate sandbox service that provides an architectural replica of the scaled production environment that can be used for production staging, scale benchmark testing, and load performance testing.


The Pega Cloud team will work with your technical experts to determine the best Cloud setup for you. Considerations such as data management, security, availability, network integrations, and backup will be taken into account to establish the environments.

The Pega Cloud team can provide additional options that are available with regards to environments, VPN integration and other Cloud services. Please refer to the Pega Cloud product area on PDN for more information.



If the solution is to be deployed within your premises on your IT infrastructure, then coordination between Pega and the client’s IT team is required. The Pega platform Support Guide details the supported versions of hosting software needed to run Pega (e.g. Operating systems, Databases and Application Servers). Using the information from the Support Guide, your IT team will obtain the relevant hardware and software required to host the Pega solution. Pega will assist by providing sizing and other application specific information required.

Once you set up the physical hardware, application servers and databases, the technical lead will either install or assist you with the installation of the Pega software as desired.



Pega captures requirements directly into the system to give early versions of working software. This is different to traditional non-Pega projects where it is usual to document requirements for many weeks or months before seeing working software.

By having a development environment available day 1, you can quickly build and show draft flows and screens to shape the thinking on how the system should work.



The environments should be provisioned before any development begins.  This is because Pega is an experiential development platform so development should occur directly in the test environment.  While it is possible to do some development on a laptop, this will only work in the short-term and is not ideal.  The Pega best practice is that your environments are provisioned before the project kickoff and before the team begins any development work.



Pega’s recommendation is to start on a Pega Cloud environment, as that is faster to provision than an on-premise install.

For Cloud based implementations, environments can be provisioned in a day by raising the appropriate request with Pega’s Cloud team once any commercial agreements are completed.

For on premise implementations, you may need to purchase and install new physical servers, which require longer lead times. For most organizations, this can take several weeks for a hardware order to be placed and for the hardware to be delivered.


Pega Cloud information.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us