GitLab Launches Isolated Hosted Runners for Dedicated
π‘Scale bursty AI CI workloads with isolated VMs without operating your own runner fleet.
β‘ 30-Second TL;DR
What Changed
Each CI job runs in a newly provisioned, isolated VM that is deleted after completion.
Why It Matters
Enterprise AI and software teams can scale agentic or high-volume CI workloads without building and maintaining their own runner fleet. The model may reduce platform-operations overhead and queue delays, while consumption pricing makes cost monitoring essential.
What To Do Next
Evaluate Hosted Runners for GitLab Dedicated in a representative AI CI project, measuring queue time, GitLab Credits consumption, and PrivateLink connectivity before migration.
Key Points
- β’Each CI job runs in a newly provisioned, isolated VM that is deleted after completion.
- β’The single-tenant runner fleet supports the same data residency and compliance requirements as GitLab Dedicated.
- β’Runners can securely connect to internal registries, secret managers, and deployment targets through AWS PrivateLink.
- β’Reserved capacity, autoscaling, and a 99.9% uptime SLA target predictable performance for bursty workloads.
- β’Usage can be tracked through the GitLab Credits Dashboard and billed through GitLab Credits.
Weekly AI Recap
Read this week's curated digest of top AI events β
πRelated Updates
AI-curated news aggregator. All content rights belong to original publishers.
Original source: GitLab Blog β
This is a summary, not the original. Read the source, or get the weekly briefing.
Weekly AI briefing
One email a week. Unsubscribe anytime.