Run agentic software delivery inside the boundaries you already trust
Many enterprises choose GitLab Dedicated for a clear reason: a single-tenant instance, managed by GitLab, in a cloud region they select.
That isolation already covers source code, project data, and the software development lifecycle they run on GitLab.
GitLab Dedicated customers can now deploy the AI Gateway for the GitLab Duo Agent Platform inside their single-tenant SaaS infrastructure, so AI-processed data stays in their environment and chosen region. GitLab Dedicated as the critical infrastructure for software delivery GitLab Dedicated is deployed in your preferred AWS region, and hosted and maintained by GitLab. You can bring your own encryption keys.
No private cloud installation required. GitLab operates the instance, including high availability and disaster recovery, and maintains 99.9% monthly availability for core services. Updates to GitLab Dedicated follow a stability-first cadence, with instances on the previous minor version (N-1) relative to the current GitLab release.
That is the infrastructure organizations already trust when they scale software delivery under audit: guardrails you can take to a regulator, SaaS operations you do not staff, and an availability target that holds when the platform is in the critical path.
Trust should travel with every agent Agentic workflows demand more from your software development lifecycle beyond the AI coding: increased pipeline volume, greater risk for vulnerabilities introduced, context that needs to travel with every agent and flow, among others.
The isolation, residency, and service-level requirements that already apply to GitLab Dedicated should apply to that inference path too, especially with growing adoption of agentic software development. Adopt AI while staying compliant Here is what's new with the introduction of AI Gateway for GitLab Dedicated: Keep AI processing in the tenancy.
The AI Gateway runs in the Dedicated single-tenant environment, aligned with data residency. Bring your own models. Connect models you control so inference follows your policy, not a one-size default outside your region. Unlock Duo Agent Platform where you already run GitLab.
Agentic work becomes available under the Dedicated deployment model your auditors already understand. GitLab Dedicated customers using GitLab Duo Agent Platform can connect the AI Gateway to Amazon Bedrock as their model backend, so inference stays in their AWS region. Or you can use your own preferred model providers.
If you have specific model requirements, data classification rules, or existing commitments, you can identify models hosted in Amazon Bedrock for your team to use with GitLab Duo Agent Platform. All capabilities of Duo Agent Platform, including its top use cases such as automating custom code reviews, fixing failed pipelines, and security analysis can now run against your chosen models.
Start your agentic software delivery on GitLab Dedicated If you are on GitLab Dedicated, review how to add a self-hosted model, validate model connectivity in a non-production project, and then expand agentic workflows under your existing change controls. If you are not using GitLab Duo Agent Platform today, you can start with a free trial.
If you are an existing subscriber to GitLab Dedicated, you can get started simply by turning on Duo Agent Platform and start using the GitLab Credits that are included with your subscription.