--- title: "Scale software delivery without owning the runner fleet" url: https://daily.dev/posts/scale-software-delivery-without-owning-the-runner-fleet-r08bafyst source_url: https://about.gitlab.com/blog/hosted-runners-for-gitlab-dedicated type: article source: "GitLab" published: 2026-08-25T11:43:33.529Z updated: 2026-08-25T11:43:58.734Z tags: ["cicd", "gitlab", "devsecops"] reading_time: 5 upvotes: 1 comments: 0 language: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Scale software delivery without owning the runner fleet **[GitLab](https://daily.dev/sources/gitlab)** · 5 min read · 1 upvotes · 0 comments ## Summary GitLab has launched Hosted Runners for GitLab Dedicated, a fully managed CI execution add-on that provisions, patches, and scales runner infrastructure inside a customer's own GitLab Dedicated region. Each job runs in an isolated, newly provisioned VM deleted after completion, and runners are self-serviceable through Switchboard. The offering ships in five machine sizes (Small through 2X-Large) on Linux x86-64 and Arm64, aiming to remove the operational burden of balancing runner over- and under-provisioning from platform teams. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What machine sizes are available for Hosted Runners on GitLab Dedicated? Five sizes are offered: Small (2 vCPUs, 8 GB memory, 30 GB storage), Medium (4 vCPUs, 16 GB, 50 GB), Large (8 vCPUs, 32 GB, 100 GB), X-Large (16 vCPUs, 64 GB, 200 GB), and 2X-Large (32 vCPUs, 128 GB, 200 GB). They run on Linux x86-64 and Linux Arm64, with linux-small-amd64 as the default tag. _daily.dev helps teams sizing CI runner fleets track infrastructure options like these as they roll out._ ### How does GitLab isolate CI jobs when using Hosted Runners for GitLab Dedicated? Each CI job runs inside a newly provisioned, isolated virtual machine that is deleted once the job completes, and the runner fleet itself is isolated from other customers. Runner creation and management happen through Switchboard, the GitLab Dedicated management console, making the setup self-serviceable for platform teams. _Platform teams evaluating CI isolation approaches can follow updates like this on daily.dev._ ## Similar posts on daily.dev - [Premium self-hosted runners are generally available](https://daily.dev/posts/premium-self-hosted-runners-are-generally-available-ovb4xrboa) · Atlassian · 0 upvotes · 0 comments - [Autoscalable GitLab runners on AWS EC2](https://daily.dev/posts/autoscalable-gitlab-runners-on-aws-ec2-myamn1tth) · Palark Blog · 1 upvotes · 0 comments --- Tags: [#cicd](https://daily.dev/tags/cicd), [#gitlab](https://daily.dev/tags/gitlab), [#devsecops](https://daily.dev/tags/devsecops) [View this post on daily.dev](https://daily.dev/posts/scale-software-delivery-without-owning-the-runner-fleet-r08bafyst)