Workloads, responsibility, reliability, and scale
Architecture Design
Start with the work GitLab needs to support, then choose who operates each part, what components can reach, how demand is handled, and how the system recovers when something fails.
Architecture library
Designs you can adapt
Each entry connects a usage pattern to component placement, access, operating responsibility, capacity, failure behavior, alternatives, and practical checks.
Architecture
Runner trust zones for mixed CI/CD workloads
Route unreviewed, protected-build, and deployment jobs to separate worker pools whose credentials and network access match the work they perform.