After extensive testing and several small UI refinements based on user feedback, the decoupled deployments feature is now out of beta and is officially supported by default for all new projects. This deployment strategy is now considered stable and production ready, providing teams with greater flexibility, faster deployment cycles, and improved management when working with multi‑site or multi‑repository implementations.
Why Decoupled deployment matters
Decoupled Deployments separate the CMS application from individual editing hosts, enabling:
Targeted deployments without triggering full CMS rebuilds
Independent codebases and repository structures for each editing host
Reduced compute and search index load, improving performance and lowering costs
Scalable multi‑site operations with isolated logs, clearer control, and faster iterations
A better developer experience, especially in organizations with multiple applications sharing one CMS
Editing hosts can now be configured to use separate Git repositories, giving teams the flexibility to isolate sites, streamline versioning, and align deployment flows with their preferred development and branching strategies.
What it means for new projects
From now on, all new SitecoreAI projects and environments automatically use decoupled deployments as it is enabled by default.
While you still can continue using the legacy Coupled Deployment model if needed, we do not recommend it. Future enhancements will primarily target the decoupled flow, so migrating ensures access to the full improvement set.
See how to create a new project
What it means for existing projects deployed with legacy coupled deployment
Current projects that were creating with the coupled deployments continue to work without requiring configuration changes. Redeployment of these projects remains coupled deployments.
We recommend to actively switch any existing coupled deployment projects to the new decoupled architecture using the Convert option in the project settings.