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

A single-server deployment is an Optimizely Customized Commerce solution deployed to a single computer. You can scale Customized Commerce for single-server deployments, typically reserved for applications and websites with modest demands and requirements. The basic requirement for Customized Commerce is a database for storing customer, user, and site information that you can install on the same or separate server as the Customized Commerce web application. Consider this type of deployment a _non-distributed deployment_, because the application's layers and functionality reside in a single server.

Many tasks used to install Customized Commerce for development apply when you deploy to a single server. See the [installation instructions](🔗) to install and the [System Requirements.](🔗)

The following is a typical single-server deployment.

You can copy the entire installation of Customized Commerce from a QA/staging server and update the configuration files and IIS on the target server. Unlike a development or QA/staging server, configure the deployment server via IIS to be publicly accessible.

If you can connect and see the public front-end site on the deployment server, you successfully deployed Customized Commerce.