[{"data":1,"prerenderedAt":855},["ShallowReactive",2],{"/en-us/blog/ultimate-guide-to-migrating-from-aws-codecommit-to-gitlab":3,"navigation-en-us":50,"banner-en-us":458,"footer-en-us":468,"blog-post-authors-en-us-Tsukasa Komatsubara|Darwin Sanoy|Samer Akkoub|Bart Zhang":708,"blog-related-posts-en-us-ultimate-guide-to-migrating-from-aws-codecommit-to-gitlab":760,"blog-promotions-en-us":792,"next-steps-en-us":845},{"id":4,"title":5,"authorSlugs":6,"body":11,"categorySlug":12,"config":13,"content":17,"description":11,"extension":35,"isFeatured":15,"meta":36,"navigation":15,"path":37,"publishedDate":26,"seo":38,"stem":43,"tagSlugs":44,"__hash__":49},"blogPosts/en-us/blog/ultimate-guide-to-migrating-from-aws-codecommit-to-gitlab.yml","Ultimate Guide To Migrating From Aws Codecommit To Gitlab",[7,8,9,10],"tsukasa-komatsubara","darwin-sanoy","samer-akkoub","bart-zhang",null,"product",{"slug":14,"featured":15,"template":16},"ultimate-guide-to-migrating-from-aws-codecommit-to-gitlab",true,"BlogPost",{"title":18,"description":19,"authors":20,"heroImage":25,"date":26,"body":27,"category":12,"tags":28},"Ultimate guide to migrating from AWS CodeCommit to GitLab","Learn how to migrate from AWS Services to GitLab and seamlessly integrate with the DevSecOps platform in this comprehensive tutorial.",[21,22,23,24],"Tsukasa Komatsubara","Darwin Sanoy","Samer Akkoub","Bart Zhang","https://res.cloudinary.com/about-gitlab-com/image/upload/v1750097810/Blog/Hero%20Images/Blog/Hero%20Images/blog-image-template-1800x945%20%2828%29_4mi0l4wzUa5VI4wtf8gInx_1750097810027.png","2024-08-26","On July 25, 2024, AWS made a significant announcement regarding its CodeCommit service. As detailed in their [official blog post](https://aws.amazon.com/blogs/devops/how-to-migrate-your-aws-codecommit-repository-to-another-git-provider/), AWS has decided to close new customer access to CodeCommit. While existing customers can continue using the service, AWS will not introduce new features, focusing only on security, availability, and performance improvements.\n\nThis announcement has prompted development teams to consider migrating their repositories to alternative Git providers. In light of these changes, we've prepared this comprehensive guide to assist teams in migrating to GitLab and integrating with other AWS services.\n\n**Note:** For more details on AWS's official migration recommendations, please refer to [their blog post](https://aws.amazon.com/blogs/devops/how-to-migrate-your-aws-codecommit-repository-to-another-git-provider/).\n\n## About this guide\n\nThis guide provides comprehensive information for development teams using GitLab who are considering integration with AWS services or planning to migrate from AWS-hosted Git repositories to GitLab.com. The guide is structured into three main sections:\n\n- [Parallel migration to GitLab](#section-1-parallel-migration-to-gitlab): Explains how to gradually migrate from existing AWS-hosted repositories to GitLab.com while minimizing risks.\n\n- [Integration with AWS CodeBuild](#section-2-integrating-gitlab-with-aws-codebuild): Provides steps to integrate GitLab repositories with AWS CodeBuild, setting up a powerful continuous integration (CI) environment.\n\n- [Integration with AWS CodePipeline](#section-3-integrating-gitlab-with-aws-codepipeline): Details how to connect GitLab repositories with AWS CodePipeline to build efficient continuous delivery (CD) pipelines.\n\n- [Downstream integrations for CodePipeline and CodeStar Connections](#section-4-migrating-to-gitlab): Explains how to leverage GitLab-AWS connections for widespread service access, unlocking a cascade of integration possibilities across the AWS ecosystem.\n\nThrough this guide, you'll learn how to combine the powerful features of GitLab and AWS to create an efficient and flexible development workflow.\n\n## Section 1: Parallel migration to GitLab\n\nFor those considering migrating Git repositories hosted on AWS to GitLab.com, this section, which is a phased approach, introduces methods to achieve migration while minimizing risks. By leveraging GitLab's mirroring capabilities, you can maintain existing development flows while testing the new environment.\n\n### Why is parallel migration important?\n\nLarge-scale system migrations always involve risks, particularly potential impacts on ongoing development work, existing integrations, and automated processes. Adopting a parallel migration approach offers the following benefits:\n\n1. Risk minimization: Test the new environment while keeping existing systems operational.\n2. Seamless transition: Development teams can gradually acclimate to the new system.\n3. Integration testing: Thoroughly test all integrations and automation in the new environment.\n4. Future-proofing: Enable teams to gradually migrate to GitLab CI/CD in parallel to existing CI.\n\nParallel migration is not required if it is already known that you want to cut over directly to GitLab.\n\n### Steps for migrating to GitLab.com\n\n#### Step 1: Get set up on GitLab.com\n\n- Check if your company already has a group in use on GitLab.com and whether they have single sign-on (SSO) set up – if they do, then you will want to use both.\n\n- If your company does not have a presence on GitLab.com, visit [GitLab.com](https://www.gitlab.com) and create a new account or log in to an existing one.\n- Create a new company namespace (a group at the root level of gitlab.com).\n- Pick a name that reflects your entire company (and is not already taken).\n\n#### Step 2: Import repository\nFor parallel migration: Use GitLab's pull mirroring feature to automatically sync changes from AWS-hosted repositories to GitLab.com.\n\n1. Navigate to the target group GitLab.com.\n2. In the upper right, click \"New project.\"\n3. On the \"Create new project\" page, click \"Import project.\"\n4. On the \"Import project\" page, click \"Repository by URL.\"\n5. Enter the URL of your AWS-hosted repository in the \"Git repository URL\" field.\n6. Underneath the Git repository URL field, check \"Mirror repository.\"\n7. Set up authentication: in the AWS CodeCommit console, select the clone URL for the repository you will migrate. If you plan on importing CodeCommit repositories into GitLab, you can use the HTTPS CodeCommit URL to clone the repository via GitLab Repository Mirroring. You will need to also provide your Git credentials from AWS for your identity and access management (IAM) user within GitLab. You can create Git credentials for AWS CodeCommit by following this [AWS guide](https://docs.aws.amazon.com/codecommit/latest/userguide/setting-up-gc.html).\n\n![Clone URL](https://res.cloudinary.com/about-gitlab-com/image/upload/v1750097822/Blog/Content%20Images/Blog/Content%20Images/clone-url-screenshot__1__aHR0cHM6_1750097822121.png)\n\nThis setup will automatically pull changes from the AWS-hosted repository to GitLab.com every five minutes by default.\n\nFor more information, read our [repository mirroring documentation](https://docs.gitlab.com/ee/user/project/repository/mirror/).\n\n#### Step 3: Test and validate integrations\n\n1. CI/CD pipelines: Set up the `.gitlab-ci.yml` file in GitLab CI to replicate existing pipelines. You can read more about [planning a migration from other CI tools into GitLab CI/CD](https://docs.gitlab.com/ee/ci/migration/plan_a_migration.html).\n2. Issue tracking: Import project issues and test workflows.\n3. Code review: Set up the merge request process and test review workflows.\n\n#### Step 4: Gradual migration\n\n1. Start with small or non-critical projects to familiarize yourself with working on GitLab.com.\n2. Provide training for team members and allow time to adapt to new workflows.\n3. Gradually migrate more projects while ensuring integrations and workflows are problem-free.\n\nFor more information, see [Automating Migrations from CodeCommit to GitLab](https://gitlab.com/guided-explorations/aws/migrating-from-codecommit-to-gitlab/-/blob/main/migrating_codecommit_to_gitlab.md).\n\n#### Step 5: Complete migration\nOnce all tests and validations are complete and the team is comfortable with the new environment, plan for full migration. For each project:\n\n1. Set a migration date and notify all stakeholders.\n2. Perform final data synchronization.\n3. Remove mirroring settings from the GitLab project.\n4. Set AWS-hosted repositories to read-only and transition all development work to GitLab.com.\n\n#### Step 6: Assess adoption of new capabilities\n\nGitLab collaboration and workflow automation for developers is far richer than CodeCommit. It merits some time to learn what these capabilities are. The merge request process is especially rich compared to CodeCommit.\n\nAfter repositories are stable on GitLab, it is very easy to experiment with GitLab CI/CD in parallel to an existing solution. Teams can take time to perfect their GitLab CI/CD automation while production workflows remain unaffected.\n\nGitLab artifact management is also very capable with the Releases feature and many package registries.\n\n### Section 1: Summary\nBy adopting a parallel migration approach to GitLab, you can achieve a smooth transition while minimizing risks. This process allows teams to gradually adapt to the new environment and ensure all integrations and automations function correctly. Cutover migrations only omit a single setting checkbox if it is known that a parallel migration is not necessary.\n\n## Section 2: Integrating GitLab with AWS CodeBuild\n\nFor those wanting to build and test code from GitLab repositories using AWS CodeBuild, this comprehensive guide will help you set up an efficient CI pipeline.\n\n### Prerequisites\n\n- GitLab.com account\n- AWS account\n- AWS CLI (configured)\n\n### Step 1: Create GitLab connection in AWS CodeStar Connections\n\n1. Log in to the AWS Management Console and navigate to the CodeBuild service.\n2. Select \"Settings\" > \"Connections\" from the left navigation panel.\n3. Click the \"Create connection\" button.\n4. Choose \"GitLab\" as the provider.\n5. Enter a connection name and click \"Connect to GitLab.\"\n6. You'll be redirected to the GitLab authentication page.\n7. Approve the necessary permissions.\n8. Once successful, the connection status will change to \"Available.\"\n\n![CodeStar Connect setup](https://res.cloudinary.com/about-gitlab-com/image/upload/v1750097822/Blog/Content%20Images/Blog/Content%20Images/codestar-connections-setup_aHR0cHM6_1750097822122.png)\n\n### Step 2: Create AWS CodeBuild project\n\n1. Click \"Create build project\" on the CodeBuild dashboard.\n2. Enter a project name and description.\n3. For source settings, select \"GitLab\" as the provider.\n4. Choose the connection you just created and specify the GitLab repository and branch.\n\n![Add CodeBuild project](https://res.cloudinary.com/about-gitlab-com/image/upload/v1750097822/Blog/Content%20Images/Blog/Content%20Images/codepipeline_step_3_add_codebuild_aHR0cHM6_1750097822123.png)\n\n**Note: From Step 3 forward, please configure the settings according to your specific environment and needs.**\n\n### Summary of Section 2\nThis section explained in detail how to integrate GitLab repositories with AWS CodeBuild. This setup enables a continuous integration pipeline where code changes in GitLab are automatically built and tested using AWS CodeBuild.\n\n## Section 3: Integrating GitLab with AWS CodePipeline\n\nFor those looking to implement continuous delivery from GitLab repositories using AWS CodePipeline, this detailed guide will be helpful. The integration has become even easier now that GitLab is available as an AWS CodeStar Connections provider.\n\n### Prerequisites\n\n- GitLab.com account\n- AWS account\n- AWS CLI (configured)\n\n### Step 1: Create GitLab connection in AWS CodeStar Connections\n\n1. Log in to the AWS Management Console and navigate to the CodePipeline service.\n2. Select \"Settings\" > \"Connections\" from the left navigation panel.\n3. Click the \"Create connection\" button.\n4. Choose \"GitLab\" as the provider.\n5. Enter a connection name and click \"Connect to GitLab.\"\n6. You'll be redirected to the GitLab authentication page.\n7. Approve the necessary permissions.\n8. Once successful, the connection status will change to \"Available.\"\n\n![CodeStar Connections setup](https://res.cloudinary.com/about-gitlab-com/image/upload/v1750097822/Blog/Content%20Images/Blog/Content%20Images/codestar-connections-setup_aHR0cHM6_1750097822125.png)\n\n### Step 2: Create AWS CodePipeline\n\n1. Click \"Create pipeline\" on the CodePipeline dashboard.\n2. Enter a pipeline name and click \"Next.\"\n3. Select \"GitLab\" as the source provider.\n4. Choose the connection you just created and specify the GitLab repository and branch.\n5. Select the Trigger type: You can trigger CodePipeline pipeline execution based on either pull or push events against specific branches and file types within your repository.\n\n![Add source provider](https://res.cloudinary.com/about-gitlab-com/image/upload/v1750097822/Blog/Content%20Images/Blog/Content%20Images/codepipeline_step_2_source_provider_aHR0cHM6_1750097822127.png)\n\n![Add source configuration](https://res.cloudinary.com/about-gitlab-com/image/upload/v1750097822/Blog/Content%20Images/Blog/Content%20Images/codepipeline_step_2_source_configured_aHR0cHM6_1750097822129.png)\n\n**Note: From Step 3 forward, please configure the settings according to your specific environment and needs.**\n\n### Summary of Section 3\nThis section detailed how to integrate GitLab repositories with AWS CodePipeline. This setup enables a continuous delivery pipeline where code changes in GitLab are automatically deployed to your AWS environment.\n\n## Section 4: Migrating to GitLab\n\nIntegrating GitLab with AWS unlocks powerful capabilities for streamlining your development and deployment workflows and helps to solve your source code management woes. This integration can be achieved in several ways, each offering unique benefits:\n\n- Using AWS CodeStar Connections to link GitLab with AWS services enables a more cohesive workflow by allowing external Git repositories, like GitLab, to connect with various AWS services. This setup supports automated builds, deployments, and other essential actions directly from your GitLab repository, making your development process more integrated and streamlined.\n\n- Connecting GitLab with AWS CodePipeline via AWS CodeStar Connections takes automation to the next level by allowing you to create a full CI/CD pipeline. This approach integrates GitLab with AWS CodePipeline, enabling you to automate the entire process – from source control and builds to testing and deployment – using AWS services like CodeBuild and CodeDeploy. This ensures a robust, scalable, and efficient delivery process.\n\n![Chart of new technology and solutions for using GitLab and AWS together](https://res.cloudinary.com/about-gitlab-com/image/upload/v1750097822/Blog/Content%20Images/Blog/Content%20Images/Announcing_New_Technology_and_Solutions_for_using_GitLab_and_AWS_Together_aHR0cHM6_1750097822130.png)\n\n1\\. Connecting GitLab with AWS services using AWS CodeStar Connections\n\nAWS CodeStar Connections is a service that allows you to connect external Git repositories (such as GitHub or Bitbucket) to AWS services. You can also connect GitLab to AWS services via CodeStar Connections. When using GitLab, you may need to set up a custom connection as an HTTP Git server.\nThe following AWS services can be connected to GitLab using this method:\n\n- **AWS Service Catalog**\n\nAWS Service Catalog helps organizations standardize and manage AWS resources. Integrating it with GitLab improves transparency in resource management and simplifies change tracking. Specifically, you can automate catalog updates based on GitLab commits, enhancing operational efficiency.\n\n- __AWS CodeBuild__\n\nAWS CodeBuild is a managed build service that compiles source code, runs tests, and produces deployable software packages. Integrating GitLab with CodeBuild allows automated build processes to start whenever code changes are pushed to GitLab. This ensures consistency in builds and facilitates easier collaboration and version control.\n\n- __AWS Glue Notebook Jobs__\n\nAWS Glue Notebook Jobs is a service that allows you to interactively develop and run data preparation and ETL (Extract, Transform, Load) tasks. Integrating GitLab with Glue Notebook Jobs enables version control for notebooks and ETL scripts, promotes collaboration among team members, and improves the quality management of data processing pipelines.\n\n- __AWS Proton__\n\nAWS Proton is a service that automates the development and deployment of microservices and serverless applications. By integrating GitLab with AWS Proton, you can manage infrastructure as code, automate deployments, and ensure consistent environment management, leading to more efficient development processes.\n\nAs AWS CodeStar Connections supports more services, connecting GitLab with additional AWS services will become easier. It's advisable to regularly check for new services that support CodeStar Connections.\n\n2. Connecting CodePipeline with GitLab via AWS CodeStar Connections (including CodeDeploy)\n\nAWS CodePipeline is a continuous delivery service that automates the release process for software. To connect GitLab with CodePipeline, you need to use AWS CodeStar Connections. This setup allows you to designate a GitLab repository as the source and automate the entire CI/CD pipeline.\nThe primary actions supported by CodePipeline include:\n- **Source control:** AWS CodeCommit, GitHub, Bitbucket, GitLab\n- **Build and test:** AWS CodeBuild, Jenkins\n- **Deploy:** AWS CodeDeploy, Elastic Beanstalk, ECS, S3\n- **Approval:** Manual approval\n- **Infrastructure management:** AWS CloudFormation\n- **Serverless:** AWS Lambda\n- **Testing:** AWS Device Farm\n- **Custom Actions:** AWS Step Functions\n\nBy integrating GitLab with CodePipeline, you can automatically trigger the pipeline whenever code changes are pushed to GitLab, allowing a consistent process from build to deployment. Additionally, combining this with GitLab's version control capabilities makes it easier to track deployment history and states, leading to more flexible and reliable software delivery.\n\n## What you've learned\nThis guide has provided comprehensive information on migrating to and integrating GitLab with AWS. Through the four main topics, we've covered:\n- Parallel migration to GitLab: How to gradually migrate from existing AWS-hosted repositories to GitLab.com while minimizing risks.\n- Integration with AWS CodeBuild: Steps to set up a powerful CI environment integrated with GitLab repositories.\n- Integration with AWS CodePipeline: How to build efficient continuous delivery pipelines using GitLab repositories.\n- Downstream integrations for CodePipeline and CodeStar Connections: Leveraging GitLab-AWS connections for widespread service access, unlocking a cascade of integration possibilities across the AWS ecosystem.\n\nAs every organization's code hosting and integration implementation strategy is unique, this tutorial may be used as a starting point for your own GitLab + AWS integration and implementation strategy.\n\n## Additional resources\n\nFor more detailed information and advanced configurations, refer to the following resources:\n\n- [GitLab documentation](https://docs.gitlab.com/)\n- [AWS CodeBuild User Guide](https://docs.aws.amazon.com/codebuild/latest/userguide/welcome.html)\n- [AWS CodePipeline User Guide](https://docs.aws.amazon.com/codepipeline/latest/userguide/welcome.html)\n- [GitLab CI/CD documentation](https://docs.gitlab.com/ee/ci/)\n- [Integrate with AWS](https://docs.gitlab.com/ee/solutions/cloud/aws/gitlab_aws_integration.html)\n\nIf you have questions or need support, please contact [GitLab Support](https://support.gitlab.com/hc/en-us/articles/11626483177756-GitLab-Support) or AWS Support. We hope this comprehensive guide helps you in your AWS-GitLab integration journey.",[29,30,31,32,33,12,34],"CI/CD","AWS","DevSecOps platform","tutorial","solutions architecture","integrations","yml",{},"/en-us/blog/ultimate-guide-to-migrating-from-aws-codecommit-to-gitlab",{"title":18,"description":19,"ogTitle":18,"ogDescription":19,"noIndex":39,"ogImage":25,"ogUrl":40,"ogSiteName":41,"ogType":42,"canonicalUrls":40},false,"https://about.gitlab.com/blog/ultimate-guide-to-migrating-from-aws-codecommit-to-gitlab","https://about.gitlab.com","article","en-us/blog/ultimate-guide-to-migrating-from-aws-codecommit-to-gitlab",[45,46,47,32,48,12,34],"cicd","aws","devsecops-platform","solutions-architecture","HPrFWDGzhHQDpfhu5mO0ftOmRhUdWdq4Rs40h6JwWtY",{"data":51},{"logo":52,"freeTrial":57,"sales":62,"login":67,"items":72,"search":378,"minimal":409,"duo":428,"switchNav":437,"pricingDeployment":448},{"config":53},{"href":54,"dataGaName":55,"dataGaLocation":56},"/","gitlab logo","header",{"text":58,"config":59},"Get free trial",{"href":60,"dataGaName":61,"dataGaLocation":56},"https://gitlab.com/-/trial_registrations/new?glm_source=about.gitlab.com&glm_content=default-saas-trial/","free trial",{"text":63,"config":64},"Talk to sales",{"href":65,"dataGaName":66,"dataGaLocation":56},"/sales/","sales",{"text":68,"config":69},"Sign in",{"href":70,"dataGaName":71,"dataGaLocation":56},"https://gitlab.com/users/sign_in/","sign in",[73,100,194,199,299,359],{"text":74,"config":75,"cards":77},"Platform",{"dataNavLevelOne":76},"platform",[78,84,92],{"title":74,"description":79,"link":80},"The intelligent orchestration platform for DevSecOps",{"text":81,"config":82},"Explore our Platform",{"href":83,"dataGaName":76,"dataGaLocation":56},"/platform/",{"title":85,"description":86,"link":87},"GitLab Duo Agent Platform","Agentic AI for the entire software lifecycle",{"text":88,"config":89},"Meet GitLab Duo",{"href":90,"dataGaName":91,"dataGaLocation":56},"/gitlab-duo-agent-platform/","gitlab duo agent platform",{"title":93,"description":94,"link":95},"Why GitLab","See the top reasons enterprises choose GitLab",{"text":96,"config":97},"Learn more",{"href":98,"dataGaName":99,"dataGaLocation":56},"/why-gitlab/","why gitlab",{"text":101,"left":15,"config":102,"link":104,"lists":108,"footer":176},"Product",{"dataNavLevelOne":103},"solutions",{"text":105,"config":106},"View all Solutions",{"href":107,"dataGaName":103,"dataGaLocation":56},"/solutions/",[109,132,155],{"title":110,"description":111,"link":112,"items":117},"Automation","CI/CD and automation to accelerate deployment",{"config":113},{"icon":114,"href":115,"dataGaName":116,"dataGaLocation":56},"AutomatedCodeAlt","/solutions/delivery-automation/","automated software delivery",[118,121,124,128],{"text":29,"config":119},{"href":120,"dataGaLocation":56,"dataGaName":29},"/solutions/continuous-integration/",{"text":85,"config":122},{"href":90,"dataGaLocation":56,"dataGaName":123},"gitlab duo agent platform - product menu",{"text":125,"config":126},"Source Code Management",{"href":127,"dataGaLocation":56,"dataGaName":125},"/solutions/source-code-management/",{"text":129,"config":130},"Automated Software Delivery",{"href":115,"dataGaLocation":56,"dataGaName":131},"Automated software delivery",{"title":133,"description":134,"link":135,"items":140},"Security","Deliver code faster without compromising security",{"config":136},{"href":137,"dataGaName":138,"dataGaLocation":56,"icon":139},"/solutions/application-security-testing/","security and compliance","ShieldCheckLight",[141,145,150],{"text":142,"config":143},"Application Security Testing",{"href":137,"dataGaName":144,"dataGaLocation":56},"Application security testing",{"text":146,"config":147},"Software Supply Chain Security",{"href":148,"dataGaLocation":56,"dataGaName":149},"/solutions/supply-chain/","Software supply chain security",{"text":151,"config":152},"Software Compliance",{"href":153,"dataGaName":154,"dataGaLocation":56},"/solutions/software-compliance/","software compliance",{"title":156,"link":157,"items":162},"Measurement",{"config":158},{"icon":159,"href":160,"dataGaName":161,"dataGaLocation":56},"DigitalTransformation","/solutions/visibility-measurement/","visibility and measurement",[163,167,171],{"text":164,"config":165},"Visibility & Measurement",{"href":160,"dataGaLocation":56,"dataGaName":166},"Visibility and Measurement",{"text":168,"config":169},"Value Stream Management",{"href":170,"dataGaLocation":56,"dataGaName":168},"/solutions/value-stream-management/",{"text":172,"config":173},"Analytics & Insights",{"href":174,"dataGaLocation":56,"dataGaName":175},"/solutions/analytics-and-insights/","Analytics and insights",{"title":177,"items":178},"GitLab for",[179,184,189],{"text":180,"config":181},"Enterprise",{"href":182,"dataGaLocation":56,"dataGaName":183},"/enterprise/","enterprise",{"text":185,"config":186},"Small Business",{"href":187,"dataGaLocation":56,"dataGaName":188},"/small-business/","small business",{"text":190,"config":191},"Public Sector",{"href":192,"dataGaLocation":56,"dataGaName":193},"/solutions/public-sector/","public sector",{"text":195,"config":196},"Pricing",{"href":197,"dataGaName":198,"dataGaLocation":56,"dataNavLevelOne":198},"/pricing/","pricing",{"text":200,"config":201,"link":203,"lists":207,"feature":286},"Resources",{"dataNavLevelOne":202},"resources",{"text":204,"config":205},"View all resources",{"href":206,"dataGaName":202,"dataGaLocation":56},"/resources/",[208,240,258],{"title":209,"items":210},"Getting started",[211,216,221,226,231,236],{"text":212,"config":213},"Install",{"href":214,"dataGaName":215,"dataGaLocation":56},"/install/","install",{"text":217,"config":218},"Quick start guides",{"href":219,"dataGaName":220,"dataGaLocation":56},"/get-started/","quick setup checklists",{"text":222,"config":223},"Learn",{"href":224,"dataGaLocation":56,"dataGaName":225},"https://university.gitlab.com/","learn",{"text":227,"config":228},"Product documentation",{"href":229,"dataGaName":230,"dataGaLocation":56},"https://docs.gitlab.com/","product documentation",{"text":232,"config":233},"Best practice videos",{"href":234,"dataGaName":235,"dataGaLocation":56},"/getting-started-videos/","best practice videos",{"text":237,"config":238},"Integrations",{"href":239,"dataGaName":34,"dataGaLocation":56},"/integrations/",{"title":241,"items":242},"Discover",[243,248,253],{"text":244,"config":245},"Customer success stories",{"href":246,"dataGaName":247,"dataGaLocation":56},"/customers/","customer success stories",{"text":249,"config":250},"Blog",{"href":251,"dataGaName":252,"dataGaLocation":56},"/blog/","blog",{"text":254,"config":255},"Remote",{"href":256,"dataGaName":257,"dataGaLocation":56},"https://handbook.gitlab.com/handbook/company/culture/all-remote/","remote",{"title":259,"items":260},"Connect",[261,266,271,276,281],{"text":262,"config":263},"GitLab Services",{"href":264,"dataGaName":265,"dataGaLocation":56},"/services/","services",{"text":267,"config":268},"Community",{"href":269,"dataGaName":270,"dataGaLocation":56},"/community/","community",{"text":272,"config":273},"Forum",{"href":274,"dataGaName":275,"dataGaLocation":56},"https://forum.gitlab.com/","forum",{"text":277,"config":278},"Events",{"href":279,"dataGaName":280,"dataGaLocation":56},"/events/","events",{"text":282,"config":283},"Partners",{"href":284,"dataGaName":285,"dataGaLocation":56},"/partners/","partners",{"backgroundColor":287,"textColor":288,"text":289,"image":290,"link":294},"#2f2a6b","#fff","Insights for the future of software development",{"altText":291,"config":292},"the source promo card",{"src":293},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1758208064/dzl0dbift9xdizyelkk4.svg",{"text":295,"config":296},"Read the latest",{"href":297,"dataGaName":298,"dataGaLocation":56},"/the-source/","the source",{"text":300,"config":301,"lists":303},"Company",{"dataNavLevelOne":302},"company",[304],{"items":305},[306,311,317,319,324,329,334,339,344,349,354],{"text":307,"config":308},"About",{"href":309,"dataGaName":310,"dataGaLocation":56},"/company/","about",{"text":312,"config":313,"footerGa":316},"Jobs",{"href":314,"dataGaName":315,"dataGaLocation":56},"/jobs/","jobs",{"dataGaName":315},{"text":277,"config":318},{"href":279,"dataGaName":280,"dataGaLocation":56},{"text":320,"config":321},"Leadership",{"href":322,"dataGaName":323,"dataGaLocation":56},"/company/team/e-group/","leadership",{"text":325,"config":326},"Team",{"href":327,"dataGaName":328,"dataGaLocation":56},"/company/team/","team",{"text":330,"config":331},"Handbook",{"href":332,"dataGaName":333,"dataGaLocation":56},"https://handbook.gitlab.com/","handbook",{"text":335,"config":336},"Investor relations",{"href":337,"dataGaName":338,"dataGaLocation":56},"https://ir.gitlab.com/","investor relations",{"text":340,"config":341},"Trust Center",{"href":342,"dataGaName":343,"dataGaLocation":56},"/security/","trust center",{"text":345,"config":346},"AI Transparency Center",{"href":347,"dataGaName":348,"dataGaLocation":56},"/ai-transparency-center/","ai transparency center",{"text":350,"config":351},"Newsletter",{"href":352,"dataGaName":353,"dataGaLocation":56},"/company/contact/#contact-forms","newsletter",{"text":355,"config":356},"Press",{"href":357,"dataGaName":358,"dataGaLocation":56},"/press/","press",{"text":360,"config":361,"lists":362},"Contact us",{"dataNavLevelOne":302},[363],{"items":364},[365,368,373],{"text":63,"config":366},{"href":65,"dataGaName":367,"dataGaLocation":56},"talk to sales",{"text":369,"config":370},"Support portal",{"href":371,"dataGaName":372,"dataGaLocation":56},"https://support.gitlab.com","support portal",{"text":374,"config":375},"Customer portal",{"href":376,"dataGaName":377,"dataGaLocation":56},"https://customers.gitlab.com/customers/sign_in/","customer portal",{"close":379,"login":380,"suggestions":387},"Close",{"text":381,"link":382},"To search repositories and projects, login to",{"text":383,"config":384},"gitlab.com",{"href":70,"dataGaName":385,"dataGaLocation":386},"search login","search",{"text":388,"default":389},"Suggestions",[390,392,396,398,402,406],{"text":85,"config":391},{"href":90,"dataGaName":85,"dataGaLocation":386},{"text":393,"config":394},"Code Suggestions (AI)",{"href":395,"dataGaName":393,"dataGaLocation":386},"/solutions/code-suggestions/",{"text":29,"config":397},{"href":120,"dataGaName":29,"dataGaLocation":386},{"text":399,"config":400},"GitLab on AWS",{"href":401,"dataGaName":399,"dataGaLocation":386},"/partners/technology-partners/aws/",{"text":403,"config":404},"GitLab on Google Cloud",{"href":405,"dataGaName":403,"dataGaLocation":386},"/partners/technology-partners/google-cloud-platform/",{"text":407,"config":408},"Why GitLab?",{"href":98,"dataGaName":407,"dataGaLocation":386},{"freeTrial":410,"mobileIcon":415,"desktopIcon":420,"secondaryButton":423},{"text":411,"config":412},"Start free trial",{"href":413,"dataGaName":61,"dataGaLocation":414},"https://gitlab.com/-/trials/new/","nav",{"altText":416,"config":417},"Gitlab Icon",{"src":418,"dataGaName":419,"dataGaLocation":414},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1758203874/jypbw1jx72aexsoohd7x.svg","gitlab icon",{"altText":416,"config":421},{"src":422,"dataGaName":419,"dataGaLocation":414},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1758203875/gs4c8p8opsgvflgkswz9.svg",{"text":424,"config":425},"Get Started",{"href":426,"dataGaName":427,"dataGaLocation":414},"https://gitlab.com/-/trial_registrations/new?glm_source=about.gitlab.com/get-started/","get started",{"freeTrial":429,"mobileIcon":433,"desktopIcon":435},{"text":430,"config":431},"Learn more about GitLab Duo",{"href":90,"dataGaName":432,"dataGaLocation":414},"gitlab duo",{"altText":416,"config":434},{"src":418,"dataGaName":419,"dataGaLocation":414},{"altText":416,"config":436},{"src":422,"dataGaName":419,"dataGaLocation":414},{"button":438,"mobileIcon":443,"desktopIcon":445},{"text":439,"config":440},"/switch",{"href":441,"dataGaName":442,"dataGaLocation":414},"#contact","switch",{"altText":416,"config":444},{"src":418,"dataGaName":419,"dataGaLocation":414},{"altText":416,"config":446},{"src":447,"dataGaName":419,"dataGaLocation":414},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1773335277/ohhpiuoxoldryzrnhfrh.png",{"freeTrial":449,"mobileIcon":454,"desktopIcon":456},{"text":450,"config":451},"Back to pricing",{"href":197,"dataGaName":452,"dataGaLocation":414,"icon":453},"back to pricing","GoBack",{"altText":416,"config":455},{"src":418,"dataGaName":419,"dataGaLocation":414},{"altText":416,"config":457},{"src":422,"dataGaName":419,"dataGaLocation":414},{"title":459,"button":460,"config":465},"See how agentic AI transforms software delivery",{"text":461,"config":462},"Watch GitLab Transcend now",{"href":463,"dataGaName":464,"dataGaLocation":56},"/events/transcend/virtual/","transcend event",{"layout":466,"icon":467,"disabled":15},"release","AiStar",{"data":469},{"text":470,"source":471,"edit":477,"contribute":482,"config":487,"items":492,"minimal":697},"Git is a trademark of Software Freedom Conservancy and our use of 'GitLab' is under license",{"text":472,"config":473},"View page source",{"href":474,"dataGaName":475,"dataGaLocation":476},"https://gitlab.com/gitlab-com/marketing/digital-experience/about-gitlab-com/","page source","footer",{"text":478,"config":479},"Edit this page",{"href":480,"dataGaName":481,"dataGaLocation":476},"https://gitlab.com/gitlab-com/marketing/digital-experience/about-gitlab-com/-/blob/main/content/","web ide",{"text":483,"config":484},"Please contribute",{"href":485,"dataGaName":486,"dataGaLocation":476},"https://gitlab.com/gitlab-com/marketing/digital-experience/about-gitlab-com/-/blob/main/CONTRIBUTING.md/","please contribute",{"twitter":488,"facebook":489,"youtube":490,"linkedin":491},"https://twitter.com/gitlab","https://www.facebook.com/gitlab","https://www.youtube.com/channel/UCnMGQ8QHMAnVIsI3xJrihhg","https://www.linkedin.com/company/gitlab-com",[493,540,592,636,663],{"title":195,"links":494,"subMenu":509},[495,499,504],{"text":496,"config":497},"View plans",{"href":197,"dataGaName":498,"dataGaLocation":476},"view plans",{"text":500,"config":501},"Why Premium?",{"href":502,"dataGaName":503,"dataGaLocation":476},"/pricing/premium/","why premium",{"text":505,"config":506},"Why Ultimate?",{"href":507,"dataGaName":508,"dataGaLocation":476},"/pricing/ultimate/","why ultimate",[510],{"title":511,"links":512},"Contact Us",[513,516,518,520,525,530,535],{"text":514,"config":515},"Contact sales",{"href":65,"dataGaName":66,"dataGaLocation":476},{"text":369,"config":517},{"href":371,"dataGaName":372,"dataGaLocation":476},{"text":374,"config":519},{"href":376,"dataGaName":377,"dataGaLocation":476},{"text":521,"config":522},"Status",{"href":523,"dataGaName":524,"dataGaLocation":476},"https://status.gitlab.com/","status",{"text":526,"config":527},"Terms of use",{"href":528,"dataGaName":529,"dataGaLocation":476},"/terms/","terms of use",{"text":531,"config":532},"Privacy statement",{"href":533,"dataGaName":534,"dataGaLocation":476},"/privacy/","privacy statement",{"text":536,"config":537},"Cookie preferences",{"dataGaName":538,"dataGaLocation":476,"id":539,"isOneTrustButton":15},"cookie preferences","ot-sdk-btn",{"title":101,"links":541,"subMenu":549},[542,545],{"text":31,"config":543},{"href":83,"dataGaName":544,"dataGaLocation":476},"devsecops platform",{"text":546,"config":547},"AI-Assisted Development",{"href":90,"dataGaName":548,"dataGaLocation":476},"ai-assisted development",[550],{"title":551,"links":552},"Topics",[553,557,562,567,572,577,582,587],{"text":554,"config":555},"CICD",{"href":556,"dataGaName":45,"dataGaLocation":476},"/topics/ci-cd/",{"text":558,"config":559},"GitOps",{"href":560,"dataGaName":561,"dataGaLocation":476},"/topics/gitops/","gitops",{"text":563,"config":564},"DevOps",{"href":565,"dataGaName":566,"dataGaLocation":476},"/topics/devops/","devops",{"text":568,"config":569},"Version Control",{"href":570,"dataGaName":571,"dataGaLocation":476},"/topics/version-control/","version control",{"text":573,"config":574},"DevSecOps",{"href":575,"dataGaName":576,"dataGaLocation":476},"/topics/devsecops/","devsecops",{"text":578,"config":579},"Cloud Native",{"href":580,"dataGaName":581,"dataGaLocation":476},"/topics/cloud-native/","cloud native",{"text":583,"config":584},"AI for Coding",{"href":585,"dataGaName":586,"dataGaLocation":476},"/topics/devops/ai-for-coding/","ai for coding",{"text":588,"config":589},"Agentic AI",{"href":590,"dataGaName":591,"dataGaLocation":476},"/topics/agentic-ai/","agentic ai",{"title":593,"links":594},"Solutions",[595,597,599,604,608,611,615,618,620,623,626,631],{"text":142,"config":596},{"href":137,"dataGaName":142,"dataGaLocation":476},{"text":131,"config":598},{"href":115,"dataGaName":116,"dataGaLocation":476},{"text":600,"config":601},"Agile development",{"href":602,"dataGaName":603,"dataGaLocation":476},"/solutions/agile-delivery/","agile delivery",{"text":605,"config":606},"SCM",{"href":127,"dataGaName":607,"dataGaLocation":476},"source code management",{"text":554,"config":609},{"href":120,"dataGaName":610,"dataGaLocation":476},"continuous integration & delivery",{"text":612,"config":613},"Value stream management",{"href":170,"dataGaName":614,"dataGaLocation":476},"value stream management",{"text":558,"config":616},{"href":617,"dataGaName":561,"dataGaLocation":476},"/solutions/gitops/",{"text":180,"config":619},{"href":182,"dataGaName":183,"dataGaLocation":476},{"text":621,"config":622},"Small business",{"href":187,"dataGaName":188,"dataGaLocation":476},{"text":624,"config":625},"Public sector",{"href":192,"dataGaName":193,"dataGaLocation":476},{"text":627,"config":628},"Education",{"href":629,"dataGaName":630,"dataGaLocation":476},"/solutions/education/","education",{"text":632,"config":633},"Financial services",{"href":634,"dataGaName":635,"dataGaLocation":476},"/solutions/finance/","financial services",{"title":200,"links":637},[638,640,642,644,647,649,651,653,655,657,659,661],{"text":212,"config":639},{"href":214,"dataGaName":215,"dataGaLocation":476},{"text":217,"config":641},{"href":219,"dataGaName":220,"dataGaLocation":476},{"text":222,"config":643},{"href":224,"dataGaName":225,"dataGaLocation":476},{"text":227,"config":645},{"href":229,"dataGaName":646,"dataGaLocation":476},"docs",{"text":249,"config":648},{"href":251,"dataGaName":252,"dataGaLocation":476},{"text":244,"config":650},{"href":246,"dataGaName":247,"dataGaLocation":476},{"text":254,"config":652},{"href":256,"dataGaName":257,"dataGaLocation":476},{"text":262,"config":654},{"href":264,"dataGaName":265,"dataGaLocation":476},{"text":267,"config":656},{"href":269,"dataGaName":270,"dataGaLocation":476},{"text":272,"config":658},{"href":274,"dataGaName":275,"dataGaLocation":476},{"text":277,"config":660},{"href":279,"dataGaName":280,"dataGaLocation":476},{"text":282,"config":662},{"href":284,"dataGaName":285,"dataGaLocation":476},{"title":300,"links":664},[665,667,669,671,673,675,677,681,686,688,690,692],{"text":307,"config":666},{"href":309,"dataGaName":302,"dataGaLocation":476},{"text":312,"config":668},{"href":314,"dataGaName":315,"dataGaLocation":476},{"text":320,"config":670},{"href":322,"dataGaName":323,"dataGaLocation":476},{"text":325,"config":672},{"href":327,"dataGaName":328,"dataGaLocation":476},{"text":330,"config":674},{"href":332,"dataGaName":333,"dataGaLocation":476},{"text":335,"config":676},{"href":337,"dataGaName":338,"dataGaLocation":476},{"text":678,"config":679},"Sustainability",{"href":680,"dataGaName":678,"dataGaLocation":476},"/sustainability/",{"text":682,"config":683},"Diversity, inclusion and belonging (DIB)",{"href":684,"dataGaName":685,"dataGaLocation":476},"/diversity-inclusion-belonging/","Diversity, inclusion and belonging",{"text":340,"config":687},{"href":342,"dataGaName":343,"dataGaLocation":476},{"text":350,"config":689},{"href":352,"dataGaName":353,"dataGaLocation":476},{"text":355,"config":691},{"href":357,"dataGaName":358,"dataGaLocation":476},{"text":693,"config":694},"Modern Slavery Transparency Statement",{"href":695,"dataGaName":696,"dataGaLocation":476},"https://handbook.gitlab.com/handbook/legal/modern-slavery-act-transparency-statement/","modern slavery transparency statement",{"items":698},[699,702,705],{"text":700,"config":701},"Terms",{"href":528,"dataGaName":529,"dataGaLocation":476},{"text":703,"config":704},"Cookies",{"dataGaName":538,"dataGaLocation":476,"id":539,"isOneTrustButton":15},{"text":706,"config":707},"Privacy",{"href":533,"dataGaName":534,"dataGaLocation":476},[709,722,736,748],{"id":710,"title":21,"body":11,"config":711,"content":713,"description":11,"extension":35,"meta":717,"navigation":15,"path":718,"seo":719,"stem":720,"__hash__":721},"blogAuthors/en-us/blog/authors/tsukasa-komatsubara.yml",{"template":712},"BlogAuthor",{"name":21,"config":714},{"headshot":715,"ctfId":716},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1749659784/Blog/Author%20Headshots/gitlab_tsukasa.jpg","31YQLiBRrJPn35BBhY69ly",{},"/en-us/blog/authors/tsukasa-komatsubara",{},"en-us/blog/authors/tsukasa-komatsubara","O5IhL3DQ7MAo8yzVzaeGvidF81OrGBrv7DgR3C9ySBc",{"id":723,"title":22,"body":11,"config":724,"content":725,"description":11,"extension":35,"meta":731,"navigation":15,"path":732,"seo":733,"stem":734,"__hash__":735},"blogAuthors/en-us/blog/authors/darwin-sanoy.yml",{"template":712},{"role":726,"name":22,"config":727},"Field Chief Cloud Architect",{"headshot":728,"linkedin":729,"ctfId":730},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1749659751/Blog/Author%20Headshots/Darwin-Sanoy-headshot-395-square-gitlab-teampage-avatar.png","https://linkedin.com/in/darwinsanoy","DarwinJS",{},"/en-us/blog/authors/darwin-sanoy",{},"en-us/blog/authors/darwin-sanoy","UkMMwmU5o2e6Y-wBltA9E_z96LvHuB-bG6VW9DsLzIY",{"id":737,"title":23,"body":11,"config":738,"content":739,"description":11,"extension":35,"meta":743,"navigation":15,"path":744,"seo":745,"stem":746,"__hash__":747},"blogAuthors/en-us/blog/authors/samer-akkoub.yml",{"template":712},{"name":23,"config":740},{"headshot":741,"ctfId":742},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1749664173/Blog/Author%20Headshots/SamerAkkoub.png","BekAzK0RFux30pt6dvtWh",{},"/en-us/blog/authors/samer-akkoub",{},"en-us/blog/authors/samer-akkoub","jYGC9dZbBzwlu9_I_Kp6z98wpaytDJkFaSAxvBwsxuU",{"id":749,"title":24,"body":11,"config":750,"content":751,"description":11,"extension":35,"meta":755,"navigation":15,"path":756,"seo":757,"stem":758,"__hash__":759},"blogAuthors/en-us/blog/authors/bart-zhang.yml",{"template":712},{"name":24,"config":752},{"headshot":753,"ctfId":754},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1749664177/Blog/Author%20Headshots/bartzhang-headshot.jpg","bartzhang",{},"/en-us/blog/authors/bart-zhang",{},"en-us/blog/authors/bart-zhang","b7CFRNFezC9yhgQ3GRiTZ4joQAY5dZB2u6FIo2bo1Xs",[761,775,781],{"content":762,"config":773},{"title":763,"description":764,"authors":765,"heroImage":767,"date":768,"body":769,"category":12,"tags":770},"GitLab 18.11: Budget guardrails for GitLab Credits","Learn how new spending caps and per-user credit limits give organizations the budget guardrails to scale GitLab Duo Agent Platform.",[766],"Bryan Rothwell","https://res.cloudinary.com/about-gitlab-com/image/upload/v1776259080/cakqnwo5ecp255lo8lzo.png","2026-04-16","Teams using GitLab Duo Agent Platform with on-demand GitLab Credits are shipping faster, catching bugs earlier, and automating tasks that used to take entire sprints. But as adoption grows, so does oversight from finance, procurement, and platform teams to prove that AI spending is bounded, predictable, and controllable.\n\nOne of the greatest barriers to broader AI adoption isn't skepticism about the technology. It's uncertainty about managing spend. Without budget caps, a busy month could produce unexpected expenses. Without per-user limits, a handful of power users could burn through the team's credits before the month is over. And without either, engineering leaders who want to expand their use of agentic AI for software development have to jump through more hoops for budget approval.\n\nSince its [general availability](https://about.gitlab.com/blog/gitlab-duo-agent-platform-is-generally-available/), GitLab Duo Agent Platform has provided usage governance and visibility. With GitLab 18.11, we're introducing usage controls for [GitLab Credits](https://about.gitlab.com/blog/introducing-gitlab-credits/): spending caps and budget guardrails that give your organization even more control and transparency over how credits are consumed.\n\n## Managing GitLab Credits\n\nGitLab 18.11 adds three layers of control over GitLab Credits consumption: a subscription-level spending cap, per-user credit limits, and visibility into cap status and enforcement.\n\n### Subscription-level spending cap\n\nBilling account managers can now set a hard monthly ceiling for on-demand GitLab Credits consumption for their entire subscription.\n\nHere's how it works:\n\n* **Set a cap** in the `Customers Portal` under your subscription's GitLab Credits settings.  \n* **Enforce spend limits automatically.**  When on-demand usage reaches the cap, DAP access is paused for all users on that subscription until the next monthly period begins.  \n* **Make adjustments as you go.** Raise or disable the cap mid-month to restore access.\n\nThe cap resets each monthly period and your configured limit carries forward unless you change it. Because usage data is synchronized periodically rather than in real time, a small amount of additional usage may occur after the cap is reached before enforcement takes effect. See the [GitLab Credits documentation](https://docs.gitlab.com/subscriptions/gitlab_credits/) for details.\n\n### User-level spending caps\n\nNot every user consumes credits at the same rate, and that's expected. But when one or two power users account for a disproportionate share of the pool, the rest of the team can lose access before the month is over.\n\nPer-user credit caps prevent any single user from consuming more than their fair share:\n\n* **Flat per-user cap.** Set a uniform credit limit that applies equally to every user on the subscription through the GitLab GraphQL API. Unlike the subscription-level cap, the per-user cap applies to a user's total consumption across all credit sources.  \n* **Custom per-user overrides.** For organizations that need differentiated limits, you can set individual credit caps for specific users through the GraphQL API. For example, you could give your staff engineers a higher allocation while applying a standard limit to the broader team.  \n* **Individual enforcement.** When a user reaches their cap, they retain full access to GitLab. Only their Duo Agent Platform credit usage is paused until the next billing cycle. Everyone else keeps working uninterrupted until they hit their own limit or the subscription-level cap is reached, whichever comes first.\n\n### Visibility and notifications\n\nWhen a subscription-level cap is reached, GitLab sends an email notification to billing account managers so they can take action: raise the cap, wait for the next period, or redistribute credits.\n\nWithin GitLab, group owners (GitLab.com) and instance administrators (Self-Managed) can view which users have been blocked due to reaching their per-user cap and restore access by adjusting the cap through the GraphQL API. \n\n## How budget guardrails help organizations scale AI usage\n\nGuardrails are essential as organizations ramp up their AI adoption. Here's why:\n\n### Predictable AI budgets\n\nUsage controls for GitLab Duo Agent Platform turn AI into a bounded, predictable budget item using on-demand GitLab Credits. That makes it easier to deploy agents across the software development lifecycle and get sign-off from finance, justify renewals, and plan quarterly spend.\n\n### Governance and chargeback\n\nLarge organizations often need to align AI consumption with internal budgets, cost centers, or departmental policies. Per-user caps give platform teams a straightforward mechanism to allocate credits fairly and track consumption at the individual level. The API import options make it practical to manage caps at enterprise scale. Combined with per-user usage data from the GitLab Credits dashboard, organizations can track consumption patterns to inform their own internal chargeback or budget allocation processes.\n\n### Confidence to scale\n\nMany customers start GitLab Duo Agent Platform with a small pilot group. Usage controls remove risks associated with expanding that pilot across the organization. You can roll out Duo Agent Platform to hundreds or thousands of developers knowing there's a hard ceiling protecting your budget. If usage grows faster than expected, you'll hit the cap, not an unexpected invoice.\n\n## Addressing the seat-based and visibility conundrum\n\nMany AI coding tools take a seat-based approach to cost management. You buy a fixed number of seats at a flat per-user price, and that's your budget. It's simple, but rigid. You pay the same whether a developer uses the tool ten times a day or never touches it. And as vendors introduce premium models and usage-based overages on top of seat pricing, the cost predictability that seat-based licensing promised starts to erode.\n\n\nGitLab takes a different approach. Usage-based pricing with hard caps and a single governance dashboard. You get the flexibility of paying for what your teams actually use, with the budget predictability of enforced spending limits.\n\n## Real-world usage controls\n\n**One example is a mid-size SaaS customer that wants to protect their monthly budget.** A 200-person engineering organization sets a subscription-level cap equal to their expected on-demand usage. Their VP of Engineering can confidently tell finance that GitLab Duo Agent Platform spend will never exceed the approved amount, even as they onboard new teams. If they approach the cap mid-month, the billing account manager gets a notification and can decide whether to raise the limit or wait for the next period.\n\n**At GitLab, we also work with large enterprises that want to keep usage fair across teams.** A global financial services company with 2,000 developers uses per-user caps to ensure equitable access. Staff engineers working on complex refactoring projects get a higher individual allocation via API, while most developers receive a standard flat cap. No single user can exhaust the pool, and the platform team uses the per-user usage data in the GitLab Credits dashboard to track consumption patterns and inform quarterly budget planning.\n\n## Getting started\n\nUsage controls are available for both GitLab.com and Self-Managed customers running GitLab 18.11. Different controls are configured in different places depending on the scope and your role.\n\n**Subscription-level cap**\n\nBilling account managers set the subscription-level on-demand cap in the Customers Portal:\n\n1. Sign in to the `Customers Portal`.  \n2. On your subscription card, navigate to **GitLab Credits** settings.  \n3. Enable the monthly on-demand credits cap and enter your desired limit.\n\n**Flat per-user cap**\n\nThe flat per-user cap can be set through the GitLab GraphQL API by namespace owners (GitLab.com) or instance administrators (Self-Managed). Check the [GitLab Credits documentation](https://docs.gitlab.com/subscriptions/gitlab_credits/) for the latest on available configuration surfaces.\n\n**Custom per-user overrides**\n\nFor differentiated limits, namespace owners (GitLab.com) and instance administrators (Self-Managed) can set individual caps programmatically. This is useful for automation and infrastructure-as-code workflows.\n\n**Monitor usage and cap status**\n\n* **Customers Portal:** View detailed usage and cap status.  \n* **GitLab.com:** Group owners can view blocked users under **Settings > GitLab Credits**.  \n* **Self-Managed:** Instance administrators can view cap status and blocked users under **Admin > GitLab Credits**.\n\n## GitLab Duo Agent Platform is ready to scale\n\nUsage controls are available now in GitLab 18.11. If you've been waiting for the right guardrails before expanding GitLab Duo Agent Platform across your organization, this is your moment. Set your caps, roll out Duo Agent Platform to more teams, and start shipping faster!\n\n> [Learn more about GitLab Credits and usage controls](https://docs.gitlab.com/subscriptions/gitlab_credits/).",[12,771,772],"AI/ML","news",{"featured":39,"template":16,"slug":774},"gitlab-18-11-budget-guardrails-for-gitlab-credits",{"content":776,"config":779},{"title":777,"heroImage":767,"description":778,"date":768,"category":12},"GitLab 18.11 release","This release includes Agentic SAST Vulnerability Resolution, Data Analyst Foundational Agent, CI Expert Agent, and more.",{"featured":39,"template":16,"externalUrl":780},"https://docs.gitlab.com/releases/18/gitlab-18-11-released/",{"content":782,"config":790},{"title":783,"description":784,"authors":785,"heroImage":767,"date":768,"body":787,"category":12,"tags":788},"GitLab 18.11: CI Expert and Data Analyst AI agents target development gaps","Set up CI and query your software development lifecycle data with two new GitLab Duo Agent Platform foundational agents available in GitLab 18.11.",[786],"Corinne Dent","AI-generated code moves faster than the systems around it can keep up with. More code means more merge requests queued, more pipelines to configure, more questions about delivery that nobody has time to answer — and most of the tooling teams rely on wasn't built for this pace.\n\nIn GitLab 18.11, two new foundational agents for Duo Agent Platform address specific gaps in the development lifecycle that AI has largely left untouched:\n* CI Expert Agent (now in beta) focuses on the gap between writing code and getting it into a running pipeline\n* Data Analyst Agent (now generally available) focuses on the gap between shipping code and being able to answer basic questions about how that delivery is actually going.\n\n\nThese are problem areas that couldn't be solved by a general-purpose assistant. A tool running outside GitLab can generate a YAML file or answer a question, but it has no awareness of how your pipelines have historically performed, where failures cluster, or what your actual MR cycle times look like. That context lives in GitLab. These agents do too.\n## Fast CI setup with CI Expert Agent\n\nAI has made it easier than ever to write code. Getting that code into a running pipeline is still something most teams do days, or weeks, later — if at all. The blank-page problem isn't in the editor anymore. The blank page is now in `.gitlab-ci.yml`.\n\nDevelopers who have never configured CI don't know what language detection looks like in YAML, what their test commands should be, or how to validate the result before pushing. Teams either copy a config from a previous project that may not fit, stitch together examples from documentation, or wait for the one person who's done it before. If that person isn't available, CI becomes the thing you'll \"get to later.\" Later becomes never.\n\nWhen CI never happens, the impact shows up everywhere else. Changes ship without a reliable safety net, regressions surface in production instead of in pipelines, and work piles up in bigger, riskier batches because no one wants to be the person who “breaks the build.” Over time, teams normalize working in the dark, often relying on undocumented institutional knowledge and ad-hoc testing, instead of having a fast, predictable feedback loop baked into every change.\n\nCI Expert Agent, now available in beta, removes that friction. It inspects your repository, identifies your language and framework, and proposes a working build and test pipeline tailored to what's actually there — then explains every decision in plain language. The target: a running pipeline in minutes, with no YAML written by hand.\n\nWhat CI Expert Agent does:\n\n* Repo-aware pipeline generation detects language, framework, and test setup \n* Generates valid, runnable build and test configurations   \n* Guided first-pipeline flow with plain-language explanation of each step in Agentic Chat  \n* Native GitLab CI semantics with no config translation required\n\nBecause it runs inside GitLab and sees real pipeline behavior over time, each improvement can build on how teams actually work, not just on static examples.\n\u003Ciframe src=\"https://player.vimeo.com/video/1183458036?badge=0&autopause=0&player_id=0&app_id=58479\" frameborder=\"0\" allow=\"autoplay; fullscreen; picture-in-picture; clipboard-write; encrypted-media; web-share\" referrerpolicy=\"strict-origin-when-cross-origin\" style=\"position:absolute;top:0;left:0;width:100%;height:100%;\" title=\"CI/CD Expert Agent\">\u003C/iframe>\u003Cscript src=\"https://player.vimeo.com/api/player.js\">\u003C/script>\n\u003Cbr>\u003C/br>\n\nCI Expert Agent is available on GitLab.com, Self-Managed, Dedicated; Free, Premium, Ultimate Editions with Duo Agent Platform enabled.\n\n## Query GitLab data in plain language with Data Analyst Agent\n\nAI has sped up how teams ship. Answering basic questions about how that work is going has gotten harder, not easier.\n\nHow long are MRs sitting in review? Which pipelines are slowing teams down? Are deployment targets actually being hit? These questions used to be answerable by glancing at a dashboard. Now, with more code, more teams, and more complexity, the data exists — it's in GitLab — but accessing it still means waiting on an analytics team, filing a dashboard request, or learning GLQL.\n\nData Analyst Agent targets that gap. Ask a natural-language question and get an instant visualization in Agentic Chat. No query language, no dashboard request, no waiting for the answers to be assembled by someone else.\n\nFor example, the agent can answer questions about the following topics for these roles:\n\n* Engineering managers: MR cycle time, throughput by project, where reviews get stuck  \n* Developers: Contribution patterns, flaky tests blocking their MRs, pipeline speed trends  \n* DevOps and platform engineers: Pipeline success/failure rates, runner utilization, deployment frequency  \n* Engineering leadership: Cross-portfolio deployment frequency, project health metrics, lead time comparisons\n\nNow generally available in 18.11, the agent covers MRs, issues, projects, pipelines, and jobs — full software development lifecycle coverage, expanded from the beta scope. Because Data Analyst Agent queries what's already in GitLab, the context is always current, and there's no pipeline to maintain or third-party tool to keep synchronized. Generated GitLab Query Language queries can be copied and used anywhere GitLab Flavored Markdown is supported, with direct export to work items and dashboards on the roadmap.\n\n\u003Ciframe src=\"https://player.vimeo.com/video/1183094817?badge=0&autopause=0&player_id=0&app_id=58479\" frameborder=\"0\" allow=\"autoplay; fullscreen; picture-in-picture; clipboard-write; encrypted-media; web-share\" referrerpolicy=\"strict-origin-when-cross-origin\" style=\"position:absolute;top:0;left:0;width:100%;height:100%;\" title=\"Data Analyst agent demo\">\u003C/iframe>\u003Cscript src=\"https://player.vimeo.com/api/player.js\">\u003C/script>\n\u003Cbr>\u003C/br>\n\nData Analyst Agent is available on GitLab.com, Self-Managed, Dedicated; Free, Premium and Ultimate Edition with Duo Agent Platform enabled.\n\n## One platform, connected context\n\nBoth agents run inside GitLab, with access to the code, pipelines, issues, and merge requests already there. That's what separates platform-native AI from a disconnected assistant: the context is always current, and it only gets more useful over time. CI Expert Agent and Data Analyst Agent represent two concrete steps toward a platform where AI doesn't just help you write code faster; it helps you understand, ship, and maintain what gets built.\n\n> [Start a free trial of GitLab Duo Agent Platform](https://about.gitlab.com/gitlab-duo/) to experience these foundational AI agents.",[771,789,12],"features",{"featured":15,"template":16,"slug":791},"ci-expert-and-data-analyst-ai-agents-target-development-gaps",{"promotions":793},[794,808,819,831],{"id":795,"categories":796,"header":798,"text":799,"button":800,"image":805},"ai-modernization",[797],"ai-ml","Is AI achieving its promise at scale?","Quiz will take 5 minutes or less",{"text":801,"config":802},"Get your AI maturity score",{"href":803,"dataGaName":804,"dataGaLocation":252},"/assessments/ai-modernization-assessment/","modernization assessment",{"config":806},{"src":807},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1772138786/qix0m7kwnd8x2fh1zq49.png",{"id":809,"categories":810,"header":811,"text":799,"button":812,"image":816},"devops-modernization",[12,576],"Are you just managing tools or shipping innovation?",{"text":813,"config":814},"Get your DevOps maturity score",{"href":815,"dataGaName":804,"dataGaLocation":252},"/assessments/devops-modernization-assessment/",{"config":817},{"src":818},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1772138785/eg818fmakweyuznttgid.png",{"id":820,"categories":821,"header":823,"text":799,"button":824,"image":828},"security-modernization",[822],"security","Are you trading speed for security?",{"text":825,"config":826},"Get your security maturity score",{"href":827,"dataGaName":804,"dataGaLocation":252},"/assessments/security-modernization-assessment/",{"config":829},{"src":830},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1772138786/p4pbqd9nnjejg5ds6mdk.png",{"id":832,"paths":833,"header":836,"text":837,"button":838,"image":843},"github-azure-migration",[834,835],"migration-from-azure-devops-to-gitlab","integrating-azure-devops-scm-and-gitlab","Is your team ready for GitHub's Azure move?","GitHub is already rebuilding around Azure. Find out what it means for you.",{"text":839,"config":840},"See how GitLab compares to GitHub",{"href":841,"dataGaName":842,"dataGaLocation":252},"/compare/gitlab-vs-github/github-azure-migration/","github azure migration",{"config":844},{"src":818},{"header":846,"blurb":847,"button":848,"secondaryButton":853},"Start building faster today","See what your team can do with the intelligent orchestration platform for DevSecOps.\n",{"text":849,"config":850},"Get your free trial",{"href":851,"dataGaName":61,"dataGaLocation":852},"https://gitlab.com/-/trial_registrations/new?glm_content=default-saas-trial&glm_source=about.gitlab.com/","feature",{"text":514,"config":854},{"href":65,"dataGaName":66,"dataGaLocation":852},1776444548772]