[{"data":1,"prerenderedAt":828},["ShallowReactive",2],{"/en-us/blog/gitlab-ux-2020-year-in-review":3,"navigation-en-us":42,"banner-en-us":463,"footer-en-us":473,"blog-post-authors-en-us-Christie Lenneville":715,"blog-related-posts-en-us-gitlab-ux-2020-year-in-review":730,"blog-promotions-en-us":765,"next-steps-en-us":818},{"id":4,"title":5,"authorSlugs":6,"authors":8,"body":10,"category":11,"categorySlug":11,"config":12,"content":16,"date":25,"description":17,"extension":26,"externalUrl":27,"featured":15,"heroImage":19,"isFeatured":15,"meta":28,"navigation":29,"path":30,"publishedDate":25,"rawbody":31,"seo":32,"slug":14,"stem":36,"tagSlugs":37,"tags":40,"template":13,"updatedDate":27,"__hash__":41},"blogPosts/en-us/blog/gitlab-ux-2020-year-in-review.md","GitLab UX 2020 Year in Review",[7],"christie-lenneville",[9],"Christie Lenneville","A global pandemic and broad social unrest have made this year difficult for everyone. When times are as tough as 2020 has proven to be, it's easy to focus on the negative and forget about the many good things that happened along the way. But our product designers, user researchers, and technical writers spend every day doing great work, and we can't let that slip by unnoticed.\n\nIn this post, I want to be intentional about celebrating our successes during a year when many of us wanted to just curl up under a comfy blanket and wait for the turmoil to pass. So, let's take a moment to reflect on some of the things we can feel really proud to have achieved.\n\n## Usability is now a key consideration in our category maturity model\n\nHistorically, we rated the maturity of our product areas fairly subjectively and based almost entirely on feature availability. This year, that changed when we introduced [Category Maturity Scorecards](https://handbook.gitlab.com/handbook/product/ux/category-maturity/category-maturity-scorecards/) that are based on user research. Now, we start by considering the Job to be Done (JTBD) that our users need to accomplish, and we gather user feedback to rate the entire experience -- not just functionality, but usability, too.\n\nWe've learned some amazing things through this new approach, and those learnings have enabled us to make [valuable recommendations](https://gitlab.com/gitlab-org/gitlab/-/issues?label_name%5B%5D=cm-scorecard-rec) to improve our product experience in areas like Code Review, Logging, and Issue Management. We have several additional scorecard initiatives underway, which means that our focus on creating an exceptional experience will only continue to grow.\n\nSo often, UX departments complain that they have to fight for executives to acknowledge the importance of usability on business outcomes. In this case, refining category maturity started as an idea from [Sid](https://gitlab.com/sytses), our CEO. This is honestly amazing! It's the kind of user-centered focus that UX teams get really excited about.\n\nAs the person who leads UX at GitLab, it was awesome for me to watch our cross-functional team immediately get on board. Because measuring product maturity isn't an industry standard, through our value of [Iteration](https://handbook.gitlab.com/handbook/values/#iteration) it took us some time (and a false start) to determine the right approach. Fortunately, Product leadership was both enthusiastic and patient, UX Researchers were persistent in taking feedback and making methodological refinements, and Product Designers were courageous in trying something they've never done before. Even better: Technical Writing has been involved, too, as we've identified documentation improvements that will refine our product maturity.\n\nThis was truly a team effort, and I appreciate everyone who participated. 🤝\n\n## Our design system evolved from an idea into reality\n\nWhen I joined GitLab in early 2019, our design system, [Pajamas](https://design.gitlab.com/), was a scrappy project that the design team was working hard to get off the ground. We had designed a set of 28 single-source-of-truth components and were working hard to build them into [GitLab UI](https://gitlab.com/gitlab-org/gitlab-ui), our Vue-based component library.\nWe now have a robust design library that's implemented in Figma, and a large collection of SSOT Vue components are available to use in the product, too. Even more exciting: We're just finishing with implementing our 8 most impactful components across the entire product UI (buttons, alerts, dropdowns, modals, tabs, popovers, and tooltips), which will result in better performance and consistency when we're done. (We're so close!)\n\nMost amazing to me was watching product designers and technical writers jump in to do much of this component migration work themselves. This was no small feat, because frontend development is not something that many of us are deeply skilled at. But, apparently we're both tenacious and brave, because we did the work anyway (with lots of help from our Frontend Engineers and the awesome documentation that our UX Foundations team created). In the process, we've gotten to know both our product features (which are complex) and our code base (which is also complex) even better, which makes us more effective in our day-to-day jobs.\n\nSpeaking of our UX Foundations team, this is another related success. At the beginning of 2020, we got the budgetary support to create a team that is dedicated solely to maintaining our design system and tooling. The team may be small, but its impact certainly isn't. They've already made some big improvements to things like:\n\n* **Improving tooling for designers:** The move to Figma allows for greater collaboration, as well as community contributions. Sketch is only available on Mac platforms and there are no real-time collaboration features. Figma allows us to provide a UI Kit that is available across platforms, while being available for community contributors to use for free. It also promotes collaboration through its use of real-time editing capabilities and version history. We were able to streamline developer handoff by simply linking to the design file, reducing the need for additional plugins such as Sketch Measure.\n* **Making our color palette consistent and accessible:** We addressed color contrast for accessibility and normalized the palette across hues, so that we can better systematize variable use throughout the UI.\n* **Improving consistency in our icons:** With the creation of our own [SVG Library](http://gitlab-org.gitlab.io/gitlab-svgs/), we've been working to [deprecate our use of Font Awesome](https://gitlab.com/groups/gitlab-org/-/epics/2331) throughout the year. With the help of the Frontend department, we've closed out 156 out of 168 issues related to this effort.\n* **Moving towards more accessible workflows:** Near the end of the year, we've started focusing more on building accessibility standards into our workflows. We are currently auditing and updating our [voluntary product accessibility template](https://design.gitlab.com/accessibility/vpat), as well as [incorporating accessibility audit guides](https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/merge_requests/2158) into Pajamas.\n\n## Actionable insights\n\nUser research is so incredibly valuable... when you take action on it. But it can be a challenge for research teams to condense their powerful findings into small but compelling insights and then track those insights to determine whether they actually make it into the product.\n\nIn the second half of this year, our user research team made two big strides in this area. First, we started using [Dovetail](https://dovetailapp.com/) to help us more easily analyze research data to find meangingful insights and share it collaboratively with Product Managers and Product Designers (and anyone else who may be interested). But, they took this a step farther by also beginning to [track actionable insights](https://handbook.gitlab.com/handbook/product/ux/performance-indicators/#actionable-insights) as a performance indicator.\n\nThe considerable effort it took to get both of these programs in place will be worth it as we watch our research efforts result in an even better product.\n\n## Beautifying our docs\n\nComplex products like GitLab require high-quality documentation. Some things you just can't (and shouldn't) communicate through the UI, so users rely on great docs to get their daily jobs done.\n\nOur Technical Writing team (many of whom have been with GitLab less than a year) worked hard to improve our docs site during 2020, including:\n\n- Several UX research projects to discover - and fix! - problems users encounter when using the docs site.\n- A \"Beautification\" effort that focused on an updated visual design. Our 2020 GitLab Contribute event included many rapid improvements to the docs site, and we made many more afterward. (Did you notice?)\n- Ongoing content improvements, including making our docs more consistent, findable, detailed, and easier to read.\n- Adding (a lot of) metadata information to product docs to help connect content contributors with Technical Writers.\n- Coding innovations for automation, such as grammar checking with Vale, a linter, to automatically catch errors before they’re merged.\n\nWe’ve also completed work on a Docs Strategy roadmap to drive even more improvements in the upcoming months.\n\n## And so much more...\n\n* GitLab Design Talks: In this fun video series, watch designers, technical writers, researchers, and product managers talk about [Iteration](https://www.youtube.com/playlist?list=PL05JrBw4t0KpgzLWbRCXf8o7iap-uoe7o) and [Collaboration](https://www.youtube.com/playlist?list=PL05JrBw4t0KrER807JktsL-addVZa4N0-) at GitLab. (Special thanks to host [Nick Post](https://gitlab.com/npost)!)\n* UX Showcase: See [100+ videos](https://www.youtube.com/playlist?list=PL05JrBw4t0Kq89nFXtkVviaIfYQPptwJz) highlighting exciting UX work happening across GitLab. I learn something new everytime I watch one of these.\n* Blog posts: Read about a variety of topics we were thinking about in 2020, including:\n    * [Designing in an all-remote company](https://about.gitlab.com/blog/designing-in-an-all-remote-company/)\n    * [Running an asynchronous sketching workshop for UX](https://about.gitlab.com/blog/async-sketching/)\n    * [Synchronous collaboration as a remote designer at GitLab](https://about.gitlab.com/blog/synchronous-collaboration-as-a-remote-designer-at-gitlab/)\n    * [A tale of two file editors](https://about.gitlab.com/blog/a-tale-of-two-editors/)\n    * [How holistic UX design increased GitLab.com free trial signups](https://about.gitlab.com/blog/how-holistic-ux-design-increased-gitlab-free-trial-signups/)\n    * [Improving iteration and collaboration with user stories](https://about.gitlab.com/blog/how-we-utilize-user-stories-as-a-collaborative-design-tool/)\n    * [Designing incident management from scratch](https://about.gitlab.com/blog/designing-alerts-and-incidents/)\n    * [Why GitLab is the right design collaboration tool for the entire team ](https://about.gitlab.com/blog/why-gitlab-is-the-right-design-collaboration-tool-for-the-whole-team/)\n\nAgain, the GitLab UX team does amazing work every single day, and there is no way to capture all of that effort in a single blog post. As this year wraps up, I hope you personally take time to think about your own successes and the impact they had on our fast-moving company.\n\nI also hope you know that we value every one of you. You are appreciated. 💜\n\n\n\n\u003Cdiv class=\"panel panel-gitlab-purple\">\n  \u003Cp class=\"panel-heading\">\u003Cstrong>One more thing...\u003C/strong>\u003C/p>\n\u003Cdiv class=\"panel-body\">\n\n\u003Cp>The final 2020 highlight I wanted to ensure is here was Christie Lenneville's own promotion to be GitLab's first \u003Cstrong>Vice President of User Experience (UX)\u003C/strong>. I knew that as both the author of this article, and as a humble (and great) leader she'd be hesitant to add this herself. But it's not only a recognition of her achievements and her potential. VP-level leadership of UX at GitLab should *also* be a signal of how important UX is to our organization and to our community. And it should indicate that usability is an important differentiator for GitLab, and a critical part of our company's strategy. Congratulations again, Christie!\u003C/p>\n\n— Eric Johnson, Chief Technology Officer\n\n\u003C/div>\n\u003C/div>","product",{"template":13,"slug":14,"featured":15},"BlogPost","gitlab-ux-2020-year-in-review",false,{"title":5,"description":17,"authors":18,"heroImage":19,"tags":20,"category":11,"date":25,"body":10},"2020 was a difficult but productive year. Let's take a look back.",[9],"https://res.cloudinary.com/about-gitlab-com/image/upload/v1749664102/Blog/Hero%20Images/gitlab-values-cover.png",[21,22,23,24],"UX","design","inside GitLab","research","2020-11-20","md",null,{},true,"/en-us/blog/gitlab-ux-2020-year-in-review","---\nseo:\n  title: GitLab UX 2020 Year in Review\n  description: 2020 was a difficult but productive year. Let's take a look back.\n  ogTitle: GitLab UX 2020 Year in Review\n  ogDescription: 2020 was a difficult but productive year. Let's take a look back.\n  noIndex: false\n  ogImage: >-\n    https://res.cloudinary.com/about-gitlab-com/image/upload/v1749664102/Blog/Hero%20Images/gitlab-values-cover.png\n  ogUrl: https://about.gitlab.com/blog/gitlab-ux-2020-year-in-review\n  ogSiteName: https://about.gitlab.com\n  ogType: article\n  canonicalUrls: https://about.gitlab.com/blog/gitlab-ux-2020-year-in-review\ntitle: GitLab UX 2020 Year in Review\ndescription: 2020 was a difficult but productive year. Let's take a look back.\nauthors:\n  - Christie Lenneville\nheroImage: https://res.cloudinary.com/about-gitlab-com/image/upload/v1749664102/Blog/Hero%20Images/gitlab-values-cover.png\ntags:\n  - UX\n  - design\n  - inside GitLab\n  - research\ncategory: product\ndate: '2020-11-20'\nslug: gitlab-ux-2020-year-in-review\nfeatured: false\ntemplate: BlogPost\n---\n\nA global pandemic and broad social unrest have made this year difficult for everyone. When times are as tough as 2020 has proven to be, it's easy to focus on the negative and forget about the many good things that happened along the way. But our product designers, user researchers, and technical writers spend every day doing great work, and we can't let that slip by unnoticed.\n\nIn this post, I want to be intentional about celebrating our successes during a year when many of us wanted to just curl up under a comfy blanket and wait for the turmoil to pass. So, let's take a moment to reflect on some of the things we can feel really proud to have achieved.\n\n## Usability is now a key consideration in our category maturity model\n\nHistorically, we rated the maturity of our product areas fairly subjectively and based almost entirely on feature availability. This year, that changed when we introduced [Category Maturity Scorecards](https://handbook.gitlab.com/handbook/product/ux/category-maturity/category-maturity-scorecards/) that are based on user research. Now, we start by considering the Job to be Done (JTBD) that our users need to accomplish, and we gather user feedback to rate the entire experience -- not just functionality, but usability, too.\n\nWe've learned some amazing things through this new approach, and those learnings have enabled us to make [valuable recommendations](https://gitlab.com/gitlab-org/gitlab/-/issues?label_name%5B%5D=cm-scorecard-rec) to improve our product experience in areas like Code Review, Logging, and Issue Management. We have several additional scorecard initiatives underway, which means that our focus on creating an exceptional experience will only continue to grow.\n\nSo often, UX departments complain that they have to fight for executives to acknowledge the importance of usability on business outcomes. In this case, refining category maturity started as an idea from [Sid](https://gitlab.com/sytses), our CEO. This is honestly amazing! It's the kind of user-centered focus that UX teams get really excited about.\n\nAs the person who leads UX at GitLab, it was awesome for me to watch our cross-functional team immediately get on board. Because measuring product maturity isn't an industry standard, through our value of [Iteration](https://handbook.gitlab.com/handbook/values/#iteration) it took us some time (and a false start) to determine the right approach. Fortunately, Product leadership was both enthusiastic and patient, UX Researchers were persistent in taking feedback and making methodological refinements, and Product Designers were courageous in trying something they've never done before. Even better: Technical Writing has been involved, too, as we've identified documentation improvements that will refine our product maturity.\n\nThis was truly a team effort, and I appreciate everyone who participated. 🤝\n\n## Our design system evolved from an idea into reality\n\nWhen I joined GitLab in early 2019, our design system, [Pajamas](https://design.gitlab.com/), was a scrappy project that the design team was working hard to get off the ground. We had designed a set of 28 single-source-of-truth components and were working hard to build them into [GitLab UI](https://gitlab.com/gitlab-org/gitlab-ui), our Vue-based component library.\nWe now have a robust design library that's implemented in Figma, and a large collection of SSOT Vue components are available to use in the product, too. Even more exciting: We're just finishing with implementing our 8 most impactful components across the entire product UI (buttons, alerts, dropdowns, modals, tabs, popovers, and tooltips), which will result in better performance and consistency when we're done. (We're so close!)\n\nMost amazing to me was watching product designers and technical writers jump in to do much of this component migration work themselves. This was no small feat, because frontend development is not something that many of us are deeply skilled at. But, apparently we're both tenacious and brave, because we did the work anyway (with lots of help from our Frontend Engineers and the awesome documentation that our UX Foundations team created). In the process, we've gotten to know both our product features (which are complex) and our code base (which is also complex) even better, which makes us more effective in our day-to-day jobs.\n\nSpeaking of our UX Foundations team, this is another related success. At the beginning of 2020, we got the budgetary support to create a team that is dedicated solely to maintaining our design system and tooling. The team may be small, but its impact certainly isn't. They've already made some big improvements to things like:\n\n* **Improving tooling for designers:** The move to Figma allows for greater collaboration, as well as community contributions. Sketch is only available on Mac platforms and there are no real-time collaboration features. Figma allows us to provide a UI Kit that is available across platforms, while being available for community contributors to use for free. It also promotes collaboration through its use of real-time editing capabilities and version history. We were able to streamline developer handoff by simply linking to the design file, reducing the need for additional plugins such as Sketch Measure.\n* **Making our color palette consistent and accessible:** We addressed color contrast for accessibility and normalized the palette across hues, so that we can better systematize variable use throughout the UI.\n* **Improving consistency in our icons:** With the creation of our own [SVG Library](http://gitlab-org.gitlab.io/gitlab-svgs/), we've been working to [deprecate our use of Font Awesome](https://gitlab.com/groups/gitlab-org/-/epics/2331) throughout the year. With the help of the Frontend department, we've closed out 156 out of 168 issues related to this effort.\n* **Moving towards more accessible workflows:** Near the end of the year, we've started focusing more on building accessibility standards into our workflows. We are currently auditing and updating our [voluntary product accessibility template](https://design.gitlab.com/accessibility/vpat), as well as [incorporating accessibility audit guides](https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/merge_requests/2158) into Pajamas.\n\n## Actionable insights\n\nUser research is so incredibly valuable... when you take action on it. But it can be a challenge for research teams to condense their powerful findings into small but compelling insights and then track those insights to determine whether they actually make it into the product.\n\nIn the second half of this year, our user research team made two big strides in this area. First, we started using [Dovetail](https://dovetailapp.com/) to help us more easily analyze research data to find meangingful insights and share it collaboratively with Product Managers and Product Designers (and anyone else who may be interested). But, they took this a step farther by also beginning to [track actionable insights](https://handbook.gitlab.com/handbook/product/ux/performance-indicators/#actionable-insights) as a performance indicator.\n\nThe considerable effort it took to get both of these programs in place will be worth it as we watch our research efforts result in an even better product.\n\n## Beautifying our docs\n\nComplex products like GitLab require high-quality documentation. Some things you just can't (and shouldn't) communicate through the UI, so users rely on great docs to get their daily jobs done.\n\nOur Technical Writing team (many of whom have been with GitLab less than a year) worked hard to improve our docs site during 2020, including:\n\n- Several UX research projects to discover - and fix! - problems users encounter when using the docs site.\n- A \"Beautification\" effort that focused on an updated visual design. Our 2020 GitLab Contribute event included many rapid improvements to the docs site, and we made many more afterward. (Did you notice?)\n- Ongoing content improvements, including making our docs more consistent, findable, detailed, and easier to read.\n- Adding (a lot of) metadata information to product docs to help connect content contributors with Technical Writers.\n- Coding innovations for automation, such as grammar checking with Vale, a linter, to automatically catch errors before they’re merged.\n\nWe’ve also completed work on a Docs Strategy roadmap to drive even more improvements in the upcoming months.\n\n## And so much more...\n\n* GitLab Design Talks: In this fun video series, watch designers, technical writers, researchers, and product managers talk about [Iteration](https://www.youtube.com/playlist?list=PL05JrBw4t0KpgzLWbRCXf8o7iap-uoe7o) and [Collaboration](https://www.youtube.com/playlist?list=PL05JrBw4t0KrER807JktsL-addVZa4N0-) at GitLab. (Special thanks to host [Nick Post](https://gitlab.com/npost)!)\n* UX Showcase: See [100+ videos](https://www.youtube.com/playlist?list=PL05JrBw4t0Kq89nFXtkVviaIfYQPptwJz) highlighting exciting UX work happening across GitLab. I learn something new everytime I watch one of these.\n* Blog posts: Read about a variety of topics we were thinking about in 2020, including:\n    * [Designing in an all-remote company](https://about.gitlab.com/blog/designing-in-an-all-remote-company/)\n    * [Running an asynchronous sketching workshop for UX](https://about.gitlab.com/blog/async-sketching/)\n    * [Synchronous collaboration as a remote designer at GitLab](https://about.gitlab.com/blog/synchronous-collaboration-as-a-remote-designer-at-gitlab/)\n    * [A tale of two file editors](https://about.gitlab.com/blog/a-tale-of-two-editors/)\n    * [How holistic UX design increased GitLab.com free trial signups](https://about.gitlab.com/blog/how-holistic-ux-design-increased-gitlab-free-trial-signups/)\n    * [Improving iteration and collaboration with user stories](https://about.gitlab.com/blog/how-we-utilize-user-stories-as-a-collaborative-design-tool/)\n    * [Designing incident management from scratch](https://about.gitlab.com/blog/designing-alerts-and-incidents/)\n    * [Why GitLab is the right design collaboration tool for the entire team ](https://about.gitlab.com/blog/why-gitlab-is-the-right-design-collaboration-tool-for-the-whole-team/)\n\nAgain, the GitLab UX team does amazing work every single day, and there is no way to capture all of that effort in a single blog post. As this year wraps up, I hope you personally take time to think about your own successes and the impact they had on our fast-moving company.\n\nI also hope you know that we value every one of you. You are appreciated. 💜\n\n\n\n\u003Cdiv class=\"panel panel-gitlab-purple\">\n  \u003Cp class=\"panel-heading\">\u003Cstrong>One more thing...\u003C/strong>\u003C/p>\n\u003Cdiv class=\"panel-body\">\n\n\u003Cp>The final 2020 highlight I wanted to ensure is here was Christie Lenneville's own promotion to be GitLab's first \u003Cstrong>Vice President of User Experience (UX)\u003C/strong>. I knew that as both the author of this article, and as a humble (and great) leader she'd be hesitant to add this herself. But it's not only a recognition of her achievements and her potential. VP-level leadership of UX at GitLab should *also* be a signal of how important UX is to our organization and to our community. And it should indicate that usability is an important differentiator for GitLab, and a critical part of our company's strategy. Congratulations again, Christie!\u003C/p>\n\n— Eric Johnson, Chief Technology Officer\n\n\u003C/div>\n\u003C/div>\n",{"title":5,"description":17,"ogTitle":5,"ogDescription":17,"noIndex":15,"ogImage":19,"ogUrl":33,"ogSiteName":34,"ogType":35,"canonicalUrls":33},"https://about.gitlab.com/blog/gitlab-ux-2020-year-in-review","https://about.gitlab.com","article","en-us/blog/gitlab-ux-2020-year-in-review",[38,22,39,24],"ux","inside-gitlab",[21,22,23,24],"gF-nOhAKuYIs50w3T1_GN_NyBGvtoN6g9_pjjwY6iJI",{"logo":43,"freeTrial":48,"sales":53,"login":58,"items":63,"search":383,"minimal":414,"duo":433,"switchNav":442,"pricingDeployment":453},{"config":44},{"href":45,"dataGaName":46,"dataGaLocation":47},"/","gitlab logo","header",{"text":49,"config":50},"Get free trial",{"href":51,"dataGaName":52,"dataGaLocation":47},"https://gitlab.com/-/trial_registrations/new?glm_source=about.gitlab.com&glm_content=default-saas-trial/","free trial",{"text":54,"config":55},"Talk to sales",{"href":56,"dataGaName":57,"dataGaLocation":47},"/sales/","sales",{"text":59,"config":60},"Sign in",{"href":61,"dataGaName":62,"dataGaLocation":47},"https://gitlab.com/users/sign_in/","sign in",[64,93,193,198,302,363],{"text":65,"config":66,"menu":68},"Platform",{"dataNavLevelOne":67},"platform",{"type":69,"columns":70},"cards",[71,77,85],{"title":65,"description":72,"link":73},"The intelligent orchestration platform for DevSecOps",{"text":74,"config":75},"Explore our Platform",{"href":76,"dataGaName":67,"dataGaLocation":47},"/platform/",{"title":78,"description":79,"link":80},"GitLab Duo Agent Platform","Agentic AI for the entire software lifecycle",{"text":81,"config":82},"Meet GitLab Duo",{"href":83,"dataGaName":84,"dataGaLocation":47},"/gitlab-duo-agent-platform/","gitlab duo agent platform",{"title":86,"description":87,"link":88},"Why GitLab","See the top reasons enterprises choose GitLab",{"text":89,"config":90},"Learn more",{"href":91,"dataGaName":92,"dataGaLocation":47},"/why-gitlab/","why gitlab",{"text":94,"left":29,"config":95,"menu":97},"Product",{"dataNavLevelOne":96},"solutions",{"type":98,"link":99,"columns":103,"feature":172},"lists",{"text":100,"config":101},"View all Solutions",{"href":102,"dataGaName":96,"dataGaLocation":47},"/solutions/",[104,128,151],{"title":105,"description":106,"link":107,"items":112},"Automation","CI/CD and automation to accelerate deployment",{"config":108},{"icon":109,"href":110,"dataGaName":111,"dataGaLocation":47},"AutomatedCodeAlt","/solutions/delivery-automation/","automated software delivery",[113,117,120,124],{"text":114,"config":115},"CI/CD",{"href":116,"dataGaLocation":47,"dataGaName":114},"/solutions/continuous-integration/",{"text":78,"config":118},{"href":83,"dataGaLocation":47,"dataGaName":119},"gitlab duo agent platform - product menu",{"text":121,"config":122},"Source Code Management",{"href":123,"dataGaLocation":47,"dataGaName":121},"/solutions/source-code-management/",{"text":125,"config":126},"Automated Software Delivery",{"href":110,"dataGaLocation":47,"dataGaName":127},"Automated software delivery",{"title":129,"description":130,"link":131,"items":136},"Security","Deliver code faster without compromising security",{"config":132},{"href":133,"dataGaName":134,"dataGaLocation":47,"icon":135},"/solutions/application-security-testing/","security and compliance","ShieldCheckLight",[137,141,146],{"text":138,"config":139},"Application Security Testing",{"href":133,"dataGaName":140,"dataGaLocation":47},"Application security testing",{"text":142,"config":143},"Software Supply Chain Security",{"href":144,"dataGaLocation":47,"dataGaName":145},"/solutions/supply-chain/","Software supply chain security",{"text":147,"config":148},"Software Compliance",{"href":149,"dataGaName":150,"dataGaLocation":47},"/solutions/software-compliance/","software compliance",{"title":152,"link":153,"items":158},"Measurement",{"config":154},{"icon":155,"href":156,"dataGaName":157,"dataGaLocation":47},"DigitalTransformation","/solutions/visibility-measurement/","visibility and measurement",[159,163,167],{"text":160,"config":161},"Visibility & Measurement",{"href":156,"dataGaLocation":47,"dataGaName":162},"Visibility and Measurement",{"text":164,"config":165},"Value Stream Management",{"href":166,"dataGaLocation":47,"dataGaName":164},"/solutions/value-stream-management/",{"text":168,"config":169},"Analytics & Insights",{"href":170,"dataGaLocation":47,"dataGaName":171},"/solutions/analytics-and-insights/","Analytics and insights",{"title":173,"type":98,"items":174},"GitLab for",[175,181,187],{"text":176,"config":177},"Enterprise",{"icon":178,"href":179,"dataGaLocation":47,"dataGaName":180},"Building","/enterprise/","enterprise",{"text":182,"config":183},"Small Business",{"icon":184,"href":185,"dataGaLocation":47,"dataGaName":186},"Work","/small-business/","small business",{"text":188,"config":189},"Public Sector",{"icon":190,"href":191,"dataGaLocation":47,"dataGaName":192},"Organization","/solutions/public-sector/","public sector",{"text":194,"config":195},"Pricing",{"href":196,"dataGaName":197,"dataGaLocation":47,"dataNavLevelOne":197},"/pricing/","pricing",{"text":199,"config":200,"menu":202},"Resources",{"dataNavLevelOne":201},"resources",{"type":98,"link":203,"columns":207,"feature":291},{"text":204,"config":205},"View all resources",{"href":206,"dataGaName":201,"dataGaLocation":47},"/resources/",[208,241,263],{"title":209,"items":210},"Getting started",[211,216,221,226,231,236],{"text":212,"config":213},"Install",{"href":214,"dataGaName":215,"dataGaLocation":47},"/install/","install",{"text":217,"config":218},"Quick start guides",{"href":219,"dataGaName":220,"dataGaLocation":47},"/get-started/","quick setup checklists",{"text":222,"config":223},"Learn",{"href":224,"dataGaLocation":47,"dataGaName":225},"https://university.gitlab.com/","learn",{"text":227,"config":228},"Product documentation",{"href":229,"dataGaName":230,"dataGaLocation":47},"https://docs.gitlab.com/","product documentation",{"text":232,"config":233},"Best practice videos",{"href":234,"dataGaName":235,"dataGaLocation":47},"/getting-started-videos/","best practice videos",{"text":237,"config":238},"Integrations",{"href":239,"dataGaName":240,"dataGaLocation":47},"/integrations/","integrations",{"title":242,"items":243},"Discover",[244,249,254,258],{"text":245,"config":246},"Customer success stories",{"href":247,"dataGaName":248,"dataGaLocation":47},"/customers/","customer success stories",{"text":250,"config":251},"Blog",{"href":252,"dataGaName":253,"dataGaLocation":47},"/blog/","blog",{"text":255,"config":256},"The Source",{"href":257,"dataGaName":253,"dataGaLocation":47},"/the-source/",{"text":259,"config":260},"Remote",{"href":261,"dataGaName":262,"dataGaLocation":47},"https://handbook.gitlab.com/handbook/company/culture/all-remote/","remote",{"title":264,"items":265},"Connect",[266,271,276,281,286],{"text":267,"config":268},"GitLab Services",{"href":269,"dataGaName":270,"dataGaLocation":47},"/services/","services",{"text":272,"config":273},"Community",{"href":274,"dataGaName":275,"dataGaLocation":47},"/community/","community",{"text":277,"config":278},"Forum",{"href":279,"dataGaName":280,"dataGaLocation":47},"https://forum.gitlab.com/","forum",{"text":282,"config":283},"Events",{"href":284,"dataGaName":285,"dataGaLocation":47},"/events/","events",{"text":287,"config":288},"Partners",{"href":289,"dataGaName":290,"dataGaLocation":47},"/partners/","partners",{"config":292,"title":295,"text":296,"link":297},{"background":293,"textColor":294},"url('https://res.cloudinary.com/about-gitlab-com/image/upload/v1777322348/qpq8yrgn8knii57omj0c.png')","#000","What’s new in GitLab","Stay updated with our latest features and improvements.",{"text":298,"config":299},"Read the latest",{"href":300,"dataGaName":301,"dataGaLocation":47},"/releases/whats-new/","whats new",{"text":303,"config":304,"menu":306},"Company",{"dataNavLevelOne":305},"company",{"type":98,"columns":307},[308],{"items":309},[310,315,321,323,328,333,338,343,348,353,358],{"text":311,"config":312},"About",{"href":313,"dataGaName":314,"dataGaLocation":47},"/company/","about",{"text":316,"config":317,"footerGa":320},"Jobs",{"href":318,"dataGaName":319,"dataGaLocation":47},"/jobs/","jobs",{"dataGaName":319},{"text":282,"config":322},{"href":284,"dataGaName":285,"dataGaLocation":47},{"text":324,"config":325},"Leadership",{"href":326,"dataGaName":327,"dataGaLocation":47},"/company/team/e-group/","leadership",{"text":329,"config":330},"Team",{"href":331,"dataGaName":332,"dataGaLocation":47},"/company/team/","team",{"text":334,"config":335},"Handbook",{"href":336,"dataGaName":337,"dataGaLocation":47},"https://handbook.gitlab.com/","handbook",{"text":339,"config":340},"Investor relations",{"href":341,"dataGaName":342,"dataGaLocation":47},"https://ir.gitlab.com/","investor relations",{"text":344,"config":345},"Trust Center",{"href":346,"dataGaName":347,"dataGaLocation":47},"/security/","trust center",{"text":349,"config":350},"AI Transparency Center",{"href":351,"dataGaName":352,"dataGaLocation":47},"/ai-transparency-center/","ai transparency center",{"text":354,"config":355},"Newsletter",{"href":356,"dataGaName":357,"dataGaLocation":47},"/company/contact/#contact-forms","newsletter",{"text":359,"config":360},"Press",{"href":361,"dataGaName":362,"dataGaLocation":47},"/press/","press",{"text":364,"config":365,"menu":366},"Contact us",{"dataNavLevelOne":305},{"type":98,"columns":367},[368],{"items":369},[370,373,378],{"text":54,"config":371},{"href":56,"dataGaName":372,"dataGaLocation":47},"talk to sales",{"text":374,"config":375},"Support portal",{"href":376,"dataGaName":377,"dataGaLocation":47},"https://support.gitlab.com","support portal",{"text":379,"config":380},"Customer portal",{"href":381,"dataGaName":382,"dataGaLocation":47},"https://customers.gitlab.com/customers/sign_in/","customer portal",{"close":384,"login":385,"suggestions":392},"Close",{"text":386,"link":387},"To search repositories and projects, login to",{"text":388,"config":389},"gitlab.com",{"href":61,"dataGaName":390,"dataGaLocation":391},"search login","search",{"text":393,"default":394},"Suggestions",[395,397,401,403,407,411],{"text":78,"config":396},{"href":83,"dataGaName":78,"dataGaLocation":391},{"text":398,"config":399},"Code Suggestions (AI)",{"href":400,"dataGaName":398,"dataGaLocation":391},"/solutions/code-suggestions/",{"text":114,"config":402},{"href":116,"dataGaName":114,"dataGaLocation":391},{"text":404,"config":405},"GitLab on AWS",{"href":406,"dataGaName":404,"dataGaLocation":391},"/partners/technology-partners/aws/",{"text":408,"config":409},"GitLab on Google Cloud",{"href":410,"dataGaName":408,"dataGaLocation":391},"/partners/technology-partners/google-cloud-platform/",{"text":412,"config":413},"Why GitLab?",{"href":91,"dataGaName":412,"dataGaLocation":391},{"freeTrial":415,"mobileIcon":420,"desktopIcon":425,"secondaryButton":428},{"text":416,"config":417},"Start free trial",{"href":418,"dataGaName":52,"dataGaLocation":419},"https://gitlab.com/-/trials/new/","nav",{"altText":421,"config":422},"Gitlab Icon",{"src":423,"dataGaName":424,"dataGaLocation":419},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1758203874/jypbw1jx72aexsoohd7x.svg","gitlab icon",{"altText":421,"config":426},{"src":427,"dataGaName":424,"dataGaLocation":419},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1758203875/gs4c8p8opsgvflgkswz9.svg",{"text":429,"config":430},"Get Started",{"href":431,"dataGaName":432,"dataGaLocation":419},"https://gitlab.com/-/trial_registrations/new?glm_source=about.gitlab.com/get-started/","get started",{"freeTrial":434,"mobileIcon":438,"desktopIcon":440},{"text":435,"config":436},"Learn more about GitLab Duo",{"href":83,"dataGaName":437,"dataGaLocation":419},"gitlab duo",{"altText":421,"config":439},{"src":423,"dataGaName":424,"dataGaLocation":419},{"altText":421,"config":441},{"src":427,"dataGaName":424,"dataGaLocation":419},{"button":443,"mobileIcon":448,"desktopIcon":450},{"text":444,"config":445},"/switch",{"href":446,"dataGaName":447,"dataGaLocation":419},"#contact","switch",{"altText":421,"config":449},{"src":423,"dataGaName":424,"dataGaLocation":419},{"altText":421,"config":451},{"src":452,"dataGaName":424,"dataGaLocation":419},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1773335277/ohhpiuoxoldryzrnhfrh.png",{"freeTrial":454,"mobileIcon":459,"desktopIcon":461},{"text":455,"config":456},"Back to pricing",{"href":196,"dataGaName":457,"dataGaLocation":419,"icon":458},"back to pricing","GoBack",{"altText":421,"config":460},{"src":423,"dataGaName":424,"dataGaLocation":419},{"altText":421,"config":462},{"src":427,"dataGaName":424,"dataGaLocation":419},{"title":464,"button":465,"config":470},"See how agentic AI transforms software delivery",{"text":466,"config":467},"Sign up for GitLab Transcend on June 10",{"href":468,"dataGaName":469,"dataGaLocation":47},"/releases/whats-new/#sign-up","transcend event",{"layout":471,"icon":472,"disabled":15},"release","AiStar",{"data":474},{"text":475,"source":476,"edit":482,"contribute":487,"config":492,"items":497,"minimal":704},"Git is a trademark of Software Freedom Conservancy and our use of 'GitLab' is under license",{"text":477,"config":478},"View page source",{"href":479,"dataGaName":480,"dataGaLocation":481},"https://gitlab.com/gitlab-com/marketing/digital-experience/about-gitlab-com/","page source","footer",{"text":483,"config":484},"Edit this page",{"href":485,"dataGaName":486,"dataGaLocation":481},"https://gitlab.com/gitlab-com/marketing/digital-experience/about-gitlab-com/-/blob/main/content/","web ide",{"text":488,"config":489},"Please contribute",{"href":490,"dataGaName":491,"dataGaLocation":481},"https://gitlab.com/gitlab-com/marketing/digital-experience/about-gitlab-com/-/blob/main/CONTRIBUTING.md/","please contribute",{"twitter":493,"facebook":494,"youtube":495,"linkedin":496},"https://twitter.com/gitlab","https://www.facebook.com/gitlab","https://www.youtube.com/channel/UCnMGQ8QHMAnVIsI3xJrihhg","https://www.linkedin.com/company/gitlab-com",[498,545,599,643,670],{"title":194,"links":499,"subMenu":514},[500,504,509],{"text":501,"config":502},"View plans",{"href":196,"dataGaName":503,"dataGaLocation":481},"view plans",{"text":505,"config":506},"Why Premium?",{"href":507,"dataGaName":508,"dataGaLocation":481},"/pricing/premium/","why premium",{"text":510,"config":511},"Why Ultimate?",{"href":512,"dataGaName":513,"dataGaLocation":481},"/pricing/ultimate/","why ultimate",[515],{"title":516,"links":517},"Contact Us",[518,521,523,525,530,535,540],{"text":519,"config":520},"Contact sales",{"href":56,"dataGaName":57,"dataGaLocation":481},{"text":374,"config":522},{"href":376,"dataGaName":377,"dataGaLocation":481},{"text":379,"config":524},{"href":381,"dataGaName":382,"dataGaLocation":481},{"text":526,"config":527},"Status",{"href":528,"dataGaName":529,"dataGaLocation":481},"https://status.gitlab.com/","status",{"text":531,"config":532},"Terms of use",{"href":533,"dataGaName":534,"dataGaLocation":481},"/terms/","terms of use",{"text":536,"config":537},"Privacy statement",{"href":538,"dataGaName":539,"dataGaLocation":481},"/privacy/","privacy statement",{"text":541,"config":542},"Cookie preferences",{"dataGaName":543,"dataGaLocation":481,"id":544,"isOneTrustButton":29},"cookie preferences","ot-sdk-btn",{"title":94,"links":546,"subMenu":555},[547,551],{"text":548,"config":549},"DevSecOps platform",{"href":76,"dataGaName":550,"dataGaLocation":481},"devsecops platform",{"text":552,"config":553},"AI-Assisted Development",{"href":83,"dataGaName":554,"dataGaLocation":481},"ai-assisted development",[556],{"title":557,"links":558},"Topics",[559,564,569,574,579,584,589,594],{"text":560,"config":561},"CICD",{"href":562,"dataGaName":563,"dataGaLocation":481},"/topics/ci-cd/","cicd",{"text":565,"config":566},"GitOps",{"href":567,"dataGaName":568,"dataGaLocation":481},"/topics/gitops/","gitops",{"text":570,"config":571},"DevOps",{"href":572,"dataGaName":573,"dataGaLocation":481},"/topics/devops/","devops",{"text":575,"config":576},"Version Control",{"href":577,"dataGaName":578,"dataGaLocation":481},"/topics/version-control/","version control",{"text":580,"config":581},"DevSecOps",{"href":582,"dataGaName":583,"dataGaLocation":481},"/topics/devsecops/","devsecops",{"text":585,"config":586},"Cloud Native",{"href":587,"dataGaName":588,"dataGaLocation":481},"/topics/cloud-native/","cloud native",{"text":590,"config":591},"AI for Coding",{"href":592,"dataGaName":593,"dataGaLocation":481},"/topics/devops/ai-for-coding/","ai for coding",{"text":595,"config":596},"Agentic AI",{"href":597,"dataGaName":598,"dataGaLocation":481},"/topics/agentic-ai/","agentic ai",{"title":600,"links":601},"Solutions",[602,604,606,611,615,618,622,625,627,630,633,638],{"text":138,"config":603},{"href":133,"dataGaName":138,"dataGaLocation":481},{"text":127,"config":605},{"href":110,"dataGaName":111,"dataGaLocation":481},{"text":607,"config":608},"Agile development",{"href":609,"dataGaName":610,"dataGaLocation":481},"/solutions/agile-delivery/","agile delivery",{"text":612,"config":613},"SCM",{"href":123,"dataGaName":614,"dataGaLocation":481},"source code management",{"text":560,"config":616},{"href":116,"dataGaName":617,"dataGaLocation":481},"continuous integration & delivery",{"text":619,"config":620},"Value stream management",{"href":166,"dataGaName":621,"dataGaLocation":481},"value stream management",{"text":565,"config":623},{"href":624,"dataGaName":568,"dataGaLocation":481},"/solutions/gitops/",{"text":176,"config":626},{"href":179,"dataGaName":180,"dataGaLocation":481},{"text":628,"config":629},"Small business",{"href":185,"dataGaName":186,"dataGaLocation":481},{"text":631,"config":632},"Public sector",{"href":191,"dataGaName":192,"dataGaLocation":481},{"text":634,"config":635},"Education",{"href":636,"dataGaName":637,"dataGaLocation":481},"/solutions/education/","education",{"text":639,"config":640},"Financial services",{"href":641,"dataGaName":642,"dataGaLocation":481},"/solutions/finance/","financial services",{"title":199,"links":644},[645,647,649,651,654,656,658,660,662,664,666,668],{"text":212,"config":646},{"href":214,"dataGaName":215,"dataGaLocation":481},{"text":217,"config":648},{"href":219,"dataGaName":220,"dataGaLocation":481},{"text":222,"config":650},{"href":224,"dataGaName":225,"dataGaLocation":481},{"text":227,"config":652},{"href":229,"dataGaName":653,"dataGaLocation":481},"docs",{"text":250,"config":655},{"href":252,"dataGaName":253,"dataGaLocation":481},{"text":245,"config":657},{"href":247,"dataGaName":248,"dataGaLocation":481},{"text":259,"config":659},{"href":261,"dataGaName":262,"dataGaLocation":481},{"text":267,"config":661},{"href":269,"dataGaName":270,"dataGaLocation":481},{"text":272,"config":663},{"href":274,"dataGaName":275,"dataGaLocation":481},{"text":277,"config":665},{"href":279,"dataGaName":280,"dataGaLocation":481},{"text":282,"config":667},{"href":284,"dataGaName":285,"dataGaLocation":481},{"text":287,"config":669},{"href":289,"dataGaName":290,"dataGaLocation":481},{"title":303,"links":671},[672,674,676,678,680,682,684,688,693,695,697,699],{"text":311,"config":673},{"href":313,"dataGaName":305,"dataGaLocation":481},{"text":316,"config":675},{"href":318,"dataGaName":319,"dataGaLocation":481},{"text":324,"config":677},{"href":326,"dataGaName":327,"dataGaLocation":481},{"text":329,"config":679},{"href":331,"dataGaName":332,"dataGaLocation":481},{"text":334,"config":681},{"href":336,"dataGaName":337,"dataGaLocation":481},{"text":339,"config":683},{"href":341,"dataGaName":342,"dataGaLocation":481},{"text":685,"config":686},"Sustainability",{"href":687,"dataGaName":685,"dataGaLocation":481},"/sustainability/",{"text":689,"config":690},"Diversity, inclusion and belonging (DIB)",{"href":691,"dataGaName":692,"dataGaLocation":481},"/diversity-inclusion-belonging/","Diversity, inclusion and belonging",{"text":344,"config":694},{"href":346,"dataGaName":347,"dataGaLocation":481},{"text":354,"config":696},{"href":356,"dataGaName":357,"dataGaLocation":481},{"text":359,"config":698},{"href":361,"dataGaName":362,"dataGaLocation":481},{"text":700,"config":701},"Modern Slavery Transparency Statement",{"href":702,"dataGaName":703,"dataGaLocation":481},"https://handbook.gitlab.com/handbook/legal/modern-slavery-act-transparency-statement/","modern slavery transparency statement",{"items":705},[706,709,712],{"text":707,"config":708},"Terms",{"href":533,"dataGaName":534,"dataGaLocation":481},{"text":710,"config":711},"Cookies",{"dataGaName":543,"dataGaLocation":481,"id":544,"isOneTrustButton":29},{"text":713,"config":714},"Privacy",{"href":538,"dataGaName":539,"dataGaLocation":481},[716],{"id":717,"title":9,"body":27,"config":718,"content":720,"description":27,"extension":724,"meta":725,"navigation":29,"path":726,"seo":727,"stem":728,"__hash__":729},"blogAuthors/en-us/blog/authors/christie-lenneville.yml",{"template":719},"BlogAuthor",{"name":9,"config":721},{"headshot":722,"ctfId":723},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1749670047/Blog/Author%20Headshots/clenneville-headshot.jpg","clenneville","yml",{},"/en-us/blog/authors/christie-lenneville",{},"en-us/blog/authors/christie-lenneville","pZQTNPPQIGFVkSCsP_Vk7W24sKVUP00o4BgHVVrekHo",[731,741,750],{"content":732,"config":739},{"title":733,"description":734,"heroImage":735,"date":736,"tags":737,"category":11},"GitLab Patch Release: 18.11.2, 18.10.5","Learn about this release for GitLab Community Edition and Enterprise Edition.","https://res.cloudinary.com/about-gitlab-com/image/upload/v1749661926/Blog/Hero%20Images/security-patch-blog-image-r2-0506-700x400-fy25_2x.jpg","2026-04-29",[738],"patch releases",{"featured":15,"template":13,"externalUrl":740},"https://docs.gitlab.com/releases/patches/patch-release-gitlab-18-11-2-released/",{"content":742,"config":748},{"title":743,"description":744,"heroImage":735,"date":745,"category":11,"tags":746},"GitLab Patch Release: 18.11.1, 18.10.4, 18.9.6","Discover what's in this latest patch release.","2026-04-22",[738,747],"security releases",{"featured":15,"template":13,"externalUrl":749},"https://docs.gitlab.com/releases/patches/patch-release-gitlab-18-11-1-released/",{"content":751,"config":763},{"title":752,"description":753,"body":754,"category":11,"tags":755,"date":758,"authors":759,"heroImage":762},"GitLab + Amazon: Platform orchestration on a trusted AI foundation","Pair GitLab Duo Agent Platform with Amazon Bedrock for agentic software development and orchestration.","If your team runs GitLab and has a strong AWS practice, a new combination of Duo Agent Platform and Amazon Bedrock is just for you. The model is simple: GitLab acts as your orchestration layer to help accelerate your entire software lifecycle with agentic AI, and Bedrock is designed to provide a secure, compliant foundation model layer with AI inference behind the scenes.\n\nGitLab Duo Agent Platform enables you to handle planning, merge pipelines, security scanning, vulnerability remediation, and more as part of your GitLab workflows, while the GitLab AI Gateway routes model calls to Bedrock (or GitLab-managed Bedrock-backed endpoints, depending on your setup). That means you can build on the identity and access management (IAM) policies, virtual private cloud (VPC) boundaries, regional controls, and cloud spend commitments you already have in AWS.\n\nIf you already use Amazon Bedrock and want AI to help inside the work you already do in GitLab, not in yet another standalone chat tool, this is the pairing for you.\n\n\nIn this article, we look at the real problem many teams face today: AI is fragmented, data paths are fuzzy, and Bedrock investment gets underused when AI sits outside the software development lifecycle. Then we break down your deployment options for GitLab Duo Agent Platform:\n\n* Integrated with self-hosted models on Amazon Bedrock for GitLab Self-Managed deployments and self-hosted AI gateway   \n* Integrated with GitLab-operated models on Amazon Bedrock (with GitLab-owned keys) for GitLab Self-Managed deployments and GitLab-hosted AI gateway  \n* Integrated with GitLab-operated models on Amazon Bedrock (with GitLab-owned keys) for GitLab.com instances and GitLab-hosted AI gateway\n\nWe wrap with a summary on how this approach helps avoid shadow AI and point-tool sprawl without creating a parallel tech stack for AI tooling.\n\n## AI everywhere, control nowhere\n\nSomewhere in your company right now, software teams might be using an AI tool that your security team hasn't approved. Prompt data might be leaving your environment through a path no one has fully mapped. And your organization’s Amazon Bedrock investment might be underused while individual teams expense separate AI tools, pulling workloads and cloud spend away from the platforms you’ve already committed to.\n\nInstead of being a people problem, this might be an architecture problem. And it surfaces the same three constraints in nearly every enterprise:\n\n**Operational fragmentation.** Each team, or sometimes even an individual developer, picks their own development toolset, including AI tooling and model selection. That fragmentation makes end-to-end governance within the software development lifecycle nearly impossible.\n\n**Security and sovereignty.** Where does prompt and code data actually flow? Who owns the logs?\n\n**Cloud spend optimization.** Commitments to key cloud providers like AWS are diluted as workloads and AI usage drift to point tools outside of customers’ existing agreements.\n\nGitLab Duo Agent Platform and Amazon Bedrock help solve this together. The division of labor is straightforward: Duo Agent Platform owns the workflow orchestration with agentic AI for software development, Bedrock owns the inference layer and hosts approved foundational models, and your organization has full control over the data and policy boundaries you already defined in AWS. Three jobs, three owners, no fragmentation.\n\n## GitLab Duo Agent Platform: The agentic control plane\n\nGitLab Duo Agent Platform is GitLab's agentic AI layer: a framework of specialized agents and flows that operate simultaneously and in-parallel, going beyond the traditional stage-based handoffs  and helping automate work across the entire software lifecycle. Rather than a single assistant responding to prompts, Duo Agent Platform enables teams to orchestrate many AI agents asynchronously using unified data and project context, including issues, merge requests, pipelines, and security findings. Linear workflows are turned into coordinated, continuous collaboration between software teams and their AI agents, at scale.\n\nWith that control plane in place, the natural next question is which AI foundation should power these agents. For customers who run GitLab Self-Managed on AWS and need inference traffic, prompt data, and logs to also stay within their AWS environment along with their software lifecycle data, Amazon Bedrock acting as the AI inference layer is the natural fit. \n\n## Amazon Bedrock: The trusted AI foundation\n\nAmazon Bedrock is a fully managed, serverless foundation model layer that runs entirely within your AWS environment. Customer data stays in the customer's AWS account: inputs and outputs are encrypted in transit and at rest, never shared with model providers, and never used to train base models. Bedrock carries compliance certifications across GDPR, HIPAA, and FedRAMP High, covering many regulated industry requirements out of the box. Teams can also bring fine-tuned models from elsewhere via Custom Model Import and deploy them alongside native Bedrock models through the same infrastructure, without managing separate deployment pipelines. Bedrock Guardrails adds configurable safeguards across all models for content filtering, hallucination detection, and sensitive data protection.\n\nTogether, GitLab Duo Agent Platform and Bedrock consolidate DevSecOps orchestration and AI model governance, helping eliminate the fragmentation that happens when teams roll out AI tools independently.\n\n## Choosing your deployment path\n\nThe integration delivers the same core GitLab Duo Agent Platform capabilities regardless of how it is deployed. What varies is who runs GitLab, who operates the AI Gateway, and whose Bedrock account the inference runs through. The right pattern depends on where your organization already operates.\n\nAt a high level, the integration has three main components:\n\n* **GitLab Duo Agent Platform:** agentic workflows embedded across the software development lifecycle  \n* **AI Gateway (GitLab-managed or self-hosted):** the abstraction layer between Duo Agent Platform and the foundational model backend   \n* **Amazon Bedrock:** the AI model and inference substrate\n\n![Deployment of GitLab and AWS Bedrock](https://res.cloudinary.com/about-gitlab-com/image/upload/v1776362365/udmvmv2efpmwtkxgydch.png)\n\nChoosing a deployment pattern is informed by where an organization wants to place the levers of control. The patterns below are designed to meet teams where they already are, whether that's SaaS-first, self-managed for compliance, or all-in on AWS with existing Bedrock investments.\n\n| Deployment Model | GitLab.com instance with GitLab-hosted AI Gateway with GitLab-operated Bedrock models   | GitLab Self-Managed with GitLab-hosted AI Gateway with GitLab-operated Bedrock models | GitLab Self-Managed  with self-hosted AI Gateway and customer-operated Bedrock models |\n| :---- | :---- | :---- | :---- |\n| **Ideal if you:** | Are primarily on GitLab.com and don’t want to self-host AI gateway and Bedrock models  | Need GitLab Self-Managed for compliance and operational reasons but don’t want to manage AI layer | Are AWS-centric with existing Bedrock usage and strict data/control needs  |\n| **Key Benefits** | Fastest, turnkey way to get Duo Agent Platform workflows: GitLab runs GitLab.com, the AI Gateway, integrated with Bedrock AI models. | Keep GitLab deployed in your own environment while consuming Bedrock models via a GitLab-managed AI Gateway, combining deployment control with simplified AI operations. | Run GitLab and AI Gateway in your AWS account, reuse existing IAM/VPC/regions, keep logs and data in your environment, and draw Bedrock usage from your existing AWS spend commitments. |\n\n## How customers use GitLab Duo Agent Platform with Amazon Bedrock\n\nPlatform teams can use GitLab Duo Agent Platform with Amazon Bedrock to standardize which models handle code suggestions, security analysis, and pipeline remediation. This helps enforce guardrails and logging centrally rather than letting individual teams adopt separate tools independently.\n\nSecurity workflows see particular benefit. GitLab Duo Agent Platform agents can propose and validate fixes for security findings within GitLab, helping reduce the manual triage work developers would otherwise handle outside the platform.\n\nFor enterprises already committed to AWS, routing AI workloads through Bedrock from within GitLab enables you to keep developer AI usage aligned with existing cloud agreements rather than generating separate, unplanned spend.\n\n## Closing the loop\n\nThe constraints that slow enterprise AI adoption are often not technical. They are organizational: fragmented tooling, ungoverned data flows, and cloud spend that never consolidates. Those are the problems that can stall AI programs even after the pilots succeed.\n\nGitLab Duo Agent Platform and Amazon Bedrock help address each one directly. Platform teams get consistent governance, auditability, and standardized paths for AI usage across the software development lifecycle. Development teams get streamlined, agentic workflows that feel native to GitLab. And AWS-centric organizations get to extend their existing Bedrock investment rather than build parallel AI infrastructure alongside it.\n\nThe result is an AI program that scales without fragmenting. Governance and velocity on the same stack, serving the same teams, under policies the organization already owns.\n\n\n> To explore which deployment pattern is right for your organization and how to align GitLab Duo Agent Platform and Amazon Bedrock with your existing AWS strategy, [contact the GitLab sales team](https://about.gitlab.com/sales/) and we’ll help you design and implement the best architecture for your environment. You can also [visit our AWS partner page](https://about.gitlab.com/partners/technology-partners/aws/) to learn more.",[290,756,757],"AWS","AI/ML","2026-04-21",[760,761],"Joe Mann","Mark Kriaf","https://res.cloudinary.com/about-gitlab-com/image/upload/v1776362275/ozbwn9tk0dditpnfddlz.png",{"featured":29,"template":13,"slug":764},"gitlab-amazon-platform-orchestration-on-a-trusted-ai-foundation",{"promotions":766},[767,781,792,804],{"id":768,"categories":769,"header":771,"text":772,"button":773,"image":778},"ai-modernization",[770],"ai-ml","Is AI achieving its promise at scale?","Quiz will take 5 minutes or less",{"text":774,"config":775},"Get your AI maturity score",{"href":776,"dataGaName":777,"dataGaLocation":253},"/assessments/ai-modernization-assessment/","modernization assessment",{"config":779},{"src":780},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1772138786/qix0m7kwnd8x2fh1zq49.png",{"id":782,"categories":783,"header":784,"text":772,"button":785,"image":789},"devops-modernization",[11,583],"Are you just managing tools or shipping innovation?",{"text":786,"config":787},"Get your DevOps maturity score",{"href":788,"dataGaName":777,"dataGaLocation":253},"/assessments/devops-modernization-assessment/",{"config":790},{"src":791},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1772138785/eg818fmakweyuznttgid.png",{"id":793,"categories":794,"header":796,"text":772,"button":797,"image":801},"security-modernization",[795],"security","Are you trading speed for security?",{"text":798,"config":799},"Get your security maturity score",{"href":800,"dataGaName":777,"dataGaLocation":253},"/assessments/security-modernization-assessment/",{"config":802},{"src":803},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1772138786/p4pbqd9nnjejg5ds6mdk.png",{"id":805,"paths":806,"header":809,"text":810,"button":811,"image":816},"github-azure-migration",[807,808],"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":812,"config":813},"See how GitLab compares to GitHub",{"href":814,"dataGaName":815,"dataGaLocation":253},"/compare/gitlab-vs-github/github-azure-migration/","github azure migration",{"config":817},{"src":791},{"header":819,"blurb":820,"button":821,"secondaryButton":826},"Start building faster today","See what your team can do with the intelligent orchestration platform for DevSecOps.\n",{"text":822,"config":823},"Get your free trial",{"href":824,"dataGaName":52,"dataGaLocation":825},"https://gitlab.com/-/trial_registrations/new?glm_content=default-saas-trial&glm_source=about.gitlab.com/","feature",{"text":519,"config":827},{"href":56,"dataGaName":57,"dataGaLocation":825},1777934803742]