Drupal Hosting Services

The Vendor is required to provide to furnish the university with enterprise-grade Drupal hosting services.
- Hosting and Running Drupal Sites
•    The platform must provide a fully managed hosting environment suitable for deploying and running Drupal sites at scale. Specifically:
•    Each site or group of sites must run in a stable, production-ready environment that includes:
•    Either an apache or nginx web server
•    A PHP runtime
•    Either a mariadb or MySQL database server
•    File storage for public and private files
•    Built-in https termination and automated certificate provisioning and renewal for all domains / environments
•    A reverse proxy cache layer that supports automatic cache entry invalidations using cache tags / surrogate keys
- The university must not be responsible for deploying, patching, or managing this infrastructure.
- The platform provides an administrative dashboard for creating and managing sites that supports role-Based access.
- Orchestrating updates across sites from a shared codebase
•    The platform must support the university’s need to manage and deploy code updates from a shared Drupal distribution to hundreds of connected sites. Specifically:
o    The platform must allow code updates to be made centrally and deployed across at least 600 sites.
o    It must provide a staging and production environment for the shared distribution to support testing and validation prior to rollout.
o    It must support site-level additions (modules, themes, and configuration) that do not prevent or block receipt of upstream updates.
o    It must support automated and scripted execution of Drupal specific configuration management workflows (e.g., Drush Config-import, Config-split: import) as part of the update process.
- Supporting site-level customization within a shared codebase model
•    The platform must support a shared Drupal distribution model in which individual sites can introduce their own custom code and configuration without breaking their connection to the central distribution. Specifically:
o    Each site must be able to add and override modules, themes, and configuration.
o    These customizations must not prevent the site from receiving future updates from the central distribution
- Integration with version control and ci/cd workflows
•    The platform must support GIT-based development workflows and enable integration with modern ci/cd tooling. Specifically:
o    All code deployments must be version-controlled and support integration with GitHub.
o    The platform must allow the university to automate platform operations in ci/cd workflows utilizing a platform-specific cli tool or API integration that can include testing, validation, and deployment steps for individual sites or groups of sites across environments.
o    It must support pre- and post-deployment hooks and automation mechanisms to run arbitrary scripts (e.g., Drush commands) during updates.

- Contract Period/Term: 3 years
- Pre-Proposal Conference Date: September 09, 2025
- Questions/Inquires Deadline: September 16, 2025