[{"data":1,"prerenderedAt":836},["ShallowReactive",2],{"/en-us/blog/new-typefaces-in-gitlab":3,"navigation-en-us":45,"banner-en-us":455,"footer-en-us":465,"blog-post-authors-en-us-Sascha Eggenberger|Jeremy Elder":707,"blog-related-posts-en-us-new-typefaces-in-gitlab":733,"blog-promotions-en-us":773,"next-steps-en-us":826},{"id":4,"title":5,"authorSlugs":6,"body":9,"categorySlug":10,"config":11,"content":15,"description":9,"extension":31,"isFeatured":13,"meta":32,"navigation":33,"path":34,"publishedDate":22,"seo":35,"stem":39,"tagSlugs":40,"__hash__":44},"blogPosts/en-us/blog/new-typefaces-in-gitlab.yml","New Typefaces In Gitlab",[7,8],"sascha-eggenberger","jeremy-elder",null,"news",{"slug":12,"featured":13,"template":14},"new-typefaces-in-gitlab",false,"BlogPost",{"title":16,"description":17,"authors":18,"heroImage":21,"date":22,"body":23,"category":10,"tags":24},"Get to know the new GitLab typefaces","Dive deep into the considerations for changing to GitLab Sans (Inter) and JetBrains Mono, including improved readability.",[19,20],"Sascha Eggenberger","Jeremy Elder","https://res.cloudinary.com/about-gitlab-com/image/upload/v1749669926/Blog/Hero%20Images/Cover3.png","2023-01-17","\nWe take the choice of typefaces very seriously around here. And, in the spirit of transparency, a [GitLab core value](https://handbook.gitlab.com/handbook/values/#transparency), we like to share our rationale for typeface changes. This blog introduces you to the new default typefaces in GitLab – GitLab Sans (Inter) and JetBrains Mono – and explores in detail why we chose them and how they will improve the user experience.\n\n## Introducing GitLab Sans and JetBrains Mono\n\nIn the recent [GitLab rebrand](/blog/devops-is-at-the-center-of-gitlab/), [Inter](https://rsms.me/inter/) was selected as the primary sans-serif typeface and we've adapted it for use in the GitLab user interface (UI) to have more continuity between the brand and product experience. It will be available for users in Release 15.8. Specifically for the UI, we've enabled disambiguation features (increased distinction between some characters) by default. Because of this change, we're including it under the name GitLab Sans in the open source package of GitLab. To complement GitLab Sans with a monospace typeface, we've chosen another open source option: [JetBrains Mono](https://www.jetbrains.com/lp/mono/).\n\nThe GitLab UI has historically relied on system fonts, like San Francisco on macOS and Segoe UI on Microsoft Windows. There are, however, limitations to using these that we'll cover in a moment.\n\n![GitLab Sans (Inter) and JetBrains Mono typefaces](https://about.gitlab.com/images/blogimages/introducing-new-typefaces/gitlab-sans-jetbrainsmono.png){: .center}\nGitLab Sans (Inter) and JetBrains Mono sample\n\n\n## Why the change?\n\nSo we've already mentioned brand continuity as a driving reason for the change, but let's step back a bit. During the rebrand process, Inter was one of many typefaces considered because it was open source and designed for UI. Choosing a font primarily designed for digital output might seem like an odd choice for branding and print application, but the primary extension and experience is the product itself. GitLab is digital-first, and the brand reflects it. Inter had all of the qualities and features we knew we could leverage to enhance and realize our vision for the UI.\n\nWe realize there's a lot of subjectivity wrapped up in a change like this. Visual updates are, well, highly visible, but we believe they have to be rooted in objective considerations that lead to adding real value, so here are a few other aspects we evaluated and will cover in greater detail:\n\n- **Less is more** - How can we limit certain choices in ways that enable more meaningful ones?\n- **Consistency** - Can we create more harmony within a single view, streamline the experience across platforms, and reinforce the brand?\n- **Enhance the content** - Can content be more readable, discernable, and generally consumable?\n\n### Less is more\n\nTypography is a crucial part of the GitLab UI, if not _the_ most crucial part. As we continue to refine and beautify the experience, it's apparent that more control over the typography would yield a better experience not only for our users, but also the ones creating the experiences — our internal product, design, and development teams. System fonts have led to everything from false positive bug reports to visual regression errors on both sides. More choice — especially when systems are choosing — doesn't always lead to better experiences.\n\nWith multiple system fonts in play, we choose compromises, not enhancements. For example, asking what alignment works best for _most_ system fonts in a button instead of what alignment works best for _this_ font. Or, what weight should we use when not all system fonts have the same available options instead of what weight creates the right hierarchy for this content. With fewer typeface options we have more ability to make meaningful decisions about disambiguation, visual weight, language support, hierarchy, type scales, and so much more.\n\n### Consistency\n\nAn experience has multiple facets: a single view or screen, a flow between multiple views, a transition from reading to editing, or a switch from settings to documentation. Consistency should happen not only within each of these, but also across them. Consistency in a single view means hierarchy, balance, and harmony. In a flow, consistency establishes patterns and understanding. When contexts change, consistency brings familiarity and enhances trust. Typography is an important aspect of all of these.\n\nInconsistencies add up and lead to design, tech, and experience debt. There are known consistency problems with system fonts, for example, in Firefox on macOS, San Francisco has tighter letter spacing than on Chrome or Safari. This leads to different experiences across browsers, and this is just for one system font.\n\n![Comparing system fonts to show varied x-height](https://about.gitlab.com/images/blogimages/introducing-new-typefaces/compare-x-height.png){: .center}\nVaried x-heights of system fonts\n\n\nOptically, system fonts are noticeably different in size. However, the difference is more visible when you compare the length of each due to character width, weight, and kerning (the space between characters). This impacts everything from truncation and component width, to wrapping and legibility.\n\n![Comparing system fonts to show varied width](https://about.gitlab.com/images/blogimages/introducing-new-typefaces/compare-width.png){: .center}\nVaried width of system fonts\n\n\nMenlo has been used as our monospaced typeface. It appears bigger than many sans-serif typefaces when using the same font size. To counter that issue, we had downscaled its size by one pixel to make it appear as the same optical size. This added unnecessary bloat to styles and is also not foolproof since sans-serif system fonts also vary.\n\nInter and JetBrains Mono have nearly identical x-height, which allows us to remove all of the downscaling overrides and more generally handle text styles consistently. While both typefaces have specific use cases, they’re almost always present next to each other in the UI, making cohesiveness that much more important.\n\n![GitLab Sans (Inter) and JetBrains Mono x-height comparison](https://about.gitlab.com/images/blogimages/introducing-new-typefaces/gitlab-sans-jetbrainsmono-x-height.png){: .center}\nGitLab Sans and JetBrains Mono with similar x-height\n\n\nBy reducing our typeface options, we're working towards consistency in so many ways we haven't before, everything from brand to product, product to documentation, and browser to browser. Consistency is not the same as uniformity though, and nor should it inhibit preference, but by creating a baseline those things can have room for more thoughtful approaches in the future too.\n\n### Enhance the content\n\nAs mentioned earlier, typography is a crucial part of the UI, and arguably most of the content is in text form. Whether communication or code, status or state, the typeface is the delivery vehicle for the content. GitLab Sans and JetBrains Mono give us better control over readability.\n\nBoth typefaces include variable webfont and contextual features, which means that the font weight and other settings can be finely tuned to enhance visual weight, hierarchy, and contextual alternates. For GitLab Sans, we've enabled the disambiguation feature set to ensure readability is a top priority. Disambiguation is used to avoid common character confusion. For example, by using the feature set [cv05](https://rsms.me/inter/lab/?feat-cv05=1) (lowercase L with tail for disambiguation), you can easily distinguish between the capital “I” and the lowercase “L” (see image below). We had discussed using either [ss04](https://rsms.me/inter/lab/?feat-ss04=1) (disambiguation without slash zero) or cv05 and decided to go with the latter for a simple, modern look.\n\n![Inter Typface character disambiguation](https://about.gitlab.com/images/blogimages/introducing-new-typefaces/inter-disambiguation.png){: .center}\nInter disambiguation options from left to right: Default, without slashed zero (ss04), lowercase L with tail (cv05)\n\n\nGitLab uses a condensed UI, meaning more content in less space and typically at smaller sizes. Inter is popular for a reason, more likely dozens, but the most applicable to GitLab is that it’s designed specifically for UI. On the [website](https://rsms.me/inter/) it states, “Inter is a typeface carefully crafted & designed for computer screens.” With a tall x-height, contextual alternates, tabular numbers, and more, Inter enables us to actually make more meaningful typography decisions that impact readability.\n\nSimilarly, JetBrains Mono has a tall x-height, which increases readability at smaller sizes, and it has a normal character width to keep more characters on a single line which limits wrapping. During our exploration, we found that typefaces like Menlo, Fira Code, Source Code, or Noto Sans Mono either have shorter x-heights or wider characters that lead to size or spacing compromises.\n\nWith these typefaces in place we've started a deep dive into our type scales and updating design resources in Figma too. The upcoming work on type scales, in particular, will provide more consistency and refinement.\n\n## Other considerations\n\nGitLab is an [open core](/blog/gitlab-is-open-core-github-is-closed-source/) product, which means the core of our product is open source, so selecting typefaces that are also open source was a crucial part of the decision.\n\nAnytime you opt to distribute your own resources versus using what's already available to the system the question of performance comes up. And while it's true that we're increasing the payload by a few kilobytes, we're able to rely on modern CSS and browser handling for delivery and caching. At the same time, we're reducing the CSS by removing styles that have been added to counter aforementioned compromises. This is something we'll continue to evaluate and optimize.\n\nAnd speaking of distribution, we're [packaging the fonts](https://www.npmjs.com/package/@gitlab/fonts) to make it easier for all of our properties to consume. This means we're also able to leverage the same resources in our design tooling.\n\nLastly, we know that changes like this have the benefit (or downside, depending on how you look at it) of exposing other inconsistencies in the UI that need to be addressed. While it seems counterintuitive to release an update that potentially introduces visual regression, we consider it as the dye in the water to let us know what else we have to fix as we continue to work towards a single source of truth for typography styles.\n\n## What's next?\n\nAs the typography changes are being rolled out, we’re working through feedback and addressing any potential regressions. Along with type scale updates, we're going to evaluate headings throughout the product to ensure heading levels align with correct Document Object Model (DOM) structure, visual weight, and styles. In short, our typography decisions are interdependent and foundational for the overall experience. By limiting typeface options, we’re removing the limits of how hard we can make typography work so that we can further refine the interface, bring harmony to the UI, and make content more consumable so that using GitLab is more productive and enjoyable.\n\nIf you’d like to provide feedback or contribute, please use this [feedback issue](https://gitlab.com/gitlab-org/gitlab/-/issues/386205).\n",[25,26,27,28,29,30],"design","frontend","open source","product","UI","UX","yml",{},true,"/en-us/blog/new-typefaces-in-gitlab",{"title":16,"description":17,"ogTitle":16,"ogDescription":17,"noIndex":13,"ogImage":21,"ogUrl":36,"ogSiteName":37,"ogType":38,"canonicalUrls":36},"https://about.gitlab.com/blog/new-typefaces-in-gitlab","https://about.gitlab.com","article","en-us/blog/new-typefaces-in-gitlab",[25,26,41,28,42,43],"open-source","ui","ux","CBbT4E11le8xY5ekt1PILoE-mhOuSbaX38OniT6qXxs",{"data":46},{"logo":47,"freeTrial":52,"sales":57,"login":62,"items":67,"search":375,"minimal":406,"duo":425,"switchNav":434,"pricingDeployment":445},{"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,95,190,195,296,356],{"text":69,"config":70,"cards":72},"Platform",{"dataNavLevelOne":71},"platform",[73,79,87],{"title":69,"description":74,"link":75},"The intelligent orchestration platform for DevSecOps",{"text":76,"config":77},"Explore our Platform",{"href":78,"dataGaName":71,"dataGaLocation":51},"/platform/",{"title":80,"description":81,"link":82},"GitLab Duo Agent Platform","Agentic AI for the entire software lifecycle",{"text":83,"config":84},"Meet GitLab Duo",{"href":85,"dataGaName":86,"dataGaLocation":51},"/gitlab-duo-agent-platform/","gitlab duo agent platform",{"title":88,"description":89,"link":90},"Why GitLab","See the top reasons enterprises choose GitLab",{"text":91,"config":92},"Learn more",{"href":93,"dataGaName":94,"dataGaLocation":51},"/why-gitlab/","why gitlab",{"text":96,"left":33,"config":97,"link":99,"lists":103,"footer":172},"Product",{"dataNavLevelOne":98},"solutions",{"text":100,"config":101},"View all Solutions",{"href":102,"dataGaName":98,"dataGaLocation":51},"/solutions/",[104,128,151],{"title":105,"description":106,"link":107,"items":112},"Automation","CI/CD and automation to accelerate deployment",{"config":108},{"icon":109,"href":110,"dataGaName":111,"dataGaLocation":51},"AutomatedCodeAlt","/solutions/delivery-automation/","automated software delivery",[113,117,120,124],{"text":114,"config":115},"CI/CD",{"href":116,"dataGaLocation":51,"dataGaName":114},"/solutions/continuous-integration/",{"text":80,"config":118},{"href":85,"dataGaLocation":51,"dataGaName":119},"gitlab duo agent platform - product menu",{"text":121,"config":122},"Source Code Management",{"href":123,"dataGaLocation":51,"dataGaName":121},"/solutions/source-code-management/",{"text":125,"config":126},"Automated Software Delivery",{"href":110,"dataGaLocation":51,"dataGaName":127},"Automated software delivery",{"title":129,"description":130,"link":131,"items":136},"Security","Deliver code faster without compromising security",{"config":132},{"href":133,"dataGaName":134,"dataGaLocation":51,"icon":135},"/solutions/application-security-testing/","security and compliance","ShieldCheckLight",[137,141,146],{"text":138,"config":139},"Application Security Testing",{"href":133,"dataGaName":140,"dataGaLocation":51},"Application security testing",{"text":142,"config":143},"Software Supply Chain Security",{"href":144,"dataGaLocation":51,"dataGaName":145},"/solutions/supply-chain/","Software supply chain security",{"text":147,"config":148},"Software Compliance",{"href":149,"dataGaName":150,"dataGaLocation":51},"/solutions/software-compliance/","software compliance",{"title":152,"link":153,"items":158},"Measurement",{"config":154},{"icon":155,"href":156,"dataGaName":157,"dataGaLocation":51},"DigitalTransformation","/solutions/visibility-measurement/","visibility and measurement",[159,163,167],{"text":160,"config":161},"Visibility & Measurement",{"href":156,"dataGaLocation":51,"dataGaName":162},"Visibility and Measurement",{"text":164,"config":165},"Value Stream Management",{"href":166,"dataGaLocation":51,"dataGaName":164},"/solutions/value-stream-management/",{"text":168,"config":169},"Analytics & Insights",{"href":170,"dataGaLocation":51,"dataGaName":171},"/solutions/analytics-and-insights/","Analytics and insights",{"title":173,"items":174},"GitLab for",[175,180,185],{"text":176,"config":177},"Enterprise",{"href":178,"dataGaLocation":51,"dataGaName":179},"/enterprise/","enterprise",{"text":181,"config":182},"Small Business",{"href":183,"dataGaLocation":51,"dataGaName":184},"/small-business/","small business",{"text":186,"config":187},"Public Sector",{"href":188,"dataGaLocation":51,"dataGaName":189},"/solutions/public-sector/","public sector",{"text":191,"config":192},"Pricing",{"href":193,"dataGaName":194,"dataGaLocation":51,"dataNavLevelOne":194},"/pricing/","pricing",{"text":196,"config":197,"link":199,"lists":203,"feature":283},"Resources",{"dataNavLevelOne":198},"resources",{"text":200,"config":201},"View all resources",{"href":202,"dataGaName":198,"dataGaLocation":51},"/resources/",[204,237,255],{"title":205,"items":206},"Getting started",[207,212,217,222,227,232],{"text":208,"config":209},"Install",{"href":210,"dataGaName":211,"dataGaLocation":51},"/install/","install",{"text":213,"config":214},"Quick start guides",{"href":215,"dataGaName":216,"dataGaLocation":51},"/get-started/","quick setup checklists",{"text":218,"config":219},"Learn",{"href":220,"dataGaLocation":51,"dataGaName":221},"https://university.gitlab.com/","learn",{"text":223,"config":224},"Product documentation",{"href":225,"dataGaName":226,"dataGaLocation":51},"https://docs.gitlab.com/","product documentation",{"text":228,"config":229},"Best practice videos",{"href":230,"dataGaName":231,"dataGaLocation":51},"/getting-started-videos/","best practice videos",{"text":233,"config":234},"Integrations",{"href":235,"dataGaName":236,"dataGaLocation":51},"/integrations/","integrations",{"title":238,"items":239},"Discover",[240,245,250],{"text":241,"config":242},"Customer success stories",{"href":243,"dataGaName":244,"dataGaLocation":51},"/customers/","customer success stories",{"text":246,"config":247},"Blog",{"href":248,"dataGaName":249,"dataGaLocation":51},"/blog/","blog",{"text":251,"config":252},"Remote",{"href":253,"dataGaName":254,"dataGaLocation":51},"https://handbook.gitlab.com/handbook/company/culture/all-remote/","remote",{"title":256,"items":257},"Connect",[258,263,268,273,278],{"text":259,"config":260},"GitLab Services",{"href":261,"dataGaName":262,"dataGaLocation":51},"/services/","services",{"text":264,"config":265},"Community",{"href":266,"dataGaName":267,"dataGaLocation":51},"/community/","community",{"text":269,"config":270},"Forum",{"href":271,"dataGaName":272,"dataGaLocation":51},"https://forum.gitlab.com/","forum",{"text":274,"config":275},"Events",{"href":276,"dataGaName":277,"dataGaLocation":51},"/events/","events",{"text":279,"config":280},"Partners",{"href":281,"dataGaName":282,"dataGaLocation":51},"/partners/","partners",{"backgroundColor":284,"textColor":285,"text":286,"image":287,"link":291},"#2f2a6b","#fff","Insights for the future of software development",{"altText":288,"config":289},"the source promo card",{"src":290},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1758208064/dzl0dbift9xdizyelkk4.svg",{"text":292,"config":293},"Read the latest",{"href":294,"dataGaName":295,"dataGaLocation":51},"/the-source/","the source",{"text":297,"config":298,"lists":300},"Company",{"dataNavLevelOne":299},"company",[301],{"items":302},[303,308,314,316,321,326,331,336,341,346,351],{"text":304,"config":305},"About",{"href":306,"dataGaName":307,"dataGaLocation":51},"/company/","about",{"text":309,"config":310,"footerGa":313},"Jobs",{"href":311,"dataGaName":312,"dataGaLocation":51},"/jobs/","jobs",{"dataGaName":312},{"text":274,"config":315},{"href":276,"dataGaName":277,"dataGaLocation":51},{"text":317,"config":318},"Leadership",{"href":319,"dataGaName":320,"dataGaLocation":51},"/company/team/e-group/","leadership",{"text":322,"config":323},"Team",{"href":324,"dataGaName":325,"dataGaLocation":51},"/company/team/","team",{"text":327,"config":328},"Handbook",{"href":329,"dataGaName":330,"dataGaLocation":51},"https://handbook.gitlab.com/","handbook",{"text":332,"config":333},"Investor relations",{"href":334,"dataGaName":335,"dataGaLocation":51},"https://ir.gitlab.com/","investor relations",{"text":337,"config":338},"Trust Center",{"href":339,"dataGaName":340,"dataGaLocation":51},"/security/","trust center",{"text":342,"config":343},"AI Transparency Center",{"href":344,"dataGaName":345,"dataGaLocation":51},"/ai-transparency-center/","ai transparency center",{"text":347,"config":348},"Newsletter",{"href":349,"dataGaName":350,"dataGaLocation":51},"/company/contact/#contact-forms","newsletter",{"text":352,"config":353},"Press",{"href":354,"dataGaName":355,"dataGaLocation":51},"/press/","press",{"text":357,"config":358,"lists":359},"Contact us",{"dataNavLevelOne":299},[360],{"items":361},[362,365,370],{"text":58,"config":363},{"href":60,"dataGaName":364,"dataGaLocation":51},"talk to sales",{"text":366,"config":367},"Support portal",{"href":368,"dataGaName":369,"dataGaLocation":51},"https://support.gitlab.com","support portal",{"text":371,"config":372},"Customer portal",{"href":373,"dataGaName":374,"dataGaLocation":51},"https://customers.gitlab.com/customers/sign_in/","customer portal",{"close":376,"login":377,"suggestions":384},"Close",{"text":378,"link":379},"To search repositories and projects, login to",{"text":380,"config":381},"gitlab.com",{"href":65,"dataGaName":382,"dataGaLocation":383},"search login","search",{"text":385,"default":386},"Suggestions",[387,389,393,395,399,403],{"text":80,"config":388},{"href":85,"dataGaName":80,"dataGaLocation":383},{"text":390,"config":391},"Code Suggestions (AI)",{"href":392,"dataGaName":390,"dataGaLocation":383},"/solutions/code-suggestions/",{"text":114,"config":394},{"href":116,"dataGaName":114,"dataGaLocation":383},{"text":396,"config":397},"GitLab on AWS",{"href":398,"dataGaName":396,"dataGaLocation":383},"/partners/technology-partners/aws/",{"text":400,"config":401},"GitLab on Google Cloud",{"href":402,"dataGaName":400,"dataGaLocation":383},"/partners/technology-partners/google-cloud-platform/",{"text":404,"config":405},"Why GitLab?",{"href":93,"dataGaName":404,"dataGaLocation":383},{"freeTrial":407,"mobileIcon":412,"desktopIcon":417,"secondaryButton":420},{"text":408,"config":409},"Start free trial",{"href":410,"dataGaName":56,"dataGaLocation":411},"https://gitlab.com/-/trials/new/","nav",{"altText":413,"config":414},"Gitlab Icon",{"src":415,"dataGaName":416,"dataGaLocation":411},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1758203874/jypbw1jx72aexsoohd7x.svg","gitlab icon",{"altText":413,"config":418},{"src":419,"dataGaName":416,"dataGaLocation":411},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1758203875/gs4c8p8opsgvflgkswz9.svg",{"text":421,"config":422},"Get Started",{"href":423,"dataGaName":424,"dataGaLocation":411},"https://gitlab.com/-/trial_registrations/new?glm_source=about.gitlab.com/get-started/","get started",{"freeTrial":426,"mobileIcon":430,"desktopIcon":432},{"text":427,"config":428},"Learn more about GitLab Duo",{"href":85,"dataGaName":429,"dataGaLocation":411},"gitlab duo",{"altText":413,"config":431},{"src":415,"dataGaName":416,"dataGaLocation":411},{"altText":413,"config":433},{"src":419,"dataGaName":416,"dataGaLocation":411},{"button":435,"mobileIcon":440,"desktopIcon":442},{"text":436,"config":437},"/switch",{"href":438,"dataGaName":439,"dataGaLocation":411},"#contact","switch",{"altText":413,"config":441},{"src":415,"dataGaName":416,"dataGaLocation":411},{"altText":413,"config":443},{"src":444,"dataGaName":416,"dataGaLocation":411},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1773335277/ohhpiuoxoldryzrnhfrh.png",{"freeTrial":446,"mobileIcon":451,"desktopIcon":453},{"text":447,"config":448},"Back to pricing",{"href":193,"dataGaName":449,"dataGaLocation":411,"icon":450},"back to pricing","GoBack",{"altText":413,"config":452},{"src":415,"dataGaName":416,"dataGaLocation":411},{"altText":413,"config":454},{"src":419,"dataGaName":416,"dataGaLocation":411},{"title":456,"button":457,"config":462},"See how agentic AI transforms software delivery",{"text":458,"config":459},"Watch GitLab Transcend now",{"href":460,"dataGaName":461,"dataGaLocation":51},"/events/transcend/virtual/","transcend event",{"layout":463,"icon":464,"disabled":33},"release","AiStar",{"data":466},{"text":467,"source":468,"edit":474,"contribute":479,"config":484,"items":489,"minimal":696},"Git is a trademark of Software Freedom Conservancy and our use of 'GitLab' is under license",{"text":469,"config":470},"View page source",{"href":471,"dataGaName":472,"dataGaLocation":473},"https://gitlab.com/gitlab-com/marketing/digital-experience/about-gitlab-com/","page source","footer",{"text":475,"config":476},"Edit this page",{"href":477,"dataGaName":478,"dataGaLocation":473},"https://gitlab.com/gitlab-com/marketing/digital-experience/about-gitlab-com/-/blob/main/content/","web ide",{"text":480,"config":481},"Please contribute",{"href":482,"dataGaName":483,"dataGaLocation":473},"https://gitlab.com/gitlab-com/marketing/digital-experience/about-gitlab-com/-/blob/main/CONTRIBUTING.md/","please contribute",{"twitter":485,"facebook":486,"youtube":487,"linkedin":488},"https://twitter.com/gitlab","https://www.facebook.com/gitlab","https://www.youtube.com/channel/UCnMGQ8QHMAnVIsI3xJrihhg","https://www.linkedin.com/company/gitlab-com",[490,537,591,635,662],{"title":191,"links":491,"subMenu":506},[492,496,501],{"text":493,"config":494},"View plans",{"href":193,"dataGaName":495,"dataGaLocation":473},"view plans",{"text":497,"config":498},"Why Premium?",{"href":499,"dataGaName":500,"dataGaLocation":473},"/pricing/premium/","why premium",{"text":502,"config":503},"Why Ultimate?",{"href":504,"dataGaName":505,"dataGaLocation":473},"/pricing/ultimate/","why ultimate",[507],{"title":508,"links":509},"Contact Us",[510,513,515,517,522,527,532],{"text":511,"config":512},"Contact sales",{"href":60,"dataGaName":61,"dataGaLocation":473},{"text":366,"config":514},{"href":368,"dataGaName":369,"dataGaLocation":473},{"text":371,"config":516},{"href":373,"dataGaName":374,"dataGaLocation":473},{"text":518,"config":519},"Status",{"href":520,"dataGaName":521,"dataGaLocation":473},"https://status.gitlab.com/","status",{"text":523,"config":524},"Terms of use",{"href":525,"dataGaName":526,"dataGaLocation":473},"/terms/","terms of use",{"text":528,"config":529},"Privacy statement",{"href":530,"dataGaName":531,"dataGaLocation":473},"/privacy/","privacy statement",{"text":533,"config":534},"Cookie preferences",{"dataGaName":535,"dataGaLocation":473,"id":536,"isOneTrustButton":33},"cookie preferences","ot-sdk-btn",{"title":96,"links":538,"subMenu":547},[539,543],{"text":540,"config":541},"DevSecOps platform",{"href":78,"dataGaName":542,"dataGaLocation":473},"devsecops platform",{"text":544,"config":545},"AI-Assisted Development",{"href":85,"dataGaName":546,"dataGaLocation":473},"ai-assisted development",[548],{"title":549,"links":550},"Topics",[551,556,561,566,571,576,581,586],{"text":552,"config":553},"CICD",{"href":554,"dataGaName":555,"dataGaLocation":473},"/topics/ci-cd/","cicd",{"text":557,"config":558},"GitOps",{"href":559,"dataGaName":560,"dataGaLocation":473},"/topics/gitops/","gitops",{"text":562,"config":563},"DevOps",{"href":564,"dataGaName":565,"dataGaLocation":473},"/topics/devops/","devops",{"text":567,"config":568},"Version Control",{"href":569,"dataGaName":570,"dataGaLocation":473},"/topics/version-control/","version control",{"text":572,"config":573},"DevSecOps",{"href":574,"dataGaName":575,"dataGaLocation":473},"/topics/devsecops/","devsecops",{"text":577,"config":578},"Cloud Native",{"href":579,"dataGaName":580,"dataGaLocation":473},"/topics/cloud-native/","cloud native",{"text":582,"config":583},"AI for Coding",{"href":584,"dataGaName":585,"dataGaLocation":473},"/topics/devops/ai-for-coding/","ai for coding",{"text":587,"config":588},"Agentic AI",{"href":589,"dataGaName":590,"dataGaLocation":473},"/topics/agentic-ai/","agentic ai",{"title":592,"links":593},"Solutions",[594,596,598,603,607,610,614,617,619,622,625,630],{"text":138,"config":595},{"href":133,"dataGaName":138,"dataGaLocation":473},{"text":127,"config":597},{"href":110,"dataGaName":111,"dataGaLocation":473},{"text":599,"config":600},"Agile development",{"href":601,"dataGaName":602,"dataGaLocation":473},"/solutions/agile-delivery/","agile delivery",{"text":604,"config":605},"SCM",{"href":123,"dataGaName":606,"dataGaLocation":473},"source code management",{"text":552,"config":608},{"href":116,"dataGaName":609,"dataGaLocation":473},"continuous integration & delivery",{"text":611,"config":612},"Value stream management",{"href":166,"dataGaName":613,"dataGaLocation":473},"value stream management",{"text":557,"config":615},{"href":616,"dataGaName":560,"dataGaLocation":473},"/solutions/gitops/",{"text":176,"config":618},{"href":178,"dataGaName":179,"dataGaLocation":473},{"text":620,"config":621},"Small business",{"href":183,"dataGaName":184,"dataGaLocation":473},{"text":623,"config":624},"Public sector",{"href":188,"dataGaName":189,"dataGaLocation":473},{"text":626,"config":627},"Education",{"href":628,"dataGaName":629,"dataGaLocation":473},"/solutions/education/","education",{"text":631,"config":632},"Financial services",{"href":633,"dataGaName":634,"dataGaLocation":473},"/solutions/finance/","financial services",{"title":196,"links":636},[637,639,641,643,646,648,650,652,654,656,658,660],{"text":208,"config":638},{"href":210,"dataGaName":211,"dataGaLocation":473},{"text":213,"config":640},{"href":215,"dataGaName":216,"dataGaLocation":473},{"text":218,"config":642},{"href":220,"dataGaName":221,"dataGaLocation":473},{"text":223,"config":644},{"href":225,"dataGaName":645,"dataGaLocation":473},"docs",{"text":246,"config":647},{"href":248,"dataGaName":249,"dataGaLocation":473},{"text":241,"config":649},{"href":243,"dataGaName":244,"dataGaLocation":473},{"text":251,"config":651},{"href":253,"dataGaName":254,"dataGaLocation":473},{"text":259,"config":653},{"href":261,"dataGaName":262,"dataGaLocation":473},{"text":264,"config":655},{"href":266,"dataGaName":267,"dataGaLocation":473},{"text":269,"config":657},{"href":271,"dataGaName":272,"dataGaLocation":473},{"text":274,"config":659},{"href":276,"dataGaName":277,"dataGaLocation":473},{"text":279,"config":661},{"href":281,"dataGaName":282,"dataGaLocation":473},{"title":297,"links":663},[664,666,668,670,672,674,676,680,685,687,689,691],{"text":304,"config":665},{"href":306,"dataGaName":299,"dataGaLocation":473},{"text":309,"config":667},{"href":311,"dataGaName":312,"dataGaLocation":473},{"text":317,"config":669},{"href":319,"dataGaName":320,"dataGaLocation":473},{"text":322,"config":671},{"href":324,"dataGaName":325,"dataGaLocation":473},{"text":327,"config":673},{"href":329,"dataGaName":330,"dataGaLocation":473},{"text":332,"config":675},{"href":334,"dataGaName":335,"dataGaLocation":473},{"text":677,"config":678},"Sustainability",{"href":679,"dataGaName":677,"dataGaLocation":473},"/sustainability/",{"text":681,"config":682},"Diversity, inclusion and belonging (DIB)",{"href":683,"dataGaName":684,"dataGaLocation":473},"/diversity-inclusion-belonging/","Diversity, inclusion and belonging",{"text":337,"config":686},{"href":339,"dataGaName":340,"dataGaLocation":473},{"text":347,"config":688},{"href":349,"dataGaName":350,"dataGaLocation":473},{"text":352,"config":690},{"href":354,"dataGaName":355,"dataGaLocation":473},{"text":692,"config":693},"Modern Slavery Transparency Statement",{"href":694,"dataGaName":695,"dataGaLocation":473},"https://handbook.gitlab.com/handbook/legal/modern-slavery-act-transparency-statement/","modern slavery transparency statement",{"items":697},[698,701,704],{"text":699,"config":700},"Terms",{"href":525,"dataGaName":526,"dataGaLocation":473},{"text":702,"config":703},"Cookies",{"dataGaName":535,"dataGaLocation":473,"id":536,"isOneTrustButton":33},{"text":705,"config":706},"Privacy",{"href":530,"dataGaName":531,"dataGaLocation":473},[708,721],{"id":709,"title":19,"body":9,"config":710,"content":712,"description":9,"extension":31,"meta":716,"navigation":33,"path":717,"seo":718,"stem":719,"__hash__":720},"blogAuthors/en-us/blog/authors/sascha-eggenberger.yml",{"template":711},"BlogAuthor",{"name":19,"config":713},{"headshot":714,"ctfId":715},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1749666141/Blog/Author%20Headshots/sascha_eggenberger_headshot.png","O6MskfzTlsw7vLqbd86bX",{},"/en-us/blog/authors/sascha-eggenberger",{},"en-us/blog/authors/sascha-eggenberger","iVzuFh00wZhV49BtPlP23EF2TmGKfCMlgYhOc61qo40",{"id":722,"title":20,"body":9,"config":723,"content":724,"description":9,"extension":31,"meta":728,"navigation":33,"path":729,"seo":730,"stem":731,"__hash__":732},"blogAuthors/en-us/blog/authors/jeremy-elder.yml",{"template":711},{"name":20,"config":725},{"headshot":726,"ctfId":727},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1749666146/Blog/Author%20Headshots/jeldergl-headshot.jpg","jeldergl",{},"/en-us/blog/authors/jeremy-elder",{},"en-us/blog/authors/jeremy-elder","BsksUFrVlSl13Z6MgAEBni-fS8lN0G0egd8LWP0JKsE",[734,747,759],{"content":735,"config":745},{"title":736,"description":737,"authors":738,"heroImage":740,"body":741,"date":742,"category":10,"tags":743},"GitLab named a 2026 Omdia Universe Leader","Omdia's 2026 report on AI-assisted software development ranked 19 vendors. Here is what GitLab's top scores mean for engineering teams.",[739],"Rebecca Carter","https://res.cloudinary.com/about-gitlab-com/image/upload/v1774465167/n5hlvrsrheadeccyr1oz.png","GitLab is named a Leader in the 2026 Omdia Universe for AI-assisted Software Development, IDE-based Tools. Of the nineteen vendors evaluated by the independent analyst firm, GitLab earned best-in-class scores in three categories: Solution Breadth (100%), Strategy and Innovation (88%), and Core Features (82%). Top-tier ratings followed for Extended Features and Vendor Execution.\n\n\nThis year's assessment is notable for a specific reason: Omdia expanded its evaluation criteria, and for the first time, AI development tools were scored on full software lifecycle capability, not just coding. That shift mirrors where the AI evolution is heading and shook up which vendors came out on top.\n\n\n![Omdia Universe chart](https://res.cloudinary.com/about-gitlab-com/image/upload/v1775848262/asyd6bpbtwlhicqonhit.png \"Source: Omdia, Universe: AI-assisted Software Development, Part 1: IDE-based Tools, 2026\")\n> [Download the full Omdia Universe report.](https://learn.gitlab.com/c/analyst-omdia-ai?x=fRC1cQ)\n\n## About Omdia Universe\n\nOmdia Universe plots vendors across Solution Capability and Strategy and Execution, producing three tiers: Leaders (strongest on both axes, recommended for every shortlist), Challengers (narrower feature range or earlier in maturity), and Prospects (earlier-stage or adjacent-fit vendors).\n\n## What changed in this year's assessment\n\nThe expansion of Omdia's criteria reflects something practitioners are already experiencing. AI coding tools have raised developer output significantly, and applications that once took weeks can now be prototyped in a fraction of the time. But acceleration at the coding stage does not automatically translate to faster delivery. Review backlogs grow. Security findings accumulate. Deployments still require coordination across teams using tools that were not designed to work together.\n\nOmdia captured this dynamic directly: The tools pulling ahead are the ones that handle testing, security, deployment, and orchestration. Not just code generation. That finding drove the decision to broaden the assessment criteria and separated the Leaders from the Challengers.\n\nThe other major shift in this year's report is how Omdia treated agentic AI. The 2026 assessment weighted agentic capabilities as a current evaluation dimension rather than a future consideration. This includes whether a platform can coordinate multiple tasks autonomously, orchestrate handoffs between specialized agents, and support teams at different stages of agent adoption.\n\n## Where GitLab scored\n\nGitLab earned best-in-class scores in three categories:\n\n**Solution Breadth: 100%.** Coverage of the full SDLC in a single platform, from planning and requirements through deployment and issue management. This includes lifecycle phases that most AI coding tools do not touch. For example, prebuilt agents like [Planner Agent](https://docs.gitlab.com/user/duo_agent_platform/agents/foundational_agents/planner/) and [Security Analyst Agent](https://docs.gitlab.com/user/duo_agent_platform/agents/foundational_agents/security_analyst_agent/) extend AI assistance into sprint planning, vulnerability triage, and remediation guidance: the parts of the lifecycle where delivery actually gets stuck.\n\n**Strategy and Innovation: 88%.** Differentiation through end-to-end orchestration, privacy-first architecture with no training on private data, and multi-model support via partnerships with Anthropic, Google, and AWS. Teams can select models suited to their workload and data requirements. The platform's approach to unified context, where agents collaborate across issues, merge requests, pipelines, and security findings without losing state, is an example of the architectural innovation Omdia recognized in this category.\n\n**Core Features: 82%.** This score reflects deep coverage across the parts of the lifecycle where engineering teams spend most of their time. Code is generated with real-time context from the IDE and codebase, tested across unit, integration, and security dimensions, and reviewed with prioritization built in. DevOps automation handles CI/CD, GitOps, and [root cause analysis](https://docs.gitlab.com/user/gitlab_duo_chat/examples/#troubleshoot-failed-cicd-jobs-with-root-cause-analysis) for pipeline failures. The [AI Impact Dashboard](https://docs.gitlab.com/user/analytics/duo_and_sdlc_trends/) gives teams measurable visibility into cycle times, deployment frequency, and where AI is actually moving the needle on productivity.\n\nGitLab also earned top-tier recognition for Extended Features (80%) and Vendor Execution (88%).\n\n## The changing role of human developers and AI agents\n\nOne of the more substantive findings in the Omdia report concerns the evolving role of the software developer alongside these tools. Development teams are increasingly a mix of AI engineers and their AI agents, with engineers supervising and directing agentic AI. With AI coding generating the bulk of the code, the human's job shifts toward ensuring technology requirements are actually met, supervising quality, applying right guardrails, designing autonomous production pipelines, and mediating between business goals and the use of agentic AI across the software lifecycle.\n\nThis shift has implications for how organizations evaluate their AI investments. A team that has automated code generation but still handles review, testing, and deployment manually has not yet truly accelerated software innovation. The productivity gain from faster coding compounds when the rest of the lifecycle can keep pace. It shrinks when it cannot, and the bottlenecks move downstream instead.\n\n## Enterprise readiness as table stakes\n\nSomething notable in how Omdia structured this year's assessment: enterprise controls and guardrails are no longer a bonus category. Compliance certifications, deployment flexibility, and privacy architecture appeared as baseline expectations for Leader-tier platforms, not as distinguishing features. Organizations in regulated industries and those with data sovereignty requirements are now weighing these factors as entry criteria.\n\nGitLab's posture on these dimensions highlight its unique differentiation in the market: SOC 2 and ISO 27001 certified platform, [privacy-first design](https://about.gitlab.com/blog/why-enterprise-independence-matters-more-than-ever-in-devsecops/) with no training on private customer data for its agentic AI capabilities, self-managed deployment support across cloud and on-premises (including air-gapped environments), and support for self-hosted AI models. Its consumption as a single-tenant SaaS application via GitLab Dedicated, with FedRAMP Moderate Authorized via GitLab Dedicated for Government, extends its leadership in deployment flexibility. \n\nThe Omdia report recognized these not as a feature list but as evidence of the platform's readiness for the organizations where the compliance bar is highest: financial services, government, healthcare, and other regulated sectors that cannot compromise on data residency or auditability.\n\n## Benchmark your maturity in software development\n\nFor teams actively evaluating where their AI development strategy stands, Omdia's recommendation is clear: GitLab belongs on the top of the list.\n\nThe deeper question for most engineering leaders right now is not which AI tool generates the best code. It is whether the code being generated can be put to production with the highest level of quality, security, and performance. It must be understood, governed, and maintained by the software teams responsible for it. With GitLab, coding speed translates to innovation velocity.\n\nIf you want to benchmark your organization’s maturity in software development best practices and evolution, you can get a personalized score and concrete next steps to take in these assessments for [AI Modernization](https://about.gitlab.com/assessments/ai-modernization-assessment/), [DevOps Modernization](https://about.gitlab.com/assessments/devops-modernization-assessment/), and [Security Modernization](https://about.gitlab.com/assessments/security-modernization-assessment/). \n\n[Download the full Omdia Universe report.](https://learn.gitlab.com/c/analyst-omdia-ai?x=fRC1cQ)\n","2026-04-13",[744,572,540,10],"research",{"featured":33,"template":14,"slug":746},"gitlab-named-a-2026-omdia-universe-leader",{"content":748,"config":757},{"title":749,"description":750,"authors":751,"heroImage":753,"date":754,"body":755,"category":10,"tags":756},"Introducing the GitLab Managed Service Provider (MSP) Partner Program","Build a profitable, services-led DevSecOps practice - backed by GitLab.",[752],"Karishma Kumar","https://res.cloudinary.com/about-gitlab-com/image/upload/v1772047747/ntihfmnu2fepamqemaas.png","2026-02-26","*This blog is written for managed service providers (MSPs) looking to build a GitLab practice. If you’re a developer or engineering leader, this is the program that can empower the partners who help teams like yours scale and move faster.*\n\nMany organizations know they need a modern DevSecOps platform. What they often don't have is the bandwidth to deploy, manage, and continuously optimize one while shipping software at the pace the business demands. That's a real opportunity for MSPs, and now GitLab has a defined program to support them.\n\nWe're excited to introduce the **GitLab MSP Partner Program**, a new global program that enables qualified MSPs to deliver GitLab as a fully managed service to their customers.\n\n## Why this matters for partners and customers\n\nFor the first time, GitLab has a formally defined, globally available program built specifically for MSPs. This means clear requirements, structured enablement, dedicated support, and real financial benefits, so partners can confidently invest in building a GitLab managed services practice.\n\nThe timing is right. Organizations are accelerating their DevSecOps journeys, but many are navigating complex migrations, sprawling toolchains, and growing security requirements on top of their core work of building and shipping software.\n\nGitLab MSP partners handle the operational side of running the platform, including deployment, migration, administration, and ongoing support, so development teams can stay focused on what they do best.\n\n## What MSP partners get\n\n**Financial benefits**: MSP partners earn GitLab partner margins plus an additional MSP premium on all transactions, new business, and renewals. You also retain 100% of the service fees you charge customers for deployment, migration, training, enablement, and strategic consulting. That's multiple recurring revenue streams built around a single platform.\n\n**Enablement and education**: Partners have access to quarterly technical bootcamps covering version updates, new features, best practices, ongoing roadmap updates, and peer sharing. Recommended cloud certifications (AWS Solutions Architect Associate, GCP Associate Cloud Engineer) round out the technical foundation.\n\n**Go-to-market support**: MSPs receive a GitLab Certified MSP Partner badge, co-brandable assets, eligibility for joint customer case studies, a Partner Locator listing, and access to Marketing Development Funds (MDF) for qualified demand generation activities.\n\n## What customers can expect\n\nCustomers working with a GitLab MSP partner get a structured, managed DevSecOps experience, documented and repeatable implementation methodologies, regular business reviews, and support with clearly defined response and escalation paths.\n\nThe result: Development teams can stay focused on building great software while their MSP partner focuses on running and optimizing the platform.\n\n## A new opportunity around AI\n\nOrganizations are increasingly looking to safely introduce AI into their software development workflows, and even experienced teams can benefit from a structured approach to rolling it out at scale. GitLab MSP partners are well-positioned to guide customers through GitLab Duo Agent Platform as part of a broader managed services offering.\n\nBy combining GitLab's DevSecOps platform with MSP-delivered operational expertise, customers can experiment with AI-assisted workflows in a governed environment, meet data residency and compliance requirements, and scale AI adoption across teams without overburdening internal resources.\n\n## Is this right for your business?\n\nThe GitLab MSP Partner Program is a strong fit if you:\n\n* Already deliver managed services in cloud, infrastructure, or application operations  \n* Want to add high-value DevSecOps to your portfolio  \n* Have or want to build technical talent interested in modern development platforms  \n* Prefer long-term customer relationships over one-time transactions\n\nIf you're already a GitLab Select and Professional Services Partner, the MSP program gives you a structured way to turn your existing expertise into a repeatable managed offering.\n\n## Getting started\n\nThe program launches with the **Certified MSP Partner** designation. There's no minimum ARR or customer count required to join. Here's how the path looks:\n\n1. **Confirm fit** - Verify you meet the business and technical requirements outlined in the [handbook page](https://handbook.gitlab.com/handbook/resellers/channel-program-guide/#the-gitlab-managed-service-provider-msp-partner-program).  \n2. **Apply via the GitLab Partner Portal** - Submit your application with business and technical documentation.  \n3. **Complete 90-day onboarding** - A structured onboarding journey covers contracts, technical enablement, sales training, and your first customer engagement.  \n4. **Launch your managed offering** - Package your services, set your SLAs, and begin engaging customers.\n\nCompleted applications are reviewed within approximately three business days.\n\n> Interested in building a GitLab managed services practice? New partners can apply [to become a GitLab Partner](https://about.gitlab.com/partners/). Existing partners can reach out to your GitLab representative to learn more about the program and tell us about the solutions you're currently offering customers through your MSP practice!\n",[572,10,282],{"featured":13,"template":14,"slug":758},"introducing-the-gitlab-managed-service-provider-msp-partner-program",{"content":760,"config":771},{"title":761,"authors":762,"date":766,"body":767,"category":10,"tags":768,"description":769,"heroImage":770},"DevSecOps-as-a-Service on Oracle Cloud Infrastructure by Data Intensity",[763,764,752,765],"Biju Thomas","Matt Genelin","Ryan Palmaro","2026-02-10","At GitLab, we know that many organizations choose GitLab Self-Managed for the control, customization, and security it provides. However, managing underlying infrastructure can be a significant operational challenge — especially for teams who want to focus on delivering software, not maintaining platforms.\n\nThat's why we're excited to work with [Oracle Cloud Infrastructure (OCI)](https://www.oracle.com/cloud/) and [Data Intensity](https://www.dataintensity.com/services/security-services/devsecops/), a trusted Oracle managed services provider, to offer a new managed service option, DevSecOps-as-a-Service, that brings together the best of both worlds: the control of GitLab Self-Managed with the operational ease of a fully managed service.\n\n## Why GitLab Self-Managed?\n\nGitLab Self-Managed gives you complete ownership of your DevSecOps platform. You control where your data lives, how your instance is configured, and can customize it to meet specific compliance, security, or operational requirements. This level of control is essential for organizations with strict regulatory requirements, data residency needs, or specific integration must-haves.\n\nThe challenge for some customers running on GitLab Self-Managed means managing servers, handling upgrades, ensuring high availability, and implementing disaster recovery. All require specialized expertise and dedicated resources.\n\n## A managed path to GitLab Self-Managed\n\nData Intensity's DevSecOps-as-a-Service on OCI removes these operational burdens while preserving the control benefits of GitLab Self-Managed. Instead of building and maintaining infrastructure yourself, you get a standalone GitLab instance managed by Data Intensity's team of experts, running on OCI's high-performance cloud infrastructure.\n\nHere's what's included:\n\n* Standalone GitLab instance on OCI infrastructure\n* 24x7 monitoring, alarming, and support\n* Quarterly patching scheduled during your chosen maintenance windows\n* Automated backups and disaster recovery protection\n\n## Scaling with your organization\n\nData Intensity’s managed service is designed to grow with your team, offering tiered architectures to match your specific user capacity and recovery requirements:\n\n| **Feature**        | **Standard**    | **Premier**     | **Premier +**   |\n|--------------------|-----------------|-----------------|-----------------|\n| **User Capacity**  | Up to 1,000     | Up to 2,000     | Up to 3,000     |\n| **Performance**    | 20 requests/sec | 40 requests/sec | 60 requests/sec |\n| **Availability**   | 99.9%           | 99.95%          | 99.99%          |\n| **Recovery (RTO)** | 48 hours        | 8 hours         | 4 hours         |\n\nFor more information, visit Data Intensity’s website to learn more about [DevSecOps-as-a-Service](https://www.dataintensity.com/services/security-services/devsecops/).\n\n## Why OCI for GitLab?\nOracle Cloud Infrastructure (OCI) provides a robust foundation for running GitLab Self-Managed, offering a secure, high-performance environment at a significantly lower cost than other hyperscalers. Organizations migrating workloads to OCI commonly realize infrastructure cost reductions of 40-50%, making it easier to fund and scale deployments.\n\nOCI supports a wide range of deployment models, from public cloud regions to specialized environments such as Government and EU Sovereign Clouds, as well as dedicated infrastructure deployed behind your firewall. These options come with consistent pricing, tooling, and operational experience, enabling teams to standardize GitLab deployments across regulated, hybrid, and global environments.\n\nThe combination of GitLab's comprehensive DevSecOps platform, OCI's high-performance infrastructure, and Data Intensity's managed services expertise provides a turnkey solution that lets your teams focus on what matters: building great software.\n\n## Is this right for your organization?\nConsider Data Intensity's DevSecOps-as-a-Service if you:\n* Want GitLab Self-Managed but need to minimize operational overhead\n* Require specific compliance, security, or data residency requirements\n* Need guaranteed SLAs and professional disaster recovery capabilities\n* Prefer predictable costs and expert management over building in-house infrastructure expertise\n* Are already using or planning to use OCI for your cloud infrastructure\n* Prioritize flexibility and control\n* Want a dedicated instance that’s managed externally but offers the control of a self-managed environment\n\n## Getting started\nOrganizations interested in running GitLab Self-Managed on OCI through Data Intensity's DevSecOps-as-a-Service can contact Data Intensity via the [Data Intensity website](https://www.dataintensity.com/services/security-services/devsecops/) to discuss specific requirements and begin deployment planning.\n\nModernizing your DevSecOps doesn't have to be complex. Data Intensity provides optional migration of code repositories and customizations to ensure a smooth transition to OCI.\n\nAs GitLab continues expanding our partner ecosystem, solutions like this demonstrate our commitment to giving organizations choice in how they deploy and manage GitLab — whether that's SaaS, self-managed, or managed services through trusted partners.",[282,540],"Run GitLab Self-Managed with minimal overhead. Data Intensity delivers DevSecOps-as-a-Service on OCI with expert management and disaster recovery.","https://res.cloudinary.com/about-gitlab-com/image/upload/v1750098794/Blog/Hero%20Images/Blog/Hero%20Images/blog-image-template-1800x945%20%289%29_DoeBNJVrhv9FpF3WCsHNc_1750098793762.png",{"featured":33,"template":14,"slug":772},"devsecops-as-a-service-on-oracle-cloud-infrastructure-by-data-intensity",{"promotions":774},[775,789,800,812],{"id":776,"categories":777,"header":779,"text":780,"button":781,"image":786},"ai-modernization",[778],"ai-ml","Is AI achieving its promise at scale?","Quiz will take 5 minutes or less",{"text":782,"config":783},"Get your AI maturity score",{"href":784,"dataGaName":785,"dataGaLocation":249},"/assessments/ai-modernization-assessment/","modernization assessment",{"config":787},{"src":788},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1772138786/qix0m7kwnd8x2fh1zq49.png",{"id":790,"categories":791,"header":792,"text":780,"button":793,"image":797},"devops-modernization",[28,575],"Are you just managing tools or shipping innovation?",{"text":794,"config":795},"Get your DevOps maturity score",{"href":796,"dataGaName":785,"dataGaLocation":249},"/assessments/devops-modernization-assessment/",{"config":798},{"src":799},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1772138785/eg818fmakweyuznttgid.png",{"id":801,"categories":802,"header":804,"text":780,"button":805,"image":809},"security-modernization",[803],"security","Are you trading speed for security?",{"text":806,"config":807},"Get your security maturity score",{"href":808,"dataGaName":785,"dataGaLocation":249},"/assessments/security-modernization-assessment/",{"config":810},{"src":811},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1772138786/p4pbqd9nnjejg5ds6mdk.png",{"id":813,"paths":814,"header":817,"text":818,"button":819,"image":824},"github-azure-migration",[815,816],"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":820,"config":821},"See how GitLab compares to GitHub",{"href":822,"dataGaName":823,"dataGaLocation":249},"/compare/gitlab-vs-github/github-azure-migration/","github azure migration",{"config":825},{"src":799},{"header":827,"blurb":828,"button":829,"secondaryButton":834},"Start building faster today","See what your team can do with the intelligent orchestration platform for DevSecOps.\n",{"text":830,"config":831},"Get your free trial",{"href":832,"dataGaName":56,"dataGaLocation":833},"https://gitlab.com/-/trial_registrations/new?glm_content=default-saas-trial&glm_source=about.gitlab.com/","feature",{"text":511,"config":835},{"href":60,"dataGaName":61,"dataGaLocation":833},1776442963480]