Area: Episerver DXC Service
Applies to versions: Not applicable


This topic explains the environments in Episerver Digital Experience Cloud Service, and their usage. The environments are used for publishing and testing of code, content and databases, to prepare for final deployment to a production site.


Depending on your DXC Service setup and products included, you will have two or more environments between which deployment is done. You can deploy to Integration, Preproduction, and Production yourself. See Deploying and DXC Service self-deployment guide


Environment usage

The following scenarios are typical for the environments. The number of environments is based on the specific cloud package in your solution. See the Digital Experience Cloud Service Description for details.

  • Integration. Partners and customers deploy the full solution, as daily builds or continuous releases. You can validate initial integrations with external systems, perform functional testing, and add initial content for a first-time deployment. The integration environment has fixed configuration and no automatic scaling.
  • Preproduction. Used to test production deployment, and verify performance and operational functionality. You also can use it for UAT, load testing, or approved penetration testing. Preproduction scales automatically. Any content added in this environment is overwritten during an upgrade.
  • Production. The live environment where website users perform authoring of content, using the Episerver content publishing flow or projects; website visitors can access public content. The Production environment scales automatically. 

Episerver Find

Episerver Find is included in Episerver DXC Service. Each of the environments described above can be a multisite setup, and each of them will have their own Find index. In a multisite scenario, the sites share the same index, but each individual site has their own partition of the index, and a shared partition for shared content.

Environment-specific configurations

When you deploy to a production environment, ensure that the correct configurations are applied. See Environment configurations about how to set up environment-specific configurations.

Note: Make sure you never use credentials, tokens, or endpoints from a Preproduction environment in a Production environment.

Related topics

Last updated: Feb 04, 2019