Scale software delivery pipelines in isolation without owning the runner fleet

Published on: August 25, 2026 3 min read GitLab provisions, patches, and scales hosted runners in your GitLab Dedicated region, moving maintenance off your platform team. Many enterprises choose GitLab Dedicated for a clear reason: a secure and compliant, single-tenant GitLab instance, managed by GitLab. As agentic workflows drive more pipeline volume, full data isolation and runner infrastructure operational burden become a challenge. This leads to the question, “Does owning the runner fleet still make sense?” With GitLab Dedicated, there is no more need to provision, patch, build, and scale your own runner fleet. Hosted Runners for GitLab Dedicated handles the heavy lifting and delivers a seamless experience across the entire software development lifecycle so your team can focus on shipping. Hosted Runners for GitLab Dedicated provides a runner fleet isolated from other customers. To support job-level security, each job runs in a newly provisioned, isolated VM that is deleted after the job completes. We provide a scalable and highly reliable runner fleet to support your bursty CI demands and resiliency needs. Creating and managing runners is self-serviceable through Switchboard (GitLab Dedicated management console). Pipeline load can be unpredictable. To account for this, runner infrastructure can be over-provisioned to give developers the best experience and maintain low wait times. But this drives up the infrastructure cost. Conversely, under-provisioning can save on infrastructure cost, but your developers will waste time waiting for their CI jobs to be picked up. Efforts to fine-tune this balance can monopolize your platform team’s time. Hosted Runners for GitLab Dedicated is a fully managed CI execution SaaS offering. It’s backed by a high-performing and reliable runner infrastructure. Key benefits include: See Hosted Runners for GitLab Dedicated in action: Hosted Runners for GitLab Dedicated is available in Linux x86-64 and Linux Arm64 architecture in the following machine sizes. | Size | vCPUs | Memory | Storage | Example tag (x86-64) | |---|---|---|---|---| | Small | 2 | 8 GB | 30 GB | linux-small-amd64 (default) | | Medium | 4 | 16 GB | 50 GB | linux-medium-amd64 | | Large | 8 | 32 GB | 100 GB | linux-large-amd64 | | X-Large | 16 | 64 GB | 200 GB | linux-xlarge-amd64 | | 2X-Large | 32 | 128 GB | 200 GB | linux-2xlarge-amd64 | Hosted Runners for GitLab Dedicated is an add-on to GitLab Dedicated. Reach out to your GitLab account team to get started. If you want to learn more about how GitLab Dedicated can support your compliance posture, talk to our team. Need inference inside the same GitLab Dedicated boundary? Learn more in our companion article on the single-tenant AI Gateway. Are you just managing tools or shipping innovation? Quiz will take 5 minutes or less Enjoyed reading this blog post or have questions or feedback? Share your thoughts by creating a new topic in the GitLab community forum. Share your feedbackStart building faster today See what your team can do with the intelligent orchestration platform for DevSecOps.