---
url: 'https://dxpr.com/markdownify/taxonomy/term/1021'
title: 'Run it in production | DXPR'
author:
  name: Anonymous
updated: '2026-10-23T14:31:17+00:00'
copyright: 'Copyright DXPR. All rights reserved.'
type: website
summary: "Keep a live site fast and its builder content under control across environments. Pick the row that matches the job in front of you. I want to ... Use Needs see which assets load for visitors and what to measure Performance Nothing extra know what to clear after a change Caching Drush run several sites from one codebase Multisite installations A Drupal multisite setup move builder content between environments Content staging Access to each environment decide what goes in git and what stays in the database Version control Nothing extra build, test and deploy the module in a pipeline CI/CD integration A CI service Which should I use Builder pages live in the database, while settings live in configuration and code. Version control and content staging explain that split; read them before your first deployment. Performance and caching matter once the site is live. What's next? Access control for managing who can edit to continue exploring DXPR Builder."
tags:
  - 'Manage the site'
image: 'https://dxpr.com/themes/custom/dxpr_com/images/dxpr-share-card.jpg'
published: true
og:
  site_name: DXPR
  'image:alt': 'DXPR, powered by Drupal: AI-powered Drupal for marketers.'
---
## [Run it in production

 ](/hc/documentation/learn-dxpr-builder/manage/production)

Keep a live site fast and its builder content under control across environments. Pick the row that matches the job in front of you.

| I want to ... | Use | Needs |
|---|---|---|
| see which assets load for visitors and what to measure | [Performance](/hc/documentation/learn-dxpr-builder/advanced/performance) | Nothing extra |
| know what to clear after a change | [Caching](/hc/documentation/learn-dxpr-builder/advanced/caching) | Drush |
| run several sites from one codebase | [Multisite installations](/hc/documentation/learn-dxpr-builder/advanced/multisite) | A Drupal multisite setup |
| move builder content between environments | [Content staging](/hc/documentation/learn-dxpr-builder/advanced/content-staging) | Access to each environment |
| decide what goes in git and what stays in the database | [Version control](/hc/documentation/learn-dxpr-builder/advanced/version-control) | Nothing extra |
| build, test and deploy the module in a pipeline | [CI/CD integration](/hc/documentation/learn-dxpr-builder/advanced/ci-cd) | A CI service |

## Which should I use

Builder pages live in the database, while settings live in configuration and code. Version control and content staging explain that split; read them before your first deployment. Performance and caching matter once the site is live.

## What's next?

[Access control for managing who can edit](/hc/documentation/learn-dxpr-builder/manage/access) to continue exploring DXPR Builder.