[{"data":1,"prerenderedAt":840},["ShallowReactive",2],{"/en-us/blog/gitlab-pages-features-review-apps-and-multiple-website-deployment":3,"navigation-en-us":46,"banner-en-us":466,"footer-en-us":476,"blog-post-authors-en-us-Matthew Macfarlane|Janis Altherr":715,"blog-related-posts-en-us-gitlab-pages-features-review-apps-and-multiple-website-deployment":742,"blog-promotions-en-us":777,"next-steps-en-us":830},{"id":4,"title":5,"authorSlugs":6,"authors":9,"body":12,"category":13,"categorySlug":13,"config":14,"content":18,"date":28,"description":19,"extension":30,"externalUrl":31,"featured":17,"heroImage":21,"isFeatured":17,"meta":32,"navigation":33,"path":34,"publishedDate":28,"rawbody":35,"seo":36,"slug":16,"stem":40,"tagSlugs":41,"tags":44,"template":15,"updatedDate":29,"__hash__":45},"blogPosts/en-us/blog/gitlab-pages-features-review-apps-and-multiple-website-deployment.md","GitLab Pages features review apps and multiple website deployment",[7,8],"matthew-macfarlane","janis-altherr",[10,11],"Matthew Macfarlane","Janis Altherr","[GitLab Pages](https://docs.gitlab.com/user/project/pages/) has long been a popular choice for hosting static websites, allowing users to showcase their projects, blogs, and documentation directly from their repositories.\n\nBefore GitLab 17.4, you could only have a single version of your GitLab Pages website. So you couldn’t preview your changes or have multiple versions of your website deployed simultaneously. Now, with a Premium or Ultimate license, you can do both!\n\n### Introducing Parallel Deployments\n\nWith Parallel Deployments, users can now easily preview changes and manage multiple environments for their GitLab Pages sites. This enhancement allows seamless experimentation with new ideas, enabling users to confidently test and refine their sites. By catching any issues early, users can ensure the live site remains stable and polished, building on the already great foundation of GitLab Pages.\n\n### Why Parallel Deployments is a game-changer\n\n1. **Version control made easy**\\\n   If your project involves software development or documentation that covers multiple versions (such as user guides for different software releases), Parallel Deployments makes it easy to manage. Or you can use the feature to localize your website for different languages.\n2. **Flexibility to experiment**\\\n   Want to try out a new design or feature? Parallel Deployments lets you experiment freely. You can create a separate version of your site to test new ideas without impacting the current site. This flexibility encourages creativity and continuous improvement.\n\n### How to add review apps to your GitLab Pages project\n\nTo add a review app to your GitLab Pages project, edit your `.gitlab-ci.yml` file to create a deployment for each merge request (MR). Let’s assume you start with a `.gitlab-ci.yml` file somewhat like this:\n\n```yaml\ncreate-pages:\n  stage: deploy\n  script:\n    - npm run build\n  pages: \n    publish: dist # the name of the folder containing the pages files\n  rules:\n    - if: $CI_COMMIT_BRANCH == $CI_DEFAULT_BRANCH # only run this job when there's a commit to the default branch\n\n```\n\nTo also run the pages pipeline when there’s an MR being opened or updated, we can add another rule to `pages.rules`:\n\n```yaml\n- if: $CI_PIPELINE_SOURCE == \"merge_request_event\"\n```\n\nIf we only add this rule, however, each Pages job will always replace the main deployment – each time an MR is opened! You likely don’t want that to happen.\n\nTo provide each individual deployment with its own URL, we’ve introduced the new `pages.path_prefix` property.\n\nA Pages deployment with this configuration...\n\n```yaml\ncreate-pages:\n  script:\n    - ...\n  pages:\n    ...\n    path_prefix: my-review-app\n\n```\n\n...will be available at `https://my-pages-app-7fe824.gitlab.io/my-review-app`, or, with unique domains disabled, `https://my-group.gitlab.io/my-project/my-review-app`.\n\nBut there’s no need to hardcode the path_prefix. You can dynamically generate it using CI variables. That’s particularly useful for review apps – to create a path for each MR, use the `CI_MERGE_REQUEST_IID variable`:\n\n```yaml\ncreate-pages:\n  script:\n    - ...\n  pages:\n    ...\n    path_prefix: mr-$CI_MERGE_REQUEST_IID\n\n```\n\nAn MR with the ID 114 would then automatically create a deployment at `https://my-pages-app-7fe824.gitlab.io/mr-114`.\n\nWith those concepts at hand, we’d like our pipeline to dynamically create either a main deployment for the default branch, or a path_prefixed-review app for MR events.\n\nFirst, let’s add a `create-pages-review-app` job to our pipeline config:\n\n```yaml\ncreate-pages-deployment:\n  # This job will create a pages deployment without path_prefix\n  # when there is a commit to the default branch\n  stage: deploy\n  script:\n    - npm run build\n  pages: \n    publish: dist \n  rules:\n    - if: $CI_COMMIT_BRANCH == $CI_DEFAULT_BRANCH\n\ncreate-pages-review-app:\n  # This job will create a pages deployment with a path_prefix\n  # when there a merge request is created or updated.\n  stage: deploy\n  script:\n    - npm run build\n  pages:\n    publish: dist \n    path_prefix: 'mr-$CI_MERGE_REQUEST_IID' # Prefix with the mr-\u003Ciid>, like `mr-123`\n  rules:\n    - if: $CI_PIPELINE_SOURCE == \"merge_request_event\"\n\n```\n\nNow you’re creating a deployment both when pushing to the default branch, and prefixed parallel deployments when creating or updating MRs!\n\nFor the best experience, add the URL to the environment job property. This will add a link to the review app to the MR page:\n\n```yaml\ncreate-pages-deployment:\n  # This job will create a pages deployment without path_prefix\n  # when there is a commit to the default branch\n  stage: deploy\n  script:\n    - npm run build\n  pages: \n    publish: dist \n  rules:\n    - if: $CI_COMMIT_BRANCH == $CI_DEFAULT_BRANCH\n\ncreate-pages-review-app:\n  # This job will create a pages deployment with a path_prefix\n  # when there a merge request is created or updated.\n  stage: deploy\n  script:\n    - npm run build\n  pages:\n    publish: dist \n    path_prefix: 'mr-$CI_MERGE_REQUEST_IID' # Prefix with the mr-\u003Ciid>, like `mr-123`\n  rules:\n    - if: $CI_COMMIT_BRANCH == $CI_DEFAULT_BRANCH\n  environment:\n    name: \"Pages Review MR ${CI_MERGE_REQUEST_IID}\"\n    url: $CI_PAGES_URL\n\n```\n\nCongratulations, you’ve now set up MR review apps for your Pages site.\n\n## How to deploy documentation for different versions of your product\n\nThe Parallel Deployments feature is also a useful tool if you maintain the documentation of multiple versions of your software simultaneously.\n\nThe below CI config will not only create a pages deployment when there is a commit to the default branch, but also for any commit to branches named `v1`, `v2`, or `v3`.\n\n```yaml\ncreate-pages:\n  stage: deploy\n  script:\n    - ...\n  variables:\n    PAGES_PREFIX: \"$CI_COMMIT_BRANCH\" # Use the branch name by default\n  pages:\n    path_prefix: \"$PAGES_PREFIX\" # use whatever value is set in the variable\n  environment:\n    name: \"Pages ${PAGES_PREFIX}\"\n    url: $CI_PAGES_URL\n  artifacts:\n    paths:\n    - public\n  rules:\n    - if: $CI_COMMIT_BRANCH == $CI_DEFAULT_BRANCH\n      variables:\n        PAGES_PREFIX: '' # No prefix\n    - if: $CI_COMMIT_BRANCH == 'v1'\n    - if: $CI_COMMIT_BRANCH == 'v2'\n    - if: $CI_COMMIT_BRANCH == 'v3'\n\n```\n\nBy using the `$CI_COMMIT_BRANCH` variable as the path_prefix value, each of these branches will deploy their documentation to their own sub-path of your website:\n\n- The branch named v1 has its docs published to \u003Cmy-domain>/v1.\n- The branch named v2 has its docs published to \u003Cmy-domain>/v2.\n- The branch named v3 has its docs published to \u003Cmy-domain>/v3.\n\nA new commit to one of these branches will then trigger a new deployment to its respective path, keeping the documentation of multiple versions up to date.\n\nThe Parallel Deployments feature is a significant upgrade to GitLab Pages, offering a more flexible and efficient way to manage your knowledge. Whether you're working on a small project or a large-scale site with multiple versions, this new capability will make your workflow smoother and more efficient\n\n> Visit our [Parallel Deployments documentation](https://docs.gitlab.com/user/project/pages/#create-multiple-deployments) to get started today!\n\n### Feedback\n\nShare your ideas and other comments in our [feedback issue](https://gitlab.com/gitlab-org/gitlab/-/issues/482040)!","product",{"template":15,"slug":16,"featured":17},"BlogPost","gitlab-pages-features-review-apps-and-multiple-website-deployment",false,{"title":5,"description":19,"authors":20,"heroImage":21,"tags":22,"category":13,"date":28,"updatedDate":29,"body":12},"GitLab Pages helps organizations reap the rewards of knowledge management, including better collaboration and accessibility. Learn how to use a new feature, Parallel Deployments.",[10,11],"https://res.cloudinary.com/about-gitlab-com/image/upload/v1749674550/Blog/Hero%20Images/blog-image-template-1800x945__1_.png",[23,24,25,26,13,27],"agile","CI/CD","DevSecOps","features","tutorial","2024-09-23","2025-04-09","md",null,{},true,"/en-us/blog/gitlab-pages-features-review-apps-and-multiple-website-deployment","---\nseo:\n  title: GitLab Pages features review apps and multiple website deployment\n  description: >-\n    GitLab Pages helps organizations reap the rewards of knowledge management,\n    including better collaboration and accessibility. Learn how to use a new\n    feature, Parallel Deployments.\n  ogTitle: GitLab Pages features review apps and multiple website deployment\n  ogDescription: >-\n    GitLab Pages helps organizations reap the rewards of knowledge management,\n    including better collaboration and accessibility. Learn how to use a new\n    feature, Parallel Deployments.\n  noIndex: false\n  ogImage: >-\n    https://res.cloudinary.com/about-gitlab-com/image/upload/v1749674550/Blog/Hero%20Images/blog-image-template-1800x945__1_.png\n  ogUrl: >-\n    https://about.gitlab.com/blog/gitlab-pages-features-review-apps-and-multiple-website-deployment\n  ogSiteName: https://about.gitlab.com\n  ogType: article\n  canonicalUrls: >-\n    https://about.gitlab.com/blog/gitlab-pages-features-review-apps-and-multiple-website-deployment\ntitle: GitLab Pages features review apps and multiple website deployment\ndescription: GitLab Pages helps organizations reap the rewards of knowledge management, including better collaboration and accessibility. Learn how to use a new feature, Parallel Deployments.\nauthors:\n  - Matthew Macfarlane\n  - Janis Altherr\nheroImage: https://res.cloudinary.com/about-gitlab-com/image/upload/v1749674550/Blog/Hero%20Images/blog-image-template-1800x945__1_.png\ntags:\n  - agile\n  - CI/CD\n  - DevSecOps\n  - features\n  - product\n  - tutorial\ncategory: product\ndate: '2024-09-23'\nupdatedDate: '2025-04-09'\nslug: gitlab-pages-features-review-apps-and-multiple-website-deployment\nfeatured: false\ntemplate: BlogPost\n---\n\n[GitLab Pages](https://docs.gitlab.com/user/project/pages/) has long been a popular choice for hosting static websites, allowing users to showcase their projects, blogs, and documentation directly from their repositories.\n\nBefore GitLab 17.4, you could only have a single version of your GitLab Pages website. So you couldn’t preview your changes or have multiple versions of your website deployed simultaneously. Now, with a Premium or Ultimate license, you can do both!\n\n### Introducing Parallel Deployments\n\nWith Parallel Deployments, users can now easily preview changes and manage multiple environments for their GitLab Pages sites. This enhancement allows seamless experimentation with new ideas, enabling users to confidently test and refine their sites. By catching any issues early, users can ensure the live site remains stable and polished, building on the already great foundation of GitLab Pages.\n\n### Why Parallel Deployments is a game-changer\n\n1. **Version control made easy**\\\n   If your project involves software development or documentation that covers multiple versions (such as user guides for different software releases), Parallel Deployments makes it easy to manage. Or you can use the feature to localize your website for different languages.\n2. **Flexibility to experiment**\\\n   Want to try out a new design or feature? Parallel Deployments lets you experiment freely. You can create a separate version of your site to test new ideas without impacting the current site. This flexibility encourages creativity and continuous improvement.\n\n### How to add review apps to your GitLab Pages project\n\nTo add a review app to your GitLab Pages project, edit your `.gitlab-ci.yml` file to create a deployment for each merge request (MR). Let’s assume you start with a `.gitlab-ci.yml` file somewhat like this:\n\n```yaml\ncreate-pages:\n  stage: deploy\n  script:\n    - npm run build\n  pages: \n    publish: dist # the name of the folder containing the pages files\n  rules:\n    - if: $CI_COMMIT_BRANCH == $CI_DEFAULT_BRANCH # only run this job when there's a commit to the default branch\n\n```\n\nTo also run the pages pipeline when there’s an MR being opened or updated, we can add another rule to `pages.rules`:\n\n```yaml\n- if: $CI_PIPELINE_SOURCE == \"merge_request_event\"\n```\n\nIf we only add this rule, however, each Pages job will always replace the main deployment – each time an MR is opened! You likely don’t want that to happen.\n\nTo provide each individual deployment with its own URL, we’ve introduced the new `pages.path_prefix` property.\n\nA Pages deployment with this configuration...\n\n```yaml\ncreate-pages:\n  script:\n    - ...\n  pages:\n    ...\n    path_prefix: my-review-app\n\n```\n\n...will be available at `https://my-pages-app-7fe824.gitlab.io/my-review-app`, or, with unique domains disabled, `https://my-group.gitlab.io/my-project/my-review-app`.\n\nBut there’s no need to hardcode the path_prefix. You can dynamically generate it using CI variables. That’s particularly useful for review apps – to create a path for each MR, use the `CI_MERGE_REQUEST_IID variable`:\n\n```yaml\ncreate-pages:\n  script:\n    - ...\n  pages:\n    ...\n    path_prefix: mr-$CI_MERGE_REQUEST_IID\n\n```\n\nAn MR with the ID 114 would then automatically create a deployment at `https://my-pages-app-7fe824.gitlab.io/mr-114`.\n\nWith those concepts at hand, we’d like our pipeline to dynamically create either a main deployment for the default branch, or a path_prefixed-review app for MR events.\n\nFirst, let’s add a `create-pages-review-app` job to our pipeline config:\n\n```yaml\ncreate-pages-deployment:\n  # This job will create a pages deployment without path_prefix\n  # when there is a commit to the default branch\n  stage: deploy\n  script:\n    - npm run build\n  pages: \n    publish: dist \n  rules:\n    - if: $CI_COMMIT_BRANCH == $CI_DEFAULT_BRANCH\n\ncreate-pages-review-app:\n  # This job will create a pages deployment with a path_prefix\n  # when there a merge request is created or updated.\n  stage: deploy\n  script:\n    - npm run build\n  pages:\n    publish: dist \n    path_prefix: 'mr-$CI_MERGE_REQUEST_IID' # Prefix with the mr-\u003Ciid>, like `mr-123`\n  rules:\n    - if: $CI_PIPELINE_SOURCE == \"merge_request_event\"\n\n```\n\nNow you’re creating a deployment both when pushing to the default branch, and prefixed parallel deployments when creating or updating MRs!\n\nFor the best experience, add the URL to the environment job property. This will add a link to the review app to the MR page:\n\n```yaml\ncreate-pages-deployment:\n  # This job will create a pages deployment without path_prefix\n  # when there is a commit to the default branch\n  stage: deploy\n  script:\n    - npm run build\n  pages: \n    publish: dist \n  rules:\n    - if: $CI_COMMIT_BRANCH == $CI_DEFAULT_BRANCH\n\ncreate-pages-review-app:\n  # This job will create a pages deployment with a path_prefix\n  # when there a merge request is created or updated.\n  stage: deploy\n  script:\n    - npm run build\n  pages:\n    publish: dist \n    path_prefix: 'mr-$CI_MERGE_REQUEST_IID' # Prefix with the mr-\u003Ciid>, like `mr-123`\n  rules:\n    - if: $CI_COMMIT_BRANCH == $CI_DEFAULT_BRANCH\n  environment:\n    name: \"Pages Review MR ${CI_MERGE_REQUEST_IID}\"\n    url: $CI_PAGES_URL\n\n```\n\nCongratulations, you’ve now set up MR review apps for your Pages site.\n\n## How to deploy documentation for different versions of your product\n\nThe Parallel Deployments feature is also a useful tool if you maintain the documentation of multiple versions of your software simultaneously.\n\nThe below CI config will not only create a pages deployment when there is a commit to the default branch, but also for any commit to branches named `v1`, `v2`, or `v3`.\n\n```yaml\ncreate-pages:\n  stage: deploy\n  script:\n    - ...\n  variables:\n    PAGES_PREFIX: \"$CI_COMMIT_BRANCH\" # Use the branch name by default\n  pages:\n    path_prefix: \"$PAGES_PREFIX\" # use whatever value is set in the variable\n  environment:\n    name: \"Pages ${PAGES_PREFIX}\"\n    url: $CI_PAGES_URL\n  artifacts:\n    paths:\n    - public\n  rules:\n    - if: $CI_COMMIT_BRANCH == $CI_DEFAULT_BRANCH\n      variables:\n        PAGES_PREFIX: '' # No prefix\n    - if: $CI_COMMIT_BRANCH == 'v1'\n    - if: $CI_COMMIT_BRANCH == 'v2'\n    - if: $CI_COMMIT_BRANCH == 'v3'\n\n```\n\nBy using the `$CI_COMMIT_BRANCH` variable as the path_prefix value, each of these branches will deploy their documentation to their own sub-path of your website:\n\n- The branch named v1 has its docs published to \u003Cmy-domain>/v1.\n- The branch named v2 has its docs published to \u003Cmy-domain>/v2.\n- The branch named v3 has its docs published to \u003Cmy-domain>/v3.\n\nA new commit to one of these branches will then trigger a new deployment to its respective path, keeping the documentation of multiple versions up to date.\n\nThe Parallel Deployments feature is a significant upgrade to GitLab Pages, offering a more flexible and efficient way to manage your knowledge. Whether you're working on a small project or a large-scale site with multiple versions, this new capability will make your workflow smoother and more efficient\n\n> Visit our [Parallel Deployments documentation](https://docs.gitlab.com/user/project/pages/#create-multiple-deployments) to get started today!\n\n### Feedback\n\nShare your ideas and other comments in our [feedback issue](https://gitlab.com/gitlab-org/gitlab/-/issues/482040)!\n",{"title":5,"description":19,"ogTitle":5,"ogDescription":19,"noIndex":17,"ogImage":21,"ogUrl":37,"ogSiteName":38,"ogType":39,"canonicalUrls":37},"https://about.gitlab.com/blog/gitlab-pages-features-review-apps-and-multiple-website-deployment","https://about.gitlab.com","article","en-us/blog/gitlab-pages-features-review-apps-and-multiple-website-deployment",[23,42,43,26,13,27],"cicd","devsecops",[23,24,25,26,13,27],"26WzTI2ShqIduih047uagwdzt85Omytvkr2y_fTqjOI",{"logo":47,"freeTrial":52,"sales":57,"login":62,"items":67,"search":386,"minimal":417,"duo":436,"switchNav":445,"pricingDeployment":456},{"config":48},{"href":49,"dataGaName":50,"dataGaLocation":51},"/","gitlab logo","header",{"text":53,"config":54},"Get free trial",{"href":55,"dataGaName":56,"dataGaLocation":51},"https://gitlab.com/-/trial_registrations/new?glm_source=about.gitlab.com&glm_content=default-saas-trial/","free trial",{"text":58,"config":59},"Talk to sales",{"href":60,"dataGaName":61,"dataGaLocation":51},"/sales/","sales",{"text":63,"config":64},"Sign in",{"href":65,"dataGaName":66,"dataGaLocation":51},"https://gitlab.com/users/sign_in/","sign in",[68,97,196,201,305,366],{"text":69,"config":70,"menu":72},"Platform",{"dataNavLevelOne":71},"platform",{"type":73,"columns":74},"cards",[75,81,89],{"title":69,"description":76,"link":77},"The intelligent orchestration platform for DevSecOps",{"text":78,"config":79},"Explore our Platform",{"href":80,"dataGaName":71,"dataGaLocation":51},"/platform/",{"title":82,"description":83,"link":84},"GitLab Duo Agent Platform","Agentic AI for the entire software lifecycle",{"text":85,"config":86},"Meet GitLab Duo",{"href":87,"dataGaName":88,"dataGaLocation":51},"/gitlab-duo-agent-platform/","gitlab duo agent platform",{"title":90,"description":91,"link":92},"Why GitLab","See the top reasons enterprises choose GitLab",{"text":93,"config":94},"Learn more",{"href":95,"dataGaName":96,"dataGaLocation":51},"/why-gitlab/","why gitlab",{"text":98,"left":33,"config":99,"menu":101},"Product",{"dataNavLevelOne":100},"solutions",{"type":102,"link":103,"columns":107,"feature":175},"lists",{"text":104,"config":105},"View all Solutions",{"href":106,"dataGaName":100,"dataGaLocation":51},"/solutions/",[108,131,154],{"title":109,"description":110,"link":111,"items":116},"Automation","CI/CD and automation to accelerate deployment",{"config":112},{"icon":113,"href":114,"dataGaName":115,"dataGaLocation":51},"AutomatedCodeAlt","/solutions/delivery-automation/","automated software delivery",[117,120,123,127],{"text":24,"config":118},{"href":119,"dataGaLocation":51,"dataGaName":24},"/solutions/continuous-integration/",{"text":82,"config":121},{"href":87,"dataGaLocation":51,"dataGaName":122},"gitlab duo agent platform - product menu",{"text":124,"config":125},"Source Code Management",{"href":126,"dataGaLocation":51,"dataGaName":124},"/solutions/source-code-management/",{"text":128,"config":129},"Automated Software Delivery",{"href":114,"dataGaLocation":51,"dataGaName":130},"Automated software delivery",{"title":132,"description":133,"link":134,"items":139},"Security","Deliver code faster without compromising security",{"config":135},{"href":136,"dataGaName":137,"dataGaLocation":51,"icon":138},"/solutions/application-security-testing/","security and compliance","ShieldCheckLight",[140,144,149],{"text":141,"config":142},"Application Security Testing",{"href":136,"dataGaName":143,"dataGaLocation":51},"Application security testing",{"text":145,"config":146},"Software Supply Chain Security",{"href":147,"dataGaLocation":51,"dataGaName":148},"/solutions/supply-chain/","Software supply chain security",{"text":150,"config":151},"Software Compliance",{"href":152,"dataGaName":153,"dataGaLocation":51},"/solutions/software-compliance/","software compliance",{"title":155,"link":156,"items":161},"Measurement",{"config":157},{"icon":158,"href":159,"dataGaName":160,"dataGaLocation":51},"DigitalTransformation","/solutions/visibility-measurement/","visibility and measurement",[162,166,170],{"text":163,"config":164},"Visibility & Measurement",{"href":159,"dataGaLocation":51,"dataGaName":165},"Visibility and Measurement",{"text":167,"config":168},"Value Stream Management",{"href":169,"dataGaLocation":51,"dataGaName":167},"/solutions/value-stream-management/",{"text":171,"config":172},"Analytics & Insights",{"href":173,"dataGaLocation":51,"dataGaName":174},"/solutions/analytics-and-insights/","Analytics and insights",{"title":176,"type":102,"items":177},"GitLab for",[178,184,190],{"text":179,"config":180},"Enterprise",{"icon":181,"href":182,"dataGaLocation":51,"dataGaName":183},"Building","/enterprise/","enterprise",{"text":185,"config":186},"Small Business",{"icon":187,"href":188,"dataGaLocation":51,"dataGaName":189},"Work","/small-business/","small business",{"text":191,"config":192},"Public Sector",{"icon":193,"href":194,"dataGaLocation":51,"dataGaName":195},"Organization","/solutions/public-sector/","public sector",{"text":197,"config":198},"Pricing",{"href":199,"dataGaName":200,"dataGaLocation":51,"dataNavLevelOne":200},"/pricing/","pricing",{"text":202,"config":203,"menu":205},"Resources",{"dataNavLevelOne":204},"resources",{"type":102,"link":206,"columns":210,"feature":294},{"text":207,"config":208},"View all resources",{"href":209,"dataGaName":204,"dataGaLocation":51},"/resources/",[211,244,266],{"title":212,"items":213},"Getting started",[214,219,224,229,234,239],{"text":215,"config":216},"Install",{"href":217,"dataGaName":218,"dataGaLocation":51},"/install/","install",{"text":220,"config":221},"Quick start guides",{"href":222,"dataGaName":223,"dataGaLocation":51},"/get-started/","quick setup checklists",{"text":225,"config":226},"Learn",{"href":227,"dataGaLocation":51,"dataGaName":228},"https://university.gitlab.com/","learn",{"text":230,"config":231},"Product documentation",{"href":232,"dataGaName":233,"dataGaLocation":51},"https://docs.gitlab.com/","product documentation",{"text":235,"config":236},"Best practice videos",{"href":237,"dataGaName":238,"dataGaLocation":51},"/getting-started-videos/","best practice videos",{"text":240,"config":241},"Integrations",{"href":242,"dataGaName":243,"dataGaLocation":51},"/integrations/","integrations",{"title":245,"items":246},"Discover",[247,252,257,261],{"text":248,"config":249},"Customer success stories",{"href":250,"dataGaName":251,"dataGaLocation":51},"/customers/","customer success stories",{"text":253,"config":254},"Blog",{"href":255,"dataGaName":256,"dataGaLocation":51},"/blog/","blog",{"text":258,"config":259},"The Source",{"href":260,"dataGaName":256,"dataGaLocation":51},"/the-source/",{"text":262,"config":263},"Remote",{"href":264,"dataGaName":265,"dataGaLocation":51},"https://handbook.gitlab.com/handbook/company/culture/all-remote/","remote",{"title":267,"items":268},"Connect",[269,274,279,284,289],{"text":270,"config":271},"GitLab Services",{"href":272,"dataGaName":273,"dataGaLocation":51},"/services/","services",{"text":275,"config":276},"Community",{"href":277,"dataGaName":278,"dataGaLocation":51},"/community/","community",{"text":280,"config":281},"Forum",{"href":282,"dataGaName":283,"dataGaLocation":51},"https://forum.gitlab.com/","forum",{"text":285,"config":286},"Events",{"href":287,"dataGaName":288,"dataGaLocation":51},"/events/","events",{"text":290,"config":291},"Partners",{"href":292,"dataGaName":293,"dataGaLocation":51},"/partners/","partners",{"config":295,"title":298,"text":299,"link":300},{"background":296,"textColor":297},"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":301,"config":302},"Read the latest",{"href":303,"dataGaName":304,"dataGaLocation":51},"/releases/whats-new/","whats new",{"text":306,"config":307,"menu":309},"Company",{"dataNavLevelOne":308},"company",{"type":102,"columns":310},[311],{"items":312},[313,318,324,326,331,336,341,346,351,356,361],{"text":314,"config":315},"About",{"href":316,"dataGaName":317,"dataGaLocation":51},"/company/","about",{"text":319,"config":320,"footerGa":323},"Jobs",{"href":321,"dataGaName":322,"dataGaLocation":51},"/jobs/","jobs",{"dataGaName":322},{"text":285,"config":325},{"href":287,"dataGaName":288,"dataGaLocation":51},{"text":327,"config":328},"Leadership",{"href":329,"dataGaName":330,"dataGaLocation":51},"/company/team/e-group/","leadership",{"text":332,"config":333},"Team",{"href":334,"dataGaName":335,"dataGaLocation":51},"/company/team/","team",{"text":337,"config":338},"Handbook",{"href":339,"dataGaName":340,"dataGaLocation":51},"https://handbook.gitlab.com/","handbook",{"text":342,"config":343},"Investor relations",{"href":344,"dataGaName":345,"dataGaLocation":51},"https://ir.gitlab.com/","investor relations",{"text":347,"config":348},"Trust Center",{"href":349,"dataGaName":350,"dataGaLocation":51},"/security/","trust center",{"text":352,"config":353},"AI Transparency Center",{"href":354,"dataGaName":355,"dataGaLocation":51},"/ai-transparency-center/","ai transparency center",{"text":357,"config":358},"Newsletter",{"href":359,"dataGaName":360,"dataGaLocation":51},"/company/contact/#contact-forms","newsletter",{"text":362,"config":363},"Press",{"href":364,"dataGaName":365,"dataGaLocation":51},"/press/","press",{"text":367,"config":368,"menu":369},"Contact us",{"dataNavLevelOne":308},{"type":102,"columns":370},[371],{"items":372},[373,376,381],{"text":58,"config":374},{"href":60,"dataGaName":375,"dataGaLocation":51},"talk to sales",{"text":377,"config":378},"Support portal",{"href":379,"dataGaName":380,"dataGaLocation":51},"https://support.gitlab.com","support portal",{"text":382,"config":383},"Customer portal",{"href":384,"dataGaName":385,"dataGaLocation":51},"https://customers.gitlab.com/customers/sign_in/","customer portal",{"close":387,"login":388,"suggestions":395},"Close",{"text":389,"link":390},"To search repositories and projects, login to",{"text":391,"config":392},"gitlab.com",{"href":65,"dataGaName":393,"dataGaLocation":394},"search login","search",{"text":396,"default":397},"Suggestions",[398,400,404,406,410,414],{"text":82,"config":399},{"href":87,"dataGaName":82,"dataGaLocation":394},{"text":401,"config":402},"Code Suggestions (AI)",{"href":403,"dataGaName":401,"dataGaLocation":394},"/solutions/code-suggestions/",{"text":24,"config":405},{"href":119,"dataGaName":24,"dataGaLocation":394},{"text":407,"config":408},"GitLab on AWS",{"href":409,"dataGaName":407,"dataGaLocation":394},"/partners/technology-partners/aws/",{"text":411,"config":412},"GitLab on Google Cloud",{"href":413,"dataGaName":411,"dataGaLocation":394},"/partners/technology-partners/google-cloud-platform/",{"text":415,"config":416},"Why GitLab?",{"href":95,"dataGaName":415,"dataGaLocation":394},{"freeTrial":418,"mobileIcon":423,"desktopIcon":428,"secondaryButton":431},{"text":419,"config":420},"Start free trial",{"href":421,"dataGaName":56,"dataGaLocation":422},"https://gitlab.com/-/trials/new/","nav",{"altText":424,"config":425},"Gitlab Icon",{"src":426,"dataGaName":427,"dataGaLocation":422},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1758203874/jypbw1jx72aexsoohd7x.svg","gitlab icon",{"altText":424,"config":429},{"src":430,"dataGaName":427,"dataGaLocation":422},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1758203875/gs4c8p8opsgvflgkswz9.svg",{"text":432,"config":433},"Get Started",{"href":434,"dataGaName":435,"dataGaLocation":422},"https://gitlab.com/-/trial_registrations/new?glm_source=about.gitlab.com/get-started/","get started",{"freeTrial":437,"mobileIcon":441,"desktopIcon":443},{"text":438,"config":439},"Learn more about GitLab Duo",{"href":87,"dataGaName":440,"dataGaLocation":422},"gitlab duo",{"altText":424,"config":442},{"src":426,"dataGaName":427,"dataGaLocation":422},{"altText":424,"config":444},{"src":430,"dataGaName":427,"dataGaLocation":422},{"button":446,"mobileIcon":451,"desktopIcon":453},{"text":447,"config":448},"/switch",{"href":449,"dataGaName":450,"dataGaLocation":422},"#contact","switch",{"altText":424,"config":452},{"src":426,"dataGaName":427,"dataGaLocation":422},{"altText":424,"config":454},{"src":455,"dataGaName":427,"dataGaLocation":422},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1773335277/ohhpiuoxoldryzrnhfrh.png",{"freeTrial":457,"mobileIcon":462,"desktopIcon":464},{"text":458,"config":459},"Back to pricing",{"href":199,"dataGaName":460,"dataGaLocation":422,"icon":461},"back to pricing","GoBack",{"altText":424,"config":463},{"src":426,"dataGaName":427,"dataGaLocation":422},{"altText":424,"config":465},{"src":430,"dataGaName":427,"dataGaLocation":422},{"title":467,"button":468,"config":473},"See how agentic AI transforms software delivery",{"text":469,"config":470},"Sign up for GitLab Transcend on June 10",{"href":471,"dataGaName":472,"dataGaLocation":51},"/releases/whats-new/#sign-up","transcend event",{"layout":474,"icon":475,"disabled":17},"release","AiStar",{"data":477},{"text":478,"source":479,"edit":485,"contribute":490,"config":495,"items":500,"minimal":704},"Git is a trademark of Software Freedom Conservancy and our use of 'GitLab' is under license",{"text":480,"config":481},"View page source",{"href":482,"dataGaName":483,"dataGaLocation":484},"https://gitlab.com/gitlab-com/marketing/digital-experience/about-gitlab-com/","page source","footer",{"text":486,"config":487},"Edit this page",{"href":488,"dataGaName":489,"dataGaLocation":484},"https://gitlab.com/gitlab-com/marketing/digital-experience/about-gitlab-com/-/blob/main/content/","web ide",{"text":491,"config":492},"Please contribute",{"href":493,"dataGaName":494,"dataGaLocation":484},"https://gitlab.com/gitlab-com/marketing/digital-experience/about-gitlab-com/-/blob/main/CONTRIBUTING.md/","please contribute",{"twitter":496,"facebook":497,"youtube":498,"linkedin":499},"https://twitter.com/gitlab","https://www.facebook.com/gitlab","https://www.youtube.com/channel/UCnMGQ8QHMAnVIsI3xJrihhg","https://www.linkedin.com/company/gitlab-com",[501,548,599,643,670],{"title":197,"links":502,"subMenu":517},[503,507,512],{"text":504,"config":505},"View plans",{"href":199,"dataGaName":506,"dataGaLocation":484},"view plans",{"text":508,"config":509},"Why Premium?",{"href":510,"dataGaName":511,"dataGaLocation":484},"/pricing/premium/","why premium",{"text":513,"config":514},"Why Ultimate?",{"href":515,"dataGaName":516,"dataGaLocation":484},"/pricing/ultimate/","why ultimate",[518],{"title":519,"links":520},"Contact Us",[521,524,526,528,533,538,543],{"text":522,"config":523},"Contact sales",{"href":60,"dataGaName":61,"dataGaLocation":484},{"text":377,"config":525},{"href":379,"dataGaName":380,"dataGaLocation":484},{"text":382,"config":527},{"href":384,"dataGaName":385,"dataGaLocation":484},{"text":529,"config":530},"Status",{"href":531,"dataGaName":532,"dataGaLocation":484},"https://status.gitlab.com/","status",{"text":534,"config":535},"Terms of use",{"href":536,"dataGaName":537,"dataGaLocation":484},"/terms/","terms of use",{"text":539,"config":540},"Privacy statement",{"href":541,"dataGaName":542,"dataGaLocation":484},"/privacy/","privacy statement",{"text":544,"config":545},"Cookie preferences",{"dataGaName":546,"dataGaLocation":484,"id":547,"isOneTrustButton":33},"cookie preferences","ot-sdk-btn",{"title":98,"links":549,"subMenu":558},[550,554],{"text":551,"config":552},"DevSecOps platform",{"href":80,"dataGaName":553,"dataGaLocation":484},"devsecops platform",{"text":555,"config":556},"AI-Assisted Development",{"href":87,"dataGaName":557,"dataGaLocation":484},"ai-assisted development",[559],{"title":560,"links":561},"Topics",[562,566,571,576,581,584,589,594],{"text":563,"config":564},"CICD",{"href":565,"dataGaName":42,"dataGaLocation":484},"/topics/ci-cd/",{"text":567,"config":568},"GitOps",{"href":569,"dataGaName":570,"dataGaLocation":484},"/topics/gitops/","gitops",{"text":572,"config":573},"DevOps",{"href":574,"dataGaName":575,"dataGaLocation":484},"/topics/devops/","devops",{"text":577,"config":578},"Version Control",{"href":579,"dataGaName":580,"dataGaLocation":484},"/topics/version-control/","version control",{"text":25,"config":582},{"href":583,"dataGaName":43,"dataGaLocation":484},"/topics/devsecops/",{"text":585,"config":586},"Cloud Native",{"href":587,"dataGaName":588,"dataGaLocation":484},"/topics/cloud-native/","cloud native",{"text":590,"config":591},"AI for Coding",{"href":592,"dataGaName":593,"dataGaLocation":484},"/topics/devops/ai-for-coding/","ai for coding",{"text":595,"config":596},"Agentic AI",{"href":597,"dataGaName":598,"dataGaLocation":484},"/topics/agentic-ai/","agentic ai",{"title":600,"links":601},"Solutions",[602,604,606,611,615,618,622,625,627,630,633,638],{"text":141,"config":603},{"href":136,"dataGaName":141,"dataGaLocation":484},{"text":130,"config":605},{"href":114,"dataGaName":115,"dataGaLocation":484},{"text":607,"config":608},"Agile development",{"href":609,"dataGaName":610,"dataGaLocation":484},"/solutions/agile-delivery/","agile delivery",{"text":612,"config":613},"SCM",{"href":126,"dataGaName":614,"dataGaLocation":484},"source code management",{"text":563,"config":616},{"href":119,"dataGaName":617,"dataGaLocation":484},"continuous integration & delivery",{"text":619,"config":620},"Value stream management",{"href":169,"dataGaName":621,"dataGaLocation":484},"value stream management",{"text":567,"config":623},{"href":624,"dataGaName":570,"dataGaLocation":484},"/solutions/gitops/",{"text":179,"config":626},{"href":182,"dataGaName":183,"dataGaLocation":484},{"text":628,"config":629},"Small business",{"href":188,"dataGaName":189,"dataGaLocation":484},{"text":631,"config":632},"Public sector",{"href":194,"dataGaName":195,"dataGaLocation":484},{"text":634,"config":635},"Education",{"href":636,"dataGaName":637,"dataGaLocation":484},"/solutions/education/","education",{"text":639,"config":640},"Financial services",{"href":641,"dataGaName":642,"dataGaLocation":484},"/solutions/finance/","financial services",{"title":202,"links":644},[645,647,649,651,654,656,658,660,662,664,666,668],{"text":215,"config":646},{"href":217,"dataGaName":218,"dataGaLocation":484},{"text":220,"config":648},{"href":222,"dataGaName":223,"dataGaLocation":484},{"text":225,"config":650},{"href":227,"dataGaName":228,"dataGaLocation":484},{"text":230,"config":652},{"href":232,"dataGaName":653,"dataGaLocation":484},"docs",{"text":253,"config":655},{"href":255,"dataGaName":256,"dataGaLocation":484},{"text":248,"config":657},{"href":250,"dataGaName":251,"dataGaLocation":484},{"text":262,"config":659},{"href":264,"dataGaName":265,"dataGaLocation":484},{"text":270,"config":661},{"href":272,"dataGaName":273,"dataGaLocation":484},{"text":275,"config":663},{"href":277,"dataGaName":278,"dataGaLocation":484},{"text":280,"config":665},{"href":282,"dataGaName":283,"dataGaLocation":484},{"text":285,"config":667},{"href":287,"dataGaName":288,"dataGaLocation":484},{"text":290,"config":669},{"href":292,"dataGaName":293,"dataGaLocation":484},{"title":306,"links":671},[672,674,676,678,680,682,684,688,693,695,697,699],{"text":314,"config":673},{"href":316,"dataGaName":308,"dataGaLocation":484},{"text":319,"config":675},{"href":321,"dataGaName":322,"dataGaLocation":484},{"text":327,"config":677},{"href":329,"dataGaName":330,"dataGaLocation":484},{"text":332,"config":679},{"href":334,"dataGaName":335,"dataGaLocation":484},{"text":337,"config":681},{"href":339,"dataGaName":340,"dataGaLocation":484},{"text":342,"config":683},{"href":344,"dataGaName":345,"dataGaLocation":484},{"text":685,"config":686},"Sustainability",{"href":687,"dataGaName":685,"dataGaLocation":484},"/sustainability/",{"text":689,"config":690},"Diversity, inclusion and belonging (DIB)",{"href":691,"dataGaName":692,"dataGaLocation":484},"/diversity-inclusion-belonging/","Diversity, inclusion and belonging",{"text":347,"config":694},{"href":349,"dataGaName":350,"dataGaLocation":484},{"text":357,"config":696},{"href":359,"dataGaName":360,"dataGaLocation":484},{"text":362,"config":698},{"href":364,"dataGaName":365,"dataGaLocation":484},{"text":700,"config":701},"Modern Slavery Transparency Statement",{"href":702,"dataGaName":703,"dataGaLocation":484},"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":536,"dataGaName":537,"dataGaLocation":484},{"text":710,"config":711},"Cookies",{"dataGaName":546,"dataGaLocation":484,"id":547,"isOneTrustButton":33},{"text":713,"config":714},"Privacy",{"href":541,"dataGaName":542,"dataGaLocation":484},[716,730],{"id":717,"title":10,"body":31,"config":718,"content":720,"description":31,"extension":724,"meta":725,"navigation":33,"path":726,"seo":727,"stem":728,"__hash__":729},"blogAuthors/en-us/blog/authors/matthew-macfarlane.yml",{"template":719},"BlogAuthor",{"name":10,"config":721},{"headshot":722,"ctfId":723},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1749663160/Blog/Author%20Headshots/matthew_mcfarlane_headshot.png","6dyod6DIfkxY5CognC5g2N","yml",{},"/en-us/blog/authors/matthew-macfarlane",{},"en-us/blog/authors/matthew-macfarlane","vE0tWG6T4IqZAY0adk9liiZWKrGOc10DZqsEtyKmTX4",{"id":731,"title":11,"body":31,"config":732,"content":733,"description":31,"extension":724,"meta":737,"navigation":33,"path":738,"seo":739,"stem":740,"__hash__":741},"blogAuthors/en-us/blog/authors/janis-altherr.yml",{"template":719},{"name":11,"config":734},{"headshot":735,"ctfId":736},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1749663163/Blog/Author%20Headshots/janis-headshot.jpg","janis",{},"/en-us/blog/authors/janis-altherr",{},"en-us/blog/authors/janis-altherr","IypsWlKRRAD566nOfIQF0sRhJjrEm0E-PxjlLJ0XGKE",[743,753,762],{"content":744,"config":751},{"title":745,"description":746,"heroImage":747,"date":748,"tags":749,"category":13},"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",[750],"patch releases",{"featured":17,"template":15,"externalUrl":752},"https://docs.gitlab.com/releases/patches/patch-release-gitlab-18-11-2-released/",{"content":754,"config":760},{"title":755,"description":756,"heroImage":747,"date":757,"category":13,"tags":758},"GitLab Patch Release: 18.11.1, 18.10.4, 18.9.6","Discover what's in this latest patch release.","2026-04-22",[750,759],"security releases",{"featured":17,"template":15,"externalUrl":761},"https://docs.gitlab.com/releases/patches/patch-release-gitlab-18-11-1-released/",{"content":763,"config":775},{"title":764,"description":765,"body":766,"category":13,"tags":767,"date":770,"authors":771,"heroImage":774},"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.",[293,768,769],"AWS","AI/ML","2026-04-21",[772,773],"Joe Mann","Mark Kriaf","https://res.cloudinary.com/about-gitlab-com/image/upload/v1776362275/ozbwn9tk0dditpnfddlz.png",{"featured":33,"template":15,"slug":776},"gitlab-amazon-platform-orchestration-on-a-trusted-ai-foundation",{"promotions":778},[779,793,804,816],{"id":780,"categories":781,"header":783,"text":784,"button":785,"image":790},"ai-modernization",[782],"ai-ml","Is AI achieving its promise at scale?","Quiz will take 5 minutes or less",{"text":786,"config":787},"Get your AI maturity score",{"href":788,"dataGaName":789,"dataGaLocation":256},"/assessments/ai-modernization-assessment/","modernization assessment",{"config":791},{"src":792},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1772138786/qix0m7kwnd8x2fh1zq49.png",{"id":794,"categories":795,"header":796,"text":784,"button":797,"image":801},"devops-modernization",[13,43],"Are you just managing tools or shipping innovation?",{"text":798,"config":799},"Get your DevOps maturity score",{"href":800,"dataGaName":789,"dataGaLocation":256},"/assessments/devops-modernization-assessment/",{"config":802},{"src":803},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1772138785/eg818fmakweyuznttgid.png",{"id":805,"categories":806,"header":808,"text":784,"button":809,"image":813},"security-modernization",[807],"security","Are you trading speed for security?",{"text":810,"config":811},"Get your security maturity score",{"href":812,"dataGaName":789,"dataGaLocation":256},"/assessments/security-modernization-assessment/",{"config":814},{"src":815},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1772138786/p4pbqd9nnjejg5ds6mdk.png",{"id":817,"paths":818,"header":821,"text":822,"button":823,"image":828},"github-azure-migration",[819,820],"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":824,"config":825},"See how GitLab compares to GitHub",{"href":826,"dataGaName":827,"dataGaLocation":256},"/compare/gitlab-vs-github/github-azure-migration/","github azure migration",{"config":829},{"src":803},{"header":831,"blurb":832,"button":833,"secondaryButton":838},"Start building faster today","See what your team can do with the intelligent orchestration platform for DevSecOps.\n",{"text":834,"config":835},"Get your free trial",{"href":836,"dataGaName":56,"dataGaLocation":837},"https://gitlab.com/-/trial_registrations/new?glm_content=default-saas-trial&glm_source=about.gitlab.com/","feature",{"text":522,"config":839},{"href":60,"dataGaName":61,"dataGaLocation":837},1777934815656]