---
title: Single-server deployment
slug: commerce-connect-13/docs/single-server-deployment
docTags: 
createdAt: 2026-07-23T09:44:51.000Z
---

A single-server deployment is an Optimizely Commerce Connect solution deployed to a single computer. You can scale Commerce Connect for single-server deployments, typically reserved for applications and websites with modest demands and requirements. The basic requirement for Commerce Connect is a database for storing customer, user, and site information that you can install on the same or separate server as the Commerce Connect 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 Commerce Connect for development apply when you deploy to a single server. See the [installation instructions](docId\:VuiU-K4aAR6ISGicFg4lk) to install and the [System Requirements.](docId\:Oe6v1ocXKbt40QjLVGoej)

The following is a typical single-server deployment.

![](https://api.archbee.com/api/optimize/BrbvVORKJ5iIeSMZye5kI/i7bJvOrElnzeIGdCVWrCw-20260723-094558.png "deploymentarchitecture.png")

You can copy the entire installation of Commerce Connect 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 Commerce Connect.