Drupal Sites Beta Adds Hostname Support for Sub-Sites
Maintainers released Sites 1.0.0-beta3 on 9 November 2026, allowing sub-sites in a shared Drupal installation to use independent hostnames and introducing a cached index for hostname and path-prefix resolution. The release notes also describe changes to site membership, environment settings and public APIs that require care when upgrading. Several companion modules received related beta updates.
Sites provides a plugin-based approach to managing multiple websites within one Drupal installation and database. Its site contexts scope content, configuration, URL generation, permissions and languages without requiring a separate Drupal instance for each website. Unlike a conventional Drupal core multisite deployment, those sites share a database; the established Domain project also provides a shared-database approach, so the architecture is not new to Drupal.
Beta3 allows a sub-site to have its own hostname. When a sub-site is accessed through its main site's hostname, it still requires its path prefix. A site type can permit main sites, sub-sites or both. The release introduces a single cached host index for hostnames, prefixes and sub-sites, replacing several earlier lookup methods. It also consolidates administration into a site list at /admin/sites, grouped by main site and limited to sites the current account can access, with compact and recently opened views.
The update changes how environment-specific list settings, including hostname aliases, work. An environment's list now replaces the site's corresponding list rather than being appended to it. The maintainers say an update migrates the lists previously shown by each environment into its own stored rows to preserve the visible result after upgrading. Implementations that depend on inherited lists should nevertheless check their environment configurations and hostname resolution.
Site membership behaviour has also changed. When a sub-site is configured to be run by its main site's people, the main site's content members and role holders now count as members of that sub-site. The release notes say this affects preview access, checks involving a site's own people and site-scoped Views. Teams should test these permission and membership paths, particularly where main sites and sub-sites serve different audiences.
Administrators upgrading to beta3 must run the database updates using drush updb or drush deploy. According to the maintainers, nine post-updates rename, merge or materialise settings, while several services have changed constructor arguments. The release explicitly conflicts with versions of sites_simple_sitemap earlier than 1.0.0-beta3 and sites_shield earlier than 1.0.0-beta2; these companion modules should be upgraded in the same Composer update operation.
Custom integrations may also require code changes. Methods for querying site IDs by hostname or prefix, resolving hostnames and retrieving sub-site IDs were removed from SitePluginManagerInterface in favour of SiteHostIndexInterface, exposed through the sites.host_lookup service. Several user-site access methods were replaced by SiteMembershipInterface::participatedSiteIds(), and SiteProxy::queryAlter() was removed. These changes were made without deprecation in this prerelease cycle, according to the beta3 notes.
The updated public APIs also include SiteInterface::getSiteEntity(), SiteSettingsInterface::keys(), PreviewFormState and SiteAspectBulkFormInterface. Code marked @internal may change without notice. The project provides InternalSitesApiGuardTrait to help companion modules detect reliance on such APIs.
Companion releases extend the shared-database setup. Sites Clone updates hostname handling when duplicating sub-sites and supports copying settings and selected content. Sites Simple Sitemap adds sitemap handling for sub-sites with their own hostnames, while Sites Diff enables comparisons of site-specific content overrides using Drupal's Diff module.
Other companion integrations address site-specific redirects through Sites Redirect, HTTP Basic Authentication through Sites Shield, automation with Sites ECA and diagnostics through Sites Devel. The wider ecosystem includes Sites Linkit, Sites Robots.txt and llms.txt sites. These modules serve different functions and should not be assumed to share the same release status or compatibility guarantees.
Beta3 also addresses language prefixes in site URLs, preview-switcher language fallback, absolute links between different sites, and preview access to Layout Builder and module administration routes. The maintainers report performance improvements from caching the hostname index and reading some alias and settings information once per request rather than once for every site. The changes describe intended implementation behaviour; the release notes do not supply independent performance benchmarks.
Sites 1.0.0-beta3 is compatible with Drupal 11.2 and later versions of Drupal 11, as well as Drupal 12. It remains a beta release without a supported stable version. Organisations considering it for production should test hostname negotiation, site access, cross-site caching, language handling, environment configuration and upgrade paths, including the compatibility of companion modules. Further details are available in the project documentation.
