HomeDev GuideAPI Reference
Dev GuideAPI ReferenceUser GuideGitHubNuGetDev CommunityDoc feedbackLog In
GitHubNuGetDev CommunityDoc feedback

Depending on your DXP 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 [DXP 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.

  • **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.

  • **Production** – The _live_ environment where website _users_ perform authoring of content, using the Optimizely content publishing flow or projects; website _visitors_ can access public content. The Production environment scales automatically.

## Optimizely Search & Navigation

[Optimizely Search & Navigation](🔗) is included in Optimizely DXP. Each of the environments can exist in a multisite setup, and each will have their own Search & Navigation 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.


A Production environment continuously updates the Search & Navigation index from the indexing job. However, for other environments and only after you change conventions, you must manually index when needed so as not to impact the Production environment.

## 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.


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