Core Concepts | Multi-Experience Operations | Acquia Product Documentation

Multi-Experience Operations organizes your digital assets in the following hierarchy:

Codebase - The root container that holds your shared code
Sites - Logical representations of individual websites
Environments - Runtime configurations shared across sites
Site Instances - Concrete deployments of sites in specific environments

Component	Description	Key characteristics
Codebase	Indicates a Git repository with the shared code that powers multiple websites and is the foundation of your Multi-Experience Operations setup.	Single source of truth: All sites that use the codebase share the same code Version control: Connected to your Git repository for code management Scalable: Can support dozens or hundreds of sites Centralized updates: Code changes propagate to all associated sites
Site	Is an individual website that you operate on Cloud Platform and indicates a logical concept that encompasses all stages of development, testing, and production.	Logical representation: Represents your website concept, not a specific deployment Lifecycle management: Covers development, testing, and production phases Independent configuration: Each site can have unique settings and domains Shared codebase: Uses code from the parent codebase
Environment	Defines the runtime configuration where sites operate, are owned by the codebase, and can host multiple sites simultaneously.	Environment types: Production environments¶ Host live websites accessible to end users Optimized for performance and reliability Support custom domains and SSL certificates Include monitoring and alerting capabilities Non-production environments¶ Used for development, testing, and staging Support multiple development teams and workflows Can be created and deleted as needed Include debugging and development tools
Site instances	Is the concrete deployment of a site in a specific environment and represents the actual running website with its database, files, and domain configuration.	Concrete deployment: Actual running instance of your site Environment-specific: Inherits configuration from its environment Independent resources: Has its own database and file system Domain mapping: Can have custom domains and SSL certificates

Multi-Experience Operations vs traditional hosting solutions¶

Feature	Traditional Hosting	Multi-Experience Operations
Code Management	Separate repository per site	Single shared codebase
Deployments	Individual site deployments	Bulk deployments across sites
Consistency	Manual synchronization	Automatic consistency
Scaling	Linear complexity increase	Centralized management

Multi-Experience Operations vs Site Factory¶

Site Factory	Multi-Experience Operations
Supports limited governance across sites.	Enables enhanced governance and synchronization across sites.
Lacks flexibility in hosting configurations.	Supports flexibility in hosting configurations tailored to customer workflows.
Manages sites	Manages Drupal codebases.
Does not support independent code deployment for each site.	Supports independent code deployment for each site.
Does not support resource isolation for all of your sites.	Supports full resource isolation for all of your sites.
Cannot run different sites on different versions of code.	Runs different sites on different versions of code.
Requires technical expertise to fully provision a site in production.	Does not require a lot of technical expertise.

Did not find what you were looking for?

If this content did not answer your questions, try searching or contacting our support team for further assistance.

Multi-Experience Operations Support