[{"data":1,"prerenderedAt":825},["ShallowReactive",2],{"/en-us/blog/structuring-the-gitlab-package-registry-for-enterprise-scale":3,"navigation-en-us":41,"banner-en-us":462,"footer-en-us":472,"blog-post-authors-en-us-Tim Rizzi":712,"blog-related-posts-en-us-structuring-the-gitlab-package-registry-for-enterprise-scale":727,"blog-promotions-en-us":762,"next-steps-en-us":815},{"id":4,"title":5,"authorSlugs":6,"authors":8,"body":10,"category":11,"categorySlug":11,"config":12,"content":16,"date":24,"description":17,"extension":25,"externalUrl":26,"featured":15,"heroImage":19,"isFeatured":15,"meta":27,"navigation":15,"path":28,"publishedDate":24,"rawbody":29,"seo":30,"slug":14,"stem":35,"tagSlugs":36,"tags":39,"template":13,"updatedDate":26,"__hash__":40},"blogPosts/en-us/blog/structuring-the-gitlab-package-registry-for-enterprise-scale.md","Structuring the GitLab Package Registry for enterprise scale",[7],"tim-rizzi",[9],"Tim Rizzi","As organizations grow, managing internal packages becomes increasingly complex. While traditional package managers, like JFrog Artifactory and Sonatype Nexus, use a centralized repository approach, GitLab takes a different path that aligns with modern development teams' work. In this post, we'll explore how to effectively structure your GitLab Package Registry for enterprise scale, focusing on Maven and npm packages as examples.\n\n## Understanding the GitLab Package Registry model\n\nIf you're coming from a traditional package manager, GitLab's approach might initially seem different. Instead of a single centralized repository, GitLab integrates package management directly into your existing project and group structure. This means:\n\n- Teams publish packages to specific projects where the code lives\n- Teams consume packages from root group registries that aggregate all packages below them\n- Access control inherits from your existing GitLab permissions\n\nThis model offers several advantages:\n\n- Clear ownership of packages alongside their source code\n- Granular access control without additional configuration\n- Simplified CI/CD integration\n- Natural alignment with team structures\n- Single URL for accessing all company packages through root group consumption\n\n### The power of root group package registry\n\nWhile GitLab supports package consumption at various group levels, using the root group level has emerged as a best practice among our users. Here's why:\n\n- **Single access point:** One URL provides access to all private packages across your organization\n- **Consistent package naming:** Group-level endpoints allow teams to maintain their preferred naming conventions without conflicts\n- **Simplified configuration:** All developers can use the same configuration to access packages\n- **Secure access management:** Combines with deploy tokens for easy rotation and access control\n- **Hierarchical organization**: Naturally maps to your organizational structure while maintaining unified access\n\n## Real-world example: Enterprise structure\n\nLet's look at how this works in practice with a large enterprise:\n\n```text\ncompany/ (root group)\n├── retail-division/\n│   ├── shared-libraries/     # Division-specific shared code\n│   └── teams/\n│       ├── checkout/        # Team publishes packages here\n│       └── inventory/       # Team publishes packages here\n├── banking-division/\n│   ├── shared-libraries/    # Division-specific shared code\n│   └── teams/\n│       ├── payments/       # Team publishes packages here\n│       └── fraud/         # Team publishes packages here\n└── shared-platform/        # Enterprise-wide shared code\n    ├── java-commons/      # Shared Java libraries\n    └── ui-components/     # Shared UI components\n\n```\n\n### Publishing configuration\n\nTeams publish packages to their specific project registries, maintaining clear ownership:\n\n1. Maven example\n\n```xml\n\u003C!-- checkout/pom.xml -->\n\u003CdistributionManagement>\n    \u003Crepository>\n        \u003Cid>gitlab-maven\u003C/id>\n        \u003Curl>${CI_API_V4_URL}/projects/${CI_PROJECT_ID}/packages/maven\u003C/url>\n    \u003C/repository>\n\u003C/distributionManagement>\n```\n\n2. npm example\n\n```json\n// ui-components/package.json\n{\n  \"name\": \"@company/ui-components\",\n  \"publishConfig\": {\n    \"registry\": \"${CI_API_V4_URL}/projects/${CI_PROJECT_ID}/packages/npm/\"\n  }\n}\n```\n\n### Consuming configuration\n\nThe power of root group consumption comes into play here. All teams configure a single endpoint for package access:\n\n1. Maven example\n\n```xml\n\u003C!-- Any project's pom.xml -->\n\u003Crepositories>\n    \u003Crepository>\n        \u003Cid>gitlab-maven\u003C/id>\n        \u003Curl>https://gitlab.example.com/api/v4/groups/company/-/packages/maven\u003C/url>\n    \u003C/repository>\n\u003C/repositories>\n```\n\n2. npm example\n\n```text\n# Any project's .npmrc\n@company:registry=https://gitlab.example.com/api/v4/groups/company/-/packages/npm/\n```\n\nThis configuration automatically provides access to all packages across your organization while maintaining the benefits of project-based publishing.\n\n## Authentication and access control\n\nGitLab's model simplifies authentication through deploy tokens and CI/CD integration.\n\n### For CI/CD pipelines\n\nGitLab automatically handles authentication in pipelines using `CI_JOB_TOKEN`:\n\n```yaml\n# .gitlab-ci.yml\npublish:\n  script:\n    - mvn deploy  # or npm publish\n  # CI_JOB_TOKEN provides automatic authentication\n\n```\n\n### For development\n\nUse group deploy tokens for package consumption:\n\n- Create read-only deploy tokens at the root group level\n- Rotate tokens periodically for security\n- Share a single configuration across all developers\n\n## Benefits of root group package registry\n\n1. Simplified configuration\n   - One URL for all package access\n   - Consistent setup across teams\n   - Easy token rotation\n2. Clear ownership\n   - Packages stay with their source code\n   - Teams maintain control over publishing\n   - Version history tied to project activity\n3. Natural organization\n   - Matches your company structure\n   - Supports team autonomy\n   - Enables cross-team collaboration\n\n## Getting started\n\n1. Set up your root group\n   - Create a clear group structure\n   - Configure appropriate access controls\n   - Create group deploy tokens\n2. Configure team projects\n   - Set up project-level publishing\n   - Implement CI/CD pipelines\n   - Document package naming conventions\n3. Standardize consumption\n   - Configure root group registry access\n   - Share deploy tokens securely\n   - Document package discovery process\n\n## Summary\n\nGitLab's package registry model, particularly when leveraging root group consumption, offers a powerful solution for enterprise package management. By combining project-based publishing with root group consumption, organizations get the best of both worlds: clear ownership and simplified access. This approach scales naturally with your organization while maintaining security and ease of use.\n\nStart by implementing this model with a single team or division, and expand as you see the benefits of this integrated approach. Remember that while this post focused on Maven and npm, the same principles apply to all package types supported by GitLab.\n\n> Get started with package registries today! Sign up for a [free trial of GitLab Ultimate](https://about.gitlab.com/free-trial/).","product",{"template":13,"slug":14,"featured":15},"BlogPost","structuring-the-gitlab-package-registry-for-enterprise-scale",true,{"title":5,"description":17,"authors":18,"heroImage":19,"tags":20,"category":11,"date":24,"body":10},"Learn how to leverage GitLab's unique project-based publishing model alongside root-group-level consumption to create a secure, flexible package management strategy.",[9],"https://res.cloudinary.com/about-gitlab-com/image/upload/v1749662332/Blog/Hero%20Images/blog-image-template-1800x945__23_.png",[21,22,23],"DevSecOps","tutorial","solutions architecture","2025-02-19","md",null,{},"/en-us/blog/structuring-the-gitlab-package-registry-for-enterprise-scale","---\nseo:\n  title: Structuring the GitLab Package Registry for enterprise scale\n  description: >-\n    Learn how to leverage GitLab's unique project-based publishing model\n    alongside root-group-level consumption to create a secure, flexible package\n    management strategy.\n  ogTitle: Structuring the GitLab Package Registry for enterprise scale\n  ogDescription: >-\n    Learn how to leverage GitLab's unique project-based publishing model\n    alongside root-group-level consumption to create a secure, flexible package\n    management strategy.\n  noIndex: false\n  ogImage: >-\n    https://res.cloudinary.com/about-gitlab-com/image/upload/v1749662332/Blog/Hero%20Images/blog-image-template-1800x945__23_.png\n  ogUrl: >-\n    https://about.gitlab.com/blog/structuring-the-gitlab-package-registry-for-enterprise-scale\n  ogSiteName: https://about.gitlab.com\n  ogType: article\n  canonicalUrls: >-\n    https://about.gitlab.com/blog/structuring-the-gitlab-package-registry-for-enterprise-scale\ntitle: Structuring the GitLab Package Registry for enterprise scale\ndescription: Learn how to leverage GitLab's unique project-based publishing model alongside root-group-level consumption to create a secure, flexible package management strategy.\nauthors:\n  - Tim Rizzi\nheroImage: https://res.cloudinary.com/about-gitlab-com/image/upload/v1749662332/Blog/Hero%20Images/blog-image-template-1800x945__23_.png\ntags:\n  - DevSecOps\n  - tutorial\n  - solutions architecture\ncategory: product\ndate: '2025-02-19'\nslug: structuring-the-gitlab-package-registry-for-enterprise-scale\nfeatured: true\ntemplate: BlogPost\n---\n\nAs organizations grow, managing internal packages becomes increasingly complex. While traditional package managers, like JFrog Artifactory and Sonatype Nexus, use a centralized repository approach, GitLab takes a different path that aligns with modern development teams' work. In this post, we'll explore how to effectively structure your GitLab Package Registry for enterprise scale, focusing on Maven and npm packages as examples.\n\n## Understanding the GitLab Package Registry model\n\nIf you're coming from a traditional package manager, GitLab's approach might initially seem different. Instead of a single centralized repository, GitLab integrates package management directly into your existing project and group structure. This means:\n\n- Teams publish packages to specific projects where the code lives\n- Teams consume packages from root group registries that aggregate all packages below them\n- Access control inherits from your existing GitLab permissions\n\nThis model offers several advantages:\n\n- Clear ownership of packages alongside their source code\n- Granular access control without additional configuration\n- Simplified CI/CD integration\n- Natural alignment with team structures\n- Single URL for accessing all company packages through root group consumption\n\n### The power of root group package registry\n\nWhile GitLab supports package consumption at various group levels, using the root group level has emerged as a best practice among our users. Here's why:\n\n- **Single access point:** One URL provides access to all private packages across your organization\n- **Consistent package naming:** Group-level endpoints allow teams to maintain their preferred naming conventions without conflicts\n- **Simplified configuration:** All developers can use the same configuration to access packages\n- **Secure access management:** Combines with deploy tokens for easy rotation and access control\n- **Hierarchical organization**: Naturally maps to your organizational structure while maintaining unified access\n\n## Real-world example: Enterprise structure\n\nLet's look at how this works in practice with a large enterprise:\n\n```text\ncompany/ (root group)\n├── retail-division/\n│   ├── shared-libraries/     # Division-specific shared code\n│   └── teams/\n│       ├── checkout/        # Team publishes packages here\n│       └── inventory/       # Team publishes packages here\n├── banking-division/\n│   ├── shared-libraries/    # Division-specific shared code\n│   └── teams/\n│       ├── payments/       # Team publishes packages here\n│       └── fraud/         # Team publishes packages here\n└── shared-platform/        # Enterprise-wide shared code\n    ├── java-commons/      # Shared Java libraries\n    └── ui-components/     # Shared UI components\n\n```\n\n### Publishing configuration\n\nTeams publish packages to their specific project registries, maintaining clear ownership:\n\n1. Maven example\n\n```xml\n\u003C!-- checkout/pom.xml -->\n\u003CdistributionManagement>\n    \u003Crepository>\n        \u003Cid>gitlab-maven\u003C/id>\n        \u003Curl>${CI_API_V4_URL}/projects/${CI_PROJECT_ID}/packages/maven\u003C/url>\n    \u003C/repository>\n\u003C/distributionManagement>\n```\n\n2. npm example\n\n```json\n// ui-components/package.json\n{\n  \"name\": \"@company/ui-components\",\n  \"publishConfig\": {\n    \"registry\": \"${CI_API_V4_URL}/projects/${CI_PROJECT_ID}/packages/npm/\"\n  }\n}\n```\n\n### Consuming configuration\n\nThe power of root group consumption comes into play here. All teams configure a single endpoint for package access:\n\n1. Maven example\n\n```xml\n\u003C!-- Any project's pom.xml -->\n\u003Crepositories>\n    \u003Crepository>\n        \u003Cid>gitlab-maven\u003C/id>\n        \u003Curl>https://gitlab.example.com/api/v4/groups/company/-/packages/maven\u003C/url>\n    \u003C/repository>\n\u003C/repositories>\n```\n\n2. npm example\n\n```text\n# Any project's .npmrc\n@company:registry=https://gitlab.example.com/api/v4/groups/company/-/packages/npm/\n```\n\nThis configuration automatically provides access to all packages across your organization while maintaining the benefits of project-based publishing.\n\n## Authentication and access control\n\nGitLab's model simplifies authentication through deploy tokens and CI/CD integration.\n\n### For CI/CD pipelines\n\nGitLab automatically handles authentication in pipelines using `CI_JOB_TOKEN`:\n\n```yaml\n# .gitlab-ci.yml\npublish:\n  script:\n    - mvn deploy  # or npm publish\n  # CI_JOB_TOKEN provides automatic authentication\n\n```\n\n### For development\n\nUse group deploy tokens for package consumption:\n\n- Create read-only deploy tokens at the root group level\n- Rotate tokens periodically for security\n- Share a single configuration across all developers\n\n## Benefits of root group package registry\n\n1. Simplified configuration\n   - One URL for all package access\n   - Consistent setup across teams\n   - Easy token rotation\n2. Clear ownership\n   - Packages stay with their source code\n   - Teams maintain control over publishing\n   - Version history tied to project activity\n3. Natural organization\n   - Matches your company structure\n   - Supports team autonomy\n   - Enables cross-team collaboration\n\n## Getting started\n\n1. Set up your root group\n   - Create a clear group structure\n   - Configure appropriate access controls\n   - Create group deploy tokens\n2. Configure team projects\n   - Set up project-level publishing\n   - Implement CI/CD pipelines\n   - Document package naming conventions\n3. Standardize consumption\n   - Configure root group registry access\n   - Share deploy tokens securely\n   - Document package discovery process\n\n## Summary\n\nGitLab's package registry model, particularly when leveraging root group consumption, offers a powerful solution for enterprise package management. By combining project-based publishing with root group consumption, organizations get the best of both worlds: clear ownership and simplified access. This approach scales naturally with your organization while maintaining security and ease of use.\n\nStart by implementing this model with a single team or division, and expand as you see the benefits of this integrated approach. Remember that while this post focused on Maven and npm, the same principles apply to all package types supported by GitLab.\n\n> Get started with package registries today! Sign up for a [free trial of GitLab Ultimate](https://about.gitlab.com/free-trial/).\n",{"title":5,"description":17,"ogTitle":5,"ogDescription":17,"noIndex":31,"ogImage":19,"ogUrl":32,"ogSiteName":33,"ogType":34,"canonicalUrls":32},false,"https://about.gitlab.com/blog/structuring-the-gitlab-package-registry-for-enterprise-scale","https://about.gitlab.com","article","en-us/blog/structuring-the-gitlab-package-registry-for-enterprise-scale",[37,22,38],"devsecops","solutions-architecture",[21,22,23],"xCQQKsMWPQIK9F1plWwQ1oDixX9JxeyLiqDryf0k-WM",{"logo":42,"freeTrial":47,"sales":52,"login":57,"items":62,"search":382,"minimal":413,"duo":432,"switchNav":441,"pricingDeployment":452},{"config":43},{"href":44,"dataGaName":45,"dataGaLocation":46},"/","gitlab logo","header",{"text":48,"config":49},"Get free trial",{"href":50,"dataGaName":51,"dataGaLocation":46},"https://gitlab.com/-/trial_registrations/new?glm_source=about.gitlab.com&glm_content=default-saas-trial/","free trial",{"text":53,"config":54},"Talk to sales",{"href":55,"dataGaName":56,"dataGaLocation":46},"/sales/","sales",{"text":58,"config":59},"Sign in",{"href":60,"dataGaName":61,"dataGaLocation":46},"https://gitlab.com/users/sign_in/","sign in",[63,92,192,197,301,362],{"text":64,"config":65,"menu":67},"Platform",{"dataNavLevelOne":66},"platform",{"type":68,"columns":69},"cards",[70,76,84],{"title":64,"description":71,"link":72},"The intelligent orchestration platform for DevSecOps",{"text":73,"config":74},"Explore our Platform",{"href":75,"dataGaName":66,"dataGaLocation":46},"/platform/",{"title":77,"description":78,"link":79},"GitLab Duo Agent Platform","Agentic AI for the entire software lifecycle",{"text":80,"config":81},"Meet GitLab Duo",{"href":82,"dataGaName":83,"dataGaLocation":46},"/gitlab-duo-agent-platform/","gitlab duo agent platform",{"title":85,"description":86,"link":87},"Why GitLab","See the top reasons enterprises choose GitLab",{"text":88,"config":89},"Learn more",{"href":90,"dataGaName":91,"dataGaLocation":46},"/why-gitlab/","why gitlab",{"text":93,"left":15,"config":94,"menu":96},"Product",{"dataNavLevelOne":95},"solutions",{"type":97,"link":98,"columns":102,"feature":171},"lists",{"text":99,"config":100},"View all Solutions",{"href":101,"dataGaName":95,"dataGaLocation":46},"/solutions/",[103,127,150],{"title":104,"description":105,"link":106,"items":111},"Automation","CI/CD and automation to accelerate deployment",{"config":107},{"icon":108,"href":109,"dataGaName":110,"dataGaLocation":46},"AutomatedCodeAlt","/solutions/delivery-automation/","automated software delivery",[112,116,119,123],{"text":113,"config":114},"CI/CD",{"href":115,"dataGaLocation":46,"dataGaName":113},"/solutions/continuous-integration/",{"text":77,"config":117},{"href":82,"dataGaLocation":46,"dataGaName":118},"gitlab duo agent platform - product menu",{"text":120,"config":121},"Source Code Management",{"href":122,"dataGaLocation":46,"dataGaName":120},"/solutions/source-code-management/",{"text":124,"config":125},"Automated Software Delivery",{"href":109,"dataGaLocation":46,"dataGaName":126},"Automated software delivery",{"title":128,"description":129,"link":130,"items":135},"Security","Deliver code faster without compromising security",{"config":131},{"href":132,"dataGaName":133,"dataGaLocation":46,"icon":134},"/solutions/application-security-testing/","security and compliance","ShieldCheckLight",[136,140,145],{"text":137,"config":138},"Application Security Testing",{"href":132,"dataGaName":139,"dataGaLocation":46},"Application security testing",{"text":141,"config":142},"Software Supply Chain Security",{"href":143,"dataGaLocation":46,"dataGaName":144},"/solutions/supply-chain/","Software supply chain security",{"text":146,"config":147},"Software Compliance",{"href":148,"dataGaName":149,"dataGaLocation":46},"/solutions/software-compliance/","software compliance",{"title":151,"link":152,"items":157},"Measurement",{"config":153},{"icon":154,"href":155,"dataGaName":156,"dataGaLocation":46},"DigitalTransformation","/solutions/visibility-measurement/","visibility and measurement",[158,162,166],{"text":159,"config":160},"Visibility & Measurement",{"href":155,"dataGaLocation":46,"dataGaName":161},"Visibility and Measurement",{"text":163,"config":164},"Value Stream Management",{"href":165,"dataGaLocation":46,"dataGaName":163},"/solutions/value-stream-management/",{"text":167,"config":168},"Analytics & Insights",{"href":169,"dataGaLocation":46,"dataGaName":170},"/solutions/analytics-and-insights/","Analytics and insights",{"title":172,"type":97,"items":173},"GitLab for",[174,180,186],{"text":175,"config":176},"Enterprise",{"icon":177,"href":178,"dataGaLocation":46,"dataGaName":179},"Building","/enterprise/","enterprise",{"text":181,"config":182},"Small Business",{"icon":183,"href":184,"dataGaLocation":46,"dataGaName":185},"Work","/small-business/","small business",{"text":187,"config":188},"Public Sector",{"icon":189,"href":190,"dataGaLocation":46,"dataGaName":191},"Organization","/solutions/public-sector/","public sector",{"text":193,"config":194},"Pricing",{"href":195,"dataGaName":196,"dataGaLocation":46,"dataNavLevelOne":196},"/pricing/","pricing",{"text":198,"config":199,"menu":201},"Resources",{"dataNavLevelOne":200},"resources",{"type":97,"link":202,"columns":206,"feature":290},{"text":203,"config":204},"View all resources",{"href":205,"dataGaName":200,"dataGaLocation":46},"/resources/",[207,240,262],{"title":208,"items":209},"Getting started",[210,215,220,225,230,235],{"text":211,"config":212},"Install",{"href":213,"dataGaName":214,"dataGaLocation":46},"/install/","install",{"text":216,"config":217},"Quick start guides",{"href":218,"dataGaName":219,"dataGaLocation":46},"/get-started/","quick setup checklists",{"text":221,"config":222},"Learn",{"href":223,"dataGaLocation":46,"dataGaName":224},"https://university.gitlab.com/","learn",{"text":226,"config":227},"Product documentation",{"href":228,"dataGaName":229,"dataGaLocation":46},"https://docs.gitlab.com/","product documentation",{"text":231,"config":232},"Best practice videos",{"href":233,"dataGaName":234,"dataGaLocation":46},"/getting-started-videos/","best practice videos",{"text":236,"config":237},"Integrations",{"href":238,"dataGaName":239,"dataGaLocation":46},"/integrations/","integrations",{"title":241,"items":242},"Discover",[243,248,253,257],{"text":244,"config":245},"Customer success stories",{"href":246,"dataGaName":247,"dataGaLocation":46},"/customers/","customer success stories",{"text":249,"config":250},"Blog",{"href":251,"dataGaName":252,"dataGaLocation":46},"/blog/","blog",{"text":254,"config":255},"The Source",{"href":256,"dataGaName":252,"dataGaLocation":46},"/the-source/",{"text":258,"config":259},"Remote",{"href":260,"dataGaName":261,"dataGaLocation":46},"https://handbook.gitlab.com/handbook/company/culture/all-remote/","remote",{"title":263,"items":264},"Connect",[265,270,275,280,285],{"text":266,"config":267},"GitLab Services",{"href":268,"dataGaName":269,"dataGaLocation":46},"/services/","services",{"text":271,"config":272},"Community",{"href":273,"dataGaName":274,"dataGaLocation":46},"/community/","community",{"text":276,"config":277},"Forum",{"href":278,"dataGaName":279,"dataGaLocation":46},"https://forum.gitlab.com/","forum",{"text":281,"config":282},"Events",{"href":283,"dataGaName":284,"dataGaLocation":46},"/events/","events",{"text":286,"config":287},"Partners",{"href":288,"dataGaName":289,"dataGaLocation":46},"/partners/","partners",{"config":291,"title":294,"text":295,"link":296},{"background":292,"textColor":293},"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":297,"config":298},"Read the latest",{"href":299,"dataGaName":300,"dataGaLocation":46},"/releases/whats-new/","whats new",{"text":302,"config":303,"menu":305},"Company",{"dataNavLevelOne":304},"company",{"type":97,"columns":306},[307],{"items":308},[309,314,320,322,327,332,337,342,347,352,357],{"text":310,"config":311},"About",{"href":312,"dataGaName":313,"dataGaLocation":46},"/company/","about",{"text":315,"config":316,"footerGa":319},"Jobs",{"href":317,"dataGaName":318,"dataGaLocation":46},"/jobs/","jobs",{"dataGaName":318},{"text":281,"config":321},{"href":283,"dataGaName":284,"dataGaLocation":46},{"text":323,"config":324},"Leadership",{"href":325,"dataGaName":326,"dataGaLocation":46},"/company/team/e-group/","leadership",{"text":328,"config":329},"Team",{"href":330,"dataGaName":331,"dataGaLocation":46},"/company/team/","team",{"text":333,"config":334},"Handbook",{"href":335,"dataGaName":336,"dataGaLocation":46},"https://handbook.gitlab.com/","handbook",{"text":338,"config":339},"Investor relations",{"href":340,"dataGaName":341,"dataGaLocation":46},"https://ir.gitlab.com/","investor relations",{"text":343,"config":344},"Trust Center",{"href":345,"dataGaName":346,"dataGaLocation":46},"/security/","trust center",{"text":348,"config":349},"AI Transparency Center",{"href":350,"dataGaName":351,"dataGaLocation":46},"/ai-transparency-center/","ai transparency center",{"text":353,"config":354},"Newsletter",{"href":355,"dataGaName":356,"dataGaLocation":46},"/company/contact/#contact-forms","newsletter",{"text":358,"config":359},"Press",{"href":360,"dataGaName":361,"dataGaLocation":46},"/press/","press",{"text":363,"config":364,"menu":365},"Contact us",{"dataNavLevelOne":304},{"type":97,"columns":366},[367],{"items":368},[369,372,377],{"text":53,"config":370},{"href":55,"dataGaName":371,"dataGaLocation":46},"talk to sales",{"text":373,"config":374},"Support portal",{"href":375,"dataGaName":376,"dataGaLocation":46},"https://support.gitlab.com","support portal",{"text":378,"config":379},"Customer portal",{"href":380,"dataGaName":381,"dataGaLocation":46},"https://customers.gitlab.com/customers/sign_in/","customer portal",{"close":383,"login":384,"suggestions":391},"Close",{"text":385,"link":386},"To search repositories and projects, login to",{"text":387,"config":388},"gitlab.com",{"href":60,"dataGaName":389,"dataGaLocation":390},"search login","search",{"text":392,"default":393},"Suggestions",[394,396,400,402,406,410],{"text":77,"config":395},{"href":82,"dataGaName":77,"dataGaLocation":390},{"text":397,"config":398},"Code Suggestions (AI)",{"href":399,"dataGaName":397,"dataGaLocation":390},"/solutions/code-suggestions/",{"text":113,"config":401},{"href":115,"dataGaName":113,"dataGaLocation":390},{"text":403,"config":404},"GitLab on AWS",{"href":405,"dataGaName":403,"dataGaLocation":390},"/partners/technology-partners/aws/",{"text":407,"config":408},"GitLab on Google Cloud",{"href":409,"dataGaName":407,"dataGaLocation":390},"/partners/technology-partners/google-cloud-platform/",{"text":411,"config":412},"Why GitLab?",{"href":90,"dataGaName":411,"dataGaLocation":390},{"freeTrial":414,"mobileIcon":419,"desktopIcon":424,"secondaryButton":427},{"text":415,"config":416},"Start free trial",{"href":417,"dataGaName":51,"dataGaLocation":418},"https://gitlab.com/-/trials/new/","nav",{"altText":420,"config":421},"Gitlab Icon",{"src":422,"dataGaName":423,"dataGaLocation":418},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1758203874/jypbw1jx72aexsoohd7x.svg","gitlab icon",{"altText":420,"config":425},{"src":426,"dataGaName":423,"dataGaLocation":418},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1758203875/gs4c8p8opsgvflgkswz9.svg",{"text":428,"config":429},"Get Started",{"href":430,"dataGaName":431,"dataGaLocation":418},"https://gitlab.com/-/trial_registrations/new?glm_source=about.gitlab.com/get-started/","get started",{"freeTrial":433,"mobileIcon":437,"desktopIcon":439},{"text":434,"config":435},"Learn more about GitLab Duo",{"href":82,"dataGaName":436,"dataGaLocation":418},"gitlab duo",{"altText":420,"config":438},{"src":422,"dataGaName":423,"dataGaLocation":418},{"altText":420,"config":440},{"src":426,"dataGaName":423,"dataGaLocation":418},{"button":442,"mobileIcon":447,"desktopIcon":449},{"text":443,"config":444},"/switch",{"href":445,"dataGaName":446,"dataGaLocation":418},"#contact","switch",{"altText":420,"config":448},{"src":422,"dataGaName":423,"dataGaLocation":418},{"altText":420,"config":450},{"src":451,"dataGaName":423,"dataGaLocation":418},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1773335277/ohhpiuoxoldryzrnhfrh.png",{"freeTrial":453,"mobileIcon":458,"desktopIcon":460},{"text":454,"config":455},"Back to pricing",{"href":195,"dataGaName":456,"dataGaLocation":418,"icon":457},"back to pricing","GoBack",{"altText":420,"config":459},{"src":422,"dataGaName":423,"dataGaLocation":418},{"altText":420,"config":461},{"src":426,"dataGaName":423,"dataGaLocation":418},{"title":463,"button":464,"config":469},"See how agentic AI transforms software delivery",{"text":465,"config":466},"Sign up for GitLab Transcend on June 10",{"href":467,"dataGaName":468,"dataGaLocation":46},"/releases/whats-new/#sign-up","transcend event",{"layout":470,"icon":471,"disabled":31},"release","AiStar",{"data":473},{"text":474,"source":475,"edit":481,"contribute":486,"config":491,"items":496,"minimal":701},"Git is a trademark of Software Freedom Conservancy and our use of 'GitLab' is under license",{"text":476,"config":477},"View page source",{"href":478,"dataGaName":479,"dataGaLocation":480},"https://gitlab.com/gitlab-com/marketing/digital-experience/about-gitlab-com/","page source","footer",{"text":482,"config":483},"Edit this page",{"href":484,"dataGaName":485,"dataGaLocation":480},"https://gitlab.com/gitlab-com/marketing/digital-experience/about-gitlab-com/-/blob/main/content/","web ide",{"text":487,"config":488},"Please contribute",{"href":489,"dataGaName":490,"dataGaLocation":480},"https://gitlab.com/gitlab-com/marketing/digital-experience/about-gitlab-com/-/blob/main/CONTRIBUTING.md/","please contribute",{"twitter":492,"facebook":493,"youtube":494,"linkedin":495},"https://twitter.com/gitlab","https://www.facebook.com/gitlab","https://www.youtube.com/channel/UCnMGQ8QHMAnVIsI3xJrihhg","https://www.linkedin.com/company/gitlab-com",[497,544,596,640,667],{"title":193,"links":498,"subMenu":513},[499,503,508],{"text":500,"config":501},"View plans",{"href":195,"dataGaName":502,"dataGaLocation":480},"view plans",{"text":504,"config":505},"Why Premium?",{"href":506,"dataGaName":507,"dataGaLocation":480},"/pricing/premium/","why premium",{"text":509,"config":510},"Why Ultimate?",{"href":511,"dataGaName":512,"dataGaLocation":480},"/pricing/ultimate/","why ultimate",[514],{"title":515,"links":516},"Contact Us",[517,520,522,524,529,534,539],{"text":518,"config":519},"Contact sales",{"href":55,"dataGaName":56,"dataGaLocation":480},{"text":373,"config":521},{"href":375,"dataGaName":376,"dataGaLocation":480},{"text":378,"config":523},{"href":380,"dataGaName":381,"dataGaLocation":480},{"text":525,"config":526},"Status",{"href":527,"dataGaName":528,"dataGaLocation":480},"https://status.gitlab.com/","status",{"text":530,"config":531},"Terms of use",{"href":532,"dataGaName":533,"dataGaLocation":480},"/terms/","terms of use",{"text":535,"config":536},"Privacy statement",{"href":537,"dataGaName":538,"dataGaLocation":480},"/privacy/","privacy statement",{"text":540,"config":541},"Cookie preferences",{"dataGaName":542,"dataGaLocation":480,"id":543,"isOneTrustButton":15},"cookie preferences","ot-sdk-btn",{"title":93,"links":545,"subMenu":554},[546,550],{"text":547,"config":548},"DevSecOps platform",{"href":75,"dataGaName":549,"dataGaLocation":480},"devsecops platform",{"text":551,"config":552},"AI-Assisted Development",{"href":82,"dataGaName":553,"dataGaLocation":480},"ai-assisted development",[555],{"title":556,"links":557},"Topics",[558,563,568,573,578,581,586,591],{"text":559,"config":560},"CICD",{"href":561,"dataGaName":562,"dataGaLocation":480},"/topics/ci-cd/","cicd",{"text":564,"config":565},"GitOps",{"href":566,"dataGaName":567,"dataGaLocation":480},"/topics/gitops/","gitops",{"text":569,"config":570},"DevOps",{"href":571,"dataGaName":572,"dataGaLocation":480},"/topics/devops/","devops",{"text":574,"config":575},"Version Control",{"href":576,"dataGaName":577,"dataGaLocation":480},"/topics/version-control/","version control",{"text":21,"config":579},{"href":580,"dataGaName":37,"dataGaLocation":480},"/topics/devsecops/",{"text":582,"config":583},"Cloud Native",{"href":584,"dataGaName":585,"dataGaLocation":480},"/topics/cloud-native/","cloud native",{"text":587,"config":588},"AI for Coding",{"href":589,"dataGaName":590,"dataGaLocation":480},"/topics/devops/ai-for-coding/","ai for coding",{"text":592,"config":593},"Agentic AI",{"href":594,"dataGaName":595,"dataGaLocation":480},"/topics/agentic-ai/","agentic ai",{"title":597,"links":598},"Solutions",[599,601,603,608,612,615,619,622,624,627,630,635],{"text":137,"config":600},{"href":132,"dataGaName":137,"dataGaLocation":480},{"text":126,"config":602},{"href":109,"dataGaName":110,"dataGaLocation":480},{"text":604,"config":605},"Agile development",{"href":606,"dataGaName":607,"dataGaLocation":480},"/solutions/agile-delivery/","agile delivery",{"text":609,"config":610},"SCM",{"href":122,"dataGaName":611,"dataGaLocation":480},"source code management",{"text":559,"config":613},{"href":115,"dataGaName":614,"dataGaLocation":480},"continuous integration & delivery",{"text":616,"config":617},"Value stream management",{"href":165,"dataGaName":618,"dataGaLocation":480},"value stream management",{"text":564,"config":620},{"href":621,"dataGaName":567,"dataGaLocation":480},"/solutions/gitops/",{"text":175,"config":623},{"href":178,"dataGaName":179,"dataGaLocation":480},{"text":625,"config":626},"Small business",{"href":184,"dataGaName":185,"dataGaLocation":480},{"text":628,"config":629},"Public sector",{"href":190,"dataGaName":191,"dataGaLocation":480},{"text":631,"config":632},"Education",{"href":633,"dataGaName":634,"dataGaLocation":480},"/solutions/education/","education",{"text":636,"config":637},"Financial services",{"href":638,"dataGaName":639,"dataGaLocation":480},"/solutions/finance/","financial services",{"title":198,"links":641},[642,644,646,648,651,653,655,657,659,661,663,665],{"text":211,"config":643},{"href":213,"dataGaName":214,"dataGaLocation":480},{"text":216,"config":645},{"href":218,"dataGaName":219,"dataGaLocation":480},{"text":221,"config":647},{"href":223,"dataGaName":224,"dataGaLocation":480},{"text":226,"config":649},{"href":228,"dataGaName":650,"dataGaLocation":480},"docs",{"text":249,"config":652},{"href":251,"dataGaName":252,"dataGaLocation":480},{"text":244,"config":654},{"href":246,"dataGaName":247,"dataGaLocation":480},{"text":258,"config":656},{"href":260,"dataGaName":261,"dataGaLocation":480},{"text":266,"config":658},{"href":268,"dataGaName":269,"dataGaLocation":480},{"text":271,"config":660},{"href":273,"dataGaName":274,"dataGaLocation":480},{"text":276,"config":662},{"href":278,"dataGaName":279,"dataGaLocation":480},{"text":281,"config":664},{"href":283,"dataGaName":284,"dataGaLocation":480},{"text":286,"config":666},{"href":288,"dataGaName":289,"dataGaLocation":480},{"title":302,"links":668},[669,671,673,675,677,679,681,685,690,692,694,696],{"text":310,"config":670},{"href":312,"dataGaName":304,"dataGaLocation":480},{"text":315,"config":672},{"href":317,"dataGaName":318,"dataGaLocation":480},{"text":323,"config":674},{"href":325,"dataGaName":326,"dataGaLocation":480},{"text":328,"config":676},{"href":330,"dataGaName":331,"dataGaLocation":480},{"text":333,"config":678},{"href":335,"dataGaName":336,"dataGaLocation":480},{"text":338,"config":680},{"href":340,"dataGaName":341,"dataGaLocation":480},{"text":682,"config":683},"Sustainability",{"href":684,"dataGaName":682,"dataGaLocation":480},"/sustainability/",{"text":686,"config":687},"Diversity, inclusion and belonging (DIB)",{"href":688,"dataGaName":689,"dataGaLocation":480},"/diversity-inclusion-belonging/","Diversity, inclusion and belonging",{"text":343,"config":691},{"href":345,"dataGaName":346,"dataGaLocation":480},{"text":353,"config":693},{"href":355,"dataGaName":356,"dataGaLocation":480},{"text":358,"config":695},{"href":360,"dataGaName":361,"dataGaLocation":480},{"text":697,"config":698},"Modern Slavery Transparency Statement",{"href":699,"dataGaName":700,"dataGaLocation":480},"https://handbook.gitlab.com/handbook/legal/modern-slavery-act-transparency-statement/","modern slavery transparency statement",{"items":702},[703,706,709],{"text":704,"config":705},"Terms",{"href":532,"dataGaName":533,"dataGaLocation":480},{"text":707,"config":708},"Cookies",{"dataGaName":542,"dataGaLocation":480,"id":543,"isOneTrustButton":15},{"text":710,"config":711},"Privacy",{"href":537,"dataGaName":538,"dataGaLocation":480},[713],{"id":714,"title":9,"body":26,"config":715,"content":717,"description":26,"extension":721,"meta":722,"navigation":15,"path":723,"seo":724,"stem":725,"__hash__":726},"blogAuthors/en-us/blog/authors/tim-rizzi.yml",{"template":716},"BlogAuthor",{"name":9,"config":718},{"headshot":719,"ctfId":720},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1749661866/Blog/Author%20Headshots/trizzi-headshot.jpg","trizzi","yml",{},"/en-us/blog/authors/tim-rizzi",{},"en-us/blog/authors/tim-rizzi","ADPqrpcnKveFJS0m_zFV0VLtb_h_txu59QVgz_YwKMc",[728,738,747],{"content":729,"config":736},{"title":730,"description":731,"heroImage":732,"date":733,"tags":734,"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",[735],"patch releases",{"featured":31,"template":13,"externalUrl":737},"https://docs.gitlab.com/releases/patches/patch-release-gitlab-18-11-2-released/",{"content":739,"config":745},{"title":740,"description":741,"heroImage":732,"date":742,"category":11,"tags":743},"GitLab Patch Release: 18.11.1, 18.10.4, 18.9.6","Discover what's in this latest patch release.","2026-04-22",[735,744],"security releases",{"featured":31,"template":13,"externalUrl":746},"https://docs.gitlab.com/releases/patches/patch-release-gitlab-18-11-1-released/",{"content":748,"config":760},{"title":749,"description":750,"body":751,"category":11,"tags":752,"date":755,"authors":756,"heroImage":759},"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.",[289,753,754],"AWS","AI/ML","2026-04-21",[757,758],"Joe Mann","Mark Kriaf","https://res.cloudinary.com/about-gitlab-com/image/upload/v1776362275/ozbwn9tk0dditpnfddlz.png",{"featured":15,"template":13,"slug":761},"gitlab-amazon-platform-orchestration-on-a-trusted-ai-foundation",{"promotions":763},[764,778,789,801],{"id":765,"categories":766,"header":768,"text":769,"button":770,"image":775},"ai-modernization",[767],"ai-ml","Is AI achieving its promise at scale?","Quiz will take 5 minutes or less",{"text":771,"config":772},"Get your AI maturity score",{"href":773,"dataGaName":774,"dataGaLocation":252},"/assessments/ai-modernization-assessment/","modernization assessment",{"config":776},{"src":777},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1772138786/qix0m7kwnd8x2fh1zq49.png",{"id":779,"categories":780,"header":781,"text":769,"button":782,"image":786},"devops-modernization",[11,37],"Are you just managing tools or shipping innovation?",{"text":783,"config":784},"Get your DevOps maturity score",{"href":785,"dataGaName":774,"dataGaLocation":252},"/assessments/devops-modernization-assessment/",{"config":787},{"src":788},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1772138785/eg818fmakweyuznttgid.png",{"id":790,"categories":791,"header":793,"text":769,"button":794,"image":798},"security-modernization",[792],"security","Are you trading speed for security?",{"text":795,"config":796},"Get your security maturity score",{"href":797,"dataGaName":774,"dataGaLocation":252},"/assessments/security-modernization-assessment/",{"config":799},{"src":800},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1772138786/p4pbqd9nnjejg5ds6mdk.png",{"id":802,"paths":803,"header":806,"text":807,"button":808,"image":813},"github-azure-migration",[804,805],"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":809,"config":810},"See how GitLab compares to GitHub",{"href":811,"dataGaName":812,"dataGaLocation":252},"/compare/gitlab-vs-github/github-azure-migration/","github azure migration",{"config":814},{"src":788},{"header":816,"blurb":817,"button":818,"secondaryButton":823},"Start building faster today","See what your team can do with the intelligent orchestration platform for DevSecOps.\n",{"text":819,"config":820},"Get your free trial",{"href":821,"dataGaName":51,"dataGaLocation":822},"https://gitlab.com/-/trial_registrations/new?glm_content=default-saas-trial&glm_source=about.gitlab.com/","feature",{"text":518,"config":824},{"href":55,"dataGaName":56,"dataGaLocation":822},1777934947737]