--- title: "Using Site Factory Stacks" date: "2024-02-14T06:18:38+00:00" summary: "Efficiently manage multiple website groups with Site Factory Stacks. Learn how to centralize governance, customize codebases, and streamline development for diverse web properties within a single subscription." image: type: "page" url: "/site-factory/using-site-factory-stacks" id: "51df03e5-a311-4d29-9672-e1d0f2cd3b29" --- With Site Factory, you can centrally manage websites using the same codebase and region—but what if some of your websites are fundamentally different from the rest? If you have discrete groups of websites sharing a set of basic, fundamental differences between the groups, you can use _stacks_ to manage your websites in a single Site Factory subscription. Stacks use the same codebase on the same managed, dedicated infrastructure for a group of websites. Stacks can be helpful in the following situations: * _Different Drupal core_: You may have some websites based on Drupal 9 or later, and others remaining on Drupal 7. * _Different installed modules_: You may have websites with fundamentally different business purposes, and each set of websites needs a different set of custom and contributed Drupal modules. Stacks in Site Factory enable you to develop and maintain each group separately while still managing the websites in the same subscription and Site Factory Management Console. Stacks provide you with much more flexibility, along with unified governance, assembly, and delivery. Getting started with stacks --------------------------- Each Site Factory subscription starts with a single stack. To add more stacks, contact your Acquia Account Manager. There is an additional cost for each stack. Acquia will provision your new stack, and then let you know when the stack is ready for you to begin development. Your first stack will be named **Stack 1**, with any subsequent stacks named in numeric order: **Stack 2**, **Stack 3**, and so forth. Although you cannot rename a stack, you can [contact Acquia Support](/service-offerings/support#contact-acquia-support) to request Acquia add a description to an existing stack. Websites managed as part of a stack share the same [default subdomain pattern](manage/domains.html#acsf-default-domain), such as `*.customer.acsitefactory.com`. The unique subdomain pattern may change if different load balancers are utilized by newly added stacks. New stacks must always be provisioned in the same region as your initial stack. To create Site Factory sites in an alternate region, contact your Acquia Account Manager for creating a new Site Factory application. Site Factory doesn’t support [Multi-Region](/acquia-cloud-platform/manage-apps/multiregion) Failover. Note Your stacks will all share the same Site Factory Management Console with your first stack. Domain names cannot be changed after provisioning, so if your stacks need significantly different domain names, discuss domain name strategies with your Account Manager when requesting a new stack. Viewing your repository information ----------------------------------- After Acquia provisions your stack, you can sign in to the Cloud Platform interface to prepare for developing websites on your new stack. 1. [Sign in to the Cloud Platform interface](/acquia-cloud-platform/cloud-ui) as a user with [platform admin](/site-factory/manage/users/admin/platform-admin) permissions. 2. Select your application. 3. Click **Actions** > **View Git Information** to display code repository information for your stack. Working with stacks ------------------- After adding additional stacks, you will still manage all of your Site Factory websites using the same Site Factory Management Console, regardless of which stack they belong to. When you perform many actions in the Site Factory Management Console, you will select which stack you want to work on. For example, you can perform the following actions on a per-stack basis: * [Creating sites and site groups](/site-factory/manage/website/groups-create) * [Managing cron tasks using the management console](/site-factory/manage/preferences/tasks/factory) * [Managing subscription usage](/site-factory/manage/preferences/usage) * [Performing a production deployment](/site-factory/workflow/deployments/steps) When [copying website data to non-production environments](/site-factory/workflow/staging#acsf-copy-data-nonprod), selecting the **Wipe target environment** checkbox will wipe all stacks on the target environment. ### Identify the stack for a website If you have more than one Site Factory stack, you can identify what stack a website belongs to by performing the following steps: 1. [Sign in](/site-factory/login) to the Site Factory Management Console as a user with the [platform admin](/site-factory/manage/users/admin/platform-admin) or [site builder](manage/users/admin/site-builder.html) role. 2. Click **Sites**. 3. Scroll to or [filter for](/site-factory/manage/website/filter) the website with the stack that you want to identify. 4. Point to the **Information** icon to display a tooltip that contains the stack information. ![The information card with stack details for a website](https://acquia.widen.net/content/2rstun1yii/png/site-factory_identifying-stacks.png?crop=false&position=c&color=ffffffff&u=soxprt&w=450&h=550) ### Updating stack labels You can update stack labels in Site Factory through the **Stack Management** setting on the **Administration** tab. 1. [Sign in](/site-factory/login) to the Site Factory Management Console. 2. In the top menu, click **Administration**. 3. Click the **Stack Management** link to access stack labels. ![Updating stack labels on Administration tab](https://acquia.widen.net/content/rvxkklymkp/jpeg/site-factory_update-stacks.jpeg?position=c&color=ffffffff&quality=80&u=u1mnox) 4. Edit the stack name and description. 5. Click **Save**.