[{"data":1,"prerenderedAt":5814},["ShallowReactive",2],{"/en-us/customers/all":3,"navigation-en-us":129,"banner-en-us":554,"footer-en-us":571,"footer-source-/en-us/customers/all/":813,"next-steps-en-us":875,"customers-en-us":890},{"_path":4,"_dir":5,"_draft":6,"_partial":6,"_locale":7,"seo":8,"content":11,"_id":122,"_type":123,"title":124,"_source":125,"_file":126,"_stem":127,"_extension":128},"/en-us/customers/all","customers",false,"",{"title":9,"description":10},"Browse all case studies from GitLab customers","From planning to production, see how GitLab brings teams together and shorten the software development lifecycle.",[12,22,120],{"componentName":13,"componentContent":14},"CommonBreadcrumbs",{"crumbs":15},[16,20],{"title":17,"config":18},"Customer Stories",{"href":19},"/customers/",{"title":21},"All customer stories",{"componentName":23,"componentContent":24},"CustomersAllCustomerCards",{"title":25,"filters":26,"cardButtonText":117,"zeroStateTitle":118,"zeroStateDescription":119},"Browse all customer stories",[27,47,94],{"options":28,"config":45},[29,33,37,41],{"label":30,"config":31},"Any company size",{"id":32},"any",{"label":34,"config":35},"Small to medium business (0 - 100)",{"id":36},"smb",{"label":38,"config":39},"Mid-market (101 - 2000)",{"id":40},"mm",{"label":42,"config":43},"Enterprise (2001+)",{"id":44},"ent",{"name":46},"size",{"options":48,"config":92},[49,52,56,60,64,68,72,76,80,84,88],{"label":50,"config":51},"Any industry",{"id":32},{"label":53,"config":54},"Aviation",{"id":55},"aviation",{"label":57,"config":58},"Consulting",{"id":59},"consulting",{"label":61,"config":62},"Ecommerce",{"id":63},"ecommerce",{"label":65,"config":66},"Education",{"id":67},"education",{"label":69,"config":70},"Financial Services",{"id":71},"financial",{"label":73,"config":74},"Open source software",{"id":75},"openSource",{"label":77,"config":78},"Public sector",{"id":79},"public",{"label":81,"config":82},"Retail",{"id":83},"retail",{"label":85,"config":86},"Science & Research",{"id":87},"scienceResearch",{"label":89,"config":90},"Technology",{"id":91},"technology",{"name":93},"industry",{"options":95,"config":115},[96,99,103,107,111],{"label":97,"config":98},"Any region",{"id":32},{"label":100,"config":101},"North America",{"id":102},"amer",{"label":104,"config":105},"Europe, the Middle East, and Africa",{"id":106},"emea",{"label":108,"config":109},"Asia-Pacific",{"id":110},"apac",{"label":112,"config":113},"Remote",{"id":114},"remote",{"name":116},"region","Learn more","No customers found","Try adjusting your filters to see more results.",{"componentName":121},"CommonNextSteps","content:en-us:customers:all.yml","yaml","All","content","en-us/customers/all.yml","en-us/customers/all","yml",{"_path":130,"_dir":131,"_draft":6,"_partial":6,"_locale":7,"data":132,"_id":550,"_type":123,"title":551,"_source":125,"_file":552,"_stem":553,"_extension":128},"/shared/en-us/main-navigation","en-us",{"logo":133,"freeTrial":138,"sales":143,"login":148,"items":153,"search":481,"minimal":512,"duo":531,"pricingDeployment":540},{"config":134},{"href":135,"dataGaName":136,"dataGaLocation":137},"/","gitlab logo","header",{"text":139,"config":140},"Get free trial",{"href":141,"dataGaName":142,"dataGaLocation":137},"https://gitlab.com/-/trial_registrations/new?glm_source=about.gitlab.com&glm_content=default-saas-trial/","free trial",{"text":144,"config":145},"Talk to sales",{"href":146,"dataGaName":147,"dataGaLocation":137},"/sales/","sales",{"text":149,"config":150},"Sign in",{"href":151,"dataGaName":152,"dataGaLocation":137},"https://gitlab.com/users/sign_in/","sign in",[154,197,294,299,402,462],{"text":155,"config":156,"cards":158,"footer":180},"Platform",{"dataNavLevelOne":157},"platform",[159,165,173],{"title":155,"description":160,"link":161},"The most comprehensive AI-powered DevSecOps Platform",{"text":162,"config":163},"Explore our Platform",{"href":164,"dataGaName":157,"dataGaLocation":137},"/platform/",{"title":166,"description":167,"link":168},"GitLab Duo (AI)","Build software faster with AI at every stage of development",{"text":169,"config":170},"Meet GitLab Duo",{"href":171,"dataGaName":172,"dataGaLocation":137},"/gitlab-duo/","gitlab duo ai",{"title":174,"description":175,"link":176},"Why GitLab","10 reasons why Enterprises choose GitLab",{"text":117,"config":177},{"href":178,"dataGaName":179,"dataGaLocation":137},"/why-gitlab/","why gitlab",{"title":181,"items":182},"Get started with",[183,188,193],{"text":184,"config":185},"Platform Engineering",{"href":186,"dataGaName":187,"dataGaLocation":137},"/solutions/platform-engineering/","platform engineering",{"text":189,"config":190},"Developer Experience",{"href":191,"dataGaName":192,"dataGaLocation":137},"/developer-experience/","Developer experience",{"text":194,"config":195},"MLOps",{"href":196,"dataGaName":194,"dataGaLocation":137},"/topics/devops/the-role-of-ai-in-devops/",{"text":198,"left":199,"config":200,"link":202,"lists":206,"footer":276},"Product",true,{"dataNavLevelOne":201},"solutions",{"text":203,"config":204},"View all Solutions",{"href":205,"dataGaName":201,"dataGaLocation":137},"/solutions/",[207,232,255],{"title":208,"description":209,"link":210,"items":215},"Automation","CI/CD and automation to accelerate deployment",{"config":211},{"icon":212,"href":213,"dataGaName":214,"dataGaLocation":137},"AutomatedCodeAlt","/solutions/delivery-automation/","automated software delivery",[216,220,224,228],{"text":217,"config":218},"CI/CD",{"href":219,"dataGaLocation":137,"dataGaName":217},"/solutions/continuous-integration/",{"text":221,"config":222},"AI-Assisted Development",{"href":171,"dataGaLocation":137,"dataGaName":223},"AI assisted development",{"text":225,"config":226},"Source Code Management",{"href":227,"dataGaLocation":137,"dataGaName":225},"/solutions/source-code-management/",{"text":229,"config":230},"Automated Software Delivery",{"href":213,"dataGaLocation":137,"dataGaName":231},"Automated software delivery",{"title":233,"description":234,"link":235,"items":240},"Security","Deliver code faster without compromising security",{"config":236},{"href":237,"dataGaName":238,"dataGaLocation":137,"icon":239},"/solutions/application-security-testing/","security and compliance","ShieldCheckLight",[241,245,250],{"text":242,"config":243},"Application Security Testing",{"href":237,"dataGaName":244,"dataGaLocation":137},"Application security testing",{"text":246,"config":247},"Software Supply Chain Security",{"href":248,"dataGaLocation":137,"dataGaName":249},"/solutions/supply-chain/","Software supply chain security",{"text":251,"config":252},"Software Compliance",{"href":253,"dataGaName":254,"dataGaLocation":137},"/solutions/software-compliance/","software compliance",{"title":256,"link":257,"items":262},"Measurement",{"config":258},{"icon":259,"href":260,"dataGaName":261,"dataGaLocation":137},"DigitalTransformation","/solutions/visibility-measurement/","visibility and measurement",[263,267,271],{"text":264,"config":265},"Visibility & Measurement",{"href":260,"dataGaLocation":137,"dataGaName":266},"Visibility and Measurement",{"text":268,"config":269},"Value Stream Management",{"href":270,"dataGaLocation":137,"dataGaName":268},"/solutions/value-stream-management/",{"text":272,"config":273},"Analytics & Insights",{"href":274,"dataGaLocation":137,"dataGaName":275},"/solutions/analytics-and-insights/","Analytics and insights",{"title":277,"items":278},"GitLab for",[279,284,289],{"text":280,"config":281},"Enterprise",{"href":282,"dataGaLocation":137,"dataGaName":283},"/enterprise/","enterprise",{"text":285,"config":286},"Small Business",{"href":287,"dataGaLocation":137,"dataGaName":288},"/small-business/","small business",{"text":290,"config":291},"Public Sector",{"href":292,"dataGaLocation":137,"dataGaName":293},"/solutions/public-sector/","public sector",{"text":295,"config":296},"Pricing",{"href":297,"dataGaName":298,"dataGaLocation":137,"dataNavLevelOne":298},"/pricing/","pricing",{"text":300,"config":301,"link":303,"lists":307,"feature":389},"Resources",{"dataNavLevelOne":302},"resources",{"text":304,"config":305},"View all resources",{"href":306,"dataGaName":302,"dataGaLocation":137},"/resources/",[308,341,361],{"title":309,"items":310},"Getting started",[311,316,321,326,331,336],{"text":312,"config":313},"Install",{"href":314,"dataGaName":315,"dataGaLocation":137},"/install/","install",{"text":317,"config":318},"Quick start guides",{"href":319,"dataGaName":320,"dataGaLocation":137},"/get-started/","quick setup checklists",{"text":322,"config":323},"Learn",{"href":324,"dataGaLocation":137,"dataGaName":325},"https://university.gitlab.com/","learn",{"text":327,"config":328},"Product documentation",{"href":329,"dataGaName":330,"dataGaLocation":137},"https://docs.gitlab.com/","product documentation",{"text":332,"config":333},"Best practice videos",{"href":334,"dataGaName":335,"dataGaLocation":137},"/getting-started-videos/","best practice videos",{"text":337,"config":338},"Integrations",{"href":339,"dataGaName":340,"dataGaLocation":137},"/integrations/","integrations",{"title":342,"items":343},"Discover",[344,348,353,356],{"text":345,"config":346},"Customer success stories",{"href":19,"dataGaName":347,"dataGaLocation":137},"customer success stories",{"text":349,"config":350},"Blog",{"href":351,"dataGaName":352,"dataGaLocation":137},"/blog/","blog",{"text":112,"config":354},{"href":355,"dataGaName":114,"dataGaLocation":137},"https://handbook.gitlab.com/handbook/company/culture/all-remote/",{"text":357,"config":358},"TeamOps",{"href":359,"dataGaName":360,"dataGaLocation":137},"/teamops/","teamops",{"title":362,"items":363},"Connect",[364,369,374,379,384],{"text":365,"config":366},"GitLab Services",{"href":367,"dataGaName":368,"dataGaLocation":137},"/services/","services",{"text":370,"config":371},"Community",{"href":372,"dataGaName":373,"dataGaLocation":137},"/community/","community",{"text":375,"config":376},"Forum",{"href":377,"dataGaName":378,"dataGaLocation":137},"https://forum.gitlab.com/","forum",{"text":380,"config":381},"Events",{"href":382,"dataGaName":383,"dataGaLocation":137},"/events/","events",{"text":385,"config":386},"Partners",{"href":387,"dataGaName":388,"dataGaLocation":137},"/partners/","partners",{"backgroundColor":390,"textColor":391,"text":392,"image":393,"link":397},"#2f2a6b","#fff","Insights for the future of software development",{"altText":394,"config":395},"the source promo card",{"src":396},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1758208064/dzl0dbift9xdizyelkk4.svg",{"text":398,"config":399},"Read the latest",{"href":400,"dataGaName":401,"dataGaLocation":137},"/the-source/","the source",{"text":403,"config":404,"lists":406},"Company",{"dataNavLevelOne":405},"company",[407],{"items":408},[409,414,420,422,427,432,437,442,447,452,457],{"text":410,"config":411},"About",{"href":412,"dataGaName":413,"dataGaLocation":137},"/company/","about",{"text":415,"config":416,"footerGa":419},"Jobs",{"href":417,"dataGaName":418,"dataGaLocation":137},"/jobs/","jobs",{"dataGaName":418},{"text":380,"config":421},{"href":382,"dataGaName":383,"dataGaLocation":137},{"text":423,"config":424},"Leadership",{"href":425,"dataGaName":426,"dataGaLocation":137},"/company/team/e-group/","leadership",{"text":428,"config":429},"Team",{"href":430,"dataGaName":431,"dataGaLocation":137},"/company/team/","team",{"text":433,"config":434},"Handbook",{"href":435,"dataGaName":436,"dataGaLocation":137},"https://handbook.gitlab.com/","handbook",{"text":438,"config":439},"Investor relations",{"href":440,"dataGaName":441,"dataGaLocation":137},"https://ir.gitlab.com/","investor relations",{"text":443,"config":444},"Trust Center",{"href":445,"dataGaName":446,"dataGaLocation":137},"/security/","trust center",{"text":448,"config":449},"AI Transparency Center",{"href":450,"dataGaName":451,"dataGaLocation":137},"/ai-transparency-center/","ai transparency center",{"text":453,"config":454},"Newsletter",{"href":455,"dataGaName":456,"dataGaLocation":137},"/company/contact/","newsletter",{"text":458,"config":459},"Press",{"href":460,"dataGaName":461,"dataGaLocation":137},"/press/","press",{"text":463,"config":464,"lists":465},"Contact us",{"dataNavLevelOne":405},[466],{"items":467},[468,471,476],{"text":144,"config":469},{"href":146,"dataGaName":470,"dataGaLocation":137},"talk to sales",{"text":472,"config":473},"Support portal",{"href":474,"dataGaName":475,"dataGaLocation":137},"https://support.gitlab.com","support portal",{"text":477,"config":478},"Customer portal",{"href":479,"dataGaName":480,"dataGaLocation":137},"https://customers.gitlab.com/customers/sign_in/","customer portal",{"close":482,"login":483,"suggestions":490},"Close",{"text":484,"link":485},"To search repositories and projects, login to",{"text":486,"config":487},"gitlab.com",{"href":151,"dataGaName":488,"dataGaLocation":489},"search login","search",{"text":491,"default":492},"Suggestions",[493,495,499,501,505,509],{"text":166,"config":494},{"href":171,"dataGaName":166,"dataGaLocation":489},{"text":496,"config":497},"Code Suggestions (AI)",{"href":498,"dataGaName":496,"dataGaLocation":489},"/solutions/code-suggestions/",{"text":217,"config":500},{"href":219,"dataGaName":217,"dataGaLocation":489},{"text":502,"config":503},"GitLab on AWS",{"href":504,"dataGaName":502,"dataGaLocation":489},"/partners/technology-partners/aws/",{"text":506,"config":507},"GitLab on Google Cloud",{"href":508,"dataGaName":506,"dataGaLocation":489},"/partners/technology-partners/google-cloud-platform/",{"text":510,"config":511},"Why GitLab?",{"href":178,"dataGaName":510,"dataGaLocation":489},{"freeTrial":513,"mobileIcon":518,"desktopIcon":523,"secondaryButton":526},{"text":514,"config":515},"Start free trial",{"href":516,"dataGaName":142,"dataGaLocation":517},"https://gitlab.com/-/trials/new/","nav",{"altText":519,"config":520},"Gitlab Icon",{"src":521,"dataGaName":522,"dataGaLocation":517},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1758203874/jypbw1jx72aexsoohd7x.svg","gitlab icon",{"altText":519,"config":524},{"src":525,"dataGaName":522,"dataGaLocation":517},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1758203875/gs4c8p8opsgvflgkswz9.svg",{"text":527,"config":528},"Get Started",{"href":529,"dataGaName":530,"dataGaLocation":517},"https://gitlab.com/-/trial_registrations/new?glm_source=about.gitlab.com/compare/gitlab-vs-github/","get started",{"freeTrial":532,"mobileIcon":536,"desktopIcon":538},{"text":533,"config":534},"Learn more about GitLab Duo",{"href":171,"dataGaName":535,"dataGaLocation":517},"gitlab duo",{"altText":519,"config":537},{"src":521,"dataGaName":522,"dataGaLocation":517},{"altText":519,"config":539},{"src":525,"dataGaName":522,"dataGaLocation":517},{"freeTrial":541,"mobileIcon":546,"desktopIcon":548},{"text":542,"config":543},"Back to pricing",{"href":297,"dataGaName":544,"dataGaLocation":517,"icon":545},"back to pricing","GoBack",{"altText":519,"config":547},{"src":521,"dataGaName":522,"dataGaLocation":517},{"altText":519,"config":549},{"src":525,"dataGaName":522,"dataGaLocation":517},"content:shared:en-us:main-navigation.yml","Main Navigation","shared/en-us/main-navigation.yml","shared/en-us/main-navigation",{"_path":555,"_dir":131,"_draft":6,"_partial":6,"_locale":7,"title":556,"button":557,"image":562,"config":566,"_id":568,"_type":123,"_source":125,"_file":569,"_stem":570,"_extension":128},"/shared/en-us/banner","is now in public beta!",{"text":558,"config":559},"Try the Beta",{"href":560,"dataGaName":561,"dataGaLocation":137},"/gitlab-duo/agent-platform/","duo banner",{"altText":563,"config":564},"GitLab Duo Agent Platform",{"src":565},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1753720689/somrf9zaunk0xlt7ne4x.svg",{"layout":567},"release","content:shared:en-us:banner.yml","shared/en-us/banner.yml","shared/en-us/banner",{"_path":572,"_dir":131,"_draft":6,"_partial":6,"_locale":7,"data":573,"_id":809,"_type":123,"title":810,"_source":125,"_file":811,"_stem":812,"_extension":128},"/shared/en-us/main-footer",{"text":574,"source":575,"edit":581,"contribute":586,"config":591,"items":596,"minimal":801},"Git is a trademark of Software Freedom Conservancy and our use of 'GitLab' is under license",{"text":576,"config":577},"View page source",{"href":578,"dataGaName":579,"dataGaLocation":580},"https://gitlab.com/gitlab-com/marketing/digital-experience/about-gitlab-com/","page source","footer",{"text":582,"config":583},"Edit this page",{"href":584,"dataGaName":585,"dataGaLocation":580},"https://gitlab.com/gitlab-com/marketing/digital-experience/about-gitlab-com/-/blob/main/content/","web ide",{"text":587,"config":588},"Please contribute",{"href":589,"dataGaName":590,"dataGaLocation":580},"https://gitlab.com/gitlab-com/marketing/digital-experience/about-gitlab-com/-/blob/main/CONTRIBUTING.md/","please contribute",{"twitter":592,"facebook":593,"youtube":594,"linkedin":595},"https://twitter.com/gitlab","https://www.facebook.com/gitlab","https://www.youtube.com/channel/UCnMGQ8QHMAnVIsI3xJrihhg","https://www.linkedin.com/company/gitlab-com",[597,644,697,738,767],{"title":295,"links":598,"subMenu":613},[599,603,608],{"text":600,"config":601},"View plans",{"href":297,"dataGaName":602,"dataGaLocation":580},"view plans",{"text":604,"config":605},"Why Premium?",{"href":606,"dataGaName":607,"dataGaLocation":580},"/pricing/premium/","why premium",{"text":609,"config":610},"Why Ultimate?",{"href":611,"dataGaName":612,"dataGaLocation":580},"/pricing/ultimate/","why ultimate",[614],{"title":615,"links":616},"Contact Us",[617,620,622,624,629,634,639],{"text":618,"config":619},"Contact sales",{"href":146,"dataGaName":147,"dataGaLocation":580},{"text":472,"config":621},{"href":474,"dataGaName":475,"dataGaLocation":580},{"text":477,"config":623},{"href":479,"dataGaName":480,"dataGaLocation":580},{"text":625,"config":626},"Status",{"href":627,"dataGaName":628,"dataGaLocation":580},"https://status.gitlab.com/","status",{"text":630,"config":631},"Terms of use",{"href":632,"dataGaName":633,"dataGaLocation":580},"/terms/","terms of use",{"text":635,"config":636},"Privacy statement",{"href":637,"dataGaName":638,"dataGaLocation":580},"/privacy/","privacy statement",{"text":640,"config":641},"Cookie preferences",{"dataGaName":642,"dataGaLocation":580,"id":643,"isOneTrustButton":199},"cookie preferences","ot-sdk-btn",{"title":198,"links":645,"subMenu":653},[646,650],{"text":647,"config":648},"DevSecOps platform",{"href":164,"dataGaName":649,"dataGaLocation":580},"devsecops platform",{"text":221,"config":651},{"href":171,"dataGaName":652,"dataGaLocation":580},"ai-assisted development",[654],{"title":655,"links":656},"Topics",[657,662,667,672,677,682,687,692],{"text":658,"config":659},"CICD",{"href":660,"dataGaName":661,"dataGaLocation":580},"/topics/ci-cd/","cicd",{"text":663,"config":664},"GitOps",{"href":665,"dataGaName":666,"dataGaLocation":580},"/topics/gitops/","gitops",{"text":668,"config":669},"DevOps",{"href":670,"dataGaName":671,"dataGaLocation":580},"/topics/devops/","devops",{"text":673,"config":674},"Version Control",{"href":675,"dataGaName":676,"dataGaLocation":580},"/topics/version-control/","version control",{"text":678,"config":679},"DevSecOps",{"href":680,"dataGaName":681,"dataGaLocation":580},"/topics/devsecops/","devsecops",{"text":683,"config":684},"Cloud Native",{"href":685,"dataGaName":686,"dataGaLocation":580},"/topics/cloud-native/","cloud native",{"text":688,"config":689},"AI for Coding",{"href":690,"dataGaName":691,"dataGaLocation":580},"/topics/devops/ai-for-coding/","ai for coding",{"text":693,"config":694},"Agentic AI",{"href":695,"dataGaName":696,"dataGaLocation":580},"/topics/agentic-ai/","agentic ai",{"title":698,"links":699},"Solutions",[700,702,704,709,713,716,720,723,725,728,730,733],{"text":242,"config":701},{"href":237,"dataGaName":242,"dataGaLocation":580},{"text":231,"config":703},{"href":213,"dataGaName":214,"dataGaLocation":580},{"text":705,"config":706},"Agile development",{"href":707,"dataGaName":708,"dataGaLocation":580},"/solutions/agile-delivery/","agile delivery",{"text":710,"config":711},"SCM",{"href":227,"dataGaName":712,"dataGaLocation":580},"source code management",{"text":658,"config":714},{"href":219,"dataGaName":715,"dataGaLocation":580},"continuous integration & delivery",{"text":717,"config":718},"Value stream management",{"href":270,"dataGaName":719,"dataGaLocation":580},"value stream management",{"text":663,"config":721},{"href":722,"dataGaName":666,"dataGaLocation":580},"/solutions/gitops/",{"text":280,"config":724},{"href":282,"dataGaName":283,"dataGaLocation":580},{"text":726,"config":727},"Small business",{"href":287,"dataGaName":288,"dataGaLocation":580},{"text":77,"config":729},{"href":292,"dataGaName":293,"dataGaLocation":580},{"text":65,"config":731},{"href":732,"dataGaName":67,"dataGaLocation":580},"/solutions/education/",{"text":734,"config":735},"Financial services",{"href":736,"dataGaName":737,"dataGaLocation":580},"/solutions/finance/","financial services",{"title":300,"links":739},[740,742,744,746,749,751,753,755,757,759,761,763,765],{"text":312,"config":741},{"href":314,"dataGaName":315,"dataGaLocation":580},{"text":317,"config":743},{"href":319,"dataGaName":320,"dataGaLocation":580},{"text":322,"config":745},{"href":324,"dataGaName":325,"dataGaLocation":580},{"text":327,"config":747},{"href":329,"dataGaName":748,"dataGaLocation":580},"docs",{"text":349,"config":750},{"href":351,"dataGaName":352,"dataGaLocation":580},{"text":345,"config":752},{"href":19,"dataGaName":347,"dataGaLocation":580},{"text":112,"config":754},{"href":355,"dataGaName":114,"dataGaLocation":580},{"text":365,"config":756},{"href":367,"dataGaName":368,"dataGaLocation":580},{"text":357,"config":758},{"href":359,"dataGaName":360,"dataGaLocation":580},{"text":370,"config":760},{"href":372,"dataGaName":373,"dataGaLocation":580},{"text":375,"config":762},{"href":377,"dataGaName":378,"dataGaLocation":580},{"text":380,"config":764},{"href":382,"dataGaName":383,"dataGaLocation":580},{"text":385,"config":766},{"href":387,"dataGaName":388,"dataGaLocation":580},{"title":403,"links":768},[769,771,773,775,777,779,781,785,790,792,794,796],{"text":410,"config":770},{"href":412,"dataGaName":405,"dataGaLocation":580},{"text":415,"config":772},{"href":417,"dataGaName":418,"dataGaLocation":580},{"text":423,"config":774},{"href":425,"dataGaName":426,"dataGaLocation":580},{"text":428,"config":776},{"href":430,"dataGaName":431,"dataGaLocation":580},{"text":433,"config":778},{"href":435,"dataGaName":436,"dataGaLocation":580},{"text":438,"config":780},{"href":440,"dataGaName":441,"dataGaLocation":580},{"text":782,"config":783},"Sustainability",{"href":784,"dataGaName":782,"dataGaLocation":580},"/sustainability/",{"text":786,"config":787},"Diversity, inclusion and belonging (DIB)",{"href":788,"dataGaName":789,"dataGaLocation":580},"/diversity-inclusion-belonging/","Diversity, inclusion and belonging",{"text":443,"config":791},{"href":445,"dataGaName":446,"dataGaLocation":580},{"text":453,"config":793},{"href":455,"dataGaName":456,"dataGaLocation":580},{"text":458,"config":795},{"href":460,"dataGaName":461,"dataGaLocation":580},{"text":797,"config":798},"Modern Slavery Transparency Statement",{"href":799,"dataGaName":800,"dataGaLocation":580},"https://handbook.gitlab.com/handbook/legal/modern-slavery-act-transparency-statement/","modern slavery transparency statement",{"items":802},[803,805,807],{"text":630,"config":804},{"href":632,"dataGaName":633,"dataGaLocation":580},{"text":635,"config":806},{"href":637,"dataGaName":638,"dataGaLocation":580},{"text":640,"config":808},{"dataGaName":642,"dataGaLocation":580,"id":643,"isOneTrustButton":199},"content:shared:en-us:main-footer.yml","Main Footer","shared/en-us/main-footer.yml","shared/en-us/main-footer",{"_path":4,"_dir":5,"_draft":6,"_partial":6,"_locale":7,"seo":814,"content":815,"_id":122,"_type":123,"title":124,"_source":125,"_file":126,"_stem":127,"_extension":128},{"title":9,"description":10},[816,822,874],{"componentName":13,"componentContent":817},{"crumbs":818},[819,821],{"title":17,"config":820},{"href":19},{"title":21},{"componentName":23,"componentContent":823},{"title":25,"filters":824,"cardButtonText":117,"zeroStateTitle":118,"zeroStateDescription":119},[825,836,861],{"options":826,"config":835},[827,829,831,833],{"label":30,"config":828},{"id":32},{"label":34,"config":830},{"id":36},{"label":38,"config":832},{"id":40},{"label":42,"config":834},{"id":44},{"name":46},{"options":837,"config":860},[838,840,842,844,846,848,850,852,854,856,858],{"label":50,"config":839},{"id":32},{"label":53,"config":841},{"id":55},{"label":57,"config":843},{"id":59},{"label":61,"config":845},{"id":63},{"label":65,"config":847},{"id":67},{"label":69,"config":849},{"id":71},{"label":73,"config":851},{"id":75},{"label":77,"config":853},{"id":79},{"label":81,"config":855},{"id":83},{"label":85,"config":857},{"id":87},{"label":89,"config":859},{"id":91},{"name":93},{"options":862,"config":873},[863,865,867,869,871],{"label":97,"config":864},{"id":32},{"label":100,"config":866},{"id":102},{"label":104,"config":868},{"id":106},{"label":108,"config":870},{"id":110},{"label":112,"config":872},{"id":114},{"name":116},{"componentName":121},{"_path":876,"_dir":131,"_draft":6,"_partial":6,"_locale":7,"header":877,"eyebrow":878,"blurb":879,"button":880,"secondaryButton":884,"_id":886,"_type":123,"title":887,"_source":125,"_file":888,"_stem":889,"_extension":128},"/shared/en-us/next-steps","Start shipping better software faster","50%+ of the Fortune 100 trust GitLab","See what your team can do with the intelligent\n\n\nDevSecOps platform.\n",{"text":139,"config":881},{"href":882,"dataGaName":142,"dataGaLocation":883},"https://gitlab.com/-/trial_registrations/new?glm_content=default-saas-trial&glm_source=about.gitlab.com/","feature",{"text":144,"config":885},{"href":146,"dataGaName":147,"dataGaLocation":883},"content:shared:en-us:next-steps.yml","Next Steps","shared/en-us/next-steps.yml","shared/en-us/next-steps",[891,952,1009,1067,1128,1180,1228,1284,1342,1404,1459,1512,1565,1618,1661,1723,1779,1834,1884,1932,1986,2034,2089,2141,2198,2240,2286,2343,2388,2434,2487,2537,2585,2639,2690,2730,2775,2819,2866,2907,2962,3011,3061,3110,3159,3205,3738,3794,3841,3885,3935,3984,4032,4084,4130,4195,4246,4293,4333,4372,4417,4460,4512,4558,4601,4649,4697,4757,4803,4848,4904,4949,4999,5047,5094,5137,5189,5237,5283,5328,5375,5425,5476,5526,5569,5618,5667,5715,5769],{"_path":892,"content":893,"config":949,"_id":951},"/en-us/customers/agoda",{"name":894,"logo":895,"hero":896,"heroImage":897,"benefits":898,"industry":910,"employeeCount":911,"location":912,"solution":913,"stats":914,"headline":924,"summary":925,"quotes":926,"content":931},"Agoda","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745517953/pm102567vvrf60bcuveh.png","Online travel giant Agoda boosts developer productivity with GitLab","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518427/demvhye8v4ixhqzmygih.png",[899,903,906],{"metric":900,"config":901},"Faster time to market",{"icon":902},"Accelerate",{"metric":904,"config":905},"Easier, faster onboarding",{"icon":322},{"metric":907,"config":908},"Increased developer retention",{"icon":909},"Group","Online Travel Services","4,000+ ","Singapore","GitLab Ultimate",[915,918,921],{"value":916,"metric":917},">98%","decrease in build queue time",{"value":919,"metric":920},"3,000 hours","developer time saved per quarter",{"value":922,"metric":923},"17%","boost in developer happiness scores","Agoda is a digital travel platform — and keeping its developers happy and productive has been a critical part of its growth.","Agoda, now part of Booking Holdings (Nasdaq:BKNG), helps users see the world for less with its value deals on a global network of 3.6 million hotels and holiday properties, along with reservations for things like flights, airport transfers, and activities. Agoda.com and the Agoda mobile app are available in 39 languages and supported by 24/7 customer support.",[927],{"quoteText":928,"author":929,"authorTitle":930,"authorCompany":894},"Dealing with our sprawling toolchain was a real nightmare for our developers. Consolidating on GitLab allowed us to give our software development team a better experience, and they are a lot happier now.","Nadav Robas","DevOps & DevSecOps Manager",[932,934,937,940,943,946],{"text":933},"Headquartered in Singapore, Agoda employs more than 6,600 staff in 31 markets. The company is dedicated to leveraging best-in-class technology to make travel easier. This means Agoda’s software development teams need to move quickly, collaborate efficiently, and ensure the apps they’re building are secure for customers worldwide.\n\nWith GitLab, Agoda has been able to consolidate various point solutions, cut costs, and boost security — all while keeping developers happier than ever, whether they’re building a mobile app or rolling out support to a new language.",{"header":935,"text":936},"Trouble with the toolchain and speed","Before migrating to GitLab’s end-to-end DevSecOps platform, Agoda had to deal with a complicated toolchain of at least nine tools. The mix of tools — and the need to integrate and support them — had become a time-consuming problem for the company’s six software DevOps teams, which total approximately 50 people. And no one on the team was skilled enough in every single tool. If one or two specific tool experts were out, then the team was at a loss for using that capability.\n\n“The everyday life of one of our developers was spread across many different services,” says Nadav Robas, DevOps & DevSecOps manager at Agoda. “We were spending so much time chasing upgrades and security patches, and we had issues maintaining so many service level agreements for all the tools. The teams were so busy just maintaining back then that it was really a nightmare.”\n\nNadav notes that Agoda’s troublesome toolchain was slowing their time to market, and their onboarding speed, along with creating governance and compliance challenges. And slow is a key problem for software development and for the overall business.\n\nOn top of that, Nadav says they also were looking to cut costs, and increase software quality and security.\n\nIt was a long list of problems to solve and advantages to find. Agoda’s tech managers knew they needed a DevSecOps platform to take on these challenges. And they knew GitLab was the one they needed.",{"header":938,"text":939},"Why choose GitLab ","“I was looking to free up the hands of my DevOps engineers from having to do everyday maintenance work, maintaining uptime, and learning domain knowledge,” says Nadav. “I didn’t want them to be experts in individual tools. Instead, I wanted them to focus on the things that actually matter – how we produce code, how we properly deploy code. We could do that with a platform.”\n\nOnce Nadav and his teammates decided to go with a single DevSecOps platform, going with GitLab was an easy choice. Actually, he says it was their only choice.\n\n“What other tool would I have even considered?” he asks, noting they started with GitLab Premium and then moved to GiltLab Ultimate. “Honestly speaking, there aren’t a lot of choices in the industry. Some of them are not mature enough to be something I would consider pitching to my leadership. Some might be well-known but aren’t easy to maintain in an on-premises environment. They just aren’t scalable enough. There was zero chance they would work for us.”\n\nAnd by going with GitLab, Agoda engineers — who work mostly on-premises but also use a mix of Amazon Web Services and Google Cloud Platform — were able to use GitLab’s Kubernetes executor to replace virtual machine-based Docker Machine runners with Kubernetes. The transition, which was fast and efficient thanks to GitLab, ultimately cut startup time, and gave them faster upgrades and recreations, better monitoring, and autohealing, as well as autoscaling.",{"header":941,"text":942},"Reducing the toolchain, increasing happiness, saving money","Since starting their GitLab adoption two years ago, Agoda has completely replaced a few tools with GitLab. Now they are in the process of replacing any remaining security tools. “I think there will be a huge gain in moving to GitLab,” says Nadav. “It will greatly benefit productivity and our developer happiness.”\n\nNadav says he’d initially been anxious about moving away from tools they had used in the past, thinking developers might push back about giving up something they were familiar with. However, the company’s bi-quarterly employee survey, which focuses on tool satisfaction, proved him wrong. As soon as the DevSecOps teams began to get past the learning curve, happiness scores began to climb and now GitLab, still in the full adoption process, has the second highest score of any tool Agoda uses.\n\n“I was concerned at the beginning, even though I knew it was a great product,” he adds. “But they really love it. We can clearly see that they love it. We wanted to increase developer happiness and we did. GitLab gets a score of more than four out of five, and that’s really, really amazing. And you know how tough tech people can be when it comes to rating something.”\n\nAlong with making developers happier, reducing the toolchain is saving Agoda a considerable amount of money per year in licensing fees, support and maintenance, according to Nadav.",{"header":944,"text":945},"Boosting security","Using GitLab’s single application, Agoda has been able to set up and enforce security policies and shift security to earlier in the development lifecycle. Without a string of security tools to integrate and manage, there’s no more security tool sprawl, eliminating related complications, expenses, and missteps.\n\n“In terms of expenses alone, it’s huge. It’s very cost effective,” says Nadav. “And the platform’s security features are efficient in that they cover everything I’m looking for. Now I have a single source of truth for governance, compliance, and security audits. I also have traceability from artifact to code commit.”",{"header":947,"text":948},"Continued benefits with GitLab","“GitLab has provided our developers with a single pane of glass they can use to see all the processes of the software development lifecycle without jumping back and forth from one tool to another,” says Nadav. “We wanted to consolidate all our services into a single platform and we did. We’re more productive, more secure, and our developers are having a better experience.”\n\nMoving ahead, Agoda is gearing up to use artificial intelligence features in the GitLab DevSecOps Platform to further propel their software development and their security.\n\n\"We're excited about the AI-assisted features from GitLab, not only for coding, but through the whole software development lifecycle, as aligned with GitLab’s vision,” says Nadav, noting they’ve demoed GitLab’s AI features. “While testing other DevOps AI features on the market, we have experienced an increase in coding velocity, but we have not yet seen an increase in quality. We're really looking forward to the solution GitLab will provide. We're keen to adopt it at Agoda.\"\n\nHe also notes that Agoda will continue to consolidate their toolchain and begin to use the analysis features inside GitLab’s platform. And he’s also looking forward to providing their developers the ability to spin up their own development environments, which he expects will improve developers’ experience and enable them to more quickly produce high-quality code.",{"template":950,"size":44,"region":110,"industry":91},"CaseStudy","content:en-us:customers:agoda.yml",{"_path":953,"content":954,"config":1007,"_id":1008},"/en-us/customers/airbus",{"name":955,"logo":956,"hero":957,"heroImage":958,"benefits":959,"industry":972,"employeeCount":973,"location":974,"solution":975,"stats":976,"headline":986,"summary":987,"quotes":988,"content":994},"Airbus","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745517924/so0ww4opgvvq7lgaiok0.png","Airbus takes flight with GitLab, releasing features 144x faster","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518408/vvs6nkyuic5grlrryeki.jpg",[960,964,968],{"metric":961,"config":962},"One unified workflow",{"icon":963},"GitlabRelease",{"metric":965,"config":966},"Improved code quality",{"icon":967},"Devsecops",{"metric":969,"config":970},"Faster releases",{"icon":971},"SpeedAlt","Aerospace","130,000","Worldwide","GitLab Premium",[977,980,983],{"value":978,"metric":979},"10,000","merge requests per year on average",{"value":981,"metric":982},"425%","project growth in 5 years",{"value":984,"metric":985},"144x","faster feature releases","Airbus Intelligence is a global leader in the geospatial industry that needed a platform for effective collaboration.","With GitLab's single-application continuous integration (CI), Airbus Intelligence has improved their workflow and code quality.\n",[989],{"quoteText":990,"author":991,"authorTitle":992,"authorCompany":993},"It’s simple. All teams operate around this one tool. Instantly, that made communication easier. We wouldn’t be where we are today if we didn’t have GitLab in our stack\n","Logan Weber","Software Automation Engineer","Airbus Defense and Space, Intelligence",[995,998,1001,1004],{"header":996,"text":997},"A global pioneer in aerospace","[Airbus Intelligence](https://www.intelligence-airbusds.com/) is a leading provider of commercial satellite imagery and premium geospatial data services as well as innovative defence solutions. The company's products and services support decision makers worldwide to increase security, optimise mission planning, boost performance, improve management of natural resources, and protect the environment.\n",{"header":999,"text":1000},"Adopt a better developer workflow","As a multinational corporation, Airbus Intelligence needs tools that can help their team collaborate and work more efficiently across the globe. The Intelligence business wanted to avoid the common challenges of many global companies: distributed teams and disconnected toolchains that cause workflow inefficiency and slow production. An improved workflow that could break through these challenges, make teams more efficient, and foster communication was a high priority. Logan Weber is a software automation engineer at the Web Factory. Finding a better developer workflow was one of his core missions, and the Web Factory’s agility makes the team an ideal testing ground for new tools and technologies. For Weber, it was important that any tools they adopt share a similar dedication to innovation. “We’re in the midst of a digital transformation,” Weber said. “We want to join forces with partners who know what they’re doing and can keep up with us.”\n\nOne of the Web Factory team’s big challenges was that their processes just weren’t efficient enough, which led to delayed releases and lost time in development. Developers could spend at least a full day on the production setup, and too much time was being spent on simple tasks that should have been automated. Developers were frustrated with these manual and lengthy processes that stopped them from focusing on code. With a new tool the Web Factory team also hoped to avoid communication breakdowns between teams. After spending time on the production setup, developers would sometimes realise that the final product didn’t correspond to the initial request, which would then lead to additional efforts. “We’d have to create a bug to modify this error. But it wasn’t a bug, it was just a lack of communication,” Weber explained.\n\nThe Web Factory team tested several tools in the search for the right developer workflow. Because the Web Factory team already used Jira, they decided to test other Atlassian products, such as Bitbucket for version control and Bamboo for CI. Unfortunately, Bitbucket and Bamboo didn’t offer a user-friendly experience, and both tools lacked some of the functionalities for their needs. The Web Factory team used Jenkins on old projects, but found it too complicated to maintain. They also wanted to be able to store their deployment script processes as code.\n",{"header":1002,"text":1003},"A unified GitLab workflow","“There was a bit of anything and everything, but we just couldn’t find what we were looking for,” Weber said. After trying other tools, the Web Factory team chose GitLab because it offers several advantages over the other tools tested. Not only does GitLab offer version control and project management capabilities, it also provides best-in-class CI — all in a single application. The Web Factory uses a Scrum methodology with two-week sprints. Developers create a user story in Jira, and once they’re ready to work on it, they create an issue in GitLab. Once teams have finished gathering information and collaborating in issues, they create a merge request (MR) which will trigger a development branch. When developers are ready, they can ask other developers to review their code. The code will go through CI testing and, once all tests are passed, the reviewer can merge this development branch into the main branch. Because all of this goes through the MR, everyone can see the entire process from start to finish. And GitLab offered the team a way to store their deployment scripts as code using the `.gitlab-ci.yml` file — one of the team’s must-have features.\n\nFor developers, having security and vulnerability scans built into the integration testing was also very helpful. “What used to happen is we would touch one part of the code and it would break another part. Now, each time a developer pushes code, we can immediately identify problems,” Weber said. With issues and MRs, people across teams have a place to collaborate. With CI included, teams can view every project from start to finish, and this visibility has also removed the guesswork from deployments. Instead of relying on one person to manage a deployment because they were more involved or more knowledgeable about the specific project, anyone can deploy because they have the same visibility as everyone else.\n",{"header":1005,"text":1006},"Better code quality, improved collaboration, happy developers","The first success the Web Factory noticed after adopting GitLab was the improvement in code quality. GitLab CI’s built-in security testing meant that developers could now identify bugs and vulnerabilities before they reached production. With GitLab CI, the Web Factory team was also able to deploy more frequently and with confidence. Instead of spending a full day setting up for production and doing manual tests, those simple tasks are now automated. This allowed release time to go from 24 hours to just 10 minutes. Today, Weber estimates that 98% of releases happen on time and the remaining 2% happen only a few hours later — a vast improvement from before.\n\nCollaboration improved because everyone can communicate in one place. Now, any technical stakeholder knows what’s being worked on, where everything is in the process, and developers know where to find the information they need to do their jobs. Developers, designers, security, and operations teams all have a place in the tool. While the improvements in code quality, cycle times, and communication were expected, there were also some unexpected benefits to adopting GitLab that were pleasant surprises for Weber and the Web Factory team: happier developers.\n\nFor one, GitLab CI took the stress out of deployments. “When someone went on vacation, it could be hell,” Weber laughed. And with better automation, developers can now focus on upgrades, technically demanding tasks, and updates. What else can developers do with this newfound free time? “We can create features!” Weber said. “We create and improve features for applications, and there just wasn’t any time for that before. We have 17 applications, and now developers can stay focused on the important things.”\n\nHappier developers also had a positive impact on recruitment. “[The Web Factory] had a hard time recruiting developers previously, but now that GitLab is a part of the tech stack, we’re receiving more applications from more experienced developers,” Weber explained. When developers can focus on their jobs, attracting other talented developers becomes easier. For Weber, adopting GitLab changed the entire development process for the better. The Web Factory team has been using GitLab for three years now, and Weber is a GitLab Hero who regularly shares his experience and expertise with others. If his team hadn’t adopted GitLab, he doesn’t think they would be as efficient. “We’d still have long processes, long periods of development, and less and less motivated developers who no longer like the projects they are working on and end up leaving,” Weber summarizes.\n",{"template":950,"size":44,"region":102,"industry":87},"content:en-us:customers:airbus.yml",{"_path":1010,"content":1011,"config":1065,"_id":1066},"/en-us/customers/airwallex",{"name":1012,"logo":1013,"hero":1014,"heroImage":1015,"benefits":1016,"industry":69,"employeeCount":1028,"location":912,"solution":975,"stats":1029,"headline":1039,"summary":1040,"quotes":1041,"content":1046},"Airwallex","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745517924/lfmipv3rommbm4gv9mug.png"," Global fintech company Airwallex meets customer needs faster with GitLab","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518409/ojiuwrdtjfpbllmt5oso.jpg",[1017,1021,1025],{"metric":1018,"config":1019},"Increased productivity",{"icon":1020},"Benefit",{"metric":1022,"config":1023},"Simplified toolchain",{"icon":1024},"Build",{"metric":1026,"config":1027},"Accelerated development",{"icon":902},"1,400+",[1030,1033,1036],{"value":1031,"metric":1032},"8x","faster deployments",{"value":1034,"metric":1035},"95%","of services moved to GitLab since 2019",{"value":1037,"metric":1038},"4x","faster feature delivery","Airwallex, a global financial platform, uses GitLab’s AI-powered, end-to-end DevSecOps platform to expand its business and meet customer requests faster, outmaneuvering competitors.","[Airwallex](https://www.airwallex.com/) is a leading global financial platform for modern businesses, offering trusted solutions to manage everything from payments, to treasury and spend management, and embedded finance. Founded in Melbourne, Airwallex supports more than 100,000 businesses around the world, and is trusted by brands like Brex, Rippling, Navan, Qantas, and SHEIN.",[1042],{"quoteText":1043,"author":1044,"authorTitle":1045,"authorCompany":1012},"Making sure that we spend our money wisely is very, very important. GitLab allowed us to reduce our costs and centralize our work in one place. It’s been money well spent.","Andy Chow","Technology Chief of Staff",[1047,1050,1053,1056,1059,1062],{"header":1048,"text":1049},"Beating competitors to win a new customer","Airwallex runs a financial platform that has become a global economic infrastructure, supporting organizations of all sizes by offering multi-currency business accounts, local and international transfers, and foreign currency exchanges. Building its customer base is critical for the young company, so when executives had a chance to bring on a leading airline carrier as a high-profile customer in 2022, they were under pressure to prove they could meet the airline’s needs in order to gain its business. That meant providing the company with a set of software features [better and faster](https://about.gitlab.com/blog/best-practices-leading-orgs-to-release-software-faster/) than their competitors could. With the help of the GitLab DevSecOps Platform, that’s exactly what they did. This leading airline now is an Airwallex customer.\n\n“To win that customer’s business, we actually had to build quite a bit of services to deliver features that they wanted,” says Andy Chow, technology chief of staff at Airwallex. “They had a lot of requirements, so there was a lot of work we had to do, a lot of new features to build. The DevSecOps platform gave our software development teams the ability to [collaborate](https://about.gitlab.com/blog/5-ways-collaboration-boosts-productivity-and-your-career/) and to iterate quickly to get it all done.”\n\nAs part of its partnership with Airwallex, the airline’s data-driven business arm, which powers customer and partner fidelity, worked with the tech company to launch a global payments platform designed to make international business payments cost-effective, simple and rewarding. It initially launched to more than 350,000 small- and medium-size businesses.\n\n“GitLab enabled us to prove ourselves to this customer on a tight deadline and that was critical,” says Chow.",{"header":1051,"text":1052},"Partnering with Google Cloud and GitLab","A young company, Airwallex has been looking to grow its user base and become an even bigger player in the market. To help them do just that, they began working with Google Cloud to deliver high-availability services Airwallex needs to support a 24-hour-a-day business. By using Google Cloud and the GitLab DevSecOps Platform, the fintech company has the tools it needs to create and run a reliable and secure IT infrastructure and a well-established international network.\n\nFor instance, with the GitLab CI/CD pipeline running on and integrating with Google’s global cloud platform, Airwallex has seamless support for various services, like international money transfers. And running GitLab on the Google Kubernetes Engine provides the fintech company with scalability and reliability.\n\n“We had to find platforms that could support our ambitions. GitLab and Google Cloud make a very good pair for that,” says Chow. “Thanks to Airwallex's partnership with these two platforms, we have been able to develop a payment infrastructure that is scalable, enhances our performance, and provides a seamless user experience. And the collaboration is ongoing and continues to prioritize innovative solutions, security, and user satisfaction. The partnership meets our business needs.”\n\nAmitabh Jacob, Google Cloud's director of APAC Technology & ISV Partnerships, expressed enthusiasm about deepening ties with GitLab to offer robust, end-to-end software supply chain security solutions for clients like Airwallex. \"In today's fast-paced environment, businesses need to speed up their software delivery without compromising security to stay ahead of the competition,\" says Jacob. \"I'm thrilled that our collaboration with GitLab enables us to meet this critical need for Airwallex.\"",{"header":1054,"text":1055},"Gaining speed with DevSecOps","When it comes to using an end-to-end DevSecOps platform, Airwallex benefits because it enables more seamless collaboration between teams, which allows for the company to increase delivery speed while also being more cost efficient.\n\nPart of what is speeding development and deployment is the testing [automation features](https://about.gitlab.com/blog/how-automation-is-making-devops-pros-jobs-easier/) built into GitLab. These capabilities generally mean 30 to 40 minutes less hands-on time per task for the development and deployment teams, according to Cathy He, engineering manager at Airwallex. When you multiply that by hundreds of engineers and projects, that is a lot of time saved.\n\n“For the business, it's important we have GitLab,” says He. “When we are able to tell a customer we can deliver faster than one of our competitors can, they’re far more likely to sign up with us. Time to market is critical to sales and it makes our customers happier.”",{"header":1057,"text":1058},"Taming a complex toolchain","Before adopting GitLab’s platform in 2019, Airwallex had more than a dozen DevOps tools in its toolchain, including GitHub, Jenkins, Spinnaker, Sonatype, New Relic, and Vault. It was a [lengthy toolchain](https://about.gitlab.com/blog/too-many-toolchains-a-devops-platform-migration-is-the-answer/) that resulted in cumbersome workflows and a lot of maintenance. Chow notes that a basic job like handling version updates became repetitive, time-intensive and difficult to wrangle when the update had to be done on multiple tools.\n\n“We couldn’t just update something once and be done,” he says. “People had to do the same thing over and over again. Having one platform to work with and update just makes sense.”\n\nAirwallex is moving to fully replace its code repository and CI/CD systems with GitLab’s platform, and they’re well on their way to meeting that goal. In five months, the software development teams were able to complete the migration from GitHub to GitLab. Over a longer period of time, they were then able to drop Jenkins and Spinnaker. Now they’re looking to let go of package and artifact management tools next.\n\nCutting down the toolchain was a way to better manage costs for Airwallex, especially at a time of rapid growth for the company. “Using GitLab makes a lot of sense because now we’re not paying for other services that can be handled on the one platform. We are reducing our costs, while centralizing our work in one place,” says Chow.",{"header":1060,"text":1061},"Healing a fractured environment","Having a complex toolchain wasn’t just costing Airwallex money and efficiency. It was creating a fractured development environment that was impeding collaboration, slowing production, and scattering repositories and templates across tools, making them hard to find and often forgotten or lost.\n\n“Before we moved to GitLab, everything was split up so it was difficult for developers to find anything they needed,” says Chow. “People just chose the tools they were familiar with. That made it difficult for people to work together, isolating teams. It got really messy really quickly in that fractured environment. We needed to bring everyone together.”\n\nSince fixing that, Airwallex has been able to:\n* Improve collaboration\n* Increase production speed\n* Make repositories more easily discoverable\n* Provide team members and executives with visibility into projects throughout the software development lifecycle\n* Onboard engineers and developers more easily and quickly because they don’t have to learn multiple tools\n",{"header":1063,"text":1064},"Building with AI","Now Airwallex is looking to use GitLab’s AI features, like [GitLab Duo Code Suggestions](https://about.gitlab.com/solutions/code-suggestions/), which uses generative AI to recommend code during software development. Code Suggestions enables developers to complete an entire line of code with one keystroke, fill in boilerplate code, or generate tests.\n\n“I think it will change how people write code,” says Chow. “But we’re also excited for all the ways GitLab is using AI beyond code suggestions. We’re looking at even more automation, reviews, configurations, test generation, bug finding, and even offloading operational work. I’m thinking AI can help us reduce our workload.”\n\nUsing the GitLab platform gives Airwallex capabilities the company simply didn’t have before and its DevSecOps teams are looking to continue with that. “GitLab brings us a good balance between velocity and quality,” says Chow. “When we deploy, we’re doing it with a lot of confidence.”",{"template":950,"size":40,"region":110,"industry":71},"content:en-us:customers:airwallex.yml",{"_path":4,"content":1068,"_id":122},[1069,1075,1127],{"componentName":13,"componentContent":1070},{"crumbs":1071},[1072,1074],{"title":17,"config":1073},{"href":19},{"title":21},{"componentName":23,"componentContent":1076},{"title":25,"filters":1077,"cardButtonText":117,"zeroStateTitle":118,"zeroStateDescription":119},[1078,1089,1114],{"options":1079,"config":1088},[1080,1082,1084,1086],{"label":30,"config":1081},{"id":32},{"label":34,"config":1083},{"id":36},{"label":38,"config":1085},{"id":40},{"label":42,"config":1087},{"id":44},{"name":46},{"options":1090,"config":1113},[1091,1093,1095,1097,1099,1101,1103,1105,1107,1109,1111],{"label":50,"config":1092},{"id":32},{"label":53,"config":1094},{"id":55},{"label":57,"config":1096},{"id":59},{"label":61,"config":1098},{"id":63},{"label":65,"config":1100},{"id":67},{"label":69,"config":1102},{"id":71},{"label":73,"config":1104},{"id":75},{"label":77,"config":1106},{"id":79},{"label":81,"config":1108},{"id":83},{"label":85,"config":1110},{"id":87},{"label":89,"config":1112},{"id":91},{"name":93},{"options":1115,"config":1126},[1116,1118,1120,1122,1124],{"label":97,"config":1117},{"id":32},{"label":100,"config":1119},{"id":102},{"label":104,"config":1121},{"id":106},{"label":108,"config":1123},{"id":110},{"label":112,"config":1125},{"id":114},{"name":116},{"componentName":121},{"_path":1129,"content":1130,"config":1178,"_id":1179},"/en-us/customers/ally",{"name":1131,"logo":1132,"hero":1133,"heroImage":1134,"benefits":1135,"industry":69,"employeeCount":1146,"location":1147,"solution":913,"stats":1148,"headline":1158,"summary":1159,"quotes":1160,"content":1165},"Ally Financial","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745517925/djabsos2wgeqgstuzlbo.png","Ally Financial cuts pipeline outages and eases security scanning with GitLab","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518410/wrulri16viyn4kkm7qq1.jpg",[1136,1139,1143],{"metric":1137,"config":1138},"Toolchain consolidation",{"icon":902},{"metric":1140,"config":1141},"More efficient security",{"icon":1142},"SecureAlt2",{"metric":1144,"config":1145},"Fewer pipeline outages",{"icon":1024},"11,600","Detroit, Michigan",[1149,1152,1155],{"value":1150,"metric":1151},"100","hours less dev downtime/month",{"value":1153,"metric":1154},"55%","boost in deployment velocity",{"value":1156,"metric":1157},"$300k","yearly cost savings","Ally Financial has to meet its customer needs solely online, but using a time-consuming toolchain hurt DevOps efficiency and productivity. Adopting GitLab’s platform has changed that.","Ally Financial Inc. is a leading digital financial services company, the largest U.S. digital-only bank, and a leading auto lender. Ally Bank, the company's direct banking subsidiary, offers an array of deposit, personal lending, and mortgage products and services. Founded in 2009, Ally is focused on making banking simpler, straightforward, and accessible.",[1161],{"quoteText":1162,"author":1163,"authorTitle":1164,"authorCompany":1131},"At the heart of engineering excellence is DevSecOps. At the heart of DevSecOps is GitLab, which has made a remarkable difference for our business and our teams at Ally.","Nans Sivaram","Executive Director and CIO of Consumer, Commercial Banking & Invest",[1166,1169,1172,1175],{"header":1167,"text":1168},"Trouble with the toolchain","Since all of Ally’s customers interact with the financial institution only online, creating secure, reliable, and innovative software is critical to strengthening customer experiences and growing the company’s user base, while supporting the overall business as well. However, the company's DevOps toolchain was slowing deployment and causing outages in pipelines, which halted developers’ ability to work.\n\nAlly had several products in its toolchain that integrated with each other. A big part of the problem was that every time there was a version update to any of those tools, it would cause defects that broke the pipeline. Every time. “Across the board, each upgrade caused 100 hours of developer downtime every month,” says Ram Kothur, director of Enterprise DevOps and Cloud Engineering at Ally. “That caused issues with our velocity. Of course, every time there was downtime, our deployments dropped.”",{"header":1170,"text":1171},"Migrating to the GitLab DevSecOps Platform","Less than two years after beginning to use a DevOps toolchain, Ally Bank teams decided it was time to trade it in for an end-to-end platform. After researching several tools, they decided to go with GitLab’s DevSecOps Platform because it had more features than its competitors and Ally had developed a supportive relationship with GitLab team members, which made them feel confident about the adoption.\n\n“There was a lot of excitement for the migration because there were challenges with the resiliency of the toolchain,” says Kothur. “The developers were excited because this was going to make their lives easier with the simplicity and inclusivity of features in GitLab’s DevSecOps Platform. Team members were eager to get on board.”\n\nThe migration began in 2021. All the heavy lifting, according to Kothur, has happened in the last two years. To do that, they formed a small group that decided what applications would be migrated as a pilot program. “We moved some critical applications first,” said Kothur. “We wanted to tackle those so we could show everyone the benefits of the migration. And we showed them that the software they were creating didn’t change, but how they deployed it changed.\"\n\nToday, Ally has migrated most of their applications to GitLab, and is continuing to trim their toolchain.\n\nKothur notes that some Ally team members received training from GitLab. Then those people shared that training with other teams.\n\n“The GitLab support team was very helpful and is making our migration easier,” said Kothur. “When we had an issue, we were able to reach out to leadership and discuss it. Whenever there was a blocker, we had excellent support from GitLab. To add to that, GitLab documentation is awesome.”",{"header":1173,"text":1174},"Cutting outages and saving money","Ally is now halfway to the goal of eliminating its toolchain altogether, and is already saving about $300,000 a year in reduced developer downtime and tool costs. What’s more, Ally Bank used to deal with 20 pipeline outages annually, but in 2022 — just a year after beginning the migration to GitLab’s DevSecOps Platform — Ally only saw a total of two outages, according to Kothur. “We’re saving all of those hours we’d spent working on pipeline outages,” he adds. “We’re 50% of the way to getting rid of all of our other tools and already seeing great benefits.”\n\nThe applications Ally has migrated to GitLab are seeing, on average, a 50% improvement in deployment time. Also, with the DevSecOps platform making development easier and more efficient, developers now have more time to be innovative, implementing more features in the same timeframe.\n\nOn top of that increased efficiency, having security built into the DevSecOps platform means Ally has been able to reduce the consumption of its security tools by using GitLab. Now Ally is monitoring and testing security from the very beginning of the software lifecycle, when it’s easier and faster to fix any problems that arise. And that means better security. They’re also employing automation built into the DevSecOps platform to perform continual security scanning, making it more efficient to ensure their apps are secure. In short, GitLab is simplifying the company’s application security efforts.\n\n“It’s making it easier to be secure and compliant,” says Kothur. “Shifting security left and using the platform’s visibility over the entire process is significant for us. Instead of checking for security and compliance later in the software lifecycle when it takes more work to go back and fix any problems. Security is our top priority. This makes it easier. And not working so much on vulnerabilities makes development and deployment more streamlined.”",{"header":1176,"text":1177},"Critical partnership drives results","In recognition of the ongoing partnership between GitLab and Ally, this year GitLab was the recipient of Ally's inaugural Velocity with Quality Award, part of the financial institution's 2023 Technology Partner Awards Program. The honor is given to the supplier that best demonstrates excellent speed to market, responsiveness, and flexibility, allowing Ally to quickly deliver value to its customers.\n\n\"At the heart of engineering excellence is DevSecOps,” says Nans Sivaram, executive director and CIO of Consumer, Commercial Banking & Invest at Ally. “At the heart of DevSecOps is GitLab, which has made a remarkable difference for our business and our teams at Ally.\"\n\nGitLab’s award is one of five Ally is giving as part of its program, which is focused on shining a spotlight on third-party suppliers that have delivered outstanding service to the company.\n\n“We launched our first annual Ally Technology Partner Awards to recognize the critical vendor partners that contribute to our success, and we are blown away by the overwhelming interest,” says Sathish Muthukrishnan, chief information, data and digital officer for Ally Financial Inc. “Each winner showcases the importance and value of superior execution, quality and partnership. We are thrilled to honor them through this awards program.”",{"template":950,"size":44,"region":102,"industry":71},"content:en-us:customers:ally.yml",{"_path":1181,"content":1182,"config":1226,"_id":1227},"/en-us/customers/alteryx",{"name":1183,"logo":1184,"hero":1185,"heroImage":1186,"benefits":1187,"industry":89,"employeeCount":1196,"location":1197,"solution":913,"stats":1198,"headline":1208,"summary":1209,"content":1210},"Alteryx","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745517954/cuyme0dq5mpdmjulmddr.svg","Removing multi-tool barriers to achieve 14 builds a day at Alteryx","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518428/n4ujp4vdkcwnlvz80gqt.jpg",[1188,1192],{"metric":1189,"config":1190},"Faster build times",{"icon":1191},"AccelerateThin",{"metric":1193,"config":1194},"Increased visibility",{"icon":1195},"Visibility","900+","Irvine, California",[1199,1202,1205],{"value":1200,"metric":1201},"10,464","commits since 2016",{"value":1203,"metric":1204},"9x","daily releases",{"value":1206,"metric":1207},"769","projects using GitLab","Data science and analytics leader Alteryx needed a new toolset to modernize their software development lifecycle.","With GitLab, Alteryx has been able to improve the development experience and accelerate the organization's pace of deployment — all with a single tool.",[1211,1214,1217,1220,1223],{"header":1212,"text":1213},"Achieving the full potential of data","Alteryx offers an end-to-end analytics platform that empowers data analysts and scientists to break data barriers, deliver insights, and get to the answer faster. Organizations all over the world rely on Alteryx daily to deliver actionable insights. The end-to-end Alteryx analytics platform enables analysts and data scientists to discover, share and prep data, perform analysis, and deploy and manage analytic models.",{"header":1215,"text":1216},"Modernizing to improve the development experience","Alteryx knew their legacy system of using Subversion with Jenkins was not the optimal toolset to accomplish the goal of improving their software development lifecycle. At that time, the repository was more than 500 gigabytes and was filled with legacy code, making it difficult to manage.\n\nThey wanted to modernize the development experience to improve deployment and build pace. To achieve this they moved to Git, established an enterprise source code repository tool, and improved their continuous integration and delivery (CI/CD). They evaluated three tools, GitHub, Perforce, and GitLab, in this process.",{"header":1218,"text":1219},"Evaluating how to best achieve the goal","GitLab allowed Alteryx to truly have everything in one place and within one tool — one place for CI, CD, source code management, code reviews, and security scanning. Having everything in one place also made it easier for them to scale because teams can just be added to GitLab and have all the things that typically take them 3 or 4 months to get set up.",{"header":1221,"text":1222},"Success with a single application and double the anticipated users","Alteryx began with the Community Edition of GitLab in 2016 but quickly moved to the Enterprise Edition so they could scale. Teams soon realized the value of a single application to manage their work and they more than doubled their planned number of users in the first six months. Alteryx staff are inspired to use it because the CI is baked right into the repository, allowing developers to actively participate in the DevOps process.",{"header":1224,"text":1225},"Accelerating deployment with everything in one place","GitLab has allowed Alteryx to have code reviews, source control, continuous integration, and continuous deployment all tied together and speaking the same language. This capability allows each commit or merge request to get a code review, which wasn’t previously happening. That code review is tied to a deployment, which is tied to a URL and so on.\n\nThe team took a build that was running legacy systems and moved it to GitLab. This build took 3 hours on the Jenkins machine and it took 30 minutes to run on GitLab after it was going. Engineers can actually look at the build and understand what’s going on; they’re able to debug it and make it successful.",{"template":950,"size":40,"region":102,"industry":91},"content:en-us:customers:alteryx.yml",{"_path":1229,"content":1230,"config":1282,"_id":1283},"/en-us/customers/anchormen",{"name":1231,"logo":1232,"hero":1233,"heroImage":1234,"benefits":1235,"industry":89,"employeeCount":1248,"location":1249,"solution":1250,"stats":1251,"headline":1261,"summary":1262,"quotes":1263,"content":1268,"contributors":1281},"Anchormen","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745517956/ykqryyflfklln7nnlytg.svg","How GitLab CI/CD supports and accelerates innovation for Anchormen","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518429/yrpqpzdzdsgfagwij0v8.jpg",[1236,1240,1244],{"metric":1237,"config":1238},"Seamless Docker deployment",{"icon":1239},"PaperAirplane",{"metric":1241,"config":1242},"Easy-to-use interface",{"icon":1243},"GitlabMonitorAlt",{"metric":1245,"config":1246},"Cost effective",{"icon":1247},"PiggyBankAlt","70","Amsterdam and Groningen","GitLab Starter",[1252,1255,1258],{"value":1253,"metric":1254},"85%","Deployment time reduction",{"value":1256,"metric":1257},84,"Software projects in GitLab",{"value":1259,"metric":1260},"3.5x","Team growth","GitLab's intuitive interface and superior integration empowers Anchormen to deliver quality solutions on schedule.\n","Data engineering and AI consultancy, Anchormen, achieves great customer success, excellent workflow efficiency, and reliable continuous deployment with GitLab.\n",[1264],{"quoteText":1265,"author":1266,"authorTitle":1267,"authorCompany":1231}," GitLab has really helped us because we can work with a lot of people on projects, maintain the quality, make sure that everybody checks each other's work, and then deploy it on an infrastructure that doesn't bear any surprises because it just follows through the continuous deployment. It just follows wherever the project is going.","Jeroen Vlek","CTO",[1269,1272,1275,1278],{"header":1270,"text":1271},"Modern data engineering and AI consultancy","Anchormen is a machine learning, data science and engineering consultancy based in The Netherlands. \u003Ca href=\"https://anchormen.nl\" target=\"_blank\">Anchormen\u003C/a> builds and develops innovative data and AI solutions that give clients meaningful insights for their business. A lot of the data, AI, and ML solutions that Anchormen deploys require solid software engineering work.\n",{"header":1273,"text":1274},"Moving away from Jenkins","Anchormen was using Jenkins, but in 2015 the development teams decided that they needed a more professional workflow. Anchormen had an urgent need for merge requests and the processes in place didn’t support the collaborative workflows they needed to be effective. The teams were also using Rancher for some projects, but weren’t pleased with the updates and decided to adopt Kubernetes.\n\nBecause Anchormen caters to a variety of companies, quality collaboration with clients is essential for delivering excellent results. Anchormen focuses on data engineering, so they need to be able to work in an environment that is like a playground for customers to be able to play and innovate in as well.\n\nAnchormen required a tool that could [integrate with AWS](https://about.gitlab.com/partners/technology-partners/aws/){data-ga-name=\"aws\" data-ga-location=\"customers content\"}, Azure, Docker, Jira, and SonarQube. They also wanted to ensure that product delivery could happen seamlessly and on time. “We're not a software company that has one long-term project. Our typical project lasts between half a year and a year, and then we hand it over to the customer, with us taking a supporting role if necessary,” according to Jeroen Vlek, CTO of Anchormen.\n",{"header":1276,"text":1277},"Easy interface, integration, and source control","Anchormen adopted GitLab in 2015, and one of the big selling points was the easy and intuitive user interface. “It's easy to use, it's logical. If I'm looking for something in GitLab, I never have to Google it. I usually just find my way rather quickly through the interface. That's a big plus. That's not what every tool can say,” according to Vlek. “I really like that GitLab's build definitions are part of the project, so that's something that can evolve with the project as it should be.”\n\nAnchormen also liked the ability to deploy runners. Dockerized runners with any underlying software means that there are no dependencies. Every build is isolated. On top of that, Anchormen had SCM prior to adopting GitLab, but the platform added another, easier layer. “This is an added layer on top of version control. So, it makes everything a lot more manageable, and it really helps you control the quality of the work, which of course, version control by itself doesn't necessarily do,” Vlek added.\n",{"header":1279,"text":1280},"CI/CD ease, product improvement, customer satisfaction","Overall, development teams are happy with the GitLab adoption. In particular, teams appreciate the configurability and ease of integration with other tools. Teams can define their own integration and deployment builds through a GMO file in the repository and then they can configure from there. “What we also really like is the LDAP integration. We have it with our access directory which makes user management very simple. And then adding users to customer groups for example, is very straightforward,” Vlek said.\n\nAnchormen [integrates Jira with GitLab](https://about.gitlab.com/solutions/jira/){data-ga-name=\"jira\" data-ga-location=\"customers content\"}. Every commit message starts with a Jira ticket number, then Jira establishes the link between the ticket and the commits in GitLab. This integration works well for the teams because if there is any progress on the ticket, or if it’s a historical ticket, they can look back to see what happened and what work has already been done. This visibility has improved the workflow and developers appreciate the transparency it delivers.\n\nThe development teams use Azure and AWS integration with GitLab. They have Cloud Formation templates for AWS as part of the [CI/CD pipeline](https://about.gitlab.com/blog/guide-to-ci-cd-pipelines/){data-ga-name=\"CI/CD pipeline\" data-ga-location=\"customers content\"} so that the infrastructure follows GitFlow through GitLab. From there, GitLab automatically pushes the cloud formation templates to AWS to update the environment. Anchormen integrates SonarQube in the CI/CD pipeline for automatic code inspection.\n\nGitLab has transformed Anchormen’s workflow processes and they now have over 80 software projects within the platform. “I don't even know how we used to manage without it. I think around 2015, we had a small team of around 20 people, and now we're with 70 people. GitLab really helped us to structure the growth in both employees and projects,” Vlek said.\n\nAnchormen’s operational efficiency has increased with GitLab as a system in place and deployment time accelerating from 20 minutes down to just three. “You can really focus on the work. You don't need to think about all these other things, because once you've had GitLab set up, you have basically this safety net. GitLab protects you, and you can just really focus on the business logic. I would definitely say it improves operational efficiency,” Vlek added.\n\nThe product outcome has also accelerated with a consistent and enhanced workflow. “Because of this kind of seamless integration of tests and deployment, there's not a lot of room for human errors anymore. By greatly reducing that risk, you also really increase the quality of your projects,” Vlek said. Anchormen are consistent in keeping their “eyes on the horizon” for where they want a project to go, with a focus on delivering superior business value.\n\nSince working with GitLab, teams have been successful in exceeding customer expectations and reaching deadlines on time. “GitLab has really helped us, because we can work with a lot of people on the projects, maintain the quality, make sure that everybody checks each other's work, and then deploy it on a stable infrastructure which follows through the continuous deployment. It just follows wherever the project is going,” Vlek said.\n",null,{"template":950,"size":36,"region":106,"industry":91},"content:en-us:customers:anchormen.yml",{"_path":1285,"content":1286,"config":1340,"_id":1341},"/en-us/customers/anwb",{"name":1287,"logo":1288,"hero":1289,"heroImage":1290,"benefits":1291,"industry":1303,"employeeCount":1304,"location":1305,"solution":913,"stats":1306,"headline":1316,"summary":1317,"quotes":1318,"content":1327},"ANWB","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745517957/apmqenhyxka9eq7le8so.svg","From bicycles to connected driving","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518430/ksadrpsjen7hqvsn60sj.jpg",[1292,1296,1299],{"metric":1293,"config":1294},"Improved collaboration",{"icon":1295},"CollaborationAlt4",{"metric":1297,"config":1298},"Improved CI/CD",{"icon":902},{"metric":1300,"config":1301},"Increased team autonomy",{"icon":1302},"BulbBolt","Travel / Insurance","3,700","The Netherlands",[1307,1310,1313],{"value":1308,"metric":1309},"100%","of developer teams using GitLab",{"value":1311,"metric":1312},"322","projects",{"value":1314,"metric":1315},"57","groups","ANWB, the largest not-for-profit association in the Netherlands, needed a one-stop, modern toolchain to increase team autonomy and eliminate process isolation.","With GitLab, development teams at ANWB can more easily choose their own pipelines and their own processes instead of having to conform to a single way of working.",[1319,1323],{"quoteText":1320,"author":1321,"authorTitle":1322,"authorCompany":1287},"We had developers that thought, Why would we do something else? Jenkins is fine. But I think those people need to see GitLab first and see what the difference is because GitLab is so much more than Jenkins. The power of GitLab is you can do so much more and you can make everything so much easier to manage.","Michiel Crefcoeur","Frontend Build and Release Engineer",{"quoteText":1324,"author":1325,"authorTitle":1326,"authorCompany":1287},"We are just replacing these outdated tools bit by bit, doing it the agile way. We really wanted to replace Jenkins and immediately we saw that Stash was the first one to replace because it was logical to also host your Git repositories in GitLab, and now we have started looking at other tools (f.i. XL Deploy, Nexus) that we can replace with GitLab.","Ramon van de Velde","Product Owner Beheer | P&I Online",[1328,1331,1334,1337],{"header":1329,"text":1330},"Keeping the Netherlands rolling","What started as a small community of bike enthusiasts has grown into a full-service mobility provider over the past 135 years. The Royal Dutch Touring Club, or Algemene Nederlandse Wielrijdersbond (ANWB), was formed in 1883 when a few local cycling clubs merged. With the evolution of automobiles, the club shifted focus to roadside service. Now, in addition to roadside services, ANWB offers credit cards, car sales, bicycle maintenance, and travel services.\n\nSome of the club’s most popular services include route planning software for mobile devices and a connected car service that enables older cars to provide intelligence to drivers.",{"header":1332,"text":1333},"Replacing multiple tools and plugins with a unified toolset","At the beginning of 2018, the product and development teams decided to make a strategic change to improve their development process. At that time, they had multiple interconnected tooling and services. This environment was driven by developer and administrator’s knowledge and background and wasn’t easily maintained. System breakdowns required someone to manually look at what was going on. These prolonged outages prevented people from doing their jobs properly. The company operated with an attitude of  ”Okay, it’s working. Don’t touch. As long as we don’t touch it, everything will be fine.”\n\nThe toolchain consisted of some outdated tools including Jenkins version 1 as a build server, and Stash (now known as Bitbucket Server) as a Git repository server. For artifact hosting, ANWB was using Artifactory and Nexus.",{"header":1335,"text":1336},"Empowering developers with a one-stop, modern toolchain","ANWB wanted to increase team autonomy and obliterate process isolation. Previously, their teams were using pipelines that were pieced together with various plugins. Every once in a while, a plug-in would break after a Jenkins update. Because of this, pipelines were kept as simple as possible. Now with some process shifts and using GitLab, developers run their jobs in separate pipelines and can upgrade in their own time.\n\nGitLab has made it easier for ANWB to manage separate teams and their individualized projects and for teams to choose their own pipelines and their own processes. Having the ability to choose their own workflows prevents teams from having to conform to a single way of working.",{"header":1338,"text":1339},"Looking to the future and the potential of a multi-cloud environment","With sights set firmly on the future, the ANWB dev team is looking to migrate from outdated backend architecture to more of a cloud-centric framework. While the path to accomplishing this hasn’t been defined yet, they know GitLab is key to this next step.\n\n“What we see is that GitLab really helps in seeing what’s out there because of the integrations that GitLab already provides out-of-the-box,” Crefcoeur said. “Our company, ANWB, uses both AWS and Azure but our department is not making use of those services yet. What we are doing is we’re currently experimenting with Google Cloud platform to see what GitLab has to offer on that.”\n\nBecause of GitLab’s integrations with Knative, ANWB is exploring Google Cloud on Kubernetes.\n\n“We think that Kubernetes is the way to go and the integration with GitLab is really helping on that one. I think the findings are rather positive for now but we still have a long way to go because it’s pretty huge what you can do with all those new techniques,” van de Velde said.",{"template":950,"size":44,"region":106,"industry":83},"content:en-us:customers:anwb.yml",{"_path":1343,"config":1344,"content":1345,"_id":1403},"/en-us/customers/avalara",{"template":950,"region":102,"size":44,"industry":91},{"heroImage":1346,"employeeCount":1347,"summary":1348,"logo":1349,"name":1350,"headline":1351,"location":1352,"quotes":1353,"content":1358,"solution":975,"hero":1380,"benefits":1381,"industry":1392,"stats":1393},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1759179323/yzfh8dmwrmwzvji7y0rh.jpg","5,300","Avalara adopted GitLab Premium in 2019 to give their hundreds of DevSecOps employees a single platform to work on, enabling them to collaborate, share reusable components, and more efficiently secure their code. The transformation delivered significant results for Avalara, which has since dramatically increased its deployments, reduced issues, and strengthened customer trust.","https://res.cloudinary.com/about-gitlab-com/image/upload/v1759179283/fondsaofrbsq1ecbb24k.png","Avalara","Avalara Inc., a leading provider of tax compliance software that enables businesses to safely and efficiently navigate complex regulations, had assembled a diverse collection of tools and systems through years of acquisitions. The opportunity to enhance cohesion, visibility, and collaboration would enable the company to respond even more effectively to customer needs and accelerate client base expansion.\n","Durham, NC, USA",[1354],{"author":1355,"authorTitle":1356,"authorCompany":1350,"quoteText":1357},"Matt Buckley","Vice President of Engineering","Our business is to provide software as a service to all of our customers, so software is our business. Without the software we’re building with GitLab, we have no business.",[1359,1362,1365,1368,1371,1374,1377],{"text":1360,"header":1361},"A global organization headquartered in Durham, North Carolina, Avalara is a privately held company with 43,000 worldwide customers. Founded in 2004, it focuses on helping customers with sales tax calculation, filing, and remittance, enabling businesses of all sizes to manage complex tax requirements across multiple states and countries. With a core mission to make tax compliance less taxing, it is widely recognized as a leader in its market."," ",{"header":1363,"text":1364},"Scaling excellence: Optimizing for predictable delivery","Rachael Marshman, director of product management at Avalara, spotted an opportunity to strengthen customer relationships: providing more precise delivery timelines for software updates and new applications. The key was optimizing Avalara's existing development toolchain and standardizing the processes around it. \"When customers needed new functionality for compliance, we wanted to deliver confident timelines,\" Marshman says. \"Standardizing our processes would make us more predictable and efficient, freeing up engineering resources to focus on innovation rather than coordination — better for both our teams and customers.\" Working with Matt Buckley, vice president of engineering at Avalara, Marshman set out to unify their DevSecOps team on a single platform while implementing pipeline gates and security processes.\n\nOver more than 20 years of company growth, including numerous acquisitions, Avalara has accumulated various software development tools, such as Jenkins and GitHub. That approach worked for a while, but Marshman and Buckley knew they'd need a more comprehensive solution to power the next phase of Avalara's growth. To support their ambitious growth trajectory, their existing toolchain presented opportunities for optimization, such as:\n\n* **Opportunities to accelerate** cycle times for code reviews and merge requests\n* **Potential to automate and standardize** security processes for greater efficiency\n* **Scope to streamline** toolchain management and reduce complexity\n* **Ability to enhance** visibility into engineering productivity metrics\n* **Capacity to optimize** deployment processes and remove bottlenecks\n* **Potential to accelerate** feature delivery and reduce time-to-market\n\nThese optimization opportunities represented significant potential for efficiency gains that could enhance the organization's ability to exceed customer expectations and strengthen their competitive position in the market.\n\n“We were deploying approximately 30 times a year and saw significant room for improvement,\" says Marshman. \"Our release cycles typically ran monthly, though our thorough integration and testing processes sometimes extended timelines to ensure quality. “We recognized that streamlining these processes could increase both our deployment frequency and consistency while maintaining our high standards.”\nBuckley also notes that since Avalara’s systems are integrated with their clients’ systems, a deployment problem could affect the customers as well.\n\n\"Precision is absolutely critical in our industry,\" says Buckley. \"When you're managing tax calculations that impact billions of dollars in transactions, accuracy isn't just important — it's fundamental to our customers' success. This environment requires robust deployment processes and multiple validation layers to maintain the reliability our customers depend on.\"\n\nRecognizing this opportunity for optimization, Avalara strategically selected a single DevSecOps platform.",{"header":1366,"text":1367},"Adopting GitLab’s single platform drives transformation","The company strategically selected GitLab, consolidating Jenkins and GitHub into a single, end-to-end DevSecOps platform. This strategic decision launched a major transformation for Avalara — one that unified developers from around the globe on a shared platform, streamlined manual processes through automation, and standardized security controls and quality gates across all projects.\n\n“With GitLab’s CI/CD pipelines, it’s been transformative,” says Buckley. “GitLab has been transformational in enabling our current capabilities. We've evolved from monthly deployments to deploying Monday through Thursday, with exceptional reliability. Our operations run smoothly with minimal disruption. GitLab's unified platform made this level of efficiency and scale possible.”\n\nToday, the organization has unified all builds and deployments through GitLab pipelines, seamlessly integrating everything from commit runs of unit tests to automatic code reviews within GitLab. \"GitLab pipelines unlocked comprehensive capabilities, including automated quality gates and enhanced visibility,\" says Buckley. \"I can access a unified dashboard that shows real-time system performance, trends, and optimization opportunities. This level of insight enables continuous improvement across all our processes. Marshman highlights the significant performance improvements since adopting GitLab.\n\nMerge request cycle times have been optimized from four weeks to just a few hours. And Seattle-based [Uplevel](https://uplevelteam.com/), an engineering metrics and insights company, reported that since adopting GitLab, Avalara has experienced a 1,100% improvement in deployment frequency, and deployment problems have been reduced by 90%. Buckley notes that these metrics provide the ability to quantify the impact of the changes they’ve made.\n\n“We can easily say that we went from maybe 30 deployments a year to easily 30 a month,” says Buckley, who used Uplevel's engineering intelligence platform to establish baseline performance metrics before the transformation. “That’s a huge change. I was specifically looking for metrics that would give me feedback on whether things were working well and if our efficacy was improving. The Uplevel metrics help me see how well this really is going.”\n\nOne signpost of improvement for Marshman is that she can now give customers target dates for when updates and new software will launch.\n\n“Now I can give customers a launch date with confidence,” she adds. “With everyone working in the same environment, we're able to move quickly. We're able to deploy the same day if we need to. And when you're a compliance business, that’s critical.”",{"header":1369,"text":1370},"DevSecOps fuels AvaTax, Avalara's core product","With GitLab’s end-to-end platform, Avalara has been enhancing and managing its flagship piece of software — AvaTax. A cornerstone of the organization’s offerings, it is aimed at replacing manual, complex, and error-prone tax processes, enabling real-time tax calculation for the vast majority of their customers' transactions. AvaTax is not just one of their products: It is the central nervous system of Avalara's tax compliance automation platform.\n\n“We brought everything onto GitLab, so, of course, our most important piece of software is run using that platform,” says Buckley. “GitLab has made it easier to build it out, to integrate, to secure it, and to keep giving our customers what they need. The fact that we have one, consistent platform that everyone works on has made everything easier.\n\n“AvaTax is our business,” he adds. “Without it, we have no business.”\n",{"header":1372,"text":1373},"Breaking silos and sharing code to boost innovation","Both Buckley and Marshman note that one of the core reasons their DevSecOps teams can keep software like AvaTax updated so smoothly and efficiently is because of their teams’ new [ability to collaborate](https://about.gitlab.com/blog/5-ways-collaboration-boosts-productivity-and-your-career/). Beyond the platform's enhanced visibility, the truly transformative element is their ability to share secured, well-built code components. This enables developers to leverage existing solutions and focus their expertise on innovation rather than rebuilding functionality that already exists across the organization.\n\nIt also means there is more consistency in the organization’s software.\n\n“GitLab transformed our collaboration model,\" says Marshman. \"Previously, teams operated more independently, but now they can easily discover and leverage existing components across the organization. Now, since they’re all engaged in building and deploying software into the same system, it’s easy and natural to [share code across teams](https://about.gitlab.com/blog/keeping-your-development-dry/). It means teams can concentrate on the overall solution, instead of every single piece of it, so they can be more innovative.”\n\nUsing a shared repository on the platform, each team is connected, enabling them to contribute reusable code components for needed components and even update pieces of shared code. \"GitLab's centralized approach has unified our development resources,\" says Marshman. “Now, it’s much easier to find what you need, so a lot more is being reused. And our developers like contributing to other projects. They like being able to say, ‘I found a way to make this better, so I updated it.’”\n\nBuckley adds that the ability to collaborate and share work also means developers are less stressed and they’re happier.",{"header":1375,"text":1376},"Automated security fortifies trust and compliance","Because Avalara processes and stores sensitive financial information, security is critical. Buckley points out that GitLab has increased their confidence in the security of their code by allowing teams to share and reuse code that has been tested and is known to be secure.\n“As a company that is responsible for protecting our clients’ data, we have to be the best in the industry in terms of security and our ability to keep things running,\" says Buckley. Because we now can, for example, have standardized processes, quality gates in the pipelines, and easily reuse secure software components, we can avoid downstream problems.”\nBefore using GitLab, there was an opportunity to standardize controls and processes.\n“We needed automated testing and we just didn’t have it before,” says Buckley. “Automating security scans and processes, along with automating documentation, has strengthened our compliance posture and even customer trust.”\nWith GitLab, Avalara can consistently implement controls over all of their source code and deployment mechanisms. They’re also able to track who is making changes to code, along with why and when. And they can automatically track what was deployed and what was included in MRs.",{"header":1378,"text":1379},"Unlocking explosive business growth with GitLab","Automating security and documentation has strengthened Avalara's operational excellence and competitive position. It’s also allowing them to do more with the same number of team members, and that is enabling them to grow their customer base significantly.\n\n“Since the adoption, we’ve been able to scale, and our customer base has grown,” says Buckley. “We’re also in more regions and more industries. We have tens of thousands of customers, and they have confidence in the software being shipped. That’s critically important.”\n\nMarshman also says Avalara is strengthening its competitive stance in the market.\n\n“When we had a lot of technical debt and we were slow to respond, we simply couldn’t move quickly, but those days are over,” she adds. “With GitLab, our increased deployment cadence is putting us back at the top spot in the market where we’d historically been.”\n\nBuckley adds that Avalara is already implementing advanced technologies to further enhance their development processes. “We're currently using agentic AI internally,” says Buckley. “We build and deploy our own agentic systems and some of those we have co-opted and used in our deployment and software delivery processes as well.”\n\nMarshman was clear that Avalara is all in with GitLab as they continue to grow and scale — both with their workflows and with their customer base. “GitLab is the only solution that we'll use now for deploying our products,” says Marshman. “We will grow and scale with GitLab in mind, as it helps us organize all of our code bases, streamline those processes, and deploy effectively.”","Global tax software giant Avalara powers customer growth with GitLab",[1382,1386,1389],{"metric":1383,"config":1384},"Improved developer productivity",{"icon":1385},"UserCollaboration",{"metric":1387,"config":1388},"More efficient feature delivery",{"icon":902},{"metric":1390,"config":1391},"Improved code sharing",{"icon":1295},"Software",[1394,1397,1400],{"metric":1395,"value":1396},"reduction in MR time","85%+",{"metric":1398,"value":1399},"improvement in deployment frequency","1,100%",{"metric":1401,"value":1402},"reduction in deployment problems","90%","content:en-us:customers:avalara.yml",{"_path":1405,"content":1406,"config":1457,"_id":1458},"/en-us/customers/axway",{"name":1407,"logo":1408,"hero":1409,"heroImage":1410,"benefits":1411,"industry":1424,"employeeCount":1425,"location":1426,"solution":975,"stats":1427,"headline":1437,"summary":1438,"quotes":1439,"content":1444,"contributors":1281},"Axway","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745517959/vffcdibbifhh2vc9kpv2.svg","Axway realizes a 26x faster release cycle by switching from Subversion to GitLab","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518431/ovojdqeqpyuvrcr4cvl2.png",[1412,1416,1420],{"metric":1413,"config":1414},"On-premises solution",{"icon":1415},"UserLaptop",{"metric":1417,"config":1418},"World-class integrations",{"icon":1419},"Bulb",{"metric":1421,"config":1422},"Simplified administration",{"icon":1423},"Cogs","Computer software","1,001 - 5,000","Paris, France and Phoenix, Arizona",[1428,1431,1434],{"value":1429,"metric":1430},"600+","developers onboarded",{"value":1432,"metric":1433},"3,000","projects migrated",{"value":1435,"metric":1436},"26x","faster release cycles","International information technology company Axway was looking for a way to improve collaboration among globally distributed software development teams.","With GitLab, Axway now has a single solution for source code management for the entire company, fostering collaboration between development and operations teams.\n",[1440],{"quoteText":1441,"author":1442,"authorTitle":1443,"authorCompany":1407},"GitLab offered the most advanced feature set on the market.\n","Eric Labourdette","Head of Global R&D Engineering Services",[1445,1448,1451,1454],{"header":1446,"text":1447},"Change agents tackling the toughest data challenges","Inventors of the world’s first business rules engine, Règle du Jeu (RDJ), Axway has been helping businesses unlock the value of their data for nearly two decades. Their cloud-enabled data integration and engagement platform, Axway AMPLIFY, orchestrates cohesive customer experience networks, enabling organizations to generate the speed, power, and agility required to meet skyrocketing customer expectations.\n\nAs change agents for data integration, keeping pace and adapting quickly to today’s fast and fluid digital customer is mission critical for Axway’s research and development (R&D) engineering services teams.",{"header":1449,"text":1450},"Legacy source code management and toolchain complexity limits worldwide collaboration","Serving over 11,000 companies spanning 100 countries, Axway’s R&D engineering services teams are spread across continents and time zones. With the teams working from nine different sites and using Subversion (SVN) on local servers for source control management (SCM), collaboration between the globally distributed teams was suffering, preventing them from implementing DevOps.\n\n“Our legacy toolchain was complex, disconnected, and difficult to manage and maintain,” said Eric Labourdette, Head of Global R&D Engineering Services and responsible for worldwide R&D operations including DevOps. “SVN was difficult to administer and didn’t scale, causing extra administrative overhead. It became unmanageable for our team size.”\n\nAs the organization looked to move to a microservices architecture and implement DevOps, they needed a solution for  SCM that could foster collaboration across locations and projects, and support DevOps practices like continuous integration and automated deploys.",{"header":1452,"text":1453},"GitLab for SCM enables DevOps","A modern solution that can be hosted on-premises, GitLab provided a single instance of source code for the entire company. Leveraging a Git-based workflow, Axway’s worldwide R&D teams can now easily share and collaborate on code with nearly zero downtime and minimal administrative overhead. Leveraging the most robust Lightweight Directory Access Protocol (LDAP) support of any SCM provider, with GitLab, Axway is able to manage access and permissions for 600 enterprise developers securely and consistently.\n\n“GitLab met our requirements and gave us the best value for the price,” said Labourdette. “The feature set with GitLab on-premise was more advanced than GitHub and we saw the pace and development [of GitLab] moving faster with a community that was active in delivering and contributing.”\n\nCollaboration between development and operations teams improved, too. Using GitLab’s Jenkins integration, developers can trigger their own builds and see the output of the pipeline status in the same view as their code within GitLab.\n\n\"All of the development we have done starts with central source code management in GitLab. This is followed with ephemeral Jenkins through GitLab CI to “eat our own dog food” in creating pipelines that build and deploy images then QA them and execute a security scan. Immutable infrastructure and common continuous deployment using Artifactory and Bintray repositories allows us to deploy Docker container images into AWS. Our new development is based on microservices, Docker on Kubernetes with GitLab being the source of our DevOps pipelines,\" Labourdette explains.",{"header":1455,"text":1456},"Faster release cycles and soaring adoption","Now, with developers empowered to self-serve with minimal guidelines, the DevOps teams at Axway have improved their release cycle time from annual releases down to two weeks for some products.\n\nIn using a bottom-up approach to choose their SCM solution, adoption of GitLab was unsurprisingly fast and natural. In just one year, 630 users were onboarded and 3,000 projects were migrated. “Everyone was asking for it,” said Labourdette. “Now, every single developer is running on GitLab without enforcement.”",{"template":950,"size":44,"region":106,"industry":91},"content:en-us:customers:axway.yml",{"_path":1460,"content":1461,"config":1510,"_id":1511},"/en-us/customers/bab",{"name":1462,"logo":1463,"hero":1464,"heroImage":1465,"benefits":1466,"industry":69,"employeeCount":1478,"location":1479,"solution":913,"stats":1480,"headline":1490,"summary":1491,"quotes":1492,"content":1497},"Bendigo and Adelaide Bank","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745517926/jpf33ho0ufokyx0r3z6x.svg","Learn how GitLab is accelerating DevOps at Bendigo and Adelaide Bank","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518411/p0qea61qbjukknzhjfib.jpg",[1467,1470,1474],{"metric":1468,"config":1469},"Simplified toolchain complexity",{"icon":1423},{"metric":1471,"config":1472},"Multi cloud deployments",{"icon":1473},"CloudTick",{"metric":1475,"config":1476},"Decreased operational costs",{"icon":1477},"TimeIsMoney","7,000","Bendigo, Australia",[1481,1484,1487],{"value":1482,"metric":1483},"4 weeks","to rapid migration",{"value":1485,"metric":1486},"3 to 1","tool simplification (GitLab replaces GitHub, Jenkins and Checkmarx)",{"value":1488,"metric":1489},"32","apps in 30 days","Bendigo and Adelaide Bank is Australia’s better big bank, helping more than 2 million customers achieve their financial goals.","Discover how the move from GitHub to GitLab advanced its cloud journey, increased efficiency, and reduced operating costs.\n",[1493],{"quoteText":1494,"author":1495,"authorTitle":1496,"authorCompany":1462},"We now have an always-innovating solution that aligns with our goal of digital transformation.\n","Caio Trevisan","Head of DevOps Enablement",[1498,1501,1504,1507],{"header":1499,"text":1500},"One of Australia’s most trusted banks","As Australia’s better big bank, [Bendigo and Adelaide Bank](https://www.bendigoadelaide.com.au/){data-ga-name=\"bendigo and adelaide bank\" data-ga-location=\"body\"} is community-focused and dedicated to supporting its customers by ensuring fairness and equity in its pricing. Committed to its customers and communities, Bendigo and Adelaide Bank has delivered high-quality customer service for over 160 years, maintaining its values of teamwork, integrity, performance, engagement, leadership, and passion. In 2019, the bank announced a multi-year transformation strategy focused on reducing complexity and investing in digital transformation.\n",{"header":1502,"text":1503},"Existing solution had high operational costs and complex tooling","The team at Bendigo and Adelaide Bank experienced a few challenges with their GitHub on-premise solution. They needed significant operational resources and heavy engineering to maintain their GitHub instance. Compounding the challenge was their reliance on other tools for CI/CD and security, and the team struggled with a complex toolchain. The lack of a single source of truth meant team members were unable to have full visibility in the software development lifecycle and tracking metrics became difficult. Understanding that continual operational support for an on-premise solution was unsustainable, Bendigo and Adelaide Bank sought a SaaS solution that would offer a robust platform. In addition, the bank was focused on a solution that would align with its strategic objectives of reducing complexity, support agility and promote continuous innovation.\n",{"header":1505,"text":1506},"A single solution accelerates business transformation","The team used GitHub only for source code management and relied on other tools to complement its software development practices. In search of a solution, the team hoped to find a tool that would decrease toolchain complexity and create a centralised location to find information. The team initially assessed GitHub as a SaaS solution, but they didn’t see all the features they needed to meet their goals.\n\nContinuing their search, the team was impressed with GitLab, believing it to be a comprehensive solution to increase operational efficiency, create a single source of truth, and simplify tooling. The team turned to GitLab to manage runners, support Kubernetes, and use security features, such as SAST, container security, and secrets management. “By reducing the number of tools, we have lower maintenance costs, since we don’t need to spend money for on-prem instances and physical servers. We were able to shift to SaaS easily with GitLab. We’ve also avoided the cost of upgrading legacy systems and patching.Using GitLab, we’ve removed complexity from our tech stack, and now we’re more agile. Overall, everyone likes GitLab. It improves our time to market.” said Caio Trevisan, Head of DevOps Enablement.\n\nThe team uses GitLab to implement elevated permissions to control access to projects to require code reviews before merging. “GitLab makes privilege and access management easy. We also now have visibility and observability by using infrastructure as code,” shared Caio. Using CI pipelines, it’s easier for the team to analyse an application and have end-to-end visibility when doing deep analyses. Infrastructure as code has also helped the team have better reverting capabilities and governance.\n",{"header":1508,"text":1509},"Increased cloud computing and operational efficiency","In migrating to GitLab, the team moved 1,500 projects, over 30 organizations, 500 users, and 50GB of data in four weeks. The team is now rapidly progressing towards meeting the corporate goal to move 50% of its applications to the cloud in three to five years. Accelerating business transformation is an important part in managing costs and maintaining sustainable growth.\n\nWith GitLab, the team has embraced cloud technology and has automated manual processes. “GitLab helps us with multi cloud deployments. We can deploy runners in any infrastructure, and we’re currently using them to deploy to AWS and GCP. Deploying to the cloud has been simple, and in the year we’ve been using GitLab, we’re in a good position to meet our goal of moving to the cloud,” explained Caio. The team’s CI runners are deployed everywhere, and team members appreciate that they always scale.\n\nSince using GitLab, the team has experienced increased communication. “With merge requests and code review capabilities, we’re able to collaborate more. Everyone knows that GitLab is our central tool, so we have a single source of truth where everyone can discuss projects,” said Caio. With tooling simplification, the team has not only streamlined its workflow but also improved productivity. The organisation has seen an added benefit of attracting new talent to Bendigo and Adelaide Bank, since software professionals want to use market leading technology to innovate. The company is well-known for its ambitious growth and transformation strategy, and by simplifying technology, the Bank has become more innovative and agile in responding to their customers’ needs.\n\nThe team has observed that GitLab has helped with onboarding new hires. By only having to learn one tool, with useful templates, new hires have been able to push code on their second day. The team has created an internal training service called “DevOps Academy,” which onboards new developers to the simplified tech stack in one week. As an open source project, DevOps Academy uses GitLab to teach team members their development workflow.\n\nThe team is looking forward to embracing GitLab features more deeply by moving away from Jenkins for CD and using GitLab to identify and track metrics. Reflecting on the move to GitLab, Caio shared, “We’ve been getting good feedback about GitLab from other teams. The team is really jumping into it and learning how to use it. Our workflow is more streamlined and efficient, and we’re accelerating business transformation.” In migrating to GitLab, the team moved 1,500 projects, over 30 organisations, 500 users, and 50GB of data in less than four weeks. GitLab represents the bank’s commitment to achieving its strategic objectives by reducing complexity, investing in new capabilities, accelerating its cloud journey to shape its vision to be Australia’s bank of choice.\n",{"template":950,"size":44,"region":110,"industry":71},"content:en-us:customers:bab.yml",{"_path":1513,"content":1514,"config":1563,"_id":1564},"/en-us/customers/bgs",{"name":1515,"logo":1516,"hero":1517,"heroImage":1518,"benefits":1519,"industry":1530,"employeeCount":1531,"location":1532,"solution":913,"stats":1533,"headline":1543,"summary":1544,"quotes":1545,"content":1550,"contributors":1281},"British Geological Survey","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745517960/rp4b9abysjpm2i5a2gj8.png","How British Geological Survey revolutionized its software development lifecycle","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518431/jdnfgcbleu4pkjnhcubo.jpg",[1520,1523,1527],{"metric":1521,"config":1522},"Improved efficiency",{"icon":902},{"metric":1524,"config":1525},"End-to-end visibility",{"icon":1526},"EyeMagnifyingGlass",{"metric":1528,"config":1529},"Built in security and compliance",{"icon":1142},"Science and Research","600","Nottingham and Edinburgh, U.K.",[1534,1537,1540],{"value":1535,"metric":1536},200,"users (including developers, scientists and stakeholders)",{"value":1538,"metric":1539},"1,000\n","hosted software projects and components",{"value":1541,"metric":1542},"+140k","automated pipeline jobs have been run to integrate, test and deploy scientific projects","The British Geological Survey needed an all-in-one tool that offered an easy to use interface, enhanced collaboration, complete visibility, and seamless integration.","With source code management (SCM) and continuous integration and delivery (CI/CD) in GitLab, the research organization has been able to remove the barriers to software development and accelerate innovative science research.",[1546],{"quoteText":1547,"author":1548,"authorTitle":1549,"authorCompany":1515},"GitLab has become our central place to store code and issues. It's become a mission critical system for our organization.","Wayne Shelley","DevOps integration leader, BGS",[1551,1554,1557,1560],{"header":1552,"text":1553},"Geosciences research organization","The British Geological Survey (BGS) is a 185-year-old science and educational research organization that focuses on the geological properties of the UK. BGS’s clients include the public, scientific organizations, universities, and the government in the UK and abroad. The [BGS](https://www.bgs.ac.uk/home.html) provides expert advice in all aspects of geosciences and helps society to use natural resources responsibly, manage environmental change, and be resilient to environmental hazards. The organization digitally records their findings and research.",{"header":1555,"text":1556},"Lacking transparency and collaboration","About two thirds of BGS's 600 employees are scientists and the other third are made up of business support and informatics teams. Communication between scientists and developers is key to ensuring that environmental projects move forward and that information relating to their interactions is recorded.\n\nPreviously software developers were using Subversion for source code management, but found the tool to be lacking the visibility the teams required. \"With Subversion we were storing our code in a secure and convenient place, but it didn't have the collaboration aspect that GitLab offers. You couldn't see the visibility of the work that you were doing and you couldn't share that with our scientists, stakeholders and managers interested in that project,\" explained Wayne Shelley, DevOps integration leader at BGS.\n\nWithout a singular tool that offered total visibility, the BGS software development lifecycle suffered. The teams were not using any CI/CD and processes were separated into siloed steps. \"If we wanted to run tests, we'd probably be doing them offline or we probably wouldn't be doing them at all! We certainly didn't have any kind of continuous integration and deployment that we have now,\" Shelley said.\n\nBGS has its own infrastructure and with developers' demand for infrastructure on the rise, DevOps practices have helped to bridge the gap between infrastructure and application development. \"We’re not a software development house, so this kind of platform infrastructure was lacking at our organization,\" Shelley added.\n\nBGS needed an all-in-one tool that offered an easy to use interface, enhanced collaboration, complete visibility, and seamless integration. As Shelley put it, they wanted \"an off-the-shelf, all-in-one solution that you know we could get behind.\"\n",{"header":1558,"text":1559},"An all-in-one, self-managed platform","About six years ago, Wayne was working on some personal software development projects at home and discovered GitLab. For him, GitLab stood out over GitHub for its ability to be self-managed. After using it personally for a few weeks, Shelley installed it at work and integrated it into some of the existing systems. From there, GitLab’s adoption spread throughout the organization quickly and organically.\n\nOne of the reasons that GitLab worked so well for BGS is that the teams needed their code and infrastructure to remain secure, not necessarily open to the public. Having GitLab locally meant that they could have private repositories on a self-managed infrastructure.\n\nShelley and his team also like that the [project management capabilities](/topics/version-control/){data-ga-name=\"project management capabilities\" data-ga-location=\"customers content\"} of GitLab integrate easily with the web interface. “It’s an excellent way of exploring your code. You can see your projects and be proud of what you're creating. You can see the changes you're making and so can everyone else in the organization. It is discoverable and more interesting. But most importantly our scientific staff are much more involved in the software development process and this accelerated our delivery and research capabilities,” Shelley said.\n",{"header":1561,"text":1562},"Accelerated software development workflow","Over the last few years GitLab has provided a fast track to an improved software development lifecycle. “When we moved to GitLab, it brought to the forefront all of the best practices that the industry is using. We're a relatively small set of developers, so for someone to have packaged up all the best practices into a nice platform is awesome,” Shelley said.\n\nDevelopers now write their own code, create builds, run tests, and develop source-controlled projects all in GitLab. There is now the ability for software developers to collaborate on various projects because of the level of transparency and accessibility within the platform. “The whole process of developing a piece of software has accelerated over the last five years. And I think GitLab has been a focal point of all of the infrastructure and tools and systems that we've built up around it,” said Shelley.\n\nBGS has created a process that is collaborative, code is visible to everyone, work is showcased, security testing is built in, and deployments have accelerated. According to Shelley, “GitLab has really revolutionized and professionalized the whole software development lifecycle in our organization.” GitLab has provided a workflow, and improved BGS best practices in terms of how they’re doing software development.\n\nGitLab Self-Managed Ultimate has a huge range of additional features that is now empowering the software development teams at BGS. But most importantly, “Knowing that GitLab Support is there for you and has your back if you need them. That's critical,” Shelley concluded.\n",{"template":950,"size":40,"region":106,"industry":87},"content:en-us:customers:bgs.yml",{"_path":1566,"content":1567,"config":1616,"_id":1617},"/en-us/customers/bi-worldwide",{"name":1568,"logo":1569,"hero":1570,"heroImage":1571,"benefits":1572,"industry":57,"employeeCount":1584,"location":1585,"solution":913,"stats":1586,"headline":1596,"summary":1597,"quotes":1598,"content":1603,"contributors":1281},"BI Worldwide","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745517961/eypjacklr1kgpavqltwz.svg","How BI WORLDWIDE increased deployments to 10 times a day","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518432/spgzsjzweaudnyi4wwbv.png",[1573,1577,1581],{"metric":1574,"config":1575},"Improved developer efficiency",{"icon":1576},"User",{"metric":1578,"config":1579},"Automated security scans",{"icon":1580},"MonitorTest",{"metric":1022,"config":1582},{"icon":1583},"GitlabCd","1,001-5,000","Minneapolis, Minnesota",[1587,1590,1593],{"value":1588,"metric":1589},"10x","daily deployments for already-modernized applications",{"value":1591,"metric":1592},"From 4 to 15","services pushed per release",{"value":1594,"metric":1595},178,"builds per day","BI WORLDWIDE is a global engagement agency that modernizes and automates their software delivery workflow with a single solution for their complete DevOps lifecycle.","BI WORLDWIDE Corporate Product Development Team removed technology barriers to focus on building microservices\n",[1599],{"quoteText":1600,"author":1601,"authorTitle":1602,"authorCompany":1568},"One tool for SCM+CI/CD was a big initial win. Now wrapping security scans into that tool as well has already increased our visibility into security vulnerabilities. The integrated Docker registry has also been very helpful for us. Issue/Product management features let everyone operate in the same space regardless of role.","Adam Dehnel ","product architect, BI WORLDWIDE",[1604,1607,1610,1613],{"header":1605,"text":1606},"Inspiring employees, sales, channel partners and customers","\nBI WORLDWIDE (BIW) inspires people and delivers measurable business results. Inspired employees solve problems and create value.  Inspired salespeople take risks and seize opportunity. And inspired channel partners and customers choose your brand every time. We work with great companies around the globe who know that extraordinary results can only be achieved when their business is energized by the people who make it happen.",{"header":1608,"text":1609},"Updating legacy systems and moving to multi-tenant configuration","\nThe BIW Corporate Product Development Team (CPD) was dealing with a large legacy codebase that was created years ago. They were looking to eliminate (or at least significantly reduce) manual testing and manual deployments to their on-premise infrastructure. They had maintenance backlogs, inefficiencies, and cross-organization visibility issues. The goal was to achieve operational efficiency by removing toolchain complexity.\n\nThe company was also trying to update the previous architecture of a single-tenant code-change-driven solution and upgrade to a multi-tenant configuration-driven solution. The legacy application installation pattern was to install from a fork that could (and would) be tweaked to a customer’s needs before deploying to the VMs. This pattern provided flexibility for customers but was inefficient and was time-consuming to maintain and upgrade.\n\n“It was entirely time-consuming to apply all of those code changes,” said Adam Dehnel, product architect, BI WORLDWIDE. “As a result, we didn’t release as frequently because the application of a new release to those disparate installations was quite a process. That would cause us to try to get ‘all the features’ into each release which would then slow the process down more.”",{"header":1611,"text":1612},"Increasing development speed","\nThe Corporate Product Development Team considered Git source code management while using CVS in 2014. At that time they achieved 9-month release cycles with another few months for the code to be distributed to the customer installations for the upgrade. This tempo impacted their pace of delivering to market and ability to respond to customer requests.\n\nTo help combat this pattern, the product architecture team was given the directive to rethink processes - essentially update and modernize everything. They had practices and tools in place at the time but were spending time on items that weren’t business differentiating features. They faced classic issues surrounding a lack of cross-team communication including inefficient mechanisms for intra-organization workflows and individualized toolsets.\n\nOne of the early moves to help solve these challenges was to migrate from CVS to Git for source control management. They experienced a self-described “painful transition to Git” because of the modernization efforts this move required. Once the initial move to GitHub was complete BIW began looking to automate the build, test and deployment process. As the first implementation of this, the team built a chain of tools with GitHub talking to Jenkins and then Checkmarx + WebInspect plus JIRA and Confluence for the setup to manage the full lifecycle microservices. While these tools were heading in the right direction, the organization was still facing challenges with toolchain complexity and experienced lost bug reports, constant context shifting and tool differences throughout the organization.",{"header":1614,"text":1615},"Improving efficiency by moving to a single tool","\nThe CPD team evaluated GitLab’s capabilities against their current toolset and against the competition and selected GitLab to help them achieve their next iteration. The group started looking at what tools they could remove to simplify their toolchain. The migration from their previous Git tools to GitLab was painless and they saw an immediate improvement of collaboration and release pace as a result of their move to GitLab.\n\nThe development, QA, UX and DevOps teams within CPD at BIW have been using GitLab since 2017. In June 2018, additional development groups started to move over to be able to easily track all features, stories, requirements and use cases in GitLab Issues. The next goal is to include ongoing bug tracking and expand GitLab to several new internal teams that will use it as a collaboration hub for future feature development requests and discussions.\n\n“GitLab is currently running on a Rancher cluster and we’re using AWS Aurora Postgres + Elasticsearch to run it.  And then we just recently migrated from a (different) Rancher cluster for our microservices to Amazon EKS and are also pushing our web applications to CloudFront,” Dehnel explains. “All of this deployment is running from GL pipelines.  We are solidly in a good CI workflow with some applications in Continuous Delivery.  Heading into 2020 we’re starting to push towards Continuous Deployment for all microservices and microexperiences. We hope to leverage some of the GitLab Kubernetes integrations and enhancements to make this transition less work and more consistent.”\n\nThe company recently started using GitLab Pipelines to scan (SAST + Dependency initially, but they plan on using DAST capabilities soon) and deploy legacy monolith installations for anyone that is running their install in AWS.  Between this setup and the microservices running in GitLab pipelines the first four days of SAST/Dependency scanning the team performed over 300 scans. This scanning helped the team identify previously unidentified vulnerabilities and allowed them to rectify the situation going forward. GitLab’s pipelines allow everyone to use the same tooling for application scanning and deployment regardless of whether it is legacy or modernized.\n\nWhile Dehnel admits that they are still using some classic methods, they now have teams that experience releases almost daily — down from the original pre-Git pace of a release every 9-12 months. BIW is using GitLab pipelines to deploy the legacy monolith to AWS.  Within those pipelines, they are performing automated infrastructure provisioning, [infrastructure as code](/topics/gitops/infrastructure-as-code/), automated security tests, and application deployments.\n\nThe ultimate win for the company is that the corporate product development team is all working in the same place. The operations infrastructure team is now working from the same platform and using the same product for their software development lifecycle. The team is pushing all of their automation tools to the same place instead of working around a daisy chain of tools anymore.",{"template":950,"size":44,"region":102,"industry":59},"content:en-us:customers:bi-worldwide.yml",{"_path":1619,"content":1620,"config":1659,"_id":1660},"/en-us/customers/bitpanda",{"name":1621,"logo":1622,"hero":1623,"heroImage":1624,"benefits":1625,"industry":69,"employeeCount":1429,"location":1637,"solution":975,"headline":1638,"summary":1639,"quotes":1640,"content":1645,"companySize":1281,"region":1281,"contributors":1281,"stickyBenefits":1658},"Bitpanda","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745517963/tm4gxdhau3ucmsmq1gwn.svg","Bitpanda uses GitLab to enable dynamic growth of its DevOps function","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518433/uwzmwgrhkpq2xzkfve9y.jpg",[1626,1630,1633],{"metric":1627,"config":1628},"Fast developer onboarding",{"icon":1629},"DevEnablement",{"metric":1631,"config":1632},"Deep visibility into project status",{"icon":1195},{"metric":1634,"config":1635},"Scalable support",{"icon":1636},"AutoScale","Vienna, Austria","Digital assets, cryptocurrencies, blockchain technology, and commission-free fractional stocks are just some of the expansive services the Bitpanda technical team builds and deploys.","GitLab enables robust scaling for hypergrowth fintech Bitpanda\n",[1641],{"quoteText":1642,"author":1643,"authorTitle":1644,"authorCompany":1621},"We don’t have a fixed release day. We are deploying every day, every hour.\n","David Papp","Head of development",[1646,1649,1652,1655],{"header":1647,"text":1648},"Empowering individual investors through innovative fintech","[Bitpanda](https://www.bitpanda.com/en), based in Vienna, Austria, is an innovative 7-year-old financial technology (fintech) company. Rooted on the tenet that investing should be safe, easy and accessible for everyone, the company has built a digital investment service, a user-friendly, trade-everything platform created to empower users to invest in stocks, cryptocurrencies and metals – with any amount of money. Working to redefine investment possibilities for people who might be left on the margins of traditional finance, Bitpanda has grown to have more than 3 million users. Focused on innovative technology, like digital assets and blockchain, that aims to compete with traditional financial methods, Bitpanda’s solutions allow both established and emerging players to accelerate digital transformation and customize products for end users. Bitpanda’s DevOps teams collaborate to create and deploy innovative, cutting-edge systems that support the company’s mission to empower individual investors.\n",{"header":1650,"text":1651},"Effectively support scalable, dynamic growth of teams and pipelines","Bitpanda has grown dramatically, going from just two or three developers relying on Subversion to creating teams with several hundred developers in less than a decade. To support Bitpanda’s mission and to keep up with this growth, its DevOps teams needed to gain better visibility into their fast-paced and complicated work. As the number of pipelines multiplied, tracking development and deployment processes became more complicated. At the same time, code version and control point tools, like Subversion, were unable to meet these necessary objectives. It wasn’t tenable. To fix the situation, they began searching for a unifying approach, evaluating platforms from GitLab, GitBucket, GitHub and Cheetah. The answer lay with GitLab. And it’s been the answer for every team at Bitpanda.\n",{"header":1653,"text":1654},"Efficient operations and simplified workflow","GitLab provides an integrated solution for pipeline creation that enables developers to be self-sufficient. With GitLab CI/CD, live updates are easier to accomplish, supporting continuous release of services. Through use of multiple GitLab labels, epics and boards, each team can readily monitor work underway. This supports simplified workflow and greater operational efficiency, while allowing scrum leads and others to tailor tooling around individual requirements. And even rollbacks, when necessary, are supported, as well. To simplify work even more, GitLab tools are a ready fit with the AWS Elastic Kubernetes Service. Since Bitpanda has been dramatically growing its team of developers, another major benefit of going with GitLab has been efficiently onboarding new engineers. Being able to rapidly and successfully scale up their DevOps teams has enabled the company to continue to be innovative and address new markets.\n",{"header":1656,"text":1657},"One DevOps platform enables agile productivity and maintains high standards","By adopting GitLab Premium, Bitpanda has been able to build and deploy pipelines using a single, comprehensive tool. “In the end, we decided on GitLab because it was a tool that basically had everything in one place,” said Christian Trummer, chief technology officer at Bitpanda. The software allows teams to quickly move work forward, while ensuring quality and compliance, and adapting to spikes in workloads. GitLab removes the need for its DevOps teams to spend extensive time and money doing heavy, manual work to obtain operation metrics. The tools uncover link issues across teams, while also monitoring lead times, cycle times, sprint editions and plan-versus-actual status. In regulated industries, this kind of monitoring is crucial to compliance. “With GitLab we know we have a well defined change process. GitLab is very intuitive, when you compare it with Jira, which is much more complicated. It is very handy in terms of audits. There is always full visibility,” said Trummer, who also commended GitLab for transparency in pricing. “With GitLab, everything is open.”\n",{"benefits":1281},{"template":950,"size":40,"region":106,"industry":71},"content:en-us:customers:bitpanda.yml",{"_path":1662,"content":1663,"config":1721,"_id":1722},"/en-us/customers/caci",{"name":1664,"logo":1665,"hero":1666,"heroImage":1667,"benefits":1668,"industry":290,"employeeCount":1679,"location":1680,"solution":913,"stats":1681,"headline":1690,"summary":1691,"quotes":1692,"content":1697},"CACI","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745517927/krm6a9ahb706vzxtpqay.png","CACI uses GitLab to boost tech delivery for public sector customers","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518411/byfbunkt62aoyer5qbzg.jpg",[1669,1672,1675],{"metric":1670,"config":1671},"Reduced costs",{"icon":1247},{"metric":1673,"config":1674},"Increased delivery velocity",{"icon":902},{"metric":1676,"config":1677},"Improved security",{"icon":1678},"SecurityOwner","24,000+","Reston, Virginia",[1682,1684,1687],{"value":1402,"metric":1683},"savings in labor/admin",{"value":1685,"metric":1686},"13x","faster security scanning",{"value":1688,"metric":1689},"7+","tools consolidated into 1 platform","With GitLab, CACI has been better able to meet customers’ software needs at scale, strengthening the company’s position in the industry, as well as its bottom line.","[CACI International Inc.](http://www.caci.com/), a $7.7 billion company whose technology and expertise play a vital role in U.S. national security and government modernization, considers itself a major industry disruptor, and its agile software development is its superpower. CACI has made a name for itself by delivering critical software and software-enabled hardware to U.S. government agencies, the U.S. intelligence community, and the Department of Defense. So, when the company realized they needed to disrupt their way of developing and deploying software, they partnered with GitLab, a company they saw as disrupting its own industry.",[1693],{"quoteText":1694,"author":1695,"authorTitle":1696,"authorCompany":1664},"We turned to GitLab to allow us to rethink, and disrupt, the way we develop and build software swiftly, without compromising security. It’s how we enable our agile software development business.","Glenn Kurowski","Senior Vice President and CTO",[1698,1700,1703,1707,1709,1712,1715,1718],{"text":1699},"CACI migrated to GitLab’s AI-powered DevSecOps platform to increase efficiency, [security](https://about.gitlab.com/blog/its-time-to-put-the-sec-in-devsecops/), and productivity, while also [consolidating what had been cumbersome and expensive toolchains](https://about.gitlab.com/blog/too-many-toolchains-a-devops-platform-migration-is-the-answer/).\n\n“Our customers rely on us because they know agile software development is our superpower,” says [Glenn Kurowski](https://www.caci.com/bio/glenn-kurowski), senior vice president and CTO of CACI. “But looking at ourselves critically revealed some programs were using DevSecOps toolchains that were great years ago but not that great today. With multiple acquisitions under our belt, we had different DevSecOps toolchains spread across our software development teams. It was working but we knew it could be more efficient. We had to disrupt ourselves to improve our superpower.\n\nAccording to Kurowski, CACI selected GitLab as its partner because of his confidence in it as a full DevSecOps platform, GitLab’s rapid pace of continuous innovation, and its willingness to partner on the emerging USG security requirements. Adopting GitLab also allowed CACI to have a more homogenous approach and eliminated seams created by using disparate products.\n",{"header":1701,"text":1702},"The backbone of CACI’s common environment","A big part of CACI’s plan was to commit to using GitLab as the central cog in building a company-wide Common Software Development Environment (CSDE).\n\nBuilding CACI’s software in the CSDE, which is set up as a service on the AWS GovCloud, ensures everything they develop is fully compliant with emerging federal regulations. The environment includes a standard set of tools, services, and rule frameworks for regulatory mandates. With CSDE as-a-service, it’s available to all projects. And the GitLab DevSecOps platform is at the center of it.\n\n“Previously, our teams frequently had to build a new DevSecOps toolchain  for every new contract that came in,” says Kyle Craft, CSDE service lead at CACI. “With GitLab at the heart of our CSDE, you just create a new account and start working on the software, instead of spending time building and administering a toolchain. It’s much more efficient.”\n\nTeams across CACI use the CSDE for the company’s nearly 190 different software development projects — unless a customer requires the use of their own environment. The company is seeing a 90% savings in labor and administrative work around toolchain administration since moving to a GitLab-based CSDE. Patch creation automation is down from hours to minutes, while security scanning has sped up by 13x versus previous implementations.",{"title":1704,"config":1705},"GitLab enables CACI to deliver software faster",{"url":1706},"https://www.youtube.com/embed/qzukFxW7Eak?si=kBEfz9RkgTo8q8RD",{"text":1708},"“Our developers love the ease of use, the availability, reliability, and scalability of our GitLab-based CSDE service,” says Craft. “GitLab is the backbone of the way we build software, and our workforce loves how fast they can start up projects and produce software for new programs and projects.”\n\nCACI has seen “explosive growth” in CSDE users since standardizing on GitLab. Rolling out CSDE started with just 110 initial users in the summer of 2022. But a little over a year later, that usage had grown to more than 1,900 developers. It helps that GitLab fits the scale at which CACI’s agile software development executes. For example, one program alone in CACI has more than 150 applications and issues 800 releases of new capability per year.\n\n“Our customers expect innovation and high-quality software. They desperately need high velocity – rapid releases of new capabilities to address evolving mission needs,” says Kurowski. “Many in our industry do software development but we take it to the next level, and at scale. To expand our leading position, we turned to GitLab to enable us to rethink, and disrupt the way we [build software swiftly without compromising security](https://about.gitlab.com/blog/how-devsecops-drives-business-success/).”",{"header":1710,"text":1711},"Supporting a major software build","The GitLab-based CSDE has been critical in CACI’s work to create a new version of a communication system for one of its customers.\n\nTwo earlier versions of the project were built using a variety of different DevSecOps tools. To support the development of the new version of the mission application, the team switched to CACI’s GitLab-based CSDE for an integrated end-to-end DevSecOps platform.\n\n“GitLab had all the features and [automation](https://about.gitlab.com/blog/how-automation-is-making-devops-pros-jobs-easier/) we needed in one application. It simplified our work,” says Wesley Monroe, technical project manager at CACI. “With all of the road mapping, issue tracking, and security scanning in one place, it’s hard to even compare it with what we were using before.”",{"header":1713,"text":1714},"Meeting government regulations","One of the greatest benefits of using GitLab’s DevSecOps platform is that it enables CACI to be prepared to handle emerging security compliance requirements, avoiding costly rework down the road.\n\nMeeting government laws, regulations, and standards is critical for a government contractor. That means not only being compliant but being able to prove it.\n\nCSDE was another example of CACI investing ahead of its customers’ needs. “We have positioned ourselves to be able to meet future contract security requirements,” says Craft. “We can attest to meeting security standards and have the data to back that up, which is tracked and stored in the GitLab platform.”\n\nUsing a single platform also enables CACI’s teams to shift security left, incorporating it into every phase of the software development lifecycle. That’s key to being able to meet security-focused US government regulations, such as the Secure Software Development Framework (SSDF).",{"header":1716,"text":1717},"Cutting costs and simplifying complexities","Before CACI launched its migration to GitLab DevSecOps, teams had been weighed down with a large number of [disparate and expensive tools](https://about.gitlab.com/the-source/platform/devops-teams-want-to-shake-off-diy-toolchains-a-platform-is-the-answer/) across the enterprise. Now they are reducing that complexity by migrating off some of those tools.\n\nBy trimming the company’s toolchains, Kurowski says they have reduced licensing costs, spent less time administering their tools, and have been able to dedicate more time to developing software. He also notes that teams are more productive, they’re launching projects much faster, and they’re more easily meeting demand surges. He says training also has been simplified, upgrades are done more smoothly and quickly, and project management has become more in line with code development. Patches are also now done with little to no downtime.\n\nSoftware developers, working on a common platform, now easily move between projects to meet surges in customer demand. “This ensures customers have access to top software development talent at speed,” says Kurowski.\n\nThe platform also has enabled them to create documentation that is “night and day better” than what they were able to produce before, notes Craft. That’s largely because the platform fosters strong collaboration inside and among DevSecOps teams, giving them better visibility into projects and the ability to share responsibility for making notes about problems, solutions, and best practices.",{"header":1719,"text":1720},"Creating a DevSecOps community","CACI’s DevSecOps users have been creating what Craft calls a “community of practice” because of the extra visibility and collaboration they’re finding through the platform. “Because we’re using the same platform, we’re aware of each other like we never were before,” he explains.\n\nPart of CACI’s expanding use of GitLab means looking forward to purposefully and responsibly leveraging AI features, like [GitLab Duo](https://about.gitlab.com/gitlab-duo/), built into the platform. Kurowski says they anticipate using AI to help learn and understand existing code, and to develop new code.\n\n“We love where GitLab is headed with augmenting DevSecOps with AI,” he adds. “Our coders spend more time understanding code than writing it. That’s just the norm for the industry. The idea of augmenting the process with code explanation, code suggestions, and code assistance, in general, is spot on with a core need.”",{"template":950,"size":44,"region":102,"industry":79},"content:en-us:customers:caci.yml",{"_path":1724,"content":1725,"config":1777,"_id":1778},"/en-us/customers/carfax",{"name":1726,"logo":1727,"hero":1728,"heroImage":1729,"benefits":1730,"industry":1742,"employeeCount":1743,"location":1744,"solution":913,"stats":1745,"headline":1752,"summary":1753,"quotes":1754,"content":1758},"CARFAX","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745517928/km5lzmch9zpxfc80oxhi.png","CARFAX improves security, cuts pipeline management and costs with GitLab","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518412/pfaykc3gyrvbvp6rtkno.jpg",[1731,1735,1739],{"metric":1732,"config":1733},"Faster deployments",{"icon":1734},"SpeedAlt2",{"metric":1736,"config":1737},"Toolchain reduction",{"icon":1738},"Cog",{"metric":1740,"config":1741},"Increased security scans",{"icon":1142},"Automotive","1,200","Centreville, VA, U.S.",[1746,1749],{"value":1747,"metric":1748},"20%","boost in deployments YoY",{"value":1750,"metric":1751},"30%","of vulnerabilities found earlier in SDLC","CARFAX had been spending too much time and money supporting its DevOps toolchain, instead of focusing on delivering new features. By adopting GitLab, they trimmed that toolchain, while also improving security.\n","[CARFAX, Inc.](https://carfax.com/), a U.S. company, helps millions of people shop for vehicles every day. With more than 31 billion records, it has the most comprehensive vehicle history database available in North America, offering users vehicle information, like odometer readings, number of owners, and damage history. CARFAX receives this information from more than [139,000 data sources](https://www.carfax.com/company/vhr-data-sources), including every U.S. and Canadian provincial motor vehicle agency.\n",[1755],{"quoteText":1756,"author":1757},"With DevSecOps, security is always front and center. It’s part of every step of the process and not easily missed.\n","Mark Portofe, Director of Platform Engineering, CARFAX",[1759,1762,1765,1768,1771,1774],{"header":1760,"text":1761},"Alleviating toolchain troubles","Many of CARFAX’s customers interact with the company online, so it relies on software to maintain and grow customer relationships and stay ahead of competitors. To do that, the company needs to efficiently and securely create new, innovative, and secure software, along with new features for its most popular software products. Over the years, CARFAX development teams had amassed a toolchain of DevOps tools that were not meeting all of the company’s needs and, even worse, were creating additional challenges.\n\n\n“We were spending too much time and budget procuring and supporting our toolchain, which had grown to 12 tools,” says Mark Portofe, Director of Platform Engineering at CARFAX. “We needed to minimize toolchain maintenance and support as much as possible so our teams could focus on actually creating new feature delivery and not just taking care of all these different tools.”\n\n\nIn addition to their efficiency and productivity concerns, CARFAX development teams needed a way to find vulnerabilities earlier in the software development lifecycle. Problems that surfaced during periodic, manual scans, instead of during the development process, were costing the organization time and money. CARFAX wanted to turn that around.\n",{"header":1763,"text":1764},"Leveraging GitLab’s DevSecOps Platform","To make these needed changes, CARFAX decided in mid-2020 to use GitLab’s DevSecOps Platform, specifically GitLab Ultimate. “With GitLab, we knew we’d get a lot of features we could leverage without doing all the stitching together,” Portofe says.\n\n\nTo get started, CARFAX first focused on mirroring the codebase into GitLab and leveraging the GitLab security scans across all of their code. This was completed within the first six months. Next, the company began using GitLab for its code repository and CI/CD pipeline capabilities. While there hasn’t been a hard migration mandate or time table, software development teams have created plans to use the GitLab platform within their individual product roadmaps. And to help the development teams that were starting to use GitLab, CARFAX established a central team to work directly with them.\n\n\nGitLab use at the company largely started with customer-facing apps. At the same time, teams began migrating corresponding pipelines for those same applications. Non-customer-facing software, along with large, legacy apps, will have a longer migration path.\n\n\n“We allowed dev teams to plan it themselves,” says Portofe. “We gave a lot of flexibility to our development teams because a lot of their roadmaps had already been baked. Doing it this way created excitement because they saw the benefits of things like security scans and better code insights.”\n",{"header":1766,"text":1767},"Reducing the toolchain and fragility","In the early stages of using GitLab, CARFAX replaced various DevOps tools in their toolchain. Ultimately, Portofe says they plan to cut their toolchain by about half.\n\n\n“The full toolchain was costing us money both in license costs and inefficiencies,” says Portofe. “By using GitLab, we saw a huge increase in security scanning because CARFAX was then able to scan the whole codebase without manual steps. And it gave us a much better picture of our security vulnerabilities. We saved money and increased security.”\n\n\nHe also points out that reducing the toolchain streamlines engineers’ workloads, increases productivity and efficiency, and makes the entire development and deployment effort more stable.\n\n\n“There was some general fragility with other tools we have used in the past and we’re not seeing that with GitLab,” says Portofe. “Indirectly, it’s a benefit for the whole business. That’s what it’s all about, really — how to be as efficient as possible to get features out to customers.”\n",{"header":1769,"text":1770},"Increasing security with automation and a shift left","Another aspect of GitLab’s DevSecOps Platform that added efficiency was its built-in automation, which brought a [whole new level of security](https://about.gitlab.com/blog/its-time-to-put-the-sec-in-devsecops/).\n\n\nCARFAX has been able to use GitLab’s automated security features to do dependency and container scanning, as well as secret detection. “Prior to using GitLab, performing security scans on our codebase was a manual, cumbersome task. It’s much easier today,” says Portofe. “While security is always an ongoing battle, GitLab’s security features are making it easier for developers to spot issues early.”\n\n\nThe platform’s automated scanning has enabled CARFAX to find nearly one-third of its vulnerabilities much earlier in the development lifecycle over the past year.\n\n\nAnd Portofe points out that using a platform has the entire development team thinking about security at the earliest point in the software lifecycle. By shifting their [focus on security](https://about.gitlab.com/the-source/security/how-to-strengthen-security-by-applying-devsecops-principles/) as far left as possible, they’re considering security needs and implications as they are coding and not later downstream — when it’s more difficult, more expensive, and less efficient to fix any problems.\n\n\n“We are always thinking about security while we design and build software,” he says. “It’s not just about trying to get features out the door but also ensuring that those features are secure. It’s part of every step of the software development lifecycle. That saves time and increases our security.”\n",{"header":1772,"text":1773},"Growing deployments with a smaller team","CARFAX has made some serious productivity gains with DevSecOps. By automating processes, shifting security left, and reducing toolchain complexity, teams have been able to simplify processes, boost productivity, and increase deployment velocity. In 2022 alone, the company saw a 14% increase in production deployments.\n\n\n“It seems that everything is just cleaner now when moving code to production,” says Portofe. “We’re putting out more new product features because teams are spending more time creating code than making sure their pipelines are running.”\n\n\nAnd what’s even more impressive about this increase in deployments is that CARFAX is making that happen with a smaller team.\n\n\nThe company’s tooling team, which is focused on building common pipelines and utilities that CARFAX’s approximately 250 software engineers can use to build code, normally has five members. However, they’ve been down to just two for a while and they’re still making productivity and deployment gains. “The platform has allowed us to operate as a two-person team and still keep things going,” says Portofe. “Actually, our production deployments, overall, went up roughly 25% for the first five months of 2023, compared to the previous five-month period. It’s pretty amazing.”\n",{"header":1775,"text":1776},"Easing a cloud migration","CARFAX, which leverages Amazon Web Services (AWS) capabilities, has had different teams with different assets on the cloud over time. They’ve also had some on-premises infrastructure. It’s been a mixed environment. Now, though, they are migrating most of their infrastructure, servers, and codebase to the cloud, with the help of GitLab.\n\n\n“Going down this path, it’s helpful that GitLab has tools to make the move to the cloud easier,” says Portofe, adding that they also are consolidating their cloud compute platform.\n\n\nAnd he adds that GitLab’s platform allows CARFAX to be cloud agnostic. “When we go to commonize our CI/CD pipelines, we can move them with a common on-ramp that makes it easier,” says Portofe.\n",{"template":950,"size":40,"region":102,"industry":91},"content:en-us:customers:carfax.yml",{"_path":1780,"content":1781,"config":1832,"_id":1833},"/en-us/customers/cern",{"name":1782,"logo":1783,"hero":1784,"heroImage":1785,"benefits":1786,"industry":1796,"employeeCount":1797,"location":1798,"solution":913,"stats":1799,"headline":1809,"summary":1810,"quotes":1811,"content":1816},"CERN","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745517928/u3qb5u9cjn9bdmxxqcyi.png","CERN advances understanding of the universe with the help of GitLab","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518413/apacz4x7stfpzuhr3ymw.jpg",[1787,1791,1793],{"metric":1788,"config":1789},"Enhanced code quality",{"icon":1790},"SourceCode",{"metric":1676,"config":1792},{"icon":1142},{"metric":1794,"config":1795},"Increased global collaboration",{"icon":1385},"Science, Technology & Education","10,000 associated members","Geneva, Switzerland",[1800,1803,1806],{"value":1801,"metric":1802},"90x","faster job startups using GitLab runners",{"value":1804,"metric":1805},"60x","faster issue identification",{"value":1807,"metric":1808},"3x","more concurrent jobs","CERN connects scientists distributed worldwide in some of the most significant collaborative efforts to uncover what the universe is made of and how it works. Teams there also use GitLab to build software that is helping researchers investigate phenomena like dark matter, and the Higgs boson.","[CERN](https://procurement.web.cern.ch/), the European Laboratory for Particle Physics, is a world-renowned intergovernmental organization that operates the largest particle physics laboratory in the world. Physicists and engineers from 24 member states study the fundamental structure of the particles that make up everything, looking to understand the greatest scientific mysteries in the universe. The CERN scientific community uses GitLab to tackle the complex challenge of securely and efficiently running the world's largest and most powerful particle accelerator, as well as processing the vast amounts of data it generates. Scientists from universities and research institutes around the world also use the platform to collaborate on shared projects.\n",[1812],{"quoteText":1813,"author":1814,"authorTitle":1815,"authorCompany":1782},"We are using software built in, updated in, and hosted on GitLab as tools for our research, which focuses on better understanding the greatest mysteries in the universe, including the Higgs boson, dark matter, and anti matter. GitLab is helping us advance physics.","Ismael Posada Trobo","Tech Lead and Engineering Manager",[1817,1820,1823,1826,1829],{"header":1818,"text":1819},"Building software to investigate the universe","Established in 1954, CERN first activated the Large Hadron Collider (LHC) in 2008. Called “one of the greatest engineering milestones of mankind,” the collider, a 17-mile, underground, vacuum-sealed loop with a number of accelerating structures, smashes particle beams together to create showers of new particles that replicate conditions in the universe just moments after its conception. The collider is designed to explore concepts like the Big Bang, dark matter, and the Higgs boson.\n\nFor years, CERN had used multiple DevOps tools, including GitHub, to build the software needed by the CERN scientific community. But their teams needed a more comprehensive solution: a move to a full end-to-end DevSecOps platform that adds security into their entire software development lifecycle and would increase their efficiency and delivery speed. They adopted GitLab’s platform with GitLab Starter in 2015. With the addition of the platform, the facility’s teams began updating, iterating, and rebuilding all of their software. And every new project from then on was built and deployed with GitLab. To further increase their efficiency and visibility, they upgraded to GitLab Premium in 2020, and then upgraded again, this time to GitLab Ultimate in 2023, to take advantage of its advanced security framework.\n\n“All of our software—the software running our complex, running the collider, creating collisions— is all built on and hosted on GitLab, says Michi Hostettler, Large Hadron Collider engineer-in-charge at CERN. “It’s important software for us. Because of the platform’s integration, automation, issue tracking, security scanning, documentation—everything is developed using  the platform. ”\n\nThe collider is an integral component of the facility’s infrastructure and scientific mission, so using GitLab-built software to keep it running optimally and to analyze the exabyte of raw data it produces each year is fundamental to what the world-class scientists there do. Understanding that data is fundamental to expanding humans’ knowledge of the world.\n\n“GitLab is considered an important piece of the ecosystem at CERN,” says Ismael Posada Trobo, version control systems tech lead and engineering manager at CERN. “With software built in and hosted on GitLab, we’re simulating particle collisions, and recreating collisions with data from the LHC. It enables scientists to research and to imagine. From a developer’s point of view, GitLab plays a valuable role in getting their work done.”",{"header":1821,"text":1822},"Enabling massive, global collaborative research efforts","GitLab’s platform isn’t just being used by DevSecOps teams at CERN to build software. According to Trobo, 30% of their use of GitLab is to connect researchers from universities, laboratories, and research institutes around the world so they can communicate about and collaborate on scientific projects.\n\nFor instance, researchers working on the ATLAS experiment, one of the largest collaborative efforts ever attempted in science, are using the platform for their Athena software. The project—designed to study the fundamental constituents of matter, using the full discovery potential of CERN’s collider— involves approximately 6,000 members and 3,000 scientific authors from 182 institutions and 42 countries. This extensive group of researchers distributed across the globe needed a way to visualize each other’s work, offer insights, and work together on problems. GitLab’ DevSecOps platform gave them the ability to do that.\n\n“ATLAS Athena is not just large in terms of lines of code, data being analyzed or the number of scientists involved,” says Zach Marshall, computing coordinator with the ATLAS experiment and senior scientist at the Lawrence Berkeley National Laboratory. “It is, by far, the biggest and most powerful project we have—in every regard. In the end, we needed a way to efficiently and collaboratively work on this massive and dynamic project. That’s why everything we’re doing with it is concentrated in GitLab. It’s important for our scientists. Whether they’re developing software or writing papers, we can easily share knowledge, iterate, and collaborate in real-time.\n\n“This makes the research both quicker and more effective,” he adds. “A huge amount of our collaborative work goes through GitLab. They can work in GitLab, visualizing the project and progress. They can comment and offer feedback. It accelerates our work.”",{"header":1824,"text":1825},"Trimming a toolchain, while increasing security","DevSecOps teams at CERN have been [trimming their toolchain](https://about.gitlab.com/the-source/platform/devops-teams-want-to-shake-off-diy-toolchains-a-platform-is-the-answer/), which has included tools like Jenkins, Bamboo, and GitHub. The five-piece toolchain has been completely replaced with GitLab’s single platform, says Trobo.\n\nEliminating their toolchain saves context switching, along with having to update, manage and pay for multiple tools. And using an end-to-end platform improves the facility’s application and software supply chain security, as well. And that means it also [increases security](https://about.gitlab.com/stages-devops-lifecycle/secure/) for scientific research, the scientists, and CERN’s valued reputation.\n\n\"Like any other organization, university, or company, CERN is under constant attack. Balanced with the academic nature of the organization, we adapt our security posture accordingly to maintain our surety,” explains Trobo. “GitLab helps us set up security policies and compliance frameworks for all the developers and the entire community. That’s significant for us.”\n\nA significant security benefit that CERN gained with GitLab—along with [automated scanning](https://about.gitlab.com/blog/how-to-integrate-custom-security-scanners-into-gitlab/), secret detection, and static application security testing—was the ability to visualize the security posture of its applications.  With built-in dashboards, teams can automatically see a collection of metrics, ratings, and charts for any vulnerabilities detected by the platform’s security scanners. All of the information is aggregated in one place.\n\n“I get scan results for everything from vulnerabilities, to critical policy findings, and required approval resolution for specific scan policies,” says Trobo. “It’s really useful because the dashboards give us an overview where we can look at all the security findings in one place. We’re now well aware of what is happening in all of our projects. The reports are almost created automagically. With one click, you can make your project more robust.”",{"header":1827,"text":1828},"Saving time, money, and inefficiencies with GitLab runners","A few years ago, CERN’s DevSecOps team members were spending a lot of time building their own runners, which operate builds in pipelines. They only had about 40 runners on up to 80 concurrent jobs throughout their ecosystem. Today, they have three times as many because they rely on GitLab runners, enabling them to automate their software delivery process so they can deliver value faster and quality code more often.\n\nCERN began using more runners in the summer of 2023 when GitLab delivered [runner updates](https://about.gitlab.com/releases/2023/05/22/gitlab-16-0-released/#create-an-instance-runner-in-the-admin-area-as-a-user) as part of the GitLab 16 release. New instances of the lightweight, scalable agents that run CI/CD jobs can be spun up in GitLab, instead of developers having to build their own private runners. The platform also enables teams to re-use runner configurations to register multiple runners with the same capabilities, and to take advantage of Kubernetes, which automates container management and includes commands for deploying applications.\n\n“Now the whole CERN community can use GitLab’s runners, instead of taking the time to build our own,” says Trobo. “Our use of runners is exploding now. This automation is saving developers time, which they now can use to focus on more important work. That saves us money and enables us to scale our software development more efficiently.”\n\nAlejandro Iribarren, a member of the AlmaLinux Board of Directors and an engineering tech lead at CERN, notes that some of their automated workflows are a good example of that.\n\n“These workflows allow us to build new cloud images, instantiate multiple virtual and physical machines, test them with various configurations and, if all the tests pass, automatically promote new images to production— all in one click,” he adds. “Thanks to these CI pipelines, we can now update our cloud images much more frequently, while having much higher confidence in the end result. The biggest value of GitLab CI is that it allows us to reduce the number of things we have to worry about.”",{"header":1830,"text":1831},"Looking ahead to AI-driven software","DevSecOps teams at CERN haven’t begun testing artificial intelligence (AI) capabilities in the platform but Trobo says they’re eager to begin doing so. “I hear developers talking about it. They’re asking me when they can use the AI features in GitLab,” he adds. “We know having AI will help our community build better code.”\n\nWith [GitLab Duo](https://about.gitlab.com/gitlab-duo/) tools like Test Generation, Code Explanation, and Vulnerability Resolution, Trobo says he sees his teams being able to gain efficiency, save money, and be able to spend less time on repetitive tasks and more time on creating innovative software. “In GitLab Duo, you can edit your code on the fly, which helps you gain a lot of speed,” he notes. “If you’re developing and you have something that can help you all along the software development lifecycle, it’s going to add so much efficiency. It’s going to make developers’ jobs easier.\n\n“There is a clear desire to use artificial intelligence here,” says Trobo. “CERN is one of the most advanced scientific organizations, known for using cutting-edge technologies. We need to be at the forefront of using AI.”\n\nCERN team members see GitLab as a key point of development and research, enabling efficient software development, data analysis, and global scientific collaboration. Because of the breadth of their usage and benefits, Trobo sees them only expanding their use of the platform. “When anyone is developing, reviewing, managing projects, tracking issues, doing security scanning, or deploying, they’re doing it in GitLab,” he adds. “No matter what they’re doing, they are working in GitLab. I don’t see that changing.”\n\n“We know having AI will help our community build better code,” says Ismael Posada Trobo, tech lead and engineering manager at CERN. “If you’re developing and you have something that can help you all along the software development lifecycle, it’s going to add so much efficiency. It’s going to make developers’ jobs easier.",{"template":950,"size":44,"region":106,"industry":87},"content:en-us:customers:cern.yml",{"_path":1835,"content":1836,"config":1882,"_id":1883},"/en-us/customers/chefkoch",{"name":1837,"logo":1838,"hero":1839,"heroImage":1840,"benefits":1841,"industry":89,"employeeCount":1853,"location":1854,"solution":975,"stats":1855,"headline":1862,"summary":1863,"quotes":1864,"content":1869,"contributors":1281},"Chefkoch","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745517965/n5dp68pywus6itwrlqif.svg","Chefkoch improved project visibility and deployment velocity with GitLab","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518434/scdhzxje2mcih2ted7zq.jpg",[1842,1846,1849],{"metric":1843,"config":1844},"Single source of truth",{"icon":1845},"ContinuousDelivery",{"metric":1847,"config":1848},"Improved workflow efficiency",{"icon":902},{"metric":1850,"config":1851},"Less time spent on maintenance",{"icon":1852},"CogCode","33","Bonn, Germany",[1856,1858,1860],{"value":1857,"metric":1032},"40%",{"value":1750,"metric":1859},"earlier identification of bugs",{"value":1747,"metric":1861},"developer time saved","Chefkoch, Europe's largest food platform, was looking for a way to streamline the company's developer workflows, improve project visibility, and provide controlled deployments.","With GitLab, the popular recipe platform, which offers customized recipes to millions of users a month, has been able to deploy faster, identify bugs sooner, and free up developers' valuable time — all while providing the end-to-end visibility the Chefkoch operations team needed.\n",[1865],{"quoteText":1866,"author":1867,"authorTitle":1868,"authorCompany":1837},"We have one tool with a global overview over the projects. We can easily see everything.\n","Roman van Gemmeren","Senior Systems Engineer",[1870,1873,1876,1879],{"header":1871,"text":1872},"The largest food platform in Europe with a recipe for every occasion","[Chefkoch](https://www.chefkoch.de/){data-ga-name=\"chefkoch\" data-ga-location=\"body\"} was built on the belief that cooking and eating together makes us happier. Recipes can tell stories and pass down traditions. Chefkoch is now the largest food platform in Europe, with a mobile app boasting more than 350,000 recipes and a community of over 22 million users a month. Users can customize Chefkoch for their preferences, like vegetarian, paleo, or low carb, and find a tried-and-true recipe to match their tastes. Users can rate recipes, share them with friends, watch how-to videos, and be inspired to try something new. The right recipe creates shared moments of happiness, and Chefkoch wants to provide a user-centric experience so that their platform can be personalized and enjoyed by everyone — from beginners to pros.\n",{"header":1874,"text":1875},"Fragmented, manual toolchain","Chefkoch has a recipe ready for any occasion, but finding the right solutions to serve up their food platform experience proved to be much trickier. “We had no versioned deployments, no Git at all. There was a lot of manual work,” said Roman van Gemmeren, senior systems engineer at Chefkoch. “We had no real insight into how the infrastructure was working or performing.” Van Gemmeren leads the operations team that maintains the infrastructure and developer tools, and provides access to services like Kubernetes cluster management and monitoring.\n\nChefkoch’s operations team was managing a complicated ecosystem with processes that were largely manual. Chefkoch was using Git with BitBucket before migrating to GitLab, but the Atlassian toolstack they had (Bitbucket, Bamboo) didn’t provide the metrics they needed for monitoring, and also didn’t integrate with Kubernetes. To properly support the development team and provide controlled deployments, Van Gemmeren’s team would need:\n\n- A streamlined developer workflow with better project visibility\n\n- Support for key integrations, like Kubernetes, Terraform, Docker, and JIRA\n\n- Autoscaling capabilities with less maintenance\n\n- Repository organization and CI/CD\n\n\nTo start, Van Gemmeren knew that the team wanted Git repositories with better naming conventions. Even something like a repository path could alleviate a lot of the confusion in development. “We wanted more visibility and kind of a global administration possibility,” Van Gemmeren said. “Before, we had a repository name, XYZ, and Docker image, ABC, and there was no relation between those tools.” Van Gemmeren considered GitHub but greatly preferred something self-managed, rather than a public solution. For CI/CD, Van Gemmeren looked at Jenkins as a replacement for Bamboo, but decided that a plugin environment was going to be way too complex to properly maintain.\n",{"header":1877,"text":1878},"GitLab is the secret ingredient","GitLab’s DevOps platform with built-in repositories and CI/CD provided the end-to-end visibility the Chefkoch operations team had been looking for. GitLab also provided a seamless interface with simple access controls. “With Bamboo, we had to provide credentials for every project. Separate credentials, even. And with GitLab, we can just configure some clusters and provide the credentials at the group level,” said Van Gemmeren.\n\nFor Van Gemmeren and his team, having visibility into what was happening in projects had been an ongoing issue. With so many tools spread out and not integrating with each other, it was difficult to know when issues were resolved. GitLab’s merge requests were able to remedy that problem by providing insight into discussions and logging actions through commits. The GitLab repositories and smooth pipelines made it easier for developers to know which Docker image belongs to which repository. The app development team experienced the greatest improvement to their processes — seeing almost 80% faster deployments. “The backend for frontend services can now be built and deployed in a very simple way by the app developers. That was not possible with Bamboo,” said Ingo Reinhart, lead developer (Android/iOS) at Chefkoch. Merge requests also improved code quality and allowed for better collaboration. “There are no more hurdles because of the CI interface. The app team is very satisfied with GitLab,” said Reinhart.\n\nGitLab’s integrations with Kubernetes, JIRA, and Grafana means that the operations team can now have oversight into projects that just weren’t possible before. “Right now, we have the metrics in GitLab for the project, specific ones, and more like a global overview in the Grafana stack that we maintain,” Van Gemmeren said. The operations team can reference specific GitLab commits and see when performance degraded or improved. It is worth mentioning that the Android app is no longer built by individual developers locally on the developer’s computer and is loaded manually into the Play Store. A developer can now do this automatically after a merge. We have thus increased compliance and reliability from zero to 80%.\n",{"header":1880,"text":1881},"A recipe for success","Chefkoch has the scalability they need with GitLab Runners and, without waiting for builds, Van Gemmeren estimates that the team is deploying to production 30% faster. GitLab’s Terraform integration means that deployments are managed from the CI/CD pipeline. GitLab has enabled them to adopt everything as code, from pipelines to infrastructure, and reduce the manual load.The streamlined developer workflow means that everyone, from dev to ops, has more visibility into projects. “Backend services, like an API gateway, can now be maintained and deployed by a mobile application developer,” said Van Gemmeren. “They’re all using the same tools and have the same UI experience.”\n\nHaving GitLab as the single source of truth has been beneficial for the Chefkoch team because it also allows them to identify a single source of managing test failures in their application development. The new workflow has helped the team shift left and they are now detecting vulnerabilities and bugs 30% earlier in the software delivery lifecycle. Most tests were manual before they adopted GitLab, but now the operations team is using automated tests in their CI/CD pipelines in conjunction with Trivy for container scanning.\n\nOne unexpected benefit of GitLab was how it improved the onboarding experience for new developers, trimming onboarding from two days to just two hours. With GitLab’s extensive documentation, new developers can adopt a more self-serve model and get up to speed quickly. Van Gemmeren estimates that developers have freed up about 20% of their time, now that they’re not having to focus so much on maintenance. Developers can now focus on developing code — not maintaining tools. “It’s a lot less time-consuming,” said Van Gemmeren.\n",{"template":950,"size":36,"region":106,"industry":91},"content:en-us:customers:chefkoch.yml",{"_path":1885,"content":1886,"config":1930,"_id":1931},"/en-us/customers/chorus",{"name":1887,"logo":1888,"hero":1889,"heroImage":1890,"benefits":1891,"industry":89,"employeeCount":1902,"location":1903,"solution":913,"headline":1904,"summary":1905,"quotes":1906,"content":1916,"contributors":1281,"stickyBenefits":1929},"Chorus","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745517967/cual5xyggisqiz6jeea7.png","Building the future of conversation intelligence","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518434/xyttkceesdkwaibt9yz3.png",[1892,1896,1899],{"metric":1893,"config":1894},"Enhanced collaboration",{"icon":1895},"Collaboration",{"metric":1897,"config":1898},"Improved testing",{"icon":1580},{"metric":1900,"config":1901},"Faster production cycles",{"icon":902},"110","San Francisco, Tel Aviv, and Boston","Chorus.ai offers sales teams an easy way to capture and summarize call notes so they can focus on really listening to customers.","GitLab’s single tool for the software development lifecycle helps Chorus.ai capture the power within sales calls.\n",[1907,1912,1914],{"quoteText":1908,"author":1909,"authorTitle":1910,"authorCompany":1911},"One tool just makes life easier. It's just less stuff to manage. When you use too many tools you end up having one thing over here and other items over there. This leads to struggles around keeping tasks together and keeping everything up to date.\n","Russell Levy","Co-founder and Chief Technology Officer","Chorus.ai",{"quoteText":1913,"author":1909,"authorTitle":1910,"authorCompany":1911},"We wanted something that was integrated and fully thought through. GitLab actually thinks about every feature built and how it fits in with the rest of the platform. When you see how everything is very well-connected in the system, it’s really, really powerful.\n",{"quoteText":1915,"author":1909,"authorTitle":1910,"authorCompany":1911},"It's amazing what you guys have done with Auto DevOps with just a few lines in a GitLab CI file. It has really helped us to shorten lead time, which has positively affected every single metric we measure. It means that we're having smaller pushes to production and are able to do more of them. We're having fewer failures in production because we have ways to test the application.\n",[1917,1920,1923,1926],{"header":1918,"text":1919},"From dream to reality","Chorus.ai was built out of the fire of three dreamers who were passionate about forming a new company. After watching the market and seeing the rise of smart home gadgets and new machine learning capabilities, the trio decided to build software around analyzing conversations. Focusing on conversations around sales, Chorus.ai enables account executives to focus on what is actually being said and respond appropriately — instead of taking notes.\n\nThey developed Chorus.ai as a conversation intelligence platform. It records, transcribes, and analyzes customer conversations to help sales teams and support teams. The platform offers transcription and AI-based analytics as well as sharable snippets to easily share conversational insights with other team members.\n",{"header":1921,"text":1922},"Creating a bold new development process","How do you design a build process from scratch? For Chorus, the founders relied on previous knowledge and experience to decide on a single development tool. They decided they didn’t want a toolchain comprised of disparate tools and plugins, so they searched for a DevOps solution to meet their needs.\n\nWith GitLab, the teams are able to focus on development instead of processes and systems. Using GitLab has also increased the collaboration between teams. “Life is just so much easier for product engineering and anyone who wants to interact with product engineering because they can just do it through GitLab,” Levy explained.\n",{"header":1924,"text":1925},"A single tool to integrate development teams","Chorus.ai selected GitLab because the team was impressed by the integration the application offers. Levy says that GitLab is the only product on the market that offered a true integration and made every process easy.\n\n“The only other company that has anything that’s close to GitLab in our view was Atlassian, and they may offer all those tools under the Atlassian company, but they’re not integrated. So you buy Bitbucket, and it somehow ties up with this one. Then you have to deal with pricing on each one, users for each one … the whole thing, it’s just a bunch of products that are stitched together,” Levy explains.\nDuring a recent audit for SOC2 compliance, the auditors said that Chorus had the fastest auditing process they have seen and most of that is due to the capabilities of GitLab. Levy explained that it was easy to write a script and get the information from the API to make the audit easier.\n",{"header":1927,"text":1928},"Speed, security, and Auto DevOps","Because Chorus was developed with GitLab from an early stage, they conquered common build challenges that many companies experience. They made the conscious decision to keep everyone collaborating with a single tool to avoid the use of plugins and disparate tools. Within GitLab, Chorus is able to increase development velocity by beginning sprints in GitLab as epics. Teams use issues and boards to improve their capacity planning. For releases, teams run their pipelines using GitLab CI/CD.\n\nChorus has also shortened its feedback loops by using the SAST and DAST capabilities within GitLab. “We started using the GitLab security dashboard a month ago. It has been very beneficial to see if there are new security issues that are coming up. It really helps the developers. We can now show them why their code and truly show them why this is an issue, and how it could be exploited,” Levy said.\n\nThe team at Chorus also credits GitLab for helping them improve their feature cycle analytics. By having test results, security reviews, performance tests, the code climate and everything in the merge requests, Chorus has been able to move quickly. Chorus is also utilizing the Auto DevOps capabilities of GitLab to deploy to their AWS S3 servers. GitLab Auto DevOps automates CI/CD configuration to simplify the execution of their development.\n",{"benefits":1281},{"template":950,"size":40,"region":102,"industry":91},"content:en-us:customers:chorus.yml",{"_path":1933,"content":1934,"config":1984,"_id":1985},"/en-us/customers/connect-i",{"name":1935,"logo":1936,"hero":1937,"heroImage":1938,"benefits":1939,"industry":1950,"employeeCount":1951,"location":1952,"solution":975,"stats":1953,"headline":1962,"summary":1963,"quotes":1964,"content":1969},"Connect-i","https://res.cloudinary.com/about-gitlab-com/image/upload/v1749138220/dwzfmawbf2kyl5akb7r4.png","Connect-i achieves 40% faster development, enhanced security with GitLab","https://res.cloudinary.com/about-gitlab-com/image/upload/v1749138352/cn3psappkeedefpa2ubj.png",[1940,1943,1947],{"metric":1941,"config":1942},"Eliminated toolchain",{"icon":902},{"metric":1944,"config":1945},"Reduced deployment issues",{"icon":1946},"AgileLarge",{"metric":1948,"config":1949},"Automated processes",{"icon":212},"Information Technology","20","Préverenges, Switzerland",[1954,1956,1959],{"value":1750,"metric":1955},"reduction in costs",{"value":1957,"metric":1958},"2 hours","saved per developer per day",{"value":1960,"metric":1961},"30-40%","faster development and deployment","Connect-i develops and maintains Opigno, a learning management system that’s focused on creating, managing, and measuring training courses. The e-learning system offers personalized social learning, blended learning, and gamification options. When it came time to update their signature product, they turned to GitLab’s end-to-end platform.","The Swiss business, which serves customers ranging from government agencies to large enterprises, had been struggling with fragmentation, and the inefficiencies, delays, and inconsistencies that manual tasks were causing. By adopting GitLab, they transformed their DevSecOps capabilities and are now building the latest version of Opigno more efficiently, securely, and collaboratively. With just two engineers handling all DevSecOps and security work for their 20-person company, they faced challenges familiar to development teams everywhere — toolchain complexity, security integration, and compliance requirements. For Connect-i, solving these universal challenges wasn't just about improving efficiency; it was essential for staying competitive in a market where their software serves enterprise clients worldwide.\n",[1965],{"quoteText":1966,"author":1967,"authorTitle":1968,"authorCompany":1935},"The quality of our software has improved significantly, Having everything — code, issues, CI/CD, and testing — in one place helped us speed up our work by 30% to 40%.\n","Axel Minck","CEO",[1970,1972,1975,1978,1981],{"text":1971},"[Connect-i](https://www.connect-i.ch/en), founded in 2008, operates in the highly competitive learning management system market but also offers advanced cyber security services, like penetration testing, for multinational companies, along with Drupal web design and development. Opigno, their flagship learning management system and main revenue driver, is used by more than 10,000 businesses and more than 1 million daily users around the world.",{"header":1973,"text":1974},"Speed meets security: Rebuilding Connect-i's core product","It’s business critical to the organization to keep Opigno not only running smoothly but updated with the latest features and meeting customer needs.\n\nStanding in their way was a [fragmented toolchain](/blog/too-many-toolchains-a-devops-platform-migration-is-the-answer/) that caused disjointed processes and limited visibility into their CI/CD pipelines. With just two engineers supporting a platform used by millions, Connect-i’s DEvSecOps team was overwhelmed by time-consuming manual tasks. Developing and deploying updates was slow, tedious, and error-prone — making it difficult to keep their enterprise platform competitive and their premier product up to date. For a company delivering mission-critical software to global organizations, this gap between capabilities and expectations had to be rectified.\n\nIn 2022, they adopted the Community Edition of GitLab's DevSecOps platform, switching from a complicated patchwork of tools that included the Packagist repository, Bitbucket, and Jenkins. This consolidation into a single platform immediately streamlined their development processes and eliminated integration headaches.\n\nThen in 2023 they upgraded to GitLab Premium to take advantage of even more features and capabilities, like customer support services, strengthened security and control features, and additional project management functionality. That move enabled them to increase efficiencies, eliminate wasted time, and ensure security is a primary focus from the very beginning of development. It also allowed them to make a 30% reduction in their security workload.\n\n“The quality of our software has improved significantly,” says Axel Minck, CEO at Connect-i. “Having everything — code, issues, CI/CD, and testing — in one place helped us speed up our work by 30% to 40%. It’s [made collaboration easier](/blog/5-ways-collaboration-boosts-productivity-and-your-career/), reduced errors, and allowed us to release updates quickly, especially for our enterprise version, where quality and speed really matter.”\n\nConnect-i used GitLab to create new features in two successive versions of Opigno. Now they are working on another major version release, building it from the ground up with the DevSecOps platform. “We’re managing the full development lifecycle in GitLab — everything from code development to reviews, quality control, documentation, and customized CI/CD pipelines with linting code analysis and testing,” adds Minck. “GitLab has been essential to transforming this product, giving us full control over every aspect of development and ensuring it is high quality.”\n\nHe also notes that they’re building software faster and more efficiently, since manual tasks that used to take days now are done within hours thanks to automation. And they’re also more confident that the code is more secure with built-in container scanning, Static Application Security Testing and Dynamic Application Security Testing.\n\n“Without a doubt, centralizing our workflows in GitLab has eliminated unnecessary context switching and toolchain overhead,” says Minck. “It all plays a major role in enabling us to catch vulnerabilities early — both in the code and the infrastructure. That’s critical for us and our enterprise clients, who expect secure, compliant software.”",{"header":1976,"text":1977},"Getting a big impact with a small team","These efficiencies — created with automation, built-in security, and streamlining — are just what a small business needs to add muscle to a two-person team, allowing them to leverage limited resources and deliver an outsized impact.\n\n“With a really small team, GitLab enables us to do more with fewer hands,” says Minck. “That’s absolutely critical. With the platform, routine tasks, like testing, deploying, and scanning, are automated so everything runs more smoothly and takes less time and effort. It allows us to do more with fewer resources, enabling us to meet customer expectations, better compete against larger businesses and expand our market reach. It gives a [small business](/small-business/) more muscle.”\n\nBy getting rid of previous problems like context switching, fragmentation, and the management challenges their old toolchain was causing, Connect-i’s DevSecOps team is saving time and expenses. Actually, they saved more than 1,400 hours of development time in the past one and a half years.\n\n“With GitLab bringing everything into a single, unified platform, we’re no longer spending time doing the same manual tasks over and over, says Minck. “Now our team can focus more on what actually matters — writing code, improving security, optimizing performance, and delivering features faster. We're also investing more time refining our DevSecOps practices and automating compliance tasks, which directly benefits our internal operations and client satisfaction.”",{"header":1979,"text":1980},"Growing compliance muscle: Meeting enterprise standards","With GitLab's built-in security capabilities, automation, and documentation, Connect-i's small team can implement enterprise-grade security and compliance practices that normally would require a dedicated team. [Remaining compliant](/blog/meet-regulatory-standards-with-gitlab/) with a myriad of certifications and standards is a big job for a company of any size — even large enterprises — so making this job easier and more efficient is a huge boost.\n\nConnect-i works with enterprise clients that expect the organization and its software to remain in accordance with government practices and mandates, like ISO 27001, an internationally recognized standard for managing sensitive company information, like financial data, intellectual property, and employee details.\n\nGitLab’s platform — with integrated security checks, access control, compliance dashboards, and audit trails built directly into workflows — helps Connect-i remain compliant. And audit logs and automated evidence collection help the organization easily and quickly prove that it has been compliant.\n\n“GitLab helps us enforce policies, manage access, and generate the necessary audit trails that make aligning with international standards easier. It would have been difficult to manage this manually,” adds Minck, noting it gives them the high level of transparency and traceability their clients demand. “Making compliance efforts straightforward and efficient have notably reduced stress on our team and improved productivity, directly contributing to overall job satisfaction and happiness.”",{"header":1982,"text":1983},"Breaking down development silos to power teamwork","Effective collaboration is essential for any software development team, whether the team is made up of two people or 2,000. It’s also a key way to not only keep developers happy but to be able to retain and attract top talent.\n\nHaving a whole different level of transparency, along with built-in tools for issue tracking, planning, and documentation have helped bridge the gap between developers, security engineers, and even project managers. And this goes beyond work on Opigno, affecting all of the software the organization is creating.\n\nUsing GitLab’s DevSecOps Platform, Connect-i also has fostered teamwork not only among its engineers, but also between people in different departments. While the organization’s core DevSecOps team is small, they collaborate with the product team, project managers, sales, and even external partners. GitLab has streamlined how all of these contributors participate in the development process, allowing others to contribute and ensuring developers know exactly what is needed.\n\nAnd that has made a big difference not just for creating software but for the company as a whole.\n\n“The quality of our software has improved significantly and part of that is directly related to our ability to collaborate,” says Minck. “GitLab's unified platform has made it much easier for developers to collaborate on code, track progress, review merge requests, and share feedback — all in one place. Now everyone has visibility into the pipeline, which encourages more open and efficient communication.”\n\n“It's had a big impact on cross-functional teams,” the CEO says. “With better collaboration, decisions are made faster, blockers are resolved more quickly, and there's a shared understanding of priorities. That leads to more predictable development cycles, fewer surprises during deployment, and better coordination when pushing updates to production.”\n\nThat collaboration, along with improved efficiency, security, and ease of compliance, is benefitting Connect-i as a whole.\n\n“It all means better software, faster delivery, and happier teams,” says Minck. “It allows us to react more quickly to client needs, reduces rework, and strengthens trust between departments. Ultimately, that boosts our overall productivity and helps us deliver more value to our clients. In a space where clients expect both innovation and trustworthiness, GitLab helps us meet those expectations and stand out from the competition.”",{"template":950,"size":36,"region":106,"industry":91},"content:en-us:customers:connect-i.yml",{"_path":1987,"content":1988,"config":2032,"_id":2033},"/en-us/customers/conversica",{"name":1989,"logo":1990,"hero":1991,"heroImage":1992,"benefits":1993,"industry":89,"employeeCount":2002,"location":2003,"solution":913,"stats":2004,"headline":2012,"summary":2013,"quotes":2014,"content":2019},"Conversica","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745517929/itkdofdnvyo3nx7wfce7.svg","Conversica leads AI innovation with help from GitLab Ultimate","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518413/hr4s3apbmduclrv8wrwk.jpg",[1994,1998,2000],{"metric":1995,"config":1996},"Transparent configuration",{"icon":1997},"ConfigureAlt2",{"metric":1524,"config":1999},{"icon":1195},{"metric":1293,"config":2001},{"icon":1295},"1,600\n","Foster City, CA",[2005,2007,2009],{"value":1308,"metric":2006},"pipeline coverage",{"value":1807,"metric":2008},"increase in CI/CD pipelines",{"value":2010,"metric":2011},"1.5x","increase in pipeline implementations","The Conversica engineering team was looking for a scalable single tool for CI/CD.\n","GitLab Ultimate provides Conversica developers with the latest in CI/CD capabilities.",[2015],{"quoteText":2016,"author":2017,"authorTitle":2018,"authorCompany":1989},"GitLab is a modern tool with a consolidated view of the toolchain and it provides us with that desired platform for a coherent implementation.","Rob Fulwell","Engineering Manager",[2020,2023,2026,2029],{"header":2021,"text":2022},"Leading the world in AI","Conversica is a leader in artificial intelligence for business and the only provider of AI-driven lead engagement software for marketing and sales organizations. Used by more than 1,500 companies worldwide, [Conversica](https://www.conversica.com/) provides SaaS in order for users to carefully craft campaigns to attract and retain customers.",{"header":2024,"text":2025},"The detriment of disjointed tools","Conversica’s development team was using TeamCity for CI/CD, Quay.io for Docker image registry, and GitHub for source control. This created a cobbled-together approach, where the tools were somewhat consolidated around GitHub, but not enough to be a controlled environment. The development team was disgruntled and struggled with the way they could access the tools successfully. “In TeamCity, it's a kind of internal XML configuration that TeamCity stores in this Byzantine way that's very opaque to developers,” said Rob Fulwell, engineering manager at Conversica. “Then they access it through the UI only, which is not the way developers like to work. They like to work on text files.”\n\nThe disjointed workflow was ultimately too slow for their business needs. “We were getting pressure from the sales and marketing folks to deliver features more quickly,” said Fulwell. “In the past, we had to focus on delivery, perhaps to the detriment of accruing this technical debt.”\n\nThe team was increasingly losing time troubleshooting pipeline failures instead of focusing on business differentiating actions. “Also, we were concerned about being able to implement future requirements around security and license scanning across our systems,” Fulwell said.",{"header":2027,"text":2028},"Creating small software projects","After subject matter experts performed research upfront, Conversica decided to mandate GitLab across the engineering teams and successfully migrated within three months. One of Conversica’s requirements in the decision-making process was that the selected tool provides clear documentation to ease migration problems. “We actually made sure that the documentation was some of the best around. And without that, I think that would have given us real pause in making that decision to move to another toolset,” Fulwell said.\n\nFulwell’s team acted as the consultants for the other engineering teams as they were learning how to implement their pipelines on GitLab. “We did a lot of pairing with developers on other teams, and in concert with them, we put together the pipelines,” Fulwell said. “We made sure we are upholding the standards that we have for what goes into a good pipeline and then have the right progression of automated testing. That's how we managed to roll it out across the whole team.”\n\nThey chose [GitLab Ultimate](/pricing/ultimate/) to get the most out of the tool without any limitations. “By self-hosting, meaning that if we need to hammer some APIs internally and spin up infrastructure to make that possible and we're able to do that now,” Fulwell said.\n\nWith GitHub, they had experienced some ‘throttling’ that had developers waiting around and unable to work. Developers were capable of accepting more calls, but they previously didn’t have the tier to allow that level of production. With GitLab Ultimate, developers are no longer idle.",{"header":2030,"text":2031},"Modern UI, transparent pipelines, increased scaling capabilities","One clear benefit of moving to GitLab is the ability to visualize the pipeline from end-to-end. Conversica recently had to do an emergency revert for something that was deployed over a weekend. In GitLab, they were able to see the specific commit that was deployed in that environment. \"The first time I did it, it kind of blew me away. I could get from this environment and literally click once to the head of master to another environment,” Fulwell said. While it was possible to emergency revert TeamCity and GitHub, it wasn’t in one click. It required several steps to find the correct commit. “So getting through basically end-to-end on the pipeline when you're doing that kind of research for a bug or what have you is so effortless with GitLab, which is a huge benefit,” he said.\n\nThe UI is cleaner and easier for developers to understand than their previous tooling workflow. The [end-to-end integration](/solutions/continuous-integration/) with source control through CI/CD to deployment provides efficiency for the development team that the previous group of tools couldn’t provide. They can now communicate more efficiently across the engineering teams, explore each other’s projects, and successfully collaborate. Deployment is simplified and can happen at a faster rate because there is trust in the pipeline delivery. Security is now occurring at the code level — something that Conversica previously didn’t have.\n\nConversica is deploying from ECR to EKS to the self-managed GitLab Ultimate instance. The company isn’t yet using a Kubernetes integration but is exploring ways to accomplish this. “The move to GitLab felt like a natural fit in terms of scale and reliability and security,” Fulwell said. “It's definitely something that worked well in terms of us being able to implement and get it right on top of AWS systems that we already understood.”",{"template":950,"size":40,"region":102,"industry":91},"content:en-us:customers:conversica.yml",{"_path":2035,"content":2036,"config":2087,"_id":2088},"/en-us/customers/cook-county",{"name":2037,"logo":2038,"hero":2039,"heroImage":2040,"benefits":2041,"industry":2050,"employeeCount":2051,"location":2052,"solution":2053,"stats":2054,"headline":2064,"summary":2065,"quotes":2066,"content":2071,"contributors":1281},"Cook County Assessor’s Office","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745517968/k6muk7bqd20auqcwcrqb.svg","How Chicago’s Cook County assesses economic data with transparency and version control","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518435/apnckwrkiyzn6tgbqski.jpg",[2042,2044,2047],{"metric":1843,"config":2043},{"icon":1845},{"metric":2045,"config":2046},"Improved version control",{"icon":902},{"metric":2048,"config":2049},"Government transformation",{"icon":259},"Government","270","Chicago, IL","GitLab Silver",[2055,2058,2061],{"value":2056,"metric":2057},1.8,"million properties assessed",{"value":2059,"metric":2060},31,"repositories, more than 1,400 commits",{"value":2062,"metric":2063},"$270","billion estimated market value","Cook County’s Assessor’s Office wanted to create a more transparent digital platform for property owners to view and understand how assessments are established.","With GitLab, the Office has been able to provide transparency and accountability with real-time data in a single source of truth.\n",[2067],{"quoteText":2068,"author":2069,"authorTitle":2070,"authorCompany":2037},"With GitLab, I can produce research and show people in the office. They suggest changes to the research and I can make those changes without having to worry about version control and saving my work. One repository makes it so that I can focus more on the actual work and less on the mechanics of working.\n","Robert Ross","Chief Data Officer",[2072,2075,2078,2081,2084],{"header":2073,"text":2074},"Assessing property for Cook County","Chicago’s Cook County Assessor’s Office (CCAO) works to predict the value of 1.8 million real estate properties in the area, including residential and commercial properties. The Assessor’s Office is headed by Assessor Fritz Kaegi and a staff of about 240 people who serve the public to establish a uniform, fair, and accurate property assessment.\n\nThe values set on real estate are used as a basis for levying taxes and determining property tax distribution among taxpayers. The CCAO reassesses properties every three years and evaluates one-third of the county each year. In any given year, they’re reviewing between 400,000 to 600,000 properties. The office leverages property characteristic data from residential sales to create the updated projected market value.\n",{"header":2076,"text":2077},"Lacking data management and version control","Record keeping is an essential part of the CCAO. Legacy scripts, the inability to integrate older software, and lack of assistance from previous officeholders presented significant challenges to ensuring an uninterrupted, timely reassessment process. On top of that, records were primarily paper-based and only recently have software development programs been used. The software development scripts in place had zero version control and no commentary, so understanding the data after the fact was nearly impossible.\n\nThe CCAO wanted to implement replicable and reportable software algorithms in order to have a single source of truth for future data. Ideally, the tool would be agile and dynamic in a rapidly changing environment, but would also be discernible to those with a similar technological background. For those who did not, the data would be used as the basis of an easy-to-understand reporting structure.\n\nThe goal was to create a more [transparent digital platform](https://about.gitlab.com/blog/creating-a-transparent-digital-democracy/) for property owners to view and understand how assessments are established. This would provide stakeholders with comprehensive data about assessments in a way that previously didn’t exist.\n",{"header":2079,"text":2080},"Creating a single source of truth and transparency","The current Cook County Assessor, Fritz Kaegi, and his team wanted to restore trust in how the government office operated and believed transparency was the basis for rebuilding that trust.\n\n“[Our office] ran on a platform of fair, ethical, and transparent assessments. In order to achieve that third pillar, we absolutely have to publish the code that we use to value (a) house,” said Robert Ross, chief data officer at the Cook County Assessor’s Office. To change the narrative, the team adopted GitLab when they entered office.\n\nThere are a number of variables in assessing property values. Code variables are central to Cook County’s assessment, which makes it imperative that the data is made public. Ross and his team now publish all the code variable information in GitLab, making it accessible for public consumption.\n\nCook County has established a single source of truth that can be updated in real time. GitLab manages the code transparently and requires little maintenance from data officers.\n",{"header":2082,"text":2083},"Changing the way government operates","The CCAO did an end-to-end audit of the legacy valuation process and replicated all the previously manual processes. In doing so, they improved the process where they saw errors and now publish all the code in GitLab.\n\nThere are four repositories, with over 1,400 commits. People can now download the data and [run the code](https://about.gitlab.com/blog/challenges-of-code-reviews/) off the data. The office has had at least 6,700 people download these large datasets. The data officers use GitLab’s Git history, issue tracker, and milestones, and document every project in real time.\n\nProperty owners can now access and own the information that creates their home’s value. Access at this level has never been done before. “No county assessor has ever used a public-facing repository for their work,” Ross said.\n\nEstablishing governing policies has primarily always been done behind closed doors. Cook County is using GitLab to take an experimental step towards open source government policies.\n\nThe level of transparency now includes documenting any mistakes and fixes. The CCAO openly tracks mistakes they have made by creating issues that showcase the errors and then commits to publicly announce how these errors will be corrected. “Accepting mistakes and righting them completely diffuses battles and is no longer a political issue,” Ross added.\n\nData is vital to predicting values and forecasting economic behaviors. At the CCAO, data scientists are part of the team that creates public policy, in that they follow the data to find physical evidence for planning. “We are publishing code that is the basis of your assessment. We think your home is worth $500,000 and if you want to know why, here is the code that produced that estimate,” Ross said.\n",{"header":2085,"text":2086},"When the world changes, how do you respond?","The team calculated the 2020 residential property assessments in January 2020, unaware of the impacts that COVID-19 would have on a global scale. By February, reassessments had been completed and sent to residents in four townships. In March, Governor J.B. Pritzker declared a state of emergency for all counties in Illinois as a result of the virus. The declaration had an immediate impact for the CCAO. The office had two choices:\n\n- Do nothing and proceed as planned with residential values and mail out assessments.\n- Do something and adjust residential values as a result of COVID-19 impacts.\n\nAfter deciding to take action by adjusting values with [COVID-19 impacts](https://about.gitlab.com/blog/startup-covid-tracking/) in mind, the CCAO’s staff realized this problem wasn’t going to be easy to solve. Estimating market values of properties requires knowing the sales information of similar properties. Residential sales data has an inherent two-month processing lag before it is published, and the team needed up-to-date information and couldn’t wait. The stay-at-home orders also halted sales and created a lapse in data.\n\nThe team used market signals, historical knowledge that residential prices fall when unemployment rates rise, census data around the composition of workers per sector, and current unemployment data to create COVID-19 adjustments to home values. Using data around employment by industry, the team predicted where in the county the greatest impacts were going to be felt and made adjustments accordingly.\n\n“What we did was actually a challenge that every state government had to face. Policymakers across the country found themselves in a position of making a decision within the absence of all of the data that they were accustomed to usually having to make such decisions,” Ross said.\n\nIn February 2020, the local unemployment rate was 3.4%, and by April it spiked to 17.5%. GitLab repositories hosted the raw data to create the analysis around how to adjust residential valuations. The code in GitLab helped them generate a vector of adjustments to make. The CCAO is able to stay up-to-date on property assessments with version control, a single source of truth, and a transparent code management system.\n",{"template":950,"size":40,"region":102,"industry":79},"content:en-us:customers:cook-county.yml",{"_path":2090,"content":2091,"config":2139,"_id":2140},"/en-us/customers/credit-agricole",{"name":2092,"logo":2093,"hero":2094,"heroImage":2095,"benefits":2096,"industry":69,"employeeCount":2106,"location":2107,"solution":2108,"stats":2109,"headline":2119,"summary":2120,"quotes":2121,"content":2126,"contributors":1281},"Crédit Agricole","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745517970/xgnjx8vijxd7v85kpjqc.png","How Crédit Agricole Corporate & Investment Bank (CACIB) transformed its global workflow with GitLab","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518436/da73qcb1bcglu7vzfc6k.jpg",[2097,2099,2102],{"metric":1847,"config":2098},{"icon":902},{"metric":2100,"config":2101},"Cross-company collaboration",{"icon":1295},{"metric":2103,"config":2104},"Ease of integration",{"icon":2105},"ContinuousIntegration","8,325","37 locations (Europe, Asia-Pacific, Americas, Africa Middle-East)","GitLab Enterprise",[2110,2113,2116],{"value":2111,"metric":2112},"50-75%","Time to delivery saved",{"value":2114,"metric":2115},"2,000","Organic users",{"value":2117,"metric":2118},"\u003C1 day","To create a new application","Worldwide banking institute, Crédit Agricole, adopted GitLab for SCM, but found it offered automation and improved efficiency.","Through user preference, CACIB adopted GitLab for source code management (SCM), robust integration management, and seamless automation.\n",[2122],{"quoteText":2123,"author":2124,"authorTitle":2125,"authorCompany":2092},"Switching to GitLab made us go from several days to create a new application to just a few hours.\n","Sedat Guclu","Head of Software Factory and Devops",[2127,2130,2133,2136],{"header":2128,"text":2129},"French banking leader","Crédit Agricole CIB is the corporate and investment banking arm of Crédit Agricole Group, the twelfth largest banking group worldwide in terms of tier 1 capital (The Banker, July 2019). Nearly 8,000 employees across Europe, the Americas, Asia-Pacific, the Middle East and Africa support the Bank’s clients, meeting their financial needs throughout the world. Crédit Agricole CIB offers its large corporate and institutional clients a range of products and services in capital markets activities, investment banking, structured finance, commercial banking and international trade. The corporate identity of the financial institution is called Crédit Agricole CIB, and there are teams in approximately 37 countries, including the division of information systems of Crédit Agricole CIB called Global IT (GIT).\n",{"header":2131,"text":2132},"Improving worldwide workflow efficiency","[Crédit Agricole CIB]( https://www.ca-cib.com/) was using centralized source code management solutions since 2011. Over time, the need for alternate options that were able to increase performances, enhance user experience and flexibility emerged, particularly for development teams spread in different areas such as Paris, London, or Singapore.\n\nOn top of that, branch management wasn’t standardized, and elements that weren’t source code were being stored in repositories, which had an impact on performances and on user experience. “We primarily needed to manage our solutions globally. Everyone uses Git, whether they need a decentralized SCM or not, it is such a predominant tool in the market that it is way easier to onboard new people when using such industry standards,” said Nicolas Jautée, Software Factory and DevOps Expert.\n\nThere was a lack of native integration with the tooling systems, and also amongst the teams. The DevOps teams manage the platform element and create access in order for teams to then manage their own content, creating as many repositories as necessary for code storage without admin constraint. One of the reasons Crédit Agricole CIB was looking for a new source code management platform was for integration with autonomy. “The goal is to have teams that can be independent and responsible within their perimeters with our support and our expertise (if needed), while being able to go as far as possible on their own to be reactive within their businesses,” Jautée said.\n",{"header":2134,"text":2135},"GitLab spreads through word of mouth","Crédit Agricole CIB intended to adopt an implementation of Git platform, which led to a comparative study and proof of concepts between various solutions. “At that time, we looked at GitLab and noticed that it offered great functionalities. In terms of implementation, it was more relevant and easier to manage than black box platforms,” Jautée said. Moreover, other entities within the Crédit Agricole group were already using GitLab with success.\n\nPreviously, Crédit Agricole CIB had done a couple of [SCM](/solutions/source-code-management/) top down migrations over time. However, with GitLab they did not want to force teams to migrate: “Consequently, for GitLab, we let word of mouth and user preference do the job. The fact is that the licenses we bought the first year were used within less than 9 months. I think we had to purchase more licenses even before the end of the first year even though we had not done any official communication on this tool; we only let viral adoption take its course,” Jautée said.\n\nContrary to what is customary, GitLab was launched from the bottom up, promoted initially from the project teams. Infrastructure teams also helped by testing functionalities and documentation. The bottom-up building and viral distribution model resulted in a rapid adoption rate. “People who really wanted to use this tool knew why they liked it; we didn’t launch a migration campaign imposed by our top management. So far, we haven’t found it necessary to do so, since projects have been coming in naturally and users saw the benefits. This is to the point where today, we provide IT for IT, since that’s our job, but we quickly found ourselves in a situation where the tool is exceeding the initial perimeter we anticipated,” said Sedat Guclu, Head of Software Factory and Devops.\n\nWith previous solutions, they had to take care of all the administrative steps, adding users, maintaining logins, etc. The process was hard to manage and time consuming, causing lengthy delays for those using it. One priority was to free up developer time with a self-service solution. Consequently, GitLab provided significant cost savings that they hadn’t previously planned on. “The community-based solution, with unlimited and free use, enables us to create documentation and tutorials, make POCs, prototypes and inner source development, to which we can have everyone contribute without having to worry about the number of licenses required,” Guclu said. “So, we keep a community-based platform, and we have an ‘Enterprise’ platform hosting the business code and all the automation systems, whether from infrastructure, CI-CD or other, to be able to cover both needs and better distribute the usage accordingly.”\n",{"header":2137,"text":2138},"Exceeding business application expectations","“GitLab is much more than a mere source manager. There is a whole ecosystem around it: integrated task management, integrated CI, etc., which is totally absent from our previous solutions. These were the primary aspects that motivated our initial approach,” Jautée added.\n\nA standout benefit of GitLab is the ability to integrate it into the existing environment. It is simpler for the teams to use a tool that can be installed and mastered quickly. The second benefit that stood out over its competitors is the superior functionality. The ability to not only manage code, but also delegate the long-term management of the content to perimeter managers.\n\nThe infrastructure teams now use GitLab for automation tasks, including machine building on a private cloud. Application release processes are also based in GitLab. “This isn’t exactly what we had foreseen. While our goal was to host the code for our business applications, other teams, by extension, saw additional benefits,” Guclu said.\n\nCrédit Agricole CIB now has GitLab users on both IT and the business side, using the tool for IT tasks and guidelines/how to’s. Some team members use Mermaid or LaTeX modules that integrate into GitLab to generate scientific documentation. “These are more uses that we hadn’t predicted. The viral mode went well beyond what we originally imagined, since we started with a small number of users. In the first year we had 400 users and today we have 2,000 Enterprise users, and this number is increasing daily. The growth is now self-sustaining, and that has helped us enormously, both in terms of standardization and automation,” according to Guclu.\n\nOnboarding has also been simplified and streamlined with GitLab. According to Guclu, “We might have needed five to 10 days to apply onboarding. Today, we can do it within a day. It only takes a few hours to create the space. If the person already has the authorizations, it’s almost instantaneous: We do it in minutes, then they manage the entire process and create their own repositories.”\n\nDevelopers now have the ability to perform migrations themselves with existing code. The primary benefit is that it allows them to make ‘blank’ migrations to test the retrieved code and adapt environments to be able to run in parallel with the application development. In the meantime, they can execute tests in GitLab while continuing deliveries, since a ‘hot fix’ isn’t necessary on the application. “For a migration, we went from almost a month with previous migration strategies to a few days that can be modulated according to the project priorities. It’s up to them to decide when they want to do it, how they test, and how they configure their factories at the same time, to continue delivering the existing applications while verifying that the work is done the same way in GitLab. That’s also a real comfort,” Guclu said.\n\nBy the end of 2021, Crédit Agricole CIB plans to host all the open source code within GitLab. In the three years since the adoption of GitLab, they went from zero users to 1500 without forcing it on teams. There is now a large automation chain, with over 200 runners, which means that they not only adopted GitLab for code management, but also for automation. “There are data scientists who are also using GitLab for notebooks they develop with Anaconda or similar solutions, that never used this type of solution before. They didn’t see any advantage in managing their source code in this type of tool. That is actually what they told us,” Guclu said. “Today, we see that they are also asking for this type of solution, because it allows them to collaborate more easily with other members of their team.”\n\nThe success of the adoption of GitLab within CACIB among other entities contributed to the promotion of this solution as a standard within Crédit Agricole group, with empowerment on inner and open source initiatives.\n",{"template":950,"size":44,"region":106,"industry":71},"content:en-us:customers:credit-agricole.yml",{"_path":2142,"content":2143,"config":2196,"_id":2197},"/en-us/customers/cube",{"name":2144,"logo":2145,"hero":2146,"heroImage":2147,"benefits":2148,"industry":89,"employeeCount":2159,"location":2160,"solution":913,"stats":2161,"headline":2168,"summary":2169,"quotes":2170,"content":2175},"Cube","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745517931/a8xrmb5vnsqejfq3plxv.png","European tech company Cube drives secure software with AI in GitLab Duo","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518414/ulmlykvh2fm7mkvf88ou.jpg",[2149,2152,2156],{"metric":2150,"config":2151},"Increased collaboration",{"icon":909},{"metric":2153,"config":2154},"Better value stream management",{"icon":2155},"ManageAlt2",{"metric":2157,"config":2158},"Boosted efficiency across SDLC ",{"icon":902},"40","Oldenzaal, Netherlands",[2162,2164,2166],{"value":2163,"metric":1436},"50%",{"value":2163,"metric":2165},"faster vulnerability detection",{"value":2159,"metric":2167},"hours saved per week","Cube, based in the Netherlands, is a software development company focused on designing and creating solutions, such as mobile apps, websites, and e-commerce software.","The company helps customers — in industries ranging from energy to real estate, wellness, food delivery and other markets — to digitize their businesses. A long-time GitLab user, Cube moved to adopt artificial intelligence (AI) features in GitLab Duo to increase their efficiency and speed in creating secure software.",[2171],{"quoteText":2172,"author":2173,"authorTitle":2174,"authorCompany":2144},"We’re already seeing improvements in speed and efficiency using Code Suggestions, test generation, and Chat for summaries. And we’re looking to work even more efficiently using AI across the entire SDLC.","Mans Booijink","Operations Manager",[2176,2178,2181,2184,2187,2190,2193],{"text":2177},"For [Cube](https://cube.nl/ons-bedrijf), the decision to adopt GitLab Ultimate was a game-changer, energizing the entire organization. Almost their entire workforce operates within a DevSecOps framework, focusing on efficiently creating, securing, and deploying products. Since adopting GitLab in 2019, Cube has continually sought ways to optimize their processes. In the spring of 2024, they expanded their toolkit with GitLab Duo, an AI-powered addition to their GitLab Ultimate plan, enhancing their ability to deliver software applications, websites, and manage background data for their clients.",{"header":2179,"text":2180},"Leveraging the full power of GitLab Ultimate with AI","While Cube leverages a wide range of Ultimate features — everything from automation to security scanning and value stream management — a major driver for the company to upgrade earlier this year was to be able to use GitLab Duo. Members of their DevSecOps teams had been asking to use artificial intelligence, wanting a time-saving boost from code creation and a chat assistant.\n\nFirst, Cube tried out GitHub’s Copilot tool and the JetBrains AI assistant. Neither provided the seamless AI integration that Cube’s teams required across the entire SDLC. Cube needs a single platform where all team members — from developers to test engineers, security specialists, and project managers — can use GitLab Duo.\n\n“We went with GitLab Duo because it has features, like Code Suggestions, test generation, and summarizations, that immediately were able to help us become more efficient,” says Mans Booijink, operations manager at Cube. “We wanted to use a whole package of AI features on one platform.”\n\nCube started using GitLab Duo in the spring of 2024, launching its AI journey by first using [Code Suggestions](https://about.gitlab.com/solutions/code-suggestions/) and [GitLab Duo Chat](https://about.gitlab.com/blog/gitlab-duo-chat-now-generally-available/), an AI-powered conversational assistant. From the onset, teams quickly began seeing benefits, especially for junior developers, who could use more help in developing code and making sense of long lists of requests or comments.\n\n“We’re still in the starting phase with using AI, mainly focused on Code Suggestions, but already people have said they’re happy when they see improvements, when they don’t have to do tasks manually, or they save time,” says Booijink. “When a developer has an issue with 20 or 30 comments, it can be a lot to sort through it all. But with Duo Chat, they can just ask what’s important or what has to be done. It gives them a quick overview, pointing them in the right direction and saving them time.”\n\nCube may only be getting started using artificial intelligence, but they’re already seeing results.\n\nDevelopers used GitLab Duo to improve and add new features to a mobile app for one of their long-time customers. The app enables its users to analyze and manage their daily gas or electricity use, as well as see how much of their energy was produced by solar panels.\n\nUsing Code Suggestions and code explanations, developers saved time and effort, while quickly delivering requested improvements to a valued customer.",{"header":2182,"text":2183},"Expanding use of AI across teams and the entire SDLC","Cube already is planning how they will expand their use of AI throughout their teams and the entire SDLC.\n\n“We want to use all the AI features available in GitLab Duo so we can make secure software faster,” says Booijink. “It’s important to our business. We need to be fast and efficient to stay competitive in the market. That means using AI features, like merge request summaries, vulnerability explanations, and issue and merge request summaries across the entire SDLC. We love that everything comes together in one system.”\n\nHe’s eager for his teams to begin using security-focused AI capabilities that can detect and raise immediate alerts about potential code risks before they even go into merge requests. Booijink, who is excited about GitLab’s roadmap for self-hosted features, also plans to use AI for resolving vulnerabilities.\n\n“I appreciate GitLab’s plans to expand with self-hosted capabilities,” Booijink. “We want to try everything as soon as it’s ready because that will help us save even more time and get more efficient.\n\nAnd as Cube expands the number of AI features it’s using, Booijink is looking for the number of team members using GitLab Duo to grow, as well. In fact, he expects to go from 60% of DevSecOps teammates using AI in July of 2024 to 100% by the end of the year. Right now, a few developers are still using Copilot but Booijink expects them to switch, as their teammates already have, to GitLab Duo on their own as they see that it will enable them to use AI for more than just Code Suggestions.\n\n“Yeah, suggestions are nice, but DevSecOps engineers have so much more work to do than only writing or checking code,” he adds. “It's about benefiting the full cycle. And that is where you can really gain efficiency. That will be the reason everyone switches to GitLab Duo.”\n",{"header":2185,"text":2186},"Setting up DevSecOps teams for long-term AI success","Cube has offered AI training but leaders are planning to provide even more educational opportunities as they move ahead. As employees within the company plan to continually increase their usage of artificial intelligence, both across teams and the entire development lifecycle, they see the need for training to keep pace with expansion.\n\nAnd part of that will be encouraging teammates with more experience to mentor others and collaborate as they move ahead.\n\n“We want to offer the help teams need but we’re also encouraging people to communicate with each other and support each other,” says Booijink, noting that they’ll also offer courses through [GitLab University](https://university.gitlab.com/). “We have already seen our people share knowledge about how they use AI in GitLab for Code Suggestions. We’ve done knowledge sharing on Fridays where we show examples on a big screen. We like learning from each other.”",{"header":2188,"text":2189},"Increasing security by adopting Ultimate","Being able to use GitLab Duo was just one reason Cube wanted to move from Premium to Ultimate. One of the other major reasons was to gain added automated security features like dependency scanning, both static and dynamic application security testing, and secret detection. DevSecOps teams immediately started implementing the new security features because they knew it would help them achieve their ISO 27001 certification, which is an international information security standard.\n\n“It's easier to develop secure software without losing any speed in development or deployment,” says Booijink. “We have automatic scanners that go over all new code, and we have approved rules set up in them that ensure every vulnerability is handled appropriately, no matter who is working on that code. It makes securing our software easier for us but it’s also better for our clients because they are assured that any problem is always handled the right way.”",{"header":2191,"text":2192},"Fostering collaboration within teams and with customers","At its heart, [DevSecOps is about collaboration](https://about.gitlab.com/blog/5-ways-collaboration-boosts-productivity-and-your-career/). It’s a team sport. And having a single, end-to-end platform fosters that collaboration.\n\nBooijink notes that by using epics, issues, milestones, and iterations in GitLab, their teams stay on the same page, are continuously updated about the status of projects, and are easily able to pitch in and help each other. “People use GitLab right from the beginning when they’re planning a project,” he says. “They communicate in issues about what needs to be done. And our clients and other stakeholders can be involved as guest users, working together in GitLab, asking and answering questions. It’s so much more efficient than emailing back and forth.”\n\nClients, he notes, even can start their own issues to raise concerns or requests. “It’s great to connect with clients, show them insights into what we’re doing and why we’re doing it, let them know where the process stands, and then quickly get their view on it,” Booijink adds. “It’s so much more collaborative.”",{"header":2194,"text":2195},"Monitoring value stream management","[Value stream management](https://about.gitlab.com/blog/three-steps-to-optimize-software-value-streams/), which is aimed at improving security and DevSecOps processes, has been important to teams at Cube. And they took big steps forward, using GitLab’s platform to create a value stream dashboard that notes where roadblocks and slowdowns are happening. If they can see what is happening and when it’s happening in the process, it’s much easier and faster to fix the problem.\n\nThat quick attention keeps Cube in line with their clients’ expectations.\n\n“It keeps us on top of our service level agreement response time,” explains Booijink. “When our clients start a new ticket for a project, our response time is part of the deal. By monitoring those dashboards, we can see where we stand with expected time to market. And we have to give clients regular updates about our response time and the dashboards give us the information we need to give to them, and to be able to fix bottlenecks and improve our timing.”\n\nBuilding those critical dashboards was easier because they did it as part of the platform. “It would have been so much harder without GitLab,” says Booijink. “It was user friendly and now we have a clear understanding of processes, numbers, and what’s behind all that data. And it works the same way for every project.”\n\nHe adds that since all of the features in Ultimate, whether AI capabilities, automatic security scanning, or value stream management, are all part of a single platform, it makes work easier for Cube employees using GitLab.",{"template":950,"size":36,"region":106,"industry":91},"content:en-us:customers:cube.yml",{"_path":2199,"content":2200,"config":2238,"_id":2239},"/en-us/customers/curve",{"name":2201,"logo":2202,"hero":2203,"heroImage":2204,"benefits":2205,"industry":69,"employeeCount":2215,"location":2216,"solution":913,"headline":2217,"summary":2218,"quotes":2219,"content":2224,"contributors":1281,"stickyBenefits":2237},"Curve","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745517971/k9fnumnnd5pstcvtjynk.svg","Fintech innovator Curve counts on the GitLab platform","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518437/ntqimtrey2uikf35kwvz.jpg",[2206,2209,2212],{"metric":2207,"config":2208},"Built-in security",{"icon":239},{"metric":2210,"config":2211},"Toolchain simplification",{"icon":1852},{"metric":2213,"config":2214},"Huge cost savings",{"icon":1247},"500","London, United Kingdom","Innovation is the lifeblood of the young fintech industry, and software engineering needs to be especially fleet of foot. Developers at fintech platform provider Curve chose GitLab to meet these pressing needs.","GitLab's improved continuous integration and delivery (CI/CD), security scans, project management, and auditability are driving innovation at the fintech startup.\n",[2220],{"quoteText":2221,"author":2222,"authorTitle":2223,"authorCompany":2201},"Before we moved to GitLab there was a big burden on operation teams. It was a battle to enable developers to effectively do their jobs. The obvious choice was to have everything in one place and well-contained through a single pane of glass.\n","Ed Shelton","Site Reliability Engineer",[2225,2228,2231,2234],{"header":2226,"text":2227},"Fintech innovator","[Curve](https://www.curve.com/en-gb/) is a fintech platform that has gone live in over 31 markets across the UK and European Economic Area and is imminently expanding into the US. Curve combines your credit cards, debit cards, and loyalty cards in one. You can even add receipts. So it’s the only card you need to carry. And the only pin you need to remember. Also known as over-the-top payment servicing, this new model of financial and payment services is enabled by Curve’s commitment to product innovation through advanced software engineering.\n",{"header":2229,"text":2230},"Fragmented toolchain reducing productivity and results","The early days of programming at Curve saw team members working mainly in PHP. As efforts advanced, teams evolved to embrace new languages, including Golang, Kotlin, Swift, and NodeJS. However, a fragmented toolchain led to difficult integration of software components, and poor visibility into development processes. There was a black box element to builds that made it difficult to identify and fix issues. Resource overhead required for administering and supporting a wide variety of software tools threatened teams’ abilities to meet productivity objectives. Pressures were further heightened by the need to ensure optimal security, Payment Card Industry (PCI) compliance, and reporting in fintech – which is a high-profile industry with continually evolving regulations.\n\nThe task of streamlining DevOps did not become less difficult as additional developers joined. Curve looked to simplify development and streamline operations to support the growth of their team. “It was a battle to enable developers to actually do their jobs efficiently. The obvious choice was to have everything in one place and well-contained on a single pane of glass,” said Ed Shelton, Site Reliability Engineer at Curve.\n",{"header":2232,"text":2233},"One DevOps platform that ensures compliance and increases efficiency","Curve engineers used GitLab to attain standardized continuous integration and continuous delivery (CI/CD) pipeline processes. As part of that, the team has gained greater control of templating issues that had stymied progress. Among the early advantages achieved with GitLab’s implementation was the ability to quickly onboard new engineers, simply by granting them access to GitLab and getting them logged in. No need to create accounts for 5+ services and generate personal access tokens for each one — just use GitLab. Developers were “good to go” on their first day.\n\nImprovements in security included use of GitLab’s security scanning for quick visibility into vulnerabilities in both new and older code. Reports now detect vulnerabilities in individual jobs automatically, and prevent risky changes from inadvertently making it to production. Meanwhile, maintenance time devoted to CI/CD has dramatically reduced. New releases can be quickly rolled out or rolled back. New initiatives can be taken on quickly without worrying about dedicating developer resources to gluing together disparate systems.\n",{"header":2235,"text":2236},"DevOps platform delivering better code and empowering developers","Use of GitLab Ultimate at Curve has vastly improved CI/CD efforts, garnered significant security benefits, eased templating, and streamlined project management and auditability. Builds that run more quickly have been beneficial, allowing programmers to focus on programming. With GitLab, Curve teams effortlessly achieved PCI compliance. GitLab dashboards now highlight vulnerabilities that could compromise security. Along with this come advances in templating that support standardization and greater governance for the organization. The result has been highly performant pipeline operations, and reduced time-to-release. Curve teams have seen an approximately 50% reduction in the time it takes for pipeline deployment.\n\nGitLab’s benefits as a project management tool are several. It is used for the full development life cycle — covering all the repositories and the software development itself, including product development, code reviews, and tracking external partners as well. Boards, milestones, and epics are particularly useful in the context of fintech requirements. Platform capabilities support creation of audit trails that mark activity on services, noting where a change comes from, how the change manifested, and how changes are actually implemented. Being able to track how services evolve is crucial in this industry. Previously, finding out how something made it into production was difficult.\n\nBy having the full software development lifecycle visible in one place, Curve has clear visibility into how developers are working and where the bottlenecks may be. The ability to roll out a new feature with agility, or just do a comprehensive bug search, has been a big win for modernization. Where there has been a need to roll out state-wide changes, teams have been able to employ the GitLab API and make these changes easily and effectively. Finally, the GitLab open-source ethos maps closely with Curve’s development philosophy. GitLab community forums always provide a preview of upcoming features and their status, and such transparency aids in planning, engineer Ed Shelton indicated. The comprehensive documentation resources empower developers to self-serve, and frees up their time to focus on code. GitLab supports this fintech innovator’s rapid growth with full compliance and increased operational efficiency.\n",{"benefits":1281},{"template":950,"size":40,"region":106,"industry":71},"content:en-us:customers:curve.yml",{"_path":2241,"content":2242,"config":2284,"_id":2285},"/en-us/customers/deakin-university",{"name":2243,"logo":2244,"hero":2245,"heroImage":2246,"benefits":2247,"industry":2255,"employeeCount":2256,"location":2257,"solution":913,"stats":2258,"headline":2264,"summary":2265,"quotes":2266,"content":2271},"Deakin University","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745517973/crygdtinlkstfrreaqtt.png","Deakin University cuts toolchain sprawl with GitLab","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518437/jkjrmsithvi3fghz3ihc.jpg",[2248,2251,2253],{"metric":2249,"config":2250},"Improved developer experience",{"icon":1629},{"metric":1137,"config":2252},{"icon":967},{"metric":965,"config":2254},{"icon":1852},"Higher Education","4500","Melbourne, Victoria, Australia",[2259,2262],{"value":2260,"metric":2261},"60%","Reduction in manual tasks",{"value":1308,"metric":2263},"Of code in major projects scanned for quality","Deakin University is driving improvements in collaboration and productivity with the ease of use and out-of-the-box security features of GitLab’s DevSecOps Platform.","Technology is a cornerstone of Deakin’s commitment to collaboration, as well as the university’s aim to become Australia’s most progressive and responsive university.\n",[2267],{"quoteText":2268,"author":2269,"authorTitle":2270,"authorCompany":2243},"One of the drivers for us to adopt GitLab was the number of different out-of-the-box security features that allowed us to replace other solutions and open source tools and therefore the skill sets that came along with them.\n","Aaron Whitehand","Director of Digital Enablement",[2272,2275,2278,2281],{"header":2273,"text":2274},"A leader in distance education through modernized software delivery","Deakin University was established in Melbourne, Victoria, Australia, in 1974, and was one of the first universities in the region to specialize in distance education. Deakin has several research institutes, including the Applied Artificial Intelligence Institute, the Institute for Frontier Materials, and the Institute for Intelligent Systems Research and Innovation. In addition to excellence in teaching and research, Deakin has a deep history of collaboration, forging partnerships with industry and government to solve problems and share ideas.\n",{"header":2276,"text":2277},"Tool proliferation creates fragmented processes","Software engineering at Deakin University sits with a dozen or more delivery teams who are responsible for application architecture, software development, testing, and software operations. Aaron Whitehand, Deakin’s director of digital enablement, began to think about how Deakin’s software engineering teams might be able to modernize their software development processes after engaging with an IT partner who used DevOps practices.\n\nTop of mind for Whitehand was the complex nature of the university’s existing software development toolchain. “We had duplicate tools in teams, which led to ad hoc software development processes,” says Whitehand. “Not just duplication of CI/CD tools, but duplication of source control management tools and package management tools as well. And also, a number of different open source SAST tools that different teams were using with no real consistency, no real ability for us to audit things easily.” Tools that Deakin was using at the time included Bamboo, Circle CI, and Jenkins for continuous integration and continuous delivery (CI/CD) and Subversion for version control and source control management (SCM).\n\nWith various departments within the software engineering organization using so many different tools — often for the same purpose — teams were burdened with manual tasks and duplicated efforts. “We had some simple code review processes that required handoffs across teams and were really lengthy, time consuming, and manual,” says Whitehand. “People were doing manual, repetitive tasks day in, day out.”\n\nUltimately, the university’s sprawling toolchain meant Whitehand’s team was unable to provide the rest of the university — researchers, faculty, and students — with the right tools for source control, CI/CD, package management, software supply chain security, and collaboration with external partners. Plus, paying for multiple point solutions to solve related challenges within the development lifecycle became untenable as the university tightened budgets. “We were really trying to rationalize our software to save on total cost of ownership — not only licensing, but the skills we needed to maintain across our staff as well,” says Whitehand. Deakin needed an end-to-end platform that would allow developers to get feedback on their code more quickly, automate security testing, and provide much-needed consistency across the organization.\n",{"header":2279,"text":2280},"A single platform to empower the university community","Deakin spun up proofs-of-concept with several tools before choosing GitLab. For Whitehand, one of the factors that stood out most during the evaluation was how well the GitLab platform was received by developers. “After we spun up the environments for the technical proof of concept, the developers came back to us and it was overwhelming, the feedback of how easy it was to use, how well it was documented, and they could just pick it up seamlessly and achieve what they needed to achieve really, really quickly,” he says.\n\nAnother advantage was the fact that GitLab integrates well with the tools that Deakin is already using — meaning they don’t need to rip and replace everything at once. The university is able to integrate GitLab with Jira for Agile and DevOps teams and HashiCorp Vault for secrets management. And thanks to [GitLab’s compatibility with Red Hat OpenShift](https://docs.gitlab.com/ee/install/openshift_and_gitlab/?_gl=1*1c41x6n*_ga*MTU1MDMzNTYwOS4xNjQ0OTYxNjk3*_ga_ENFH3X7M5Y*MTY4MTkzMzY3MC40MTUuMS4xNjgxOTM1Mjg4LjAuMC4w), Whitehand’s team is able to deploy GitLab to OpenShift clusters.\n\nGitLab’s regular release cadence, with valuable new features coming out on the 22nd of every month, was another standout factor in the decision. “We get excited when we see the next rounds of releases coming through because they tackle the challenges we always have,” says Michael Heley, group manager of software engineering. “Security is the biggest challenge for us along with many other organizations, so to see the growth and the maturity of the security options that are coming with the licensing we’ve got is great.” With GitLab, Deakin was able to implement a wide range of security scanners and then put the results straight into developers’ hands. This has allowed the university to replace various security point solutions and open source tools, cutting costs and complexity while also reducing the number of tool-related skill sets that had to be managed across teams.\n\nAccording to Hayden McFadyen, manager of software engineering at Deakin, one of the biggest benefits of GitLab is that it’s an all-in-one solution, which makes it easier to implement and maintain. “We’ve been upgrading since V13 and every upgrade has been painless,” he says. “The big win was really consolidating the products we were using for source control (SVN and Bitbucket), CI (Bamboo and Jenkins), and CD (Jenkins and Buildkite).”\n\nGitLab also offered a special package tailored to Deakin’s unique needs as an educational institution. The [GitLab for Campuses](https://about.gitlab.com/solutions/education/){data-ga-name=\"campus\" data-ga-location=\"customers content\"} solution, which provides qualifying educational institutions with unlimited seats for all use cases and deployment methods, allowed Deakin to drive growth in GitLab usage across the university without being constrained by per-seat pricing. With GitLab for Campuses, Deakin is empowering research staff, faculty, interns, and students with a single tool for DevOps, source control, CI/CD, package management, and software supply chain security.\n",{"header":2282,"text":2283},"Improved collaboration and code quality","Deakin now has over 300 unique GitLab users in their internal environment. Since introducing GitLab, the university has been able to dramatically decrease manual efforts across their entire software supply chain, meaning teams can get code into production much faster. “With GitLab, the majority of those manual tasks have been automated, and I think we’ve cut at least 60% of that time down,” says Whitehand.\n\nOne area where the software engineering organization has seen significant improvement is the code review process. Previously, teams had been following a number of different processes, including various manual static application security testing (SAST) tools, to check code. With GitLab, these processes are automated and built into reusable pipelines. “Now developers can commit code and get immediate feedback from their peers,” says Whitehand. “We didn’t have that in the past — developers would wait sometimes days to get feedback from their seniors or their team leads on their code.”\n\nDeakin’s enablement team has also been able to build standardized processes and reusable templates — such as custom merge request templates, templated build pipelines, and a security and compliance framework — that can be shared with the broader university community and citizen developers, driving innovation and collaboration both inside the university and with key partners. “We were trying to bring in a community of practice and help it thrive for quite some time, but we were never successful until we had this tool,” says Whitehand.\n\nProcess improvements in Deakin’s software development lifecycle have translated into higher-quality software and better experiences for end users. Since adopting GitLab, mean time to resolution (MTTR) for support tickets has dropped significantly. What’s more, GitLab’s end-to-end DevSecOps platform is driving closer connections between Deakin’s development and security teams. “We work quite closely with our security team now to understand our release risk,” says Whitehand. “Before GitLab, when we got to the stage where we were deploying something to production, we didn’t always know exactly what was going to happen.” Now, the university’s developers have newfound confidence that their code is going to work when it hits production.\n\nIn 2021, Deakin was awarded a [Gartner Eye on Innovation Award for Higher Education](https://dteach.deakin.edu.au/2022/02/deakin-wins-gartner-innovation-award-for-3d-app/) for its work on ideAR, an approach to enabling teachers and learning designers to create interactive and engaging 3D and augmented reality experiences. Deakin used GitLab to support the development of the ideAR project.\n\nDeakin sees strong potential in investing in GitLab — both for the future of the university and its students, staff, and faculty. As part of Deakin’s central IT intern program, over the past 12 months the university has granted GitLab access to around 20 student interns from different departments, allowing those students to build real-world experience with GitLab and setting them up for success after graduation. Looking to the future, Deakin plans to make GitLab the platform of choice for teaching DevOps and other topics within computer science across the university.\n\n“There’s been a significant shift in developer empowerment as a result of our uptake of GitLab,” says Whitehand. “There really hasn’t been another initiative that has sparked the developers like GitLab has.”\n",{"template":950,"size":44,"region":110,"idnustry":67},"content:en-us:customers:deakin-university.yml",{"_path":2287,"config":2288,"content":2289,"_id":2342},"/en-us/customers/deutsche-bahn-ag",{"template":950,"size":44,"region":106,"industry":91},{"heroImage":2290,"imageAttribution":2291,"employeeCount":2292,"summary":2293,"logo":2294,"name":2295,"headline":2296,"location":2297,"quotes":2298,"content":2304,"solution":2319,"hero":2320,"benefits":2321,"industry":2331,"stats":2332},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1759342186/d6evi8o1ervlhy0srtej.jpg","Deutsche Bahn AG / Volker Emersleben","338,000","Germany's national railway company and one of Europe's largest railway operators adopted GitLab's end-to-end DevSecOps platform in 2016 to build a world-class booking system, ease compliance needs, and create a collaborative culture where users share code and project insights.\n","https://res.cloudinary.com/about-gitlab-com/image/upload/v1759342156/esegvvgcuoryyhyylt5s.png","Deutsche Bahn AG","Deutsche Bahn’s high-speed trains are national symbols of German engineering and efficiency — so they need an equally high-speed and efficient way to build software for their millions of users. They also need a high-performance application that serves as a comprehensive travel companion for people looking to book tickets and get timely schedule information. ","Berlin, Germany",[2299],{"quoteText":2300,"author":2301,"authorTitle":2302,"authorCompany":2303},"We built our primary digital platform — the interface for millions of our customers — from the ground up with GitLab. This software is critical to our success, so GitLab is, too.","Lukas Pradel","software engineer","Deutsche Bahn",[2305,2307,2310,2313,2316],{"text":2306,"header":1361},"Based in Berlin, Deutsche Bahn was founded in 1994 following German reunification. It operates as a private company wholly owned by the German government. Today it manages about 33,500 kilometers of tracks, holding a unique position as the country’s transportation backbone, connecting virtually every city and town through its comprehensive network. With nearly 340,000 employees and transporting nearly 2 billion passengers a year, the organization stands out for its integrated business model, including long-distance and regional passenger services, freight operations, and global logistics.",{"header":2308,"text":2309},"Building DB Navigator: A critical app for 23 million unique visitors","For millions of German travelers, Deutsche Bahn’s DB Navigator isn't just another app — it's their essential connection to the organization's vast railway network. In fact, it is Deutsche Bahn’s most used app, handling 1.5 billion travel information requests in 2023 with an average of 42 million visitors per month the same year. The app serves as the organization's primary digital interface for millions of customers, serving as a critical driver of ticket sales, and a source of real-time travel information and trip planning. It is Deutsche Bahn’s most important piece of software.\n\nThe organization built it from the ground up with GitLab.\n\nTo build DB Navigator, about 400 people across about 35 DevSecOps teams used GitLab’s platform to share code, documentation, and best practices. GitLab also enabled them to collaboratively share information about different projects and ask each other for guidance.\n\n“We have such a large community and a complex IT landscape at Deutsche Bahn that we have been trying to foster a way for people in different teams to share code, as well as libraries and insights,” says Martin Ortmann, product owner at Deutsche Bahn. “Having a [collaborative platform](https://about.gitlab.com/blog/5-ways-collaboration-boosts-productivity-and-your-career/) allows us to foster learning and discussions that have definitely been a big benefit to us.\n\n“People have built wide-ranging communities where they discuss all aspects of coding, including fixing bottlenecks and increasing efficiencies,” he adds. “GitLab is important for our collaboration.”\n\nThat kind of collaboration made it faster and more efficient to build DB Navigator, their flagship piece of software.\n\n“We built our primary digital platform — the interface for millions of customers — from the ground up with GitLab,” says Pradel. “It’s significant to our success, so GitLab is too.”\n\nWhen Deutsche Bahn originally adopted GitLab they began using the GitLab Community Edition, which provides basic DevSecOps functionality, including unlimited public and private repositories. “It really helped us,” says Ortmann.\n\nThe organization and its DevSecOps teams, however, wanted more – more capabilities that would enable them to efficiently build apps like DB Navigator. And to get more — more planning features, more analytics and reporting, and more priority support — they upgraded to GitLab Premium in 2023. Today they have 11,500 active users, 75,000 hosted repositories, and a 91% success rate in continuous deployments.\n\nPart of that developer happiness came from the fact that Premium gave their team members the opportunity to use more planning features, like merge request boards, Issues, roadmaps, and Epics. These features were available in the Community version but the DevSecOps teams found using them felt more seamless in Premium, encouraging more people to take advantage of the additional features. For instance, approval rules are automatically enforced, and the upgrade also eliminated the need for a separate code search tool. \"Since we didn't have to buy another tool, we were able to save that expense and complexity,\" says Pradel, highlighting Premium's Advanced Search capabilities for cross-repository searches and vulnerability detection.\n\nFor the developers it is more seamless because the approval rules are enforced and the fulltext code search is integrated into the product (no switch to separate product needed)",{"header":2311,"text":2312},"Streamlining: Reducing toolchain complexity and costs","Deutsche Bahn also was able to [reduce its toolchain](https://about.gitlab.com/the-source/platform/devops-teams-want-to-shake-off-diy-toolchains-a-platform-is-the-answer/) — and the expenses and challenges that come along with it — because of GitLab’s end-to-end DevSecOps platform. In fact, Pradel says GitLab has enabled them to save 15% in infrastructure costs.\n\nHeiko Maaß, system engineer at Deutsche Bahn, notes that they previously had a “very complex” Jenkins setup, including an array of plugins, for their pipeline engine.\n\nThey also had at least half a dozen instances of Jenkins running throughout various teams. Each instance, which had its own configurations, was managed by those individual teams. This decentralized evolution led to resource inefficiencies, wasted time, knowledge silos, and maintenance overhead. Today with GitLab, Deutsche Bahn has been able to eliminate most of their Jenkins instances and Ortmann's team alone runs the DevSecOps platform, freeing all the other teams from the mental load of maintaining tools.\n\nDeutsche Bahn is moving toward completely replacing Jenkins with GitLab.\n\n“All those Jenkins plugins often needed to be updated due to security issues, and we had to do plugin upgrades every month. It was very time consuming,” says Maaß. “Those tasks are gone now so we can use that time to create new features, instead of maintaining Jenkins.”",{"header":2314,"text":2315},"Simplifying compliance: Easing complexities and developer burden","Operating the most extensive transportation network in the country, Deutsche Bahn has to comply with an extensive framework of compliance regulations. And that can be a tough job if an organization has inconsistent processes and documentation, manual coordination of compliance tasks, visibility gaps, and manual handoffs between tools or teams. Deutsche Bahn has been able to avoid these pitfalls by using GitLab’s single application, which has [automated compliance](https://about.gitlab.com/blog/meet-regulatory-standards-with-gitlab/) checks, eased consistent documentation, enabled policy as code, and standardized workflows.\n\n“Before using GitLab Premium, a lot of our compliance work was manual,” says Maaß. “For instance, in certain cases, you had to write tickets and report that you did a code review to keep up with compliance regulations. We had to worry that approvals would be forgotten. Now we have automation that relieves that stress. And everything is documented so we can prove our compliance whenever we need to. It’s really increased our developer happiness because they have less to worry about.”",{"header":2317,"text":2318},"Reliability: GitLab Support offers 'immediate' assistance","With GitLab Premium, the Deutsche Bahn team has access to GitLab Support, providing them with assistance when needed, which gives them less to worry about. Ortmann says having this service — which offers help with troubleshooting, multiple support channels, named support contacts, and upgrade assistance — has made work easier and their systems more reliable.\n\nSince the railway services are considered critical infrastructure in Germany, the organization’s technical departments are critical as well. That means Deutsche Bahn’s DevSecOps teams are under constant pressure to supply rapid incident response, maintain app performance under load, and provide continuous availability. GitLab Support helps them do that.\n\n“Having that vendor support is important to us because it enables us to act quickly if something goes wrong,” says Ortmann.\n\nThe organization leaned on that support when they needed assistance setting up the GitLab architecture with Kubernetes. “We knew we needed GitLab and its support teams to figure out how best to do it, while keeping the system stable,” says Ortmann. “We received an immediate response from the support team. It was a big relief.”\n\nThe immediate value of GitLab Support reinforced that they had made the right decision to upgrade to Premium. And their developers agreed.\n\n “There was a rush of active users who moved to GitLab Premium. It was 40% greater than expected,” says Ortmann. “We shouldn’t have been too surprised, though. People on our teams had started coming to me, saying, ‘Come on. When do we get Premium?’ They were demanding an upgrade. It was all developer driven and the move has really increased their happiness.”\n\nWith GitLab Premium powering their critical infrastructure, Deutsche Bahn continues to deliver the reliable railway services that millions of passengers depend on daily, while building the digital innovations that will shape Germany's transportation future.","GitLab Premium ","Deutsche Bahn uses GitLab to drive critical rail app used by millions",[2322,2325,2328],{"metric":2323,"config":2324},"Better quality software",{"icon":967},{"metric":2326,"config":2327},"Faster development",{"icon":971},{"metric":2329,"config":2330},"More competitive business",{"icon":1295},"Transportation",[2333,2336,2339],{"value":2334,"metric":2335},"10%-20%","infrastructure cost savings",{"metric":2337,"value":2338},"pipeline builds per month","1 million",{"value":2340,"metric":2341},"80%","less time spent on pipeline-maintenance","content:en-us:customers:deutsche-bahn-ag.yml",{"_path":2344,"content":2345,"config":2386,"_id":2387},"/en-us/customers/deutsche-telekom",{"name":2346,"logo":2347,"hero":2348,"heroImage":2349,"benefits":2350,"industry":2358,"employeeCount":2359,"location":1854,"solution":913,"stats":2360,"headline":2367,"summary":2368,"quotes":2369,"content":2373},"Deutsche Telekom","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745517932/nimkzywtrp5merof9krh.jpg","Deutsche Telekom drives DevSecOps transformation with GitLab Ultimate","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518415/yxkdhpqcskxysu0oxjmd.jpg",[2351,2353,2356],{"metric":900,"config":2352},{"icon":902},{"metric":2354,"config":2355},"Streamlined security",{"icon":1142},{"metric":1293,"config":2357},{"icon":1295},"Telecommunications","216,500",[2361,2364],{"value":2362,"metric":2363},"6x","faster time to market",{"value":2365,"metric":2366},"13,000","active GitLab users","With GitLab, Deutsche Telekom has created a single source of truth for the company's developers, driving increased productivity, enhanced security, and faster time to market.\n","Europe's leading telco turned to the GitLab DevSecOps Platform to foster collaboration and eliminate inefficiencies without sacrificing security.\n",[2370],{"quoteText":2371,"author":2372},"Time to market was a big issue for us. Before our transformation to Agile and DevOps started, we had release cycles of nearly 18 months in some cases. We've been able to dramatically reduce that to roughly 3 months.\n","Thorsten Bastian,  Business Owner IT, CI/CD Hub, Telekom IT",[2374,2377,2380,2383],{"header":2375,"text":2376},"Deutsche Telekom: The leading telco","[Deutsche Telekom AG](https://www.telekom.com/en/company/companyprofile/company-profile-625808) is a German telecommunications company and one of the world's leading integrated telecommunications companies, serving more than 240 million mobile customers, 26 million fixed-network lines, and 22 million broadband lines in more than 50 countries. By taking a legacy industry — the classic telephone company — and digitizing all aspects of the business, Deutsche Telekom represents a new type of service company: a software company that sells telecommunications services.\n",{"header":2378,"text":2379},"Improving efficiency and reducing time to market with GitLab Premium","As Europe's leading telco, Deutsche Telekom understands the importance of DevOps in driving efficiencies in the software development lifecycle. “Of course, DevOps is not just the tooling, but also the mindset, the culture, the way people work together,” says Thorsten Bastian, business owner of the CI/CD Hub of Telekom IT. DevOps methodologies have become a cornerstone of Deutsche Telekom's efforts to streamline software development and cut down on manual tasks, break down silos, increase collaboration and productivity, and speed up time to market.\n\n\nBut that didn't happen overnight. For several years, as Deutsche Telekom transitioned from a waterfall approach to Agile methodology, different software development teams within the company began to consider how to leverage automation and continuous integration and delivery (CI/CD), but adoption was spotty in the beginning. Because teams used different tools for automation, a single source of truth for sharing or collaborating on code was not available.\n\n\nTelekom IT, a division of Deutsche Telekom that designs, develops, and runs IT systems for the company, saw the need for a centralized platform where developers could share code and draw from a common set of functionalities for automation and CI/CD. “We needed to reduce manual tasks so that people can really focus on more complex activities in innovative parts of the whole development process,” says Bastian.\n\n\nNorman Stamnitz, product manager of Telekom IT's CI/CD toolsuite — which is built on top of GitLab — explains that a user-driven selection process ultimately brought them to GitLab. “As part of the whole DevOps and Agile approach, we didn't want to decide this from the top down,” says Stamnitz. “We really wanted the people who would be using the platform to decide what makes sense for them. That's how we came to GitLab.” Stamnitz and team started with GitLab's Premium tier, as they wanted access to enterprise-level features such as priority support.\n\n\nTelekom IT made it a priority to ensure that all developers or DevOps engineers within Deutsche Telekom could use GitLab. The CI/CD toolsuite needed to be accessible on any kind of laptop, without the need to register for a separate account or fill out a complicated order form. “After the system was available, we only did a little advertising in internal communities, and after that it ran by itself,” says Stamnitz. “In a very short time we had over 1,000 users on the platform — and that was without any requirements from IT governance or the like. Our CI/CD toolsuite with GitLab at its core spread like wildfire via word of mouth.”\n\n\nAnd it wasn't just projects and users from Telekom IT that moved over to GitLab. Other IT units across the company also decided to switch off their own CI/CD systems (some of them already using GitLab, some using other tools) and migrate to Telekom IT's central GitLab Premium instance.\n\n\nNow, two and a half years later, Telekom IT has more than 13,000 active users from all over the company in GitLab, and roughly 75% of the company's Agile programs are using Telekom IT's CI/CD toolsuite. Feedback from users has been overwhelmingly positive, Stamnitz says. “They're always very thankful that we offer the platform, and that they don't have to maintain it themselves — that it's just there, and it's just working. The experience for the developers, I think, is quite good.”\n\n\nPart of this enhanced developer experience is a shift towards “inner source” — a culture of sharing code and knowledge inside the organization. “Before purchasing GitLab Premium, it was difficult to find a way to facilitate code sharing across different departments within the company. Of course we had various code repositories, like Git or Subversion, but code sharing was always a problem,” says Stamnitz. “People would say, ‘I'm sure this has already been developed hundreds of times, but I can't access the source code.’ That has changed with our central GitLab installation, because now, we are all hosting our source code, more or less, on the same platform. Everybody can see it and participate.”\n",{"header":2381,"text":2382},"Shifting security left with GitLab Ultimate","Two years after rolling out GitLab Premium, Telekom IT began to examine parts of its software development lifecycle where manual tasks and bottlenecks remained. What stood out most was security.\n\n\n“We decided to extend to GitLab Ultimate because we wanted to have the security and compliance features and all in one security dashboard,” says Stamnitz. “If you can reduce manual security processes, do all this security scanning before a go-live — that brings us the ability to speed up or to reduce the time to market even more. And of course, we wanted to shift left. We wanted our developers to have security scanners as part of their daily tasks.”\n\n\n“Regarding the security functionality, of course, it's a huge benefit,” says Bastian. “If you have it integrated in one application, you can immediately jump to the right place and fix the problem, instead of sending reports to the projects about the findings. This is increasing the efficiency of handling security findings.”\n",{"header":2384,"text":2385},"Partnering with GitLab","In GitLab, Telekom IT has found a trusted technology partner, and Telekom IT plans to make GitLab the standard software development platform across the company. As one aspect of this long-term strategic partnership, Telekom IT has become a key contributor to the GitLab platform and works closely with GitLab product teams on feature requests and open beta programs.\n\n\n“We've submitted several feature requests to ask for new features and made some small contributions to GitLab on our own,” says Stamnitz. “In general, that's going very smoothly. Things that we contributed have been included in the very next release, and overall the GitLab team helps us get things solved really quickly.”\n\n\nDevelopers at Deutsche Telekom also appreciate GitLab's high-velocity release schedule, with releases happening on the 22nd of every month. Telekom IT usually installs GitLab updates within one or two days of the release due to high demand from across the company. “People see that new GitLab features are out and they immediately ask us when we're installing it,” says Stamnitz.\n\n\nA more collaborative culture is empowering Deutsche Telekom's software development teams to produce more software faster, with the same number of people. “Before, some people were using GitLab, but others were using GitHub Actions, and still others were using Jenkins or other tools. Everybody was using their own thing,” Stamnitz adds. “Now, everybody's using the same platform. I would say that we are better in what we are doing now than we were before. And quicker.”\n",{"template":950,"size":44,"region":102,"industry":91},"content:en-us:customers:deutsche-telekom.yml",{"_path":2389,"content":2390,"config":2432,"_id":2433},"/en-us/customers/drupalassociation",{"name":2391,"logo":2392,"hero":2393,"heroImage":2394,"benefits":2395,"industry":1392,"location":2405,"solution":913,"stats":2406,"headline":2412,"summary":2413,"quotes":2414,"content":2418,"contributors":2431},"Drupal Association","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745517974/alueoyjcoznregjdngex.png","Drupal Association eases entry for new committers, speeds implementations","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518438/ph8wsr59lxhgrdrerloo.jpg",[2396,2399,2403],{"metric":2397,"config":2398},"Faster implementations",{"icon":971},{"metric":2400,"config":2401},"Greater user involvement",{"icon":2402},"UserGroup",{"metric":1893,"config":2404},{"icon":1295},"Drupal.org",[2407,2409],{"value":1807,"metric":2408},"faster CI implementation",{"value":2410,"metric":2411},"10%","increase in Drupal core contributions","Implementation of GitLab placed Drupal platform development in the mainstream of open-source evolution, while better supporting the contribution efforts of a wider range of the Drupal user community.","Adopting GitLab as The DevOps Platform enabled greater contribution and collaboration.\n",[2415],{"quoteText":2416,"author":2417,"authorTitle":1267,"authorCompany":2391},"You do not need any tools other than your browser in order to contribute, and not just in our module ecosystem, but even to Drupal core itself. That was not possible in our project prior to the move to GitLab, and that's a really big deal.","Timothy Lehnen",[2419,2422,2425,2428],{"header":2420,"text":2421},"Drupal evolves with open source to grow its platform","The Drupal Association, steward of the free Drupal web content management system, stands as one of the most remarkable success stories of the open source software era. Drupal serves as the capable backend framework for an estimated 13% of the top 10,000 websites worldwide, with users including the Fortune 50 companies, government, higher education and many more. From website development to advanced content management and more, the platform has evolved, while relying on the innovation, know-how, and dedication of open source contributors. As of early 2021, the Drupal community included 121,000 active contributors. The Drupal Association enables thousands of websites to upgrade to use innovative and stable modules at an increasingly rapid pace.\n",{"header":2423,"text":2424},"Moving forward, reducing obstacles for new contributors","Drupal had its 20th anniversary in 2021. As a veteran open source project, it actually predates git, let alone hosted collaboration platforms like GitLab or GitHub, or continuous integration (CI) services like Travis. Like many of the projects of this era, Drupal built its own bespoke git backend, bespoke code collaboration tools, and bespoke continuous integration systems. Well into 2020, the Drupal ecosystem still primarily relied on patches submitted to Drupal.org’s custom issue tracker, and the bespoke DrupalCI system for integration testing. At the same time, Drupal as a product evolved in complexity and capability — making it an industry-leader in building ambitious digital experiences — but exposing the flaws and friction points of the aging collaboration tools.\n\nThe Drupal.org development team realized that, for Drupal to continue to thrive as an open source platform, they needed to increase focus on their beginner experience, facilitating the continual growth of an essential and vibrant contributor community. New contributors needed to be able to quickly take part in frictionless development efforts. Drupal also needed end-to-end, browser-based management to give new users the ability to manage code contributions and workflow — and to empower users around the globe without access to powerful machines the tools they need to continue to contribute. Achieving these goals was essential to putting the focus back on what makes the Drupal project successful: empowered and energized contributors, focused on innovation, and free of friction.",{"header":2426,"text":2427},"GitLab opens up access and collaboration for more developers","To achieve their new goals, the team looked to leverage an open collaboration and DevOps platform that would offer [end-to-end support](/solutions/devops-platform/){data-ga-name=\"end-to-end support\" data-ga-location=\"customers content\"}. The Drupal.org engineering team was faced with the choice of continuing to maintain custom collaboration tools, or moving to a well supported, modern solution. During a multi-year evaluation process, the team evaluated GitLab, GitHub, and Bitbucket, and ultimately went with GitLab as the collaboration and DevOps platform of choice to support their open source project because it offered “that modernized, feature-rich contribution workflow that developers expect, as well as allowing us to run our own self-hosted instance, which was crucial to configuring our new tools to meet Drupal’s very open collaboration style,” noted Timothy Lehnen, Chief Technology Officer at the Drupal Association.\n\n“After conducting an independent evaluation of multiple collaboration platforms including Github, Atlassian BitBucket, and GitLab, GitLab emerged as a clear winner do to its commitment to co-operation and collaboration with the Drupal project and the [open source community](/solutions/open-source/){data-ga-name=\"open source\" data-ga-location=\"customers content\"},” continued Lehnen. Adopting GitLab also provided a ready leg-up for the many contributors already familiar with git, and that enabled them to recruit more people into the Drupal Community. This modernization also allowed the team to benefit from add-ons created by the ecosystem of tooling providers who extend GitLab’s functionality, including Drupal service providers who had already adopted GitLab for their own internal work.\n\n“With GitLab, Drupal contributors have the tools they need, without the barrier of learning a full development stack that isn’t actually relevant to their domain,” said Lehnen. “It just makes it easier to collaborate on projects both for coders and non-coders.” Community members are now able to employ a browser interface that supports the full end-to-end process of making a contribution. [GitLab CI](/solutions/continuous-integration/){data-ga-name=\"continuous integration\" data-ga-location=\"customers content\"} supports a range of new workflows for the Drupal project. Both coders and non-coders alike can use GitLab’s WebIDE to support writing better code comments and in-code doc-blocks. A variety of users, including non-coders, such as product managers, accessibility engineers, content editors, and project managers, are now integrated into the overall workflow. This integration between coders and non-coders enables unprecedented collaboration across Drupal.\n\nUse of GitLab also coincides with the project’s first implementations of Kubernetes clusters, as GitLab CI runners are being made available in beta to select projects in the Drupal ecosystem, and soon in wider release. This helps the Drupal project move from a centralized CI model to one where project maintainers can implement their CI workflows of choice, innovating faster. As one example, Drupal is expanding beyond just a php project, and now publishes several JavaScript components to NPM, via GitLab CI/Pipelines.",{"header":2429,"text":2430},"Enhanced efficiency and expanded capabilities","Implementation has helped widely grow the capabilities of the Drupal community. GitLab is allowing more Drupal users to be more comfortable submitting fixes against the Drupal core. “We are seeing 400+ merge requests in the Drupal ecosystem per month since the change, and about a 50% close rate within the month,” said Lehnen. Since the transition to merge requests, contribution to Drupal core itself is up by around 10%. Contributor resources now are applied more efficiently as the WebIDE saves contributor community members significant time configuring and setting up jobs. “You can make an end-to-end contribution to Drupal with just your browser. You do not need the command line. You do not need a local development environment,” added Lehnen.\n\n“Now, contributors don’t need to learn how to be a local Drupal developer in order to review new features for accessibility concerns. The ability to contribute without setting up complex local development environments has made it easier for everyone from our accessibility maintainers, documentation editors, product managers, and others to review and comment on the work of our developers,” said Lehnen.\n\nMeanwhile, the Drupal core team has come very close to 100% test coverage for the Drupal core, and will be able to expand that coverage to new parts of the codebase much more easily with GitLabCI. They’ve achieved primary goals like increased developer satisfaction for the Drupal contributor ecosystem and dramatically reduced dependence on the internal team for contributor feature development. Contributions have been expanded to include the first JavaScript packages to be added to the mostly PHP project.\n\nGoing forward, further GitLab implementations will expand capabilities of the Drupal credit system, which highlights contributors’ efforts and innovations, providing useful metadata to help better understand how the Drupal community works. “Drupal leads the open source world in measuring and understanding our contribution ecosystem. This is one element of our bespoke tools that we’d love to keep, so we’re thrilled that the GitLab team is supporting the idea of bringing this feature to GitLab. That will let the rest of the open source community benefit from these community health metrics as well,” said Lehnen.","120,000+",{"template":950,"size":40,"region":102,"industry":75},"content:en-us:customers:drupalassociation.yml",{"_path":2435,"content":2436,"config":2485,"_id":2486},"/en-us/customers/dublin-city-university",{"name":2437,"logo":2438,"hero":2439,"heroImage":2440,"benefits":2441,"industry":65,"employeeCount":2452,"location":2453,"solution":2454,"stats":2455,"headline":2465,"summary":2466,"quotes":2467,"content":2473,"contributors":1281},"Dublin City University","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745517975/ojs0cjyxniutyyk5ra2y.svg","How Dublin City University empowers students for the IT industry with GitLab","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518439/vybywhjnpq8pauvpsr7k.jpg",[2442,2446,2448],{"metric":2443,"config":2444},"Students own their workflow",{"icon":2445},"OpenSource",{"metric":1524,"config":2447},{"icon":1302},{"metric":2449,"config":2450},"Improved IT employability",{"icon":2451},"Increase","625","Dublin, Ireland","GitLab Gold",[2456,2459,2462],{"value":2457,"metric":2458},"11,720","CI jobs running",{"value":2460,"metric":2461},"2,529","Repos running",{"value":2463,"metric":2464},472,"Current project repos","GitLab CI and SCM provides DCU with an elevated education experience in software development.","DCU, a pioneer in computer applications education, uses GitLab SCM and CI to drive students’ software projects and achieve top results.\n",[2468],{"quoteText":2469,"author":2470,"authorTitle":2471,"authorCompany":2472},"It’s a big plus for DCU that they can offer GitLab as part of the training curriculum to ensure students are abreast with technology. It's excellent preparation for getting in the industry.\n","Jacob Byrne","Fourth-year student","DCU",[2474,2477,2480,2482],{"header":2475,"text":2476},"Dublin’s premiere computer applications university","Dublin City University, DCU, is a Dublin-based university that was established in 1975. The school has approximately 17,000 enrolled students and over 50,000 alumni. In addition, [DCU](https://www.dcu.ie/){data-ga-name=\"dcu\" data-ga-location=\"body\"} has over 1,200 students enrolled in its online education program called DCU Connected. The electronic engineering and computer applications courses are the school’s most popular degrees and are considered amongst Ireland’s most sought after and prestigious computer courses.\n",{"header":2478,"text":2479},"Updating how coding is delivered","As an academic program, part of the software engineering schools’ focus is managing and delivering various software development projects. In the past, these projects were all paper-based and manual. Some students were learning to code and some were not, thereby creating an imbalanced educational program.\n\nTo ensure that students kept up with technology, learning methods needed to be innovated and transformed. The school was looking to implement a single, open source software platform. Ideally, the solution would provide [source code management](https://about.gitlab.com/solutions/source-code-management/){data-ga-name=\"source code management\" data-ga-location=\"body\"} for the students and also the academic staff. The software platform also needed to offer a structured way to evaluate students on their testing and validation, coupled with continuous integration capabilities.\n",{"header":2027,"text":2481},"DCU looked at BitBucket, Jenkins, GitHub, and other platforms to implement into the school system. However, about six years ago, Dr. Stephen Blott, senior lecturer at DCU, started using GitLab’s Community Edition on his personal desktop. He pitched the idea of using the platform for one of his project groups. GitLab usage garnered success and it was then rolled out to all the project groups. “Now all of those groups use GitLab for all of their projects. We expect them to have all their code available there. That gives us lots of advantages over what we had previously,” Blott said.\n\nStudents can now learn how to use Git, which is important when they go on work placements and eventually into the competitive workforce. It adds huge value to their resume and prepares them for the software industry. GitLab provides clear documentation for source code management, which alleviates the stress of learning a new tool. Students now have code and documentation that they previously didn’t have and are capable of creating small software projects that are developed over the course of a semester.\n\n“Because the code is linked into our LDAP server, it means that we know who they are so we know which code belongs to which student. We can find their code, and by reviewing the commit logs, we know when they’ve been working, what they’ve been working on, and we get a lot more insight into the projects,” Blott explained.\n\nGitLab provides visibility into what each student is working on because there is [end-to-end transparency](https://about.gitlab.com/customers/cook-county/){data-ga-name=\"cook county\" data-ga-location=\"body\"} in the tool. “At the end of the year, the examiners sit down and there’s an external examiner who comes in to review our work and to assess whether we’re marking it properly, and the external examiner can see everything,” Blott added. “Previously, the external examiner would only see some documentation which had been printed out and just had to guess at everything else.”\n",{"header":2483,"text":2484},"Using Git, SCM, and CI for future success","DCU students get a real world view of [managing software projects](https://about.gitlab.com/solutions/source-code-management/){data-ga-name=\"source code management\" data-ga-location=\"body\"}. The teachers can manage the students and the students get an in-depth understanding of Git and software build systems. GitLab is running on a virtual server and can be managed remotely. “It’s a great thing for the students because now they can actually set up their own workflow which they push, they run their tests, they can even deploy, and all of that happens through the CI environment,” Blott said. “It’s way superior because the students can come back and they can demonstrate and say, ‘Yeah, I did testing and validation. Look, here it is, you can see it running.’ So that’s a big step forward for us, as well.”\n\nThere are currently 2,529 repos running and 472 project repos. A project repo is associated with a formal academic software engineering project. A total of 11,720 CI jobs have been run to date. Third-year, fourth-year, and the masters levels programs use GitLab. “One of the things we hope to achieve is that, when they go out on that work placement, they already have those skills and they don’t feel like they’re being thrown into something they can’t handle,” Blott advised. Graduates of the software engineering program have been successfully finding work as engineers and as software consultants.\n\nJacob Byrne, fourth-year student at DCU, is a current GitLab user. Using the issues and boards has helped with sprint tracking and he considers the tool an excellent resource. “It’s a huge advantage in relation to preparing for the jobs market, adding great value as you are able to ramp up quickly in DevOps teams,” Byrne explained. “It’s a big plus for DCU that they can offer GitLab as part of the training curriculum to ensure students are abreast with technology. It’s excellent preparation for getting in the industry.”\n",{"template":950,"size":40,"region":106,"industry":67},"content:en-us:customers:dublin-city-university.yml",{"_path":2488,"content":2489,"config":2535,"_id":2536},"/en-us/customers/duncan-aviation",{"name":2490,"logo":2491,"hero":2492,"heroImage":2493,"benefits":2494,"industry":53,"employeeCount":2504,"location":2505,"solution":913,"stats":2506,"headline":2515,"summary":2516,"quotes":2517,"content":2522,"companySize":1281,"region":1281,"contributors":1281},"Duncan Aviation","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745517977/u62oabyqh8exxwq50wkr.svg","GitLab ensures confident automation and compliance, secures deployments at Duncan Aviation","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518439/mapdepmsoifehtrwx2zx.jpg",[2495,2498,2501],{"metric":2496,"config":2497},"Conserved admin resources",{"icon":1477},{"metric":2499,"config":2500},"Ensured vulnerability checks",{"icon":239},{"metric":2502,"config":2503},"Automated manual processes",{"icon":902},"2,761\n","Lincoln, NE",[2507,2510,2512],{"value":2508,"metric":2509},"20x","faster deploy time in Development environment",{"value":1203,"metric":2511},"faster deploy time in Production environment",{"value":2513,"metric":2514},"1,339","hours saved annually across teams","Duncan Aviation relies on GitLab Ultimate's SaaS offering to streamline software deployments and adapt to evolving security and compliance requirements\n","This leading aviation services company relies on GitLab Ultimate's SaaS offering to streamline software deployments and adapt to evolving security and compliance requirements.\n",[2518],{"quoteText":2519,"author":2520,"authorTitle":2521,"authorCompany":2490},"GitLab helped us to automate manual processes using pipelines. Now we are deploying code regularly, getting essential changes and fixes to our customers a lot faster","Ben Ferguson","Senior Programmer, Duncan Aviation",[2523,2526,2529,2532],{"header":2524,"text":2525},"Duncan Aviation deploys software that supports its jet services offerings, including maintenance, repair and operations","\n[Duncan Aviation](https://www.duncanaviation.aero/) is the world's largest privately owned jet service provider, maintaining jets for business and government agencies, as well as for other aircraft service providers. Services include 24x7 system troubleshooting, repairs, and overhauls. The company's systems allow clients to track the progress of work being done on their aircraft. The company, founded in 1956, has three full-service facilities located in Battle Creek, MI, Lincoln, NE, and Provo, UT.   Duncan Aviation works to comply with Cybersecurity Maturity Model Certification (CMMC) guidelines, in keeping with federal guidelines, to better secure software infrastructure. To do this, they establish and enforce security configuration settings for information technology products employed in the organization's systems. Secure configurations are an important aspect of Duncan Aviation's competitive advantage.",{"header":2527,"text":2528},"Automate and speed builds, while meeting evolving security compliance goals","\n\nAs development teams looked to accelerate software delivery, they quickly concluded that their collection of in-house deployment tools were not effectively scaling. Deploying code to a production environment required manual builds, testing, and deploying, which were prone to human error. Due to the lack of concrete documentation of what was actually deployed, errors were often solved by a redeploy rather than digging into the problem. Development managers knew automated scanning, tests, and linting were required. At the same time, Duncan Aviation's efforts to implement emerging government guidelines for secure applications highlighted its lack of dependable, repeatable, and full-featured deployment processes.\n\nTo solve these problems, the company needed a single-solution, end-to-end DevOps platform. A tech team at Duncan Aviation appraised a host of DevOps options, including both GitLab and GitHub. The team chose GitLab Ultimate. The SaaS-based platform, which is ideal for organizations looking to optimize and accelerate delivery while managing priorities, security, risk, and compliance, was brought on, in part, to scan for and identify vulnerabilities, and perform auditing and documentation. Choosing GitLab helped Duncan Aviation ensure compliance, while monitoring deployment status and providing insights into, and feedback on, pipeline issues.",{"header":2530,"text":2531},"Agile methods take off with help from GitLab","\n\nGitLab Ultimate enables Duncan Aviation teams to conserve development and administration resources and implement Agile DevOps methods, while advancing shift-left security, enabling them to identify and fix defects much earlier in the software development lifecycle. The platform also automates formerly manual pipeline and scanning processes. “GitLab does everything we need it to. It ensures compliance, automates testing, and implements our changes quickly and consistently,” said Ben Ferguson, senior programmer/analyst at Duncan Aviation. “As a result, we worry less about implementing code and more about solving problems for our customers.”\n\nUsing GitLab's DevOps platform, Duncan Aviation's production time dropped on average from 45 minutes to 5 minutes. Regular platform updates are assured, giving Duncan Aviation immediate access to all of the platform's latest security, automation, collaboration, and online learning features. The platform also provides visibility across projects, reducing development time from 20 minutes to just 1 minute. GitLab also decreases administrative burdens, annually saving the team approximately 1,339 hours.  Many CMMC requirements are addressed with GitLab, including efficient and fast identification and correction of system flaws; enforcement of security configuration settings for tools used in organizational systems; tracking of log changes; and analysis of the security impact caused by implementation changes.",{"header":2533,"text":2534},"Code insight drives software confidence and secures vital aviation services","\nWith GitLab Ultimate, Duncan Aviation saves time on system administration requirements. Its continuous integration and source code management capabilities streamline processes, supporting Agile methods. Team members can see pipeline issues, as well as security reports, all in one place, without the need to load and access multiple tools. Complex software fixes that could have delayed status updates for clients now are seamless and immediate.\n\nGitLab security scanning has made Duncan Aviation teams more aware of vulnerability issues at the development stage as well as throughout the software lifecycle, positively impacting practices, according to Ferguson. “We deploy a lot more code than we used to, and it's a lot easier to deploy,” he said. “GitLab has helped us with our confidence that everything is working correctly. GitLab helps us, because we have more insight as to what code is running and where.” All and all, GitLab empowers teams, mitigates risk, differentiates customer services, and keeps Duncan Aviation software efforts at the forefront of change.",{"template":950,"size":44,"region":102,"industry":55},"content:en-us:customers:duncan-aviation.yml",{"_path":2538,"content":2539,"config":2583,"_id":2584},"/en-us/customers/dunelm",{"name":2540,"logo":2541,"hero":2542,"heroImage":2543,"benefits":2544,"industry":81,"employeeCount":2554,"location":2555,"solution":913,"stats":2556,"headline":2563,"summary":2564,"quotes":2565,"content":2570},"Dunelm","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745517933/b6rf2h72y0rvv8pwzgaf.svg","Dunelm “shifts left”: U.K. homewares leader moves security to front of cycle, boosts cloud move","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518416/tddtgezk4ce1fs1akh0a.png",[2545,2548,2551],{"metric":2546,"config":2547},"Increased security",{"icon":239},{"metric":2549,"config":2550},"Streamlined collaboration",{"icon":1895},{"metric":1026,"config":2552},{"icon":2553},"Agile","3300+","Leicester, U.K.",[2557,2560],{"value":2558,"metric":2559},"75-85","deployments per week (previously 10-20)",{"value":2561,"metric":2562},"Hours","For onboarding instead of days","Dunelm Group PLC vigorously pursued fast development and deployment that baked in security at the outset.","The retailer chose GitLab SaaS Ultimate to integrate tools and seamlessly deploy secure pipelines on the AWS cloud.\n",[2566],{"quoteText":2567,"author":2568,"authorTitle":2569,"authorCompany":2540},"GitLab can do everything we want it to do, from security, performance, testing, and more.\n","Chintan Parmar","Principal Platform Engineer",[2571,2574,2577,2580],{"header":2572,"text":2573},"CI/CD improvements help drive Dunelm’s tech culture","Founded in 1979, Dunelm grew into the United Kingdom’s top homewares retailer, with distribution centers, 178 stores, and a robust ecommerce operation. The company sees over 12 million online transactions per year, while maintaining a large online catalog of homewares and home furnishings. More than ever, Dunelm relies on innovative technology engineering to improve customer experiences.\n\nThis occurs in a retail environment that was dramatically altered by digital transformation. Continuous integration and deployment (CI/CD), assured security, test-driven development, agile sprint-based planning, and advanced DevOps tooling are key parts of Dunelm tech culture. The company’s technology teams are also readily embracing serverless technologies, event-driven architecture, and cloud-first development.\n",{"header":2575,"text":2576},"Retailer looked to build open-source dexterity on stable automation platform","As Dunelm engineering teams accelerated their move to their target architecture of serverless technologies and cloud first, they identified serious gaps in their existing CI/CD tooling. Greater automation, improved governance, security, and agility were necessary in order to integrate a variety of plug-ins and to quickly create resilient software pipelines. Existing workflows — including those based primarily on Jenkins — called for hands-on management and an undue degree of firefighting for any cases of breaking code, and visibility into pipelines was lacking.\n\nThis loomed as a continual and pressing strain on administrative management for Dunelm. Engineering leadership wanted a strategic, stable platform that was scalable. Importantly, better static application security testing (SAST) and dynamic application security testing (DAST) were needed in the face of global cybersecurity threats. Comparative evaluations led Dunelm leadership to identify GitLab CI/CD as the DevOps platform to enable tech teams to “shift left” — that is, to take on performance, testing, and security issues at the beginning of, and throughout, the software development lifecycle, according to Chintan Parmar, Principal Platform Engineer at Dunelm.\n",{"header":2578,"text":2579},"Seamless pipeline deployments to AWS using GitLab","Today, GitLab’s DevOps platform is used to effectively and securely manage builds, integrations, and deployments of Dunelm’s services. “Previously, we built the libraries and functionality in-house for our CI/CD pipelines. If we wanted to do anything new, we had to write this ourselves,” says Parmar. “GitLab can do everything we want it to do, from security, performance, testing, and more. We can build our pipelines in a readable, modular, and consistent fashion.” The platform’s integration capabilities have proved to be particularly useful in creating pipelines on AWS. “Pipelines are deployed seamlessly to AWS using GitLab,” Parmar adds.\n\nAt the same time, the GitLab platform offers other benefits to Dunelm.\n\nFor example, fully onboarding a new developer into Dunelm’s technology stack now may take hours as opposed to days. Furthermore, GitLab’s fully documented workflows get members of multiple teams quickly up to speed on any issues coming out of Dunelm’s pipelines. The GitLab platform facilitates effective collaboration with features such as the merge request process. As a result, developers, quality engineers, site reliability engineers, and others can work in tandem when addressing issues with pipelines. “GitLab’s tech teams have been helpful to engage with us in the implementation of the platform,” says Parmar.\n",{"header":2581,"text":2582},"Teams run more scans, tackle vulnerabilities, collaborate effectively","GitLab effectively supports Dunelm’s objective to “shift left” as part of their DevSecOps strategy. Dunelm teams can run more sophisticated scans more often and in an automated fashion within GitLab pipelines. With SAST/DAST scanning, secret detection, dependency scanning, and more at early stages, security vulnerabilities are captured much earlier in the process, and consequently are remediated much earlier in the software development cycle. The benefits are passed down to customers using Dunelm’s ecommerce platform, because so much security work is done well ahead of software delivery.\n\nThe platform also supports increased numbers of deployments through automation without requiring additional developer and administrator effort. Meanwhile, the GitLab platform has enabled better collaboration between teams, supporting true DevOps partnerships between the different squads and tribes. The software provides visibility into pipeline work that is useful for management of overall operations. This also enables teams to be prepared for code audits. With GitLab Ultimate SaaS, Dunelm was able to manage an open source tool chain using a convenient self-service model. GitLab’s plug-and-play integrations with third-party tools such as Jira, Datadog, Terraform, Slack, and others means teams were no longer “managing blind.”\n\n“We were looking for a platform that made sure we could build pipelines seamlessly, and also had security built in from the onset,” says Parmar. “That meant the platform aligned with our tech principles — a fast feedback loop, continuous improvement, and delivering working software quickly and safely to our customers.”\n\n“The GitLab user interface is designed and built to provide an end-to-end stack view. As far as visibility goes, projects are easier to see within GitLab. So, I can see what’s going on much more easily, but if I want, I can still get my hands dirty, and look at what code is being produced. We are generally releasing more quality software with GitLab,” Parmar adds. He also pointed to GitLab’s regularly published technology roadmaps and its monthly release cycle as important factors in making sure Dunelm stays at the forefront of cutting-edge technology.\n\nFinally, GitLab has contributed to that highly treasured benefit: developer happiness.\n\n“One thing to point out is that it makes engineering teams happier, which is something we’re always striving to improve,” says Parmar. “When you’re using good tooling and good products, this always helps. If techies love using it, they’re going to work happier, smarter, more efficiently.”\n",{"template":950,"size":44,"region":106,"industry":83},"content:en-us:customers:dunelm.yml",{"_path":2586,"content":2587,"config":2637,"_id":2638},"/en-us/customers/european-space-agency",{"name":2588,"logo":2589,"hero":2590,"heroImage":2591,"benefits":2592,"industry":1530,"employeeCount":2601,"location":2602,"solution":975,"stats":2603,"headline":2612,"summary":2613,"quotes":2614,"content":2624,"contributors":1281},"European Space Agency","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745517978/yowlmyzlt1fycrddtqhw.svg","How the European Space Agency uses GitLab to focus on space missions","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518440/fo1fhbsp5wz2fznpilgn.jpg",[2593,2595,2599],{"metric":1022,"config":2594},{"icon":1738},{"metric":2596,"config":2597},"Faster code deploys",{"icon":2598},"Code",{"metric":1293,"config":2600},{"icon":1895},"5,000","France, Netherlands, Italy, Germany, Spain, United Kingdom, Belgium",[2604,2607,2609],{"value":2605,"metric":2606},"~15%","of ESA employees using GitLab",{"value":2608,"metric":1315},140,{"value":2610,"metric":2611},"60k+","jobs the first year","The European Space Agency (ESA) has always carefully deployed new technologies. But without a central version control system in place, opportunities for collaboration, synergies and multiple exploitations of effort were less visible.","With GitLab, teams across ESA can now collaborate and share code and insights both within their teams and with other teams. GitLab is allowing teams to cross borders, increase cooperation and reshape working culture.\n",[2615,2620],{"quoteText":2616,"author":2617,"authorTitle":2618,"authorCompany":2619},"To see people collaborating is contagious. People are saying, ‘Hey, I want to have a project like that!’ or ‘I want to participate.’ These kinds of things can happen because everybody has access,\n","Redouane Boumghar","Research Fellow","ESA",{"quoteText":2621,"author":2622,"authorTitle":2623,"authorCompany":2619},"I think our use case is quite interesting at ESA. Our team develops software, and we are also flying spacecraft. So developing software is in addition to our main activity. There are a lot of tools that we\nrequire to support us in our actual job. In that sense, we want to minimize the time that we spend to build these tools. Furthermore,\nGitLab has also shown that it is very effective in sharing our tools with other teams.\n","Bruno Sousa","Spacecraft Operations Manager",[2625,2628,2631,2634],{"header":2626,"text":2627},"Leading the charge as Europe’s gateway to space","The European Space Agency (ESA) provides a European-wide Space Programme. ESA's programmes are designed to find out more about Earth, its immediate space environment, our Solar System, and the Universe, as well as to develop satellite-based technologies and services and to promote European industries. ESA also works closely with space organizations outside Europe.\n\nESA is responsible for coordinating the financial and intellectual resources of its 22 member states to ensure that investment in space continues to deliver benefits to the citizens of Europe and the world. The organization focuses on a wide variety of missions focused on space exploration and continued research. Some of their recent missions include sending orbiters to Mercury and studying hypervelocity stars in the Milky Way.\n",{"header":2629,"text":2630},"Lacking version control and collaboration","TESAhas always carefully deployed new technologies. Validation and security have been at the fore, and there is less drive to invoke newer practices or technologies for their own sake unless they clearly bring added benefits for ESA’s core business. This sometimes resulted in using older, trusted tools to share code, at the expense of timeliness.\n\nIn 2015 different teams within ESA were using a heterogeneous approach to control systems, such as Subversion or CVS. The emergence of Git, and its subsequent adoption by the ESA IT Department, was a harmonious intersection of user needs and secure technology. GitLab was validated and adopted by ESA as a code repository platform in 2016. Usage was initially limited to a hand-picked group of first-wave users, but demand quickly escalated.\n\nIn just two years, more than 140 groups adopted GitLab as their software versioning tool. Across ESA, more than 1,500 software projects have been created. These range from mission control systems and onboard software for spacecraft to image processing and monitoring tools for labs. The ESA IT Department also uses GitLab to host their code tools and configurations infrastructure.\n",{"header":2632,"text":2633},"Creating a culture where collaboration is contagious","GitLab was introduced to the ESA population in 2016. Teams across Europe embraced the tool at all ESA establishments and sites. They can now collaborate and share code and insights both within their teams and with other teams. The process is faster, in real time, and produces reliable, stable results. Users can use more of their time to focus on their mission-critical tasks and spend less time keeping tools running.\n\nThe adoption rate was high. Within one week 40 projects were running in GitLab. “Right now, we have 15% of our user population using GitLab”, a representative from the ESA IT Department GitLab project commented.\n\nFor ESA, this represents a departure from the previous software development culture. In the past, it was assumed that there were fewer synergies to be exploited. Version control systems were individualised, or teams had not implemented them. As the technology now matches ESA’s needs, GitLab lets ESA approach more standardisation and efficiency.\n\nInitially, ESA implemented GitLab to exploit the version control capabilities within the tool. However, the user community has also benefitted from the continuous integration and delivery (CI/CD) capabilities within GitLab. ESA began using CI/CD capabilities in November 2017, and there are currently 60,000 jobs in GitLab. Feedback to the ESA IT Department from the user community has conveyed the user’s satisfaction with this development. One user reported, “We initially started using version control, but we discovered that we could use CI on our project. We tried it out and were immensely impressed with how well it all worked together”.\n\nESA’s diversity of teams and tasks provides unique challenges. Bruno Sousa explains why his tasks require CI/CD, saying, “For our use case, in particular, the CI/CD capabilities are extremely important. In my role I am simultaneously responsible for flying a spacecraft and developing a tool for us, and also potentially for other missions. I don’t have the time to deploy the software over and over again, so GitLab is very helpful in facilitating the whole process. It makes everything easier so that I can focus on my core task of flying the spacecraft.”\n",{"header":2635,"text":2636},"Increasing excitement and speed around code deployments","GitLab has provided a software development turnaround speed that ESA had not previously been able to achieve. The code is now continuously deployed in a matter of minutes, when previously it may have taken weeks.\n\nGitLab is able to address challenges along many stages of the software development pipeline. In the past, different ESA teams were using a variety of CI/CD engines. Now they are being replaced with GitLab CI because GitLab is more user-friendly. As more users move to GitLab, ESA’s obligation to maintain other tools is removed. GitLab CI is then integrated into more version control systems.\n\nThe automation in GitLab also saves ESA IT Department resources. With operation and backup fully automated, IT Specialists can focus on monitoring the tool and, importantly, addressing more IT challenges for the agency.\n",{"template":950,"size":44,"region":106,"industry":87},"content:en-us:customers:european-space-agency.yml",{"_path":2640,"content":2641,"config":2688,"_id":2689},"/en-us/customers/everymatrix",{"name":2642,"logo":2643,"hero":2644,"heroImage":2645,"benefits":2646,"industry":2656,"employeeCount":2657,"location":2658,"solution":975,"stats":2659,"headline":2668,"summary":2669,"quotes":2670,"content":2675,"contributors":1281},"EveryMatrix","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745517980/i8aoclmauk91m7kg74o4.png","Learn how EveryMatrix wins big with GitLab","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518441/z2csnv0ltc1ynyy5ydl0.jpg",[2647,2650,2653],{"metric":2648,"config":2649},"Seamless support for peer review",{"icon":1295},{"metric":2651,"config":2652},"Improved automation",{"icon":1423},{"metric":2654,"config":2655},"More transparency",{"icon":2445},"Gaming","300","Bucharest, Romania (HQ)",[2660,2662,2665],{"value":2163,"metric":2661},"user growth in 1 year",{"value":2663,"metric":2664},"42%","yearly growth in pipelines",{"value":2666,"metric":2667},"25%","yearly growth in 1,700 projects","When they decided to adopt a DevOps platform, EveryMatrix's development and infrastructure leaders turned to GitLab Self-Managed Premium.","The full-service B2B gaming platform provider wanted faster iterations and better control over open-source innovation.\n",[2671],{"quoteText":2672,"author":2673,"authorTitle":2674,"authorCompany":2642},"With GitLab, it’s not just a set of tools, it’s also the culture of the company. If there is an incident, we receive answers in a very transparent way. That’s important for our culture here, too. We are dealing with gaming players. If players feel you are not transparent, they run away. Trust is key.\n","Rafael Campuzano","Group CTO",[2676,2679,2682,2685],{"header":2677,"text":2678},"Moving gaming services forward","[EveryMatrix](https://everymatrix.com/){data-ga-name=\"everymatrix\" data-ga-location=\"body\"} provides an API-based B2B product suite for casino, sports betting, payments and affiliate management in highly regulated industry segments across the globe. Elements provided include delivery of content, betting odds, and scores, as well as transactional support for real-time settlements, analytics, and risk management, all encompassed in a platform providing assured player protection. Work is supported by a dedicated infrastructure team that is responsible for governance and ensuring adherence to regional and local regulations. Services can be deployed as independent or integrated solutions. With live sports on hold during parts of the COVID-19 pandemic, the company successfully included more virtual sport events in its offerings. EveryMatrix solutions have evolved to cover more than 125 sports and virtual sports, comprising over 105,000 live events in early 2021.\n",{"header":2680,"text":2681},"Building a practical open-source services delivery platform for a fast-paced sector","As a global provider of advanced gaming services, EveryMatrix is focused on fast-paced, innovative solution development and dependable software deployment for users in a wide selection of countries and regions. Such lively progress is tempered in gaming, as elsewhere, by a need for security, high availability, and reliability that helps ensure trust of clients and their online customers. With a growing focus on APIs and Kubernetes, it became clear the development teams needed more streamlined and automated workflows.\n\nGeneral tooling advances and the need to install important add-ons underscored the requirement to adapt to tools flexibly and quickly. To effectively implement agile processes, EveryMatrix teams needed assurance that everything was in one place, that workflows were well-documented, and that front-line developers didn’t have to be versed in a different installation method for each tool they needed to use. Programmer teams needed dependable peer review and approvals processes. In addition, the system had to be capable of providing transparency to other stakeholders in the organization. CI/CD support that enabled such innovation was a must-have, and GitLab Premium was the choice.\n",{"header":2683,"text":2684},"A unified GitLab workflow and one DevOps platform","GitLab Premium implementation meets EveryMatrix requirements for a single repository that reduces the complexity of working with multiple open-source frameworks. Integrated, flexible tooling supports teams’ initiatives to automate repetitive tasks and to deploy open-source software quickly and securely. Now, developers no longer need to change from tool to tool, managing multiple different installations, according to Rafael Campuzano, Group CTO at EveryMatrix. GitLab thus supports the company’s daily DevOps-oriented project work by providing everything necessary in a single tool, with regularly updated functionality.\n\nAll business units have implemented GitLab’s container registry, Campuzano said, and all teams are able to set up rules for code pushes through the repository. Importantly, he added, GitLab has been implemented in such a way that different business units can effectively interact with one another, while sharing and integrating code based on teams’ individual priority cycles. “GitLab for us is a really important tool to achieve an internal open-source model,” said Campuzano.\n",{"header":2686,"text":2687},"Trust is key for open-source model","The new platform has become key to improvements in processes and workflows, and now supports more than 200 developers. “With GitLab, all approval processes and code review mechanisms provide exactly the features we need. It’s a perfect fit with our intentions,” said Teodor Coman, Frontend Technical Director at EveryMatrix. “GitLab CI/CD tools are the core of our operations.”\n\nTeams can set up pipelines and manage deployments with much better control. Moreover, with GitLab, teams benefit from workflow approval and peer review capabilities. EveryMatrix team members give GitLab high marks for culture and adherence to open-source philosophy. Incidents and updates are handled in a transparent way. EveryMatrix has reaped huge benefits using GitLab; 50% user growth from 200 to 300 in just one year, 25% annual project growth, and over 42% annual growth in pipelines, with over 250,000 pipelines per year.\n\n“With GitLab, it’s not just a set of tools, it’s also the culture of the company. If there is an incident, we receive answers in a very transparent way. That’s important for our culture here, too,” said Campuzano. “We are dealing with gaming players. If players feel you are not transparent, they run away. Trust is key.”\n",{"template":950,"size":40,"region":106,"industry":91},"content:en-us:customers:everymatrix.yml",{"_path":2691,"content":2692,"config":2728,"_id":2729},"/en-us/customers/extra-hop-networks",{"name":2693,"logo":2694,"hero":2695,"heroImage":2696,"benefits":2697,"industry":2704,"employeeCount":2705,"location":2706,"solution":975,"headline":2707,"summary":2708,"quotes":2709,"content":2714,"contributors":1281,"stickyBenefits":2727},"ExtraHop Networks","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745517981/ddgtfnktgwqij5gptgdf.svg","ExtraHop fully embraces CI/CD process transformation with GitLab","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518441/tmmpxhxeenwo32ewfzax.jpg",[2698,2700,2702],{"metric":2249,"config":2699},{"icon":1629},{"metric":961,"config":2701},{"icon":963},{"metric":1297,"config":2703},{"icon":902},"IT management","300-500","Seattle, Washington, USA","ExtraHop provides analytics and investigation solutions to improve enterprise security and performance at scale. The world's leading organizations trust ExtraHop to support core digital business initiatives like security, IT modernization, and application service delivery.","GitLab’s highly integrative tool drove alignment across the ExtraHop development team and accelerated transition to CI/CD\n",[2710],{"quoteText":2711,"author":2712,"authorTitle":2713,"authorCompany":2693},"With GitLab, we finally had a single tool that not only aligned to divergent engineering workflows, but also allowed for meaningful continuous integration.\n","Bri Hatch","Director of IT",[2715,2718,2721,2724],{"header":2716,"text":2717},"Provider of analytics and investigation solutions that improve enterprise security and performance at scale","ExtraHop applies real-time analytics and advanced machine learning to every business transaction to deliver unprecedented visibility, definitive insights, and immediate answers that enable security and IT teams to act quickly and with confidence. The world’s leading organizations, including Microsoft, Paypal, Sutter Health, and many others, trust ExtraHop to support core digital business initiatives like security, IT modernization, and application service delivery.\n",{"header":2719,"text":2720},"Meeting the needs of a divided development team","Like many engineering organizations, the ExtraHop development team was deeply divided on how to best execute changes to their code. While the organization traditionally used Gerrit, a new generation of engineers experimented with Bitbucket. What was to be a six-month trial turned into a four-year standoff, with the company finding itself sandwiched between two factions of engineers rallying behind the tool that allowed for their preferred method of commits: bulk versus single.\n\n“Gerrit would always have, essentially, just one single commit at a time that was being amended on each change,” said Bri Hatch, Director of IT at ExtraHop. “That worked great for dinosaurs like myself who like a pristine linear commit history where each commit pushed is fully functional. An equally valid option championed by those who cut their teeth on the GitHub model is to iterate and push multiple commits together, dead-ends and all, via a single merge request.”\n\nExtraHop needed to strike a balance between maintaining the happiness of veteran and newer engineers alike.\n\nHatch continued, “Engineers are an opinionated bunch, and the holy war centered around amended commits (Gerrit) versus merge requests (Bitbucket). But unlike vi versus emacs – where every engineer can use the tools they like and not interfere with each other’s workflows – here we needed a single production system for code review that supported meaningful cross-team collaboration.”\n\nThe division regarding commit models was also impacting the engineering team’s ability to fully embrace the CI/CD model. While continuous delivery was possible with their multi-tool approach, continuous integration – and the ability to identify issues in the code before it ever got to test – was still largely aspirational.\n\n“Achieving a true CI/CD model is kinda like Nirvana: great if you can get there, but pretty hard to do,” said Hatch. “We had a lot of the processes in place, but we lacked critical alignment and the right technology to support the model.”\n",{"header":2722,"text":2723},"Flexible workflow options with GitLab","With no end in sight to the multi-year Gerrit/Bitbucket standoff, engineering management was open to other options. Their first experience with GitLab came during the annual ExtraHop hackathon: “One of the engineers spun up their own GitLab instance on their workstation,” said Kevin Tatum, IT Systems Engineer at ExtraHop. “They migrated some repositories over and worked in parallel between the systems, doing all the code review in GitLab on the sly.”\n\nWhen the team looked at the results, they saw a promising compromise. GitLab offered a model that aligned to the two different workflows that had long divided the development team: single and bulk commits.\n\nGitLab Auto DevOps also delivered the technology component required for true CI/CD, accelerating product delivery with an end-to-end pipeline out of the box.\n\n“With GitLab, we finally had a single tool that not only aligned to divergent engineering workflows, but also allowed for meaningful continuous integration,” said Hatch.\n",{"header":2725,"text":2726},"Accelerating business process transformation with CI/CD and engineering alignment","While ExtraHop had been following a CI/CD model for a few years, the use of disparate developer tools left gaps in the model. Moreover, while the tools they were using supported continuous delivery, they didn’t function well for the critical continuous integration piece.\n\nWith GitLab, ExtraHop is well on the way to fully embracing the CI/CD model from both a process and tooling perspective. When the engineering team first began working with GitLab, they found that GitLab CI/CD runners were powerful yet easy to manage.\n\n“One of our IT engineers had some ‘spare time’ during a meeting and implemented CI against the unit tests they’d been running manually in the Gerrit world. When training the rest of the team they waited for the other shoe to drop, but no - it really was as straightforward as it looked.”\n\nNow the ExtraHop engineering team gets web and email notifications on build breaks and cannot commit code that will not work in production.\n\n“Our initial GitLab scope did not include adding or migrating to their CI/CD up front,” said Hatch. “Given the ease of use, however, we’ve bumped the priority of moving to GitLab’s CI/CD and it’s something we’re actively working on. When we saw what was possible for our team, it was a no-brainer.”\n\nMoving to GitLab has also allowed ExtraHop to meet the code review preferences of its entire development team with ease. With GitLab’s integration capabilities, single and bulk commits are available to the entire development team. The versatility appeases the varied workflow needs of ExtraHop engineers who may prefer Gerrit over Bitbucket and vice versa.\n\nThe intuitive user interface (UI) was also a significant bonus for the ExtraHop team.\n\n“When looking at UIs, we wanted something that was extremely intuitive to use, as well as fresh, dynamic, and evolving. GitLab was great. I find GitLab, the UI, infinitely more accessible than the Bitbucket UI,” said Hatch.\n\nExtraHop is still in the process of transitioning to GitLab, with 80% of its repositories now migrated over to the application. They are currently migrating their legacy build environments and are interested in GitLab’s Kubernetes capabilities.\n\n“GitLab was the right choice for us. Every tool is different; every tool has ups and downs,” he said. “But for us, GitLab worked on so many levels.”\n",{"benefits":1281},{"template":950,"size":40,"region":102,"industry":91},"content:en-us:customers:extra-hop-networks.yml",{"_path":2731,"content":2732,"config":2773,"_id":2774},"/en-us/customers/fanatics",{"name":2733,"logo":2734,"hero":2735,"heroImage":2736,"benefits":2737,"industry":81,"employeeCount":978,"location":2749,"solution":913,"stats":2750,"headline":2758,"summary":2759,"content":2760},"Fanatics","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745517983/mmjjsj2yycc3igvjokrb.svg","GitLab offers Fanatics the CI stability they were searching for","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518442/tddr7ccwzmfrevg9hzxf.png",[2738,2741,2745],{"metric":2739,"config":2740},"Improved CI stability",{"icon":2105},{"metric":2742,"config":2743},"Improved job scheduling",{"icon":2744},"ClockAlt",{"metric":2746,"config":2747},"Increased user happiness",{"icon":2748},"Values","Jacksonville, FL; San Mateo, CA; Manchester, England; Boulder, CO",[2751,2754,2756],{"value":2752,"metric":2753},"800","projects migrated in three months",{"value":2657,"metric":2755},"users",{"value":1034,"metric":2757},"user happiness rating","Fanatics improved CI stability by moving to GitLab.","Fanatics’ successful GitLab CI transition empowers innovation cycles and speed",[2761,2764,2767,2770],{"header":2762,"text":2763},"Bringing the game home to fans","Fanatics is a sports retailer that operates more than 300 online and offline stores. Fanatics offers a tech-infused approach to the world’s largest collection of sports team apparel and jerseys. Their mission is to amplify pride and create connections for all sports fans.",{"header":2765,"text":2766},"Going around in circles","The Fanatics cloud team has approximately 20 members tasked with all operations pertaining to cloud services and DevOps — including any Amazon Web Services (AWS) integrations. The integration team leader is responsible for running the continuous integration and continuous delivery (CI/CD) pipelines for Fanatics. In late 2018, the team was burdened with working on ongoing issues, such as patches and putting out fires. “It was not a very happy experience,” said Guilherme Goncalves, cloud tech lead. “The support was not very good. We had to solve all the issues ourselves.”\n\nMost of his time was spent fixing patches and working to solve issues with their legacy tooling, which included CircleCI. The issues were directly impacting the cloud team and slowed down release times, stopped the deployment of block ends, and caused memory leaks. The whole CI flow was unstable, especially impacting the cloud team.\n\nThe Fanatics team spun up proofs-of-concept with several tools, including Travis and CodeBuild, but they ended up discarding them due to issues such as vendor lock-in, performance, flexibility, and scalability. This burdened Goncalves’ role to the point that his boss said that if he found a solution, a better tool, then he could make the call to make the switch.",{"header":2768,"text":2769},"Finding stability in a unique tool","Goncalves took his time to find a tool that had the same performance values as their existing tool, but included a level of stability that other tools couldn’t provide. “I researched everything. I looked at the CI tools out there, and I found GitLab and I loved it,” he said.\n\nHe was the company’s biggest advocate for driving change. He created a GitLab channel, made demos, and asked all the important questions ahead of time. He also implemented multiple proofs-of-concept in his research for a tool that would be stable and integrate seamlessly into the existing infrastructure. Goncalves encouraged people to experiment for themselves, he said, because GitLab is very powerful.\n\nAfter the push from Goncalves, the decision was made to move over to GitLab at the end of 2018. It took the team about three months to make the entire transition and fully migrate 800 projects. There are now 300 users and about 60 teams using GitLab for CI. “I would say my first three months the cloud team was shifted to entirely GitLab,\" he said. \"It was a good investment because GitLab is now running and I don’t need to take care of it anymore.”",{"header":2771,"text":2772},"Gaining time to focus on business-differentiating efforts","With GitLab, the cloud team at Fanatics has gained the ability to focus on innovation instead of worrying about patches and constant issues. “Because GitLab is much more stable, we are able to focus on Fanatics-specific challenges, rather than basic infrastructure issues,” Goncalves said. GitLab’s support system is responsive and transparent, so if and when issues arise, there is help.\n\nThe team has started to put more focus on continuous deployments, now that they don’t have to constantly put out fires in the CI world. They can also schedule jobs, which is a feature that CircleCI doesn’t offer. Team members are able to work with group-level environment variables, empowering them to experiment more with workflows and schedule jobs. The benefits to moving to GitLab’s stable CI not only increased the ability to deliver, but allowed the development and engineering teams to collaborate more efficiently.\n\nSome teams are experimenting with GitLab’s source code management capabilities and are exploring how GitLab can help with continuous deployment into the future.\n\nOverall, Goncalves believes that GitLab would receive an approval rating of over 90% from fellow users at Fanatics. “Everyone is just happy that their builds are running in a timely fashion and stable enough that they never fail,” Goncalves said.",{"template":950,"size":40,"region":102,"industry":83},"content:en-us:customers:fanatics.yml",{"_path":2776,"content":2777,"config":2817,"_id":2818},"/en-us/customers/fujitsu",{"name":2778,"logo":2779,"hero":2780,"heroImage":2781,"benefits":2782,"industry":89,"employeeCount":2793,"location":2794,"solution":975,"headline":2795,"summary":2796,"quotes":2797,"content":2803,"contributors":1281,"stickyBenefits":2816},"Fujitsu","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745517985/d2olilyww13vx13xv54j.png","Fujitsu Cloud Technologies improves deployment velocity and cross-functional workflows with GitLab","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518442/xrobqjbuh28xhf1w8hr5.jpg",[2783,2786,2789],{"metric":2784,"config":2785},"All-in-one DevOps environment",{"icon":967},{"metric":1847,"config":2787},{"icon":2788},"RemoteChat",{"metric":2790,"config":2791},"Access to quick audits",{"icon":2792},"ClipboardTest","296","Tokyo, Japan","Fujitsu Cloud Technologies was looking for a way to share the knowledge and expertise of the company's internal developers and operators across projects.","By adopting GitLab as a single integrated DevOps platform for source code management (SCM) and continuous integration (CI), Fujitsu Cloud Technologies has seen significant improvements in efficiency and quality.\n",[2798],{"quoteText":2799,"author":2800,"authorTitle":2801,"authorCompany":2802},"We believe it is the right tool for achieving DevOps in Japanese business practices.\n","Yuichi Saotome","Principal Engineer, Cloud Infra Division","Fujitsu Technologies",[2804,2807,2810,2813],{"header":2805,"text":2806},"Leader in global cloud technology","[Fujitsu Cloud Technologies](https://fjct.fujitsu.com/) is a service provider offering Infrastructure as a Service (IaaS), Platform as a Service (PaaS), and Software as a Service (SaaS) to over 8,000 customers. Since 2010, the company has been providing software as a service through the Internet via its cloud service NIFCLOUD, a domestically produced public cloud service that utilizes cutting-edge technology. They contribute to a vision of a sustainable society by providing reliable cloud services that everyone can use. They aim to become the “No. 1 enterprise cloud” of Japanese quality.\n",{"header":2808,"text":2809},"Moving from VCS to Git","Before GitLab, each project had a separate Git and SVN management tool. It is common in Japanese business practice to bring in development and operations engineers from outside the company on a project-by-project basis. However, it is difficult to properly manage the authorization to work with internal engineers to achieve DevOps. “I wanted to create a way to share the knowledge and expertise of our internal developers and operators across projects,” said Yuichi Saotome, Principle Engineer, Cloud Infra Division, Fujitsu Cloud Technologies.\n\nDue to the inability to properly manage authorizations, various tools were introduced on a project-by-project basis, causing knowledge and expertise to be siloed. They were indiscriminately deploying different tools for different teams and distributing the necessary elements of service development among the tools. Some of the tools used on a project-by-project basis included:\n\n* GitBucket\n* BitBucket\n* Redmine\n* Jira\n* Jenkins\n* Drone CI\n* Circle CI\n\nAround 2014, the momentum to unify VCS to Git grew. There were many different VCSs, but Git was able to meet a majority of their needs. The biggest priority for Saotome and his team was the ability to manage approvals in line with Japanese business practices. Secondly, it must be an all-in-one (complete) DevOps environment. “We knew that using a combination of various tools would be very wasteful, so we looked for a tool that integrated the elements we needed at the time: issue management, progress management, code management, CI, and CD,” Saotome said.\n",{"header":2811,"text":2812},"Open DevOps platform for all","Initially, GitLab was adopted by a small team; however, its use gradually expanded. By 2016, the entire company was using a unified GitLab environment. The platform’s ability to be used cross-functionally created a shared know-how amongst team members throughout the company.\n\n“All of our employees (including non-engineers) and external engineers are using it. They say, ‘GitLab has allowed the concept of project management to permeate not only the development team, but also the operations, design, and sales teams, making it [easier to share knowledge and expertise](/solutions/devops-platform/){data-ga-name=\"devops platform\" data-ga-location=\"body\"},’” according to Saotome.\n\nGitLab’s “excellent” authorization management allows internal engineers to freely implement DevOps on any project they want. External engineers can also implement DevOps on a per-project basis with authorization. The coexistence of internal and external authorization made it easier to share know-how and expertise without fear of information leakage or internal or external barriers. Also, the addition of the Diff function for images and the WebIDE made it easier for non-engineers to use the software and expanded the range of its use.\n",{"header":2814,"text":2815},"Unified integrations, shared capabilities","After adopting GitLab, some initial successes included the ability to migrate Git repositories under project management tools that were previously scattered. On top of that, the GitLab service operation flow was praised by Fujitsu’s audit firm for being an “excellent workflow that [takes risk management into account](/solutions/application-security-testing/){data-ga-name=\"devsecops\" data-ga-location=\"body\"}.”\n\nEfficiency and quality have improved significantly with GitLab SCM. The development cycle previously took up to six months for the same team. Now, cycles can be released in as little as a few days. Team members also depend on GitLab’s monthly releases. “We’re excited about the new GitLab features that come out every month,” said Saotome.\n\nDetecting bugs earlier in the life cycle has increased output capabilities. “Quality testing goes smoothly right before release so that release dates can be met and marketing can be executed as planned,” Saotome shared. Validation is done in conjunction with GitLab CI using an in-house tool called vCell that recreates a small, virtualized infrastructure.\n\n[GitLab CI](/solutions/continuous-integration/){data-ga-name=\"continuous integration\" data-ga-location=\"body\"} has enabled teams to achieve fast deployments of small development units, such as blue-green deployments. The teams have gone from deploying once every six months (at the longest), which took about a day, to now deploying once every few weeks (at the shortest), which takes about five minutes.\n\nSlack, Jenkins, Prometheus, and Redmine are all plugged into GitLab. The integration has unified the procedures for issue management, progress management, code management, CI, and CD. All of these processes were previously different for each team, but GitLab’s DevOps platform has made it easier for teams to “flex their personnel and makes it easier for new members to join the team immediately,” Saotome added.\n",{"benefits":1281},{"template":950,"size":40,"region":110,"industry":91},"content:en-us:customers:fujitsu.yml",{"_path":2820,"content":2821,"config":2864,"_id":2865},"/en-us/customers/fullsave",{"name":2822,"logo":2823,"hero":2824,"heroImage":2825,"benefits":2826,"industry":2358,"employeeCount":1150,"location":2837,"solution":913,"stats":2838,"headline":2844,"summary":2845,"quotes":2846,"content":2851},"FullSave","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745517935/l1nyfg3uwhnanpl06cso.png","French telecom FullSave uses GitLab to reduce DevOps toolchain and dramatically multiply deployments","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518416/k3cylvdcxoziswn0sgmj.jpg",[2827,2830,2833],{"metric":2828,"config":2829},"Consolidated toolchain",{"icon":1423},{"metric":2831,"config":2832},"Increased code output",{"icon":2451},{"metric":2834,"config":2835},"Automated project deployment",{"icon":2836},"AutomatedCode","Labège, France",[2839,2841],{"value":1034,"metric":2840},"faster deployment time",{"value":2842,"metric":2843},"12x","increase in deployment frequency","FullSave, a telecommunications infrastructure operator based in France, is able to release software faster and more efficiently with GitLab's DevSecOps Platform.","A change in the licensing model of the company's previous issue tracking and project management tool, plus a desire to consolidate their toolchain, pushed FullSave to switch to GitLab.\n",[2847],{"quoteText":2848,"author":2849,"authorTitle":2850,"authorCompany":2822},"GitLab is an all-in-one solution that offers clarity and helps to improve the whole team’s efficiency.\n","Laurent Lavallade","Chief Technology Officer",[2852,2855,2858,2861],{"header":2853,"text":2854},"The customer","[FullSave](https://www.fullsave.com/) is a telecommunications infrastructure operator based in Labège, France. Founded in 2004, the private company has about 100 employees and provides connectivity services, cloud infrastructure, and shared hosting in its data centers. It also deploys and operates its own fiber network and offers adapted internet access services.\n\nFullSave has a history with GitLab. While the company has used several other DevOps tools for more than five years, it has also been using different versions of GitLab’s platform, such as the free version and the Enterprise edition. For instance, seven developers used the free version to deploy 302 projects, along with managing about 100 issues and 50 merge requests per month. Other teams used GitLab to exchange source code and configuration files with customers, to build and launch network and data center tools, and to automate project deployments and Docker builds.",{"header":2856,"text":2857},"The challenge","FullSave faced several challenges that were causing development and deployment slowdowns.\n\nThe company’s policy is to host its own tools but its previous tool’s new licensing model did not allow for self-hosting. As FullSave was met with this licensing issue, the company’s IT managers also recognized that they needed to replace their DevOps toolchain with a single, end-to-end DevOps platform for better CI/CD integration, to reduce complexity and boost productivity. They also knew that a single application would give them the issue and commit traceability they needed to obtain an ISO27001 certification, an internationally recognised standard that deals with the overall management of information security.\n\nGoing all in with GitLab’s platform was an easy decision for FullSave.\n\n“We’ve been using GitLab for several years as it had all the features we needed,” says Laurent Lavallade, chief technology officer at FullSave. “This helped us consolidate from the use of several tools to a single platform that had all the features integrated within it. Switching to GitLab’s Enterprise edition was the natural next step.”\n\nGitLab checked all of their boxes. And FullSave’s IT professionals were familiar with everything the platform brings to the table – increased collaboration, efficiency, security, and automation.\n\nIn their last environment, integration between FullSave’s previous tool and GitLab did work but it did not work as well, or as efficiently, as simply using GitLab’s single, end-to-end platform alone.",{"header":2859,"text":2860},"The solution","By replacing FullSave’s old issue tracking and project management tool and upgrading to GitLab Ultimate SaaS, FullSave has been able to take on its biggest DevOps challenges.\n\nFor instance, developers previously were merging issues directly into the development branch. But thanks to GitLab's merge request workflow, FullSave has been able to solve challenges around the validation of code changes and increase efficiency.\n\nCollaboration across teams also has improved with GitLab. Issue dependencies, for example, help front-end and back-end teams see where a project stands, know when they need one another, and communicate more readily and easily. That kind of collaboration helps team members share responsibilities and reduces individual efforts. It also increases everyone’s overview of a project and the progress it’s making along its lifecycle.",{"header":2862,"text":2863},"The results","By more fully adopting GitLab’s single platform, FullSave has been able to improve communication, collaboration, and efficiencies in both development and deployment. All of this eased their entire software development lifecycle.\n\nOne of the biggest improvements FullSave’s team has seen is in the speed of development and deployment. Before expanding their use of GitLab, they generally saw deployments only two or three times a month. Now, they are deploying software many times a day, and those deployments are a lot cleaner. Previously, many deployments were done manually, but now with GitLab’s deployment automation, there has been a noticeable reduction in errors and deployment time has been slashed from two to three hours to a few minutes.\n\nIncreased use of GitLab is:\n\n* Decreasing integration issues and errors\n* Improving software quality\n* Increasing code output\n* Simplifying software development processes and workflow\n* Enabling FullSave to obtain their ISO27001 certification, which some of its customers require them to have\n* Facilitating collaboration\n* Helping staff plan and build roadmaps and custom boards\n\nThe company has experienced a lot of benefits to handling so many parts of the software lifecycle within a single platform, instead of relying on a complex toolchain. GitLab’s all-in-one solution empowers FullSave’s developers and gives them clarity over projects and how they are progressing, so team members can see where they stand and how they can contribute.\n\nAnd by enabling collaboration and making developers’ work more efficient, team members now have additional time to create more, and better software products with increased security. For a small team like the one at FullSave, that means they are able to maintain more projects because they use GitLab.",{"template":950,"size":36,"region":106,"industry":91},"content:en-us:customers:fullsave.yml",{"_path":2867,"content":2868,"config":2905,"_id":2906},"/en-us/customers/glympse",{"name":2869,"logo":2870,"hero":2871,"heroImage":2872,"benefits":2873,"industry":89,"employeeCount":2883,"location":2884,"solution":913,"headline":2885,"summary":2886,"quotes":2887,"content":2891,"stickyBenefits":2904},"Glympse","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745517936/oxnhkvahexyrdws827jx.svg","Glympse is making geo-location sharing easy","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518417/rsb8xnxmcty56be2mgkz.jpg",[2874,2876,2880],{"metric":1521,"config":2875},{"icon":2451},{"metric":2877,"config":2878},"Streamlined pipelines",{"icon":2879},"PipelineAlt",{"metric":2881,"config":2882},"Faster deploys",{"icon":1734},"30","Seattle, Washington","Glympse is a fast, free, and simple way to share your real-time location and estimated arrival time using GPS tracking. The tracking is temporary and secure – and Glympse recipients don’t need to download an app to see the shared location.\n","With GitLab, Glympse is able to improve security scanning and deploy time.",[2888],{"quoteText":2889,"author":2890,"authorTitle":2223,"authorCompany":2869},"We had something like 20 odd different tools to kind of wrap around the system that we already had. But luckily, our leadership understood the importance of simplifying our processes and once we got GitLab in, we were off to the races.","Cillian Dwyer",[2892,2895,2898,2901],{"header":2893,"text":2894},"Tracking the last mile of delivery","Watching food delivery or seeing when a repair person will arrive is powered by real-time location tracking. But once the food is delivered or the service is complete, you want your location forgotten. Glympse Inc. technology provides end-users with a temporary real-time location tracking platform to share their location. Glympse works with retailers and home service providers around the globe to provide real-time location sharing in their last-mile offerings.\n",{"header":2896,"text":2897},"Overcoming a disparate toolchain","At the end of 2017, Glympse was faced with the challenges associated with disparate processes. Code management and reviews were performed in different tools than pipelines were run in. At that time, pipelines consisted of disjointed Jenkins jobs. They tried Shippable, which improved the process a bit, but they still weren’t able to connect merge requests to production. \n",{"header":2899,"text":2900},"GitLab makes the audit process easier","Glympse is in the process of earning a SOC 2 Type II audit and GitLab is vital to achieving the certification. Because Glympse is using Gold they can leverage built-in language agnostic CI pipelines. This allowed them to quickly respond to auditor’s feedback on the compliances of over 50 repositories and build a complete security package for integrating code changes into their environment.\n\nOne of the senior auditors commented in passing that having the code quality, SAST and container scanning, and pipelines all automated in GitLab is almost better than a manual review. “My response was, ‘Well, we're going to keep the manual review, that's part of our process’ but it's cool that he was almost okay with, not needing another developer for review. The security jobs in place are catching vulnerabilities from migrating to production through the product,\" explained Zaq Wiedmann, lead software engineer.\n\nWiedmann said the auditor also mentioned that Glympse had remediated security issues faster than any other company that he had worked with before in his 20-year career. Within one sprint, just 2 weeks, Glympse was able to implement security jobs across all of their repositories using GitLab's CI templates and their pre-existing Docker-based deployment scripts.\n",{"header":2902,"text":2903},"Improving deployment speed by 8x","The team fully integrated GitLab into their environment in January 2019 over the course of a single month. GitLab allowed the teams to suggest a merge request, run unit tests on it, then automatically build a new Docker image which is deployed to the sandbox environment. GitLab triggers tests in the sandbox and production deploys which are all managed on auto-scaling GitLab runners.\n\n“The managers are excited (about GitLab) because it helps reduce the amount of time we spend on things that we don't need to be spending time on. Focusing on the important stuff basically, get back to actually engineering and not focusing on building weird pipelines with Jenkins and Shippable and GitHub and trying to hook everything together in crazy scripts and stuff,” said Cillian Dwyer, site reliability engineer.\n\nGlympse wired their GitLab pipelines to AWS and deploy directly into their VPCs across the world. Thanks to deploy environments Glympse is able to track and version across production and staging environments.\n\nGlympse is also using all of the GitLab security jobs including SAST and DAST for static and dynamic applications security testing. Additionally, the company has container scanning, code quality, and license compliance jobs running. Jobs are managed within templates and imported by all production services.\n\n“GitLab has had a positive effect on our culture. Everyone feels better about shipping code and deployments. There is more confidence in the org and deployment is a non-issue,” said Zaq Wiedmann, lead software engineer.\n",{},{"template":950,"size":36,"region":102,"industry":91},"content:en-us:customers:glympse.yml",{"_path":2908,"content":2909,"config":2960,"_id":2961},"/en-us/customers/goldman-sachs",{"name":2910,"logo":2911,"hero":2912,"heroImage":2913,"benefits":2914,"industry":69,"employeeCount":2924,"location":2925,"solution":975,"stats":2926,"headline":2936,"summary":2937,"quotes":2938,"content":2947},"Goldman Sachs","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745517938/f0tpqvgmc6qfxlelaiuc.svg","Goldman Sachs improves from 1 build every 2 weeks to over 1,000 per day","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518418/mdyzl3qzdzpo7cnyemdc.jpg",[2915,2918,2922],{"metric":2916,"config":2917},"Larger number of builds",{"icon":1024},{"metric":2919,"config":2920},"Streamlined workflow",{"icon":2921},"Cycle",{"metric":1421,"config":2923},{"icon":1852},"35,000+","United States",[2927,2930,2933],{"value":2928,"metric":2929},"1,000+","CI feature branch builds a day by some teams",{"value":2931,"metric":2932},"52k","test cases across 11k test classes",{"value":2934,"metric":2935},"1,500+","adopters in the first two weeks","The dynamic environment at Goldman Sachs requires innovative strategic thinking and immediate, real-time solutions.","Engineering teams removed toolchain complexity and accelerated DevOps adoption through GitLab’s automation.\n",[2939,2943],{"quoteText":2940,"author":2941,"authorTitle":2942,"authorCompany":2910},"GitLab has allowed us to dramatically increase the velocity of development in our Engineering Division. We believe GitLab’s dedication to helping enterprises rapidly and effectively bring software to market will help other companies achieve the same sort of efficiencies we have seen inside Goldman Sachs. We now see some teams running and merging 1,000+ CI feature branch builds a day!\n","Andrew Knight","Managing Director",{"quoteText":2944,"author":2945,"authorTitle":2946,"authorCompany":2910},"We’re bringing into the firm a platform that our engineers actually want to use – which helps drive adoption across multiple teams and increase productivity without having to ‘force’ anyone to adopt it. This is really helping to create an ecosystem where our end users are actively helping us drive towards our strategic goals - more releases, better controls, better software.\n","George Grant","VP Technology Fellow",[2948,2951,2954,2957],{"header":2949,"text":2950},"Goldman Sachs solves clients' engineering challenges","Goldman Sachs is achieving what was previously assumed to be impossible. With the help of GitLab, the engineering team is now self-serving thousands of daily builds and dozens of teams are moving to production on a daily basis. Goldman Sachs empowered users with a strategic development tool and removed barriers around tool confusion and communication to speed up the delivery cycle. The Goldman Sachs engineering group is part of the technology division and global strategy groups, which are the critical center of the financial service provider’s business. They solve the most challenging and pressing engineering problems for Goldman Sachs clients. The group builds massively scalable software and systems, architects low-latency infrastructure solutions, proactively guards against cyber threats, and leverages machine learning alongside financial engineering to continuously turn data into action. Goldman Sachs' dynamic environment requires innovative strategic thinking and immediate, real solutions. The group was looking to increase developer efficiency and software quality through faster development cycles and decreasing the time spent from feature design to production rollout. They wanted to accomplish all of this while enabling concurrent development activities.\n",{"header":2952,"text":2953},"Increasing build speed by demolishing toolchain complexity","The firm had built its own toolchain but was looking for a solution to increase concurrent development. They wanted a modern toolset for managing code that developers coming into the firm would likely already be familiar with; this led to an evaluation of GitLab and other git-based vendor products. From their discovery process, they decided GitLab had the best CI/CD infrastructure to meet their needs. Initial users reported that it was easy to use and offered a complete end-to-end platform for software development, allowing them to replace their current toolchain and increase speed and coordination in the process.\n",{"header":2955,"text":2956},"GitLab increases Goldman Sachs' build velocity","GitLab is used as a complete ecosystem for development, source code control and reviews, builds, testing, QA, and production deployments. All the new strategic pieces of Goldman Sachs’ software development platforms are tied into GitLab.\n\nGitLab is helping the business-line engineering teams move faster to develop and improve their software and deliver for clients. One of the firm’s most important projects has moved from a release cycle of once every 1-2 weeks to once every few minutes because of GitLab.\n\nGitLab provided them a single application to roll out DevOps to the thousands of users at the bank. The ease of people only having to learn one application accelerated their adoption time. They were concerned that multiple tools, like most companies use, would be confusing, difficult to maintain and would deter adoption.\n",{"header":2958,"text":2959},"Dozens of teams pushing to production in less than 24 hours","The engineering group at Goldman Sachs is achieving this increased efficiency and speed by collaborating and connecting on a new level. They are seeing dozens of teams pushing to production in less than 24 hours. By tying together all the different parts of the development lifecycle into one consistent ecosystem, GitLab has helped developers work more effectively. All the different parts of what they need to do can be brought together under a single umbrella to be more efficient.\n\nThe team is also using GitLab as a means of moving teams to more strategic infrastructure which supports containers, as well as other strategic initiatives that are only offered on the new platform. This really helps make sure that the group is focusing efforts to use the latest technologies in the right places, and not just retrofit to the legacy infrastructure. GitLab also works well with Kubernetes out of the box which simplified their process.\n",{"template":950,"size":44,"region":102,"industry":71},"content:en-us:customers:goldman-sachs.yml",{"_path":2963,"content":2964,"config":3009,"_id":3010},"/en-us/customers/hackerone",{"name":2965,"logo":2966,"hero":2967,"heroImage":2968,"benefits":2969,"industry":89,"employeeCount":2978,"location":2979,"solution":913,"stats":2980,"headline":2989,"summary":2990,"quotes":2991,"content":2996},"HackerOne","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745517941/ofyosacgljvxg2u6bq16.png","HackerOne achieves 5x faster deployments with GitLab’s integrated security","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518419/cvuwmupb4lhbfks5onwp.jpg",[2970,2972,2975],{"metric":1732,"config":2971},{"icon":1845},{"metric":2973,"config":2974},"Less context switching",{"icon":902},{"metric":2976,"config":2977},"Tool consolidation",{"icon":1852},"300+","San Francisco, US; London, UK; Groningen, NL",[2981,2984,2986],{"value":2982,"metric":2983},"7.5x","faster pipeline time",{"value":2985,"metric":2840},"5x",{"value":2987,"metric":2988},"4 hours","development time per engineer saved/weekly","The world's most trusted hacker-powered security company, HackerOne, adopted GitLab to eliminate disparate toolchains and shift security left.","HackerOne improved pipeline time, deployment speed, and developer efficiency with GitLab Ultimate.\n",[2992],{"quoteText":2993,"author":2994,"authorTitle":2995,"authorCompany":2965},"GitLab is helping us catch security flaws early and it's integrated it into the developer's flow. An engineer can push code to GitLab CI, get that immediate feedback from one of many cascading audit steps and see if there's a security vulnerability built in there, and even build their own new step that might test a very specific security issue.\n","Mitch Trale","Head of Infrastructure",[2997,3000,3003,3006],{"header":2998,"text":2999},"Hacker-powered security platform","HackerOne empowers the world to build a safer internet. As the world’s most trusted human-powered security platform, HackerOne gives organizations access to the largest community of hackers on the planet. Armed with the most robust database of vulnerability trends and industry benchmarks, the hacker community mitigates cyber risk by searching, finding, and safely reporting real-world security weaknesses for organizations across all industries and attack surfaces.\n\nAs the world becomes more connected and organizations move to the cloud, cybersecurity must keep up. [HackerOne](https://www.hackerone.com/){data-ga-name=\"hackerone site\" data-ga-location=\"body\"} helps security teams scale with their agile attack surfaces by providing hacker-powered security testing and vulnerability insights that help reduce risk across the SDLC.\n",{"header":3001,"text":3002},"Looking for speed of development and deployment","HackerOne is a globally distributed company, so dependencies exist between teams in order to complete projects. There were often times when a developer in the Netherlands worked on code, then someone in North America would pick up where the other left off. Lengthy pipeline times could interrupt handoffs. According to Mitch Trale, Head of Infrastructure at HackerOne, “In many cases, you would wind up stranding a merge request in a place where you wish you would have gone live … if we’d had faster tools, we could have put that out there.”\n\nHackerOne was using separate tools for code version control and continuous integration. As HackerOne began to scale, growing the engineering team from 10 to 30 members, Mitch indicated that these tools were “significantly limited … one example of this is just the time it took to run a single pipeline within our old system that made it sort of prohibitive to do this frequently,” Trale said. “So engineers started to work around these limitations. We started creating these downstream side effects, which we then had to deal with separately.” The team needed a tool that could grow alongside HackerOne’s development and would be able to manage multiple projects that would affect multiple squads.\n\nPrimary drivers for the team in their consideration of new software tools was speed of development, speed of deployment, and developer happiness. “We’re optimizing for happy engineers, wherever possible. Better tools help us automate more, providing us with better throughput and higher quality,” Trale clarified. The team needed a platform that would improve the developer experience from end-to-end, from development to deployment.\n",{"header":3004,"text":3005},"Scalability and developer ownership","HackerOne adopted GitLab in late 2018 for [source management](/solutions/source-code-management/){data-ga-name=\"source code management\" data-ga-location=\"customers content\"}, [issues management](/stages-devops-lifecycle/plan/){data-ga-name=\"plan stage\" data-ga-location=\"customers content\"}, CI/CD, and security and compliance features that didn’t exist in the team’s previous tooling system. GitLab buy-in increased dramatically across the company because of the various agility offerings that can work in different environments. “HackerOne adopted GitLab all around, but we also saw brand new features that product managers and sprint owners could take advantage of. Now we’re seeing teams cross-planning out further in the future,” Trale reports. “We’re seeing Gantt charts that represent dependencies. And that kind of sophistication was really critical at that stage in HackerOne’s development, because we were scaling.”\n\nGitLab not only provided a way for teams to scale, but it also provided a way for application development processes to become more egalitarian. Because of GitLab’s intuitive user interface, [the number of users expanded](/enterprise/){data-ga-name=\"gitlab enterprise\" data-ga-location=\"customers content\"} at HackerOne. “We have technical product managers who can now make code changes affecting copy text on the site or affecting, for example, a font color,” Trale added. “It’s easier for individuals to go in using GitLab’s visual editing tools, and a merge request that can easily be approved and deployed atomically. That simply wasn’t viable before.”\n\nGitLab’s ease of use makes working within the platform more manageable for developers and engineers. As an open source tool, GitLab is modern, but not overly complex. It offers a lot of capabilities, but it is functionally available to engineers at every level of the company. “Now we can democratize control over our pipelines. We can have individual engineers acting as DevOps, acting as infrastructure … and administering the tooling in a way that they simply couldn’t before. Our old tooling was clunky, hard to maintain and manage,” Trale said.\n",{"header":3007,"text":3008},"Baked-in security generates faster deploys","One of the biggest benefits of adopting GitLab is the ability to find code issues sooner in the pipeline. When combined with faster pipelines, the teams can now work iteratively to resolve security flaws. The engineering team used to spend at least 60 minutes per integration pipeline run. It would go end-to-end from commit to test, to smoke test, test, deploy, and take an hour. If there was a single error, they would have to rerun the whole process.\n\n“It made people overly cautious about pushing code. And what we really want to do is to make that cycle time as tight as possible and reduce risk associated with any given release of code,” Trale explained. “So GitLab was strategically important for us because it really enabled us to refine this code and build it according to our own quality specifications.”\n\nThe team can also rerun specific parts of the pipeline, which was not feasible before. They can focus on the part of the continuous integration pipeline that might be failing, without having to restart. “Speed matters … now it takes about eight minutes to run a pipeline. That eight minutes is massive. That alone would have been meaningful enough for us to consider the switch, the promise of this high-speed continuous integration pipeline,” Trale remarked. On top of that, there is now deeper visibility into audit logs, so they can see what is going on behind the scenes to understand what is contributing to performance degradation.\n\nUsing GitLab’s API and security capabilities, the engineering team created a bot that generates merge requests automatically based on outdated packages. The bot scans repos and creates merge requests according to those that need to be updated. Engineers only need to review and approve them in order to then deploy. This automation saves manual cycle time and creates faster security scanning. It’s no longer an individual’s job to spend an additional hour per deploy testing this. “We deploy code multiple times a day … now at least between one to five times a day, new versions of HackerOne are going live to the web. There was at least an hour spent on each of those by an engineer,” Trale described. “Maybe a half hour between two engineers, making sure that the work made sense. I think, conservatively, we’re saving four to five hours a day of energy per engineer by consolidating this work using the tools.”\n\nPrior to GitLab, HackerOne’s deployment cycle was closer to one to two times per day. But with everything in one place, correctly labeled and efficiently organized, PMs and those who manage sprints can now pick what they want to work on. “GitLab is helping us catch these things early — it’s integrating it into the developer’s flow.\n\nHaving all the tools in one place has made security scanning and audits an easier process from the team’s previous workflow. “The cost of running security scans in GitLab is significantly lower than it was previously. And so we’re much more inclined to run more thorough scans, faster. Whether that’s on individual packages or even running a suite of security tests. I do think that we’re much more cognizant of it and we’re using GitLab for this purpose,” Trale explained.\n\nThe engineering team also built a custom Slack bot that integrates with GitLab and triggers deployments. All deployments are public in the Slack channel, where a lot of work happens for HackerOne. With the integration, they can see deployment status in Slack rather than locating the pipeline or audit log. In cases where the deployment goes wrong, there are 30 people who can help debug in real time. Bringing deployments close to Slack and using GitLab for CI/CD provides easier, faster access to code and security management.\n\nWhile tool consolidation and deployment speed are priorities that led HackerOne to make the switch, it’s GitLab’s active development that continues to impress team members. GitLab has monthly releases that build upon existing features — such as security — using customer feedback. “The partnership that we have with GitLab is ever deepening. Whereas some of these other tools that we evaluated didn’t have that strength of development, that sort of momentum that GitLab has,” Trale said. “The monthly cadence speaks to this — new features arrive frequently that we can take advantage of. That active development is a contemporary mindset that GitLab has, which is appealing to us.”\n",{"template":950,"size":40,"region":102,"industry":91},"content:en-us:customers:hackerone.yml",{"_path":3012,"content":3013,"config":3059,"_id":3060},"/en-us/customers/haven-technologies",{"name":3014,"logo":3015,"hero":3016,"heroImage":3017,"benefits":3018,"industry":3026,"employeeCount":3027,"location":3028,"solution":913,"stats":3029,"headline":3039,"summary":3040,"quotes":3041,"content":3046,"contributors":1281},"Haven Technologies","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745517985/cn8r4icftxdvywoz7vil.png","How Haven Technologies moved to Kubernetes with GitLab","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518443/w0fknjkdl82dtqcsx1g7.jpg",[3019,3022,3024],{"metric":3020,"config":3021},"Increased efficiency",{"icon":1020},{"metric":1676,"config":3023},{"icon":1142},{"metric":1026,"config":3025},{"icon":902},"Insurance Tech","400","New York, New York, United States",[3030,3033,3036],{"value":3031,"metric":3032},"$7","Cost savings per user monthly, across 150+ users",{"value":3034,"metric":3035},"62%","Of users ran a secret detection job in the last month",{"value":3037,"metric":3038},"66%","Of users have run a secure scanner job in the last month","Haven Technologies is doubling down on a Kubernetes strategy — and GitLab is helping the digital insurance leader cut costs and drive efficiency during the transition.","GitLab’s DevSecOps Platform is helping Haven Technologies drive improvements to efficiency, security, and development velocity.\n",[3042],{"quoteText":3043,"author":3044,"authorTitle":3045,"authorCompany":3014},"GitLab’s commitment to an open source community meant that we could engage directly with engineers to work through difficult technical problems.\"\n","Evan O’Connor","Platform Engineering Manager",[3047,3050,3053,3056],{"header":3048,"text":3049},"Making insurance more accessible through a world-class digital platform","Haven Technologies is an insurance technology software as a service (SaaS) provider based in New York, New York. Prior to becoming Haven Technologies, the company helped transform the life insurance industry in 2015 with the launch of Haven Life, a digital insurance technology company that allowed customers to get a quote, apply for a policy, get approved, and manage that policy, almost entirely online. Now, Haven Technologies makes its unique cloud-native insurance platform available to other businesses in the life, annuities, and disability industries. An example was [HealthBridge](https://www.massmutual.com/healthbridge), a free online life insurance policy offered by MassMutual to eligible frontline healthcare workers and volunteers in the wake of the COVID pandemic, that was built and launched in just a few weeks using the Haven Technologies solution.\n",{"header":3051,"text":3052},"A growing organization reaches a breaking point","As an insurance technology company, Haven Technologies is strongly aware of the need to protect sensitive customer data. The company’s code is valuable intellectual property, says platform engineering manager Evan O’Connor.\n\nHaven Technologies started using GitLab for version control and source code management (SCM). By 2019, the company was heavily utilizing GitLab CI/CD and container registry. Developers were continuously adding new projects, each of which had pipelines to build Docker images, run units, regression and integration tests, and security scanning.\n\nAn early project was to move all Docker builds to GitLab and build images there, which was a big time-saver as images were pre-built and tested come deploy time, says O’Connor.\n\nIn late 2019, Haven Technologies began its journey to migrate to a self-managed GitLab instance on Kubernetes using Helm charts to allow for greater scalability, customization, and security. Prior to that time, Haven Technologies used the Omnibus deployment, a more commonly used installation that requires minimal configuration to get up and running.\n\nBefore Kubernetes, the team used Convox, which is built on Docker and ECS (Elastic Container Service) and aims to make it easy to deploy and manage applications in the cloud. This setup worked well as a smaller organization, but O’Connor says that eventually, they reached a breaking point where Convox did not provide enough control over their cloud resources. During peak usage days (especially around release time), GitLab would become painfully slow and users would receive frequent 500 errors in the UI and failed pipelines, he recalls.\n",{"header":3054,"text":3055},"Braving the unknown with a trusted partner","As an innovator in the insurance tech space, the Haven Technologies engineering team felt they were a natural fit to become an early adopter of [GitLab’s Helm Chart](https://docs.gitlab.com/charts/?_gl=1*d7zk1c*_ga*MTU1MDMzNTYwOS4xNjQ0OTYxNjk3*_ga_ENFH3X7M5Y*MTY4MTkzMzY3MC40MTUuMC4xNjgxOTMzNjgyLjAuMC4w). Haven Technologies leadership was given fair warning that because the product was new, they might encounter roadblocks that would require help from GitLab’s support and engineering teams.\n\nBut Haven Technologies was undaunted. “Our team was somewhat new to Kubernetes and Helm, but GitLab became an opportunity for us to learn and gain experience that we could apply when we moved the rest of our apps to Kubernetes,” says O’Connor.\n\nAnd GitLab made the communication seamless. “GitLab’s commitment to an open source community meant that we could engage directly with engineers to work through difficult technical problems,’’ says O’Connor. “Overall, I would recommend adopting the Helm Charts if your team is experienced with Kubernetes or if, like us, you are willing to brave the unknown with the goal of using the latest technology and a desire to contribute to improving the Helm Charts for everyone.”\n\nThe decision to adopt GitLab’s Helm Chart was in part influenced by a larger move to Kubernetes for all of Haven Technologies’ applications. At the same time Haven Technologies decided to become an early adopter of the GitLab Helm Chart, the engineering team was also planning to move the entire production and user acceptance testing (UAT) environments to run on Kubernetes. It made a lot of sense to deploy GitLab in the same way as their other applications, so all of the configurations would be in one place, says O’Connor.\n\nThe other advantage of Kubernetes was that autoscaling and high availability are native to the software and are easy to enable via Helm Charts. “If we went in the direction of multiple EC2 instances, we would have to manage many different configurations that each would require their own solutions for autoscaling and high availability,’’ says O’Connor.\n\nThe first prerequisite for running GitLab on Kubernetes is to build a cluster. Haven Technologies chose Amazon EKS, since all of the company’s applications reside in AWS. Engineers decided to build out GitLab in both UAT and production environments to allow them to test upgrades and other configuration changes before they went live.\n\nHaven Technologies uses Jira and Terraform, and uses GitLab pipelines to automate Terraform tasks.\n\nO’Connor highly recommends maintaining a staging environment for GitLab to maintain stability and reduce the risk of data loss during difficult updates. “GitLab makes this easy, and only one license is needed to support both environments,’’ he says. “Using Terraform and Helm, our UAT and production environments are configured almost identically, aside from more conservative scaling in UAT to save money.”\n\nIn the future, O’Connor says engineers will aim to build a way to easily shut down or spin up their UAT GitLab system so they do not have idle machines running when they are not needed.\n\nAnother struggle was finding a way to load test their UAT setup before cutting it into production. Volunteers from the development and QA teams were asked to help load test GitLab and search for abnormalities. O’Connor’s team created a spreadsheet and had users enter any abnormalities they found. This helped the team fix some misconfigurations before fully cutting over, he says.\n\nEngineers had built out the monitoring portion of the Helm Charts after they had cut over their production GitLab system to Kubernetes. This made diagnosing issues that were caused by load especially difficult. At the time, all they had were pod-level CPU and memory metrics reported by the Kubernetes cluster. These dashboards helped team members resolve issues where their pod limits were set too conservatively.\n\nHaven Technologies also utilized AWS CloudWatch metrics and log queries to look for bottlenecks and correlate issues with AWS resources.\n\nGoing forward, as issues come up when testing GitLab on Kubernetes, O’Connor says they will create dashboards to identify them more quickly.\n",{"header":3057,"text":3058},"More deployments, more testing, lower costs","By using the GitLab package registry, Haven Technologies has been able to stop using the public npm registry — at a cost of $7 per user for more than 150 users (as of December 23, 2022). By implementing autoscaling Docker-machine and Kubernetes runners, O’Connor’s team was able to increase the number of regression and integration tests performed on each commit to developer branches.\n\nThe team has also greatly increased the number of security pipelines they are running on each merge request, which has helped them to increase developer involvement in securing applications earlier in the development lifecycle.\n\nOverall, using GitLab CI has added value to Haven Technologies’ software development lifecycle by automating a number of processes — especially around branching — and freeing up developer time.\n",{"template":950,"size":40,"region":102,"industry":91},"content:en-us:customers:haven-technologies.yml",{"_path":3062,"content":3063,"config":3108,"_id":3109},"/en-us/customers/hemmersbach",{"name":3064,"logo":3065,"hero":3066,"heroImage":3067,"benefits":3068,"industry":89,"employeeCount":3077,"location":3078,"solution":913,"stats":3079,"headline":3087,"summary":3088,"quotes":3089,"content":3096,"contributors":1281},"Hemmersbach","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745517986/gcm55k7kh1x7yehlhhjl.png","Hemmersbach reorganized their build chain and increased build speed 59x","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518443/wbc9rizl5ecripy0eot5.jpg",[3069,3072,3074],{"metric":3070,"config":3071},"Faster cycle time",{"icon":902},{"metric":1293,"config":3073},{"icon":1302},{"metric":3075,"config":3076},"Impoved code quality",{"icon":2451},"3,400","Germany, Poland, Hungary, Bulgaria, Austria",[3080,3082,3085],{"value":1804,"metric":3081},"more builds per day",{"value":3083,"metric":3084},"530","automated tests daily",{"value":2883,"metric":3086},"automated daily deploys","Global IT service provider Hemmersbach was struggling with multiple tools, difficult build cycles, and an out of sync planning process. With Gitlab Ultimate, Hemmersbach is now able to connect the portfolio planning process with actual work to deliver new capabilities.","With over 4,000 permanent colleagues in more than 40 subsidiaries worldwide, Hemmersbach enables Device as a Service for the IT industry in 190+ countries. DaaS combines hardware, software, lifecycle services, and financing into a single contract with a fee per device.\n",[3090,3094],{"quoteText":3091,"author":3092,"authorTitle":3093,"authorCompany":3064},"We renewed the complete process. We didn't just take what was in Jenkins and move to GitLab, we redid everything. We took all of the findings we had from Jenkins, which wasn’t good, and we took what was good and we set it up completely new. We reinvented the wheel, just to make it better.\n","Alexander Schmid","Head of Software Development",{"quoteText":3095,"author":3092,"authorTitle":3093,"authorCompany":3064},"GitLab is the one tool that connects our whole team. You always see GitLab open and everything is based on GitLab. GitLab is the backbone of our software development.\n",[3097,3100,3103,3106],{"header":3098,"text":3099},"Providing IT support on a global scale","Hemmersbach provides vital support for the leading companies in the IT industry. The company offers global services for manufacturers and outsourcing companies to meet the wide variety of needs of their end customers. They provide technology services for thousands of organizations and specialize in supporting hardware of all sizes, from printers to the largest servers.\n",{"header":3101,"text":3102},"Collaboration and speed at a global scale","Hemmersbach has three teams working on the company’s proprietary software. A few years ago, they faced challenges around these teams working disparately. They struggled with collaboration and geography — with speed suffering as a result. They were using a scrum framework with a toolchain that included Jira, Jenkins, Tulip, and a variety of open source tools. With this complex toolchain, teams lacked traceability and had to overcome inefficiencies.\n\n“Most of our code was not connected to our process,” explained Alexander Schmid, Head of Software Development. “We had tools and repositories and all the merge request stuff. But, these things were not related to what guys wrote on comments and the stuff it was not connected.”\n\nStruggling with multiple tools, difficult build cycles, and an out of sync planning process in Jira, Hemmersbach needed a new process. They tried a wide variety of tools to solve the dilemma but still couldn’t achieve the speed they desired. During this time, teams were using GitLab Core and the business was impressed by how connected issues are with code repositories and how GitLab helped them improve team efficiency.\n",{"header":3104,"text":3105},"Rebuilding the wheel to achieve speed and collaboration","The Hemmersbach development group evaluated their process and overcame the challenges they were facing by rethinking how they worked together. They had a team utilizing GitLab and were impressed with how everything is connected to the commit and offers an overview for all of the pipeline steps — in one tool.\n\nGitLab Core provided built-in CI/CD, and project issue boards and teams were able to increase build speed and collaboration. Building on this momentum, they decided to rebuild the entire structure and move from scrum development to feature-driven development. While they saw progress, they still needed a tool that offered the ability to categorize items and then break them down so the team could continue to iterate faster.\n\nGitlab Ultimate connected the portfolio planning process with the actual work to deliver new capabilities. The multi-level epics and roadmap review capabilities powered their teams to move at unprecedented speed. The code reviews and comments in GitLab helped improve overall code quality.\n",{"header":3104,"text":3107},"Using GitLab helped Hemmersbach decreased the time from planning to production by 6.5 days. By working in a single environment, they are also achieving 60 builds per day when previously they were only performing a single daily build.\n\nHemmersbach has over 100 developers using GitLab on a daily basis to run their software. The deployments now begin with epics which allow everyone to collaborate as they work through the resulting issues and merge requests. Having all of the collaboration capabilities under one umbrella has enabled the company to bring teams together and achieve unprecedented deployment speed.\n\n“Everybody can see what’s going on across other projects as well,” Schmid said. “And then if there are comments or concerns with the code, you just write it, you just do it. GitLab has helped us bring teams together.”\n",{"template":950,"size":44,"region":106,"industry":91},"content:en-us:customers:hemmersbach.yml",{"_path":3111,"content":3112,"config":3157,"_id":3158},"/en-us/customers/hilti",{"name":3113,"logo":3114,"hero":3115,"heroImage":3116,"benefits":3117,"industry":3127,"employeeCount":3128,"location":3129,"solution":913,"stats":3130,"headline":3137,"summary":3138,"quotes":3139,"content":3144},"Hilti","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745517942/ian7zidxv2sunjovk64o.svg","How CI/CD and robust security scanning accelerated Hilti’s SDLC","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518420/unkmnzd74gwwahcvec19.jpg",[3118,3121,3124],{"metric":3119,"config":3120},"Streamlined code management",{"icon":1302},{"metric":3122,"config":3123},"Improved delivery time",{"icon":971},{"metric":3125,"config":3126},"CI/CD capabilities",{"icon":2105},"Manufacturing","30,000","Schaan, Liechtenstein (HQ)",[3131,3134,3136],{"value":3132,"metric":3133},"400%","increase in code checks",{"value":2163,"metric":3135},"shorter feedback loops",{"value":2842,"metric":2840},"GitLab’s SCM, seamless CI/CD, and exceptional security scanning empowered Hilti to bring code in-house.","Hilti expanded its software capabilities and adopted GitLab to bring code in-house with SCM, CI/CD, and security scanning.\n",[3140],{"quoteText":3141,"author":3142,"authorTitle":3143,"authorCompany":3113},"GitLab is bundled together like a suite and then ships with a very sophisticated installer. And then it somehow works. This is very nice if you're a company which just wants to get it up and running.\n","Daniel Widerin","Head of Software Delivery",[3145,3148,3151,3154],{"header":3146,"text":3147},"Global construction services provider","Hilti is a world leader in the design and manufacturing of cutting-edge technologies, software, and services for the professional construction industry. One sector of [Hilti](https://www.hilti.group/content/hilti/CP/XX/en.html) specifically focuses on business unit tool solutions. This team creates software for customers in the area of software development tools which meets governance, risk, and compliance regulations. Hilti ensures that the correct procedures are in place to adhere with regulatory compliances across different regions.\n",{"header":3149,"text":3150},"Enrich software capabilities, security, and SCM","About two years ago, Hilti was looking for a software platform to rebuild their projects. They had previously outsourced one of their software development projects to an external vendor as the software capability could not be 100% managed in-house. The source code was owned by a joint venture which used GitHub. Hilti owned the majority of the joint venture, but it was not hosting source code in-house. There wasn’t any internal CI/CD and also the teams didn’t perform security testing according to the highest standards. This situation was challenging because the software teams wanted full visibility and management of their code.\n\nHilti’s goal was to move software development in-house to enable the engineering and architecture teams to conduct proper reviews, truly collaborate, and to share best practices with other teams. As Hilti wanted a solution that adheres to the highest standards, the ideal tool would need to be easy to onboard, be intuitive, and offer seamless integration. “We wanted to bring a tool on to our own premises so that we have it under our control, and also have it in real time. That was really a big step forward,” said Raphael Hauser, Head of Governance at Hilti. Security scanning was high on the priority list. Hilti has between 10 to 15 distributed teams working in parallel on large-scale solutions at any given time globally. Security needs to be under control and aggregated so that by the time a software release is ready, vulnerabilities are visible ahead of time. Hilti needed a tool with powerful and reliable security capabilities.\n\nDevelopment and test teams previously found themselves in “reactive mode” when catching bugs. A tool that offers a way to find vulnerabilities within the pipeline would be more efficient, increase workflow speed, and empower developers. “I want to be sure, once we release a package to production, that we're not bringing in any packages of code that are eventually creating a risk for Hilti; exposing source code is an access security problem, not a code scanning problem,” Hauser added.\n",{"header":3152,"text":3153},"Bringing security and code in-house","After a review and working with various tools, GitLab was adopted for its ease of integration, SCM capabilities, and comprehensive security scanning. GitLab delivered the capabilities to maintain high software performance standards and to quickly provide multiple types of in-depth scanning. Hilti is using GitLab’s static and dynamic application security testing (SAST and DAST, respectively), along with container scanning, dependency scanning, secret detection, and license compliance. “GitLab is far ahead of its competitors and provides one product which offers an easy-to-set-up, easy-to-start product with all these capabilities integrated,” said Daniel Widerin, Head of Software Delivery.\nHilti has compliance regulations that they must follow, including license reviewing, application testing, and source code access. Hilti opted for GitLab Ultimate in order to use the compliance and security scanning. “From a risk point of view, the key factor was that we can now control much tighter and much closer who really has access to the source code, who is managing the source code, and the current state in regard to security and IP compliance,” Hauser said.\n\nWith GitLab, Hilti now has full access to their source code and is able to manage it properly. Owning their own code reduces the risk of any source code leakage and increases the level of code change capabilities. “It has given me much more insight into what is actually happening within the code and doing that in real time. It has also sped up my way of giving approvals in regard to security, code security, and the IP compliance in order to still comply with the faster pace of delivery,” Hauser said.\n",{"header":3155,"text":3156},"Secure code, end-to-end visibility, and faster deployments","Hilti’s engineering and architecture teams now use GitLab for SCM, CI/CD, and security dashboards that are compatible with their technology stack. With GitLab, they were able to build software in-house and at a faster rate than if they had used a complicated set of tools. The ease of integration allows the teams to work with Jira, Docker, and Amazon Web Services (AWS). All services integrated with GitLab, including build artifacts and runners, are running on AWS and deployed to a Kubernetes cluster.\n“GitLab has done a really great job with the source code to bring feedback directly after you have opened the merge request or after you have done a comment or a push,” said Widerin. “I mean, you basically don’t have to develop all these things on your own. GitLab is bundled together like a suite and then ships with a very sophisticated installer. And then it somehow works. This is very nice if you're a company which just wants to get it up and running.” With GitLab, feedback loops have shortened by 50%, from 6 days to 3 days, supporting greater efficiency and collaboration.\n\nTeam members appreciate that the pipeline is directly integrated into the source code and they’re able to get immediate feedback from the merge request including security scan results. “People really like that they have a center point where they can log in and see all the different microservices and components while they are working, even with mobile apps and web UI,” Widerin added. Code checks have increased significantly from six times every three months to twice a week, thereby maintaining high quality.\n\nDeployment speeds have increased because now development and test teams own the code and can see when there are vulnerabilities ahead of time. Deployment times have decreased from an average of three hours to just 15 minutes with GitLab. They now have clear guidance on what they accept for any release with regard to severity of vulnerabilities within the code. “We are faster to remedy critical findings and the teams get a bit more stability because they do not have to do a firefight before the release ... it helps us to give them the overview of where they stand so they don't have to rework after the sprint is complete,” Hauser said.\n",{"template":950,"size":44,"region":106,"industry":91},"content:en-us:customers:hilti.yml",{"_path":3160,"content":3161,"config":3203,"_id":3204},"/en-us/customers/hotjar",{"name":3162,"logo":3163,"hero":3164,"heroImage":3165,"benefits":3166,"industry":89,"employeeCount":3174,"location":112,"solution":2053,"stats":3175,"headline":3183,"summary":3184,"quotes":3185,"content":3190,"contributors":1281},"Hotjar","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745517987/rftxar3kua72mbdaitbi.svg","How Hotjar deploys 50% faster with GitLab","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518444/tdr3e9h2bzgmkliwjpxl.jpg",[3167,3170,3172],{"metric":3168,"config":3169},"Kubernetes integration",{"icon":902},{"metric":1524,"config":3171},{"icon":1195},{"metric":1732,"config":3173},{"icon":2598},"100 employees",[3176,3179,3181],{"value":3177,"metric":3178},"2-15","deploys per day",{"value":1750,"metric":3180},"decrease in CI build time",{"value":2163,"metric":3182},"deployment time saved","Hotjar, a growing all-remote company, was looking for an enhanced CI/CD tool to replace Jenkins.","Hotjar turned to GitLab for Kubernetes integration, CI/CD, and source code management, replacing existing tools.\n",[3186],{"quoteText":3187,"author":3188,"authorTitle":3189,"authorCompany":3162},"GitLab made it easier for all developers to work with CI/CD pipelines, making the process of bootstrapping a new service much more transparent and approachable and removing the DevOps/SRE team as a bottleneck.\n","Vasco Pinho","TEAM LEAD, SRE",[3191,3194,3197,3200],{"header":3192,"text":3193},"A leading behavior analytics software","Hotjar is a behavior analytics software that makes it easy to go beyond traditional web analytics and to understand what users are really doing on a website. With both quantitative and qualitative behavior analytics tools, [Hotjar](https://www.hotjar.com/) provides an overview of how to improve customer experience, performance, and conversion rates.\n\nThe company was formed in 2014 and is fully remote, with over 100 people across 20 countries. Over 500,000 sites use Hotjar worldwide, with most customers within the United States and Europe. Word of mouth has been the backbone of the marketing strategy, driving the majority of the customer base.\n",{"header":3195,"text":3196},"Looking for a better tool for remote workers","Because Hotjar is fully remote, communication is one of the biggest challenges. As the company grows, communication becomes increasingly important. “The communication between 100 versus 18 people is incredibly different. There’s a lot more information now. So I think that there’s an element of trying to make sure that we have the information available to the team as they need it, but without drowning everybody in information which is, at points, irrelevant,” said Sara Bent, People Ops specialist at Hotjar.\n\nHotjar had challenges with how the growing number of developers structured their work and the cumbersome legacy systems in place. All the developers had to work on the same code base using legacy tools, which was slowing productivity. “The problem that we were trying to solve was how to go from this to a more diverse set up, where we have a few infrastructure legacy pieces, but also some new microservice deployments and how to integrate all the new things in a nice way so that we could continue to grow the number of developers internally without productivity going down,” according to Vasco Pinho, Team Lead, SRE at Hotjar.\n\nDevelopers were using BitBucket for hosting source code and Jenkins for CI/CD. Due to the constraints of some of the legacy applications, they had to develop and maintain large amounts of Jenkins-specific code to support pipelines. This used up a lot of resources and was not an effective use of their time. They were using Kubernetes as a platform for all their microservices and some of the build pipelines.\n\nHotjar was looking for a tool that offers a [Kubernetes integration](https://about.gitlab.com/solutions/kubernetes/) and a replacement for Jenkins CI/CD. They tried using BitBucket for CI/CD and Concourse, but neither provided the solution they needed. “In terms of Kubernetes native product that supplies the whole life cycle, we actually didn’t find that many competitors. There were some that we looked at, some that we had to self host. Jenkins X is Kubernetes native but we actually found it to be super immature and it still had a lot of bugs,” Pinho said.\n",{"header":3198,"text":3199},"Getting more, natively","Hotjar set up GitLab, ran it locally, and found through the trial that they landed on the right tool. “While our pain points started a search for a replacement to Jenkins, once we tried GitLab’s pipelines, we saw the way they fully integrated the development experience into a single tool, as well as fulfilling all our CI/CD requirements, we started considering moving our code into GitLab as well,” Pinho said. “Our developers considered GitLab’s interface and features to be superior to Bitbucket, namely the code review flow and as such we embraced the whole platform.”\n\nWith Jenkins, the teams created a lot of custom codes to do a lot of the work that they are now getting natively with GitLab. On the code management side, they used the cloud version of Bitbucket. Now, they use GitLab.com for all of the development work and to host the [CI/CD runs](https://about.gitlab.com/solutions/continuous-integration/). “It is great and it’s not something that a lot of other providers offer. Being able to not have to worry about hosting the actual website, but still allowing us to have the flexibility to run our own build infrastructure,” Pinho said.\n\nPart of the flexibility that Hotjar wants to maintain is the ability to work remotely, and do it well. “[The founders] worked remotely from the outset and therefore had to establish all of these processes around working remotely. And that’s done a huge job towards making sure we have this very firm foundation on making sure that our remote communication and collaboration works well. We pay conscious effort to this,” Bent says. GitLab’s end-to-end visibility of the workflow process allows developers to see what everyone is working on at all times. The access of information helps to maintain Hotjar’s remote communication.\n",{"header":3201,"text":3202},"Increased deployments, better AWS EKS, improved development workflow","Every engineering team and some of the customer support team members are using GitLab. Users are happy with the MR process. The overall user experience is a big improvement over BitBucket and the review environments are a game changer for any work that requires visual review. With the review environment, they can catch errors earlier in the pipeline and not hit the stage environment as they previously did.\n\nGitLab integrates natively with Kubernetes, which gives the development team peace of mind because they can trust that the tool will work automatically without constant maintenance. The team previously had issues using Jenkins because a lot of time was spent “gluing things together,” according to Pinho. Developers are now able to focus on production, rather than bugs and fixes. Build CI time has decreased by 30% over previous implementation in Jenkins. Build CI variability has decreased significantly, due to higher density of builds per node and less scale up operations needed.\n\nHotjar wanted to stay away from solutions where they had to host the source code management and their own workflows. Now, their teams are able to focus on their priority tasks and the main line of business, instead of trying to figure out why [Git repositories](https://about.gitlab.com/blog/optimize-gitops-workflow/) are down. With GitLab, Hotjar is able to see which updates are in the planning process. “It was definitely something that was impressive. During the trial I think there were two releases. So we got issues that we were finding during the trial fixed in the releases that came out during the trial,” Pinho said.\n\nGitLab projects connect to their AWS EKS cluster, the tests run within the cluster using Kubernetes Operator, it reports back with coverage results, then artifacts are uploaded to AWS ECR/S3. Review environments spin up inside the EKS cluster during review. After the merge, artifacts are deployed again to the EKS to the production environment. “We went from the deployment itself to production that in our old system was taking something like eight minutes and is now gone down to something like four, so half the time to deploy. Within the whole incident resolution scheme, this sounds like very little, but it still impacts things across the board,” Pinho said. Developers are saving time and effort by making use of standalone review-environments instead of in-the-loop shared staging environments, which create bottlenecks.\n\nHotjar’s remote culture continues to thrive. “Most people are online at the same time, you can expect an MR to be reviewed within hours or minutes, and be able to jump on a video call together to debug issues, discuss projects, etc. We definitely don’t suffer from the usual pains of fully remote offices where any query will only be answered by the next morning,” Pinho said.\n\nGitLab improves Hotjar’s development collaboration capabilities, but also influences how transparent they are. “I think often we see the similarities and it’s a reassuring thing of like, ‘Okay, they’re doing that too and that’s working really well for both of us, so well done,’” Bent said.\n\nHotjar recently published their [handbook](https://hotjar.atlassian.net/wiki/spaces/REC/pages/269942983/Team+Manual+Public) after seeing that [GitLab’s handbook](https://handbook.gitlab.com/handbook/) is public. “It’s nice to be able to see what other companies are doing and even just how people word things and how that reflects their company. But it’s true we didn’t use to have a public team manual and now we do,” Bent added. GitLab’s integrated platform helps to keep Hotjar up to date with cutting-edge software and inspires all-remote culture modernity.\n",{"template":950,"size":36,"region":114,"industry":91},"content:en-us:customers:hotjar.yml",{"_path":3206,"content":3207,"_id":3737},"/en-us/customers",[3208,3250,3448,3524,3672,3726],{"componentName":3209,"componentContent":3210},"CustomersVideoCarousel",{"heading":3211,"eyebrow":3212,"button":3213,"controls":3219,"cards":3222},"Customers ship software faster with GitLab","Customer stories",{"text":3214,"config":3215},"See all customer stories",{"href":3216,"dataGaName":3217,"dataGaLocation":3218},"/customers/all/","all customers","hero",{"prev":3220,"next":3221},"Previous case study","Next case study",[3223,3232,3241],{"text":3224,"video":3225,"config":3230},"Nasdaq is using “the power and elegance of GitLab” to achieve its cloud transformation vision",{"altText":3226,"config":3227},"Nasdaq Video Thumbnail",{"thumbnail":3228,"href":3229},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1757959728/ng5mhxawywemzcefvxp2.webp","https://www.youtube.com/embed/sT85nT9X2mM?si=yteUs01zfjRPLo1m/",{"dataGaName":3231,"dataGaLocation":3218},"Nasdaq Video",{"text":3233,"video":3234,"config":3239},"Southwest Airlines is using GitLab to bring consistency to metrics, security, and code quality.",{"altText":3235,"config":3236},"Southwest Airlines Video Thumbnail",{"thumbnail":3237,"href":3238},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1757959730/jay1ykrhx2bjtzavv4su.webp","https://www.youtube.com/embed/xLA69Qq5cVs?si=qJjlhx0YKXMJpJ3Z/",{"dataGaName":3240,"dataGaLocation":3218},"Southwest Airlines Video",{"text":3242,"video":3243,"config":3248},"For CACI International, using GitLab better ensures software security and developer efficiency.",{"altText":3244,"config":3245},"CACI International Video Thumbnail",{"thumbnail":3246,"href":3247},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1757959447/aknzno6oqxtxybqhygch.webp","https://www.youtube.com/embed/qzukFxW7Eak?si=bXhWwa18YtYXUM0i/",{"dataGaName":3249,"dataGaLocation":3218},"CACI International Video",{"componentName":3251,"componentContent":3252},"CustomersShowcaseTabs",{"heading":3253,"button":3254,"tabs":3257},"From planning to production, see how GitLab brings teams together",{"text":3214,"config":3255},{"href":3216,"dataGaName":3217,"dataGaLocation":3256},"customer showcase",[3258,3308,3356,3400],{"heading":3259,"config":3260,"cards":3262},"Featured",{"dataGaName":3261,"dataGaLocation":3256},"featured",[3263,3281,3295],{"cardImage":3264,"logo":3268,"quote":3272,"button":3276},{"altText":3265,"config":3266},"thales",{"src":3267},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1747754964/xcst1i1bgzqcyf9mg1ux.png",{"altText":3269,"config":3270},"thales logo",{"src":3271},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1747747296/aiapfpoushxzdrao0sii.svg",{"text":3273,"author":3274,"role":3275},"With GitLab, we went from a completely isolated situation to a collaborative environment that enables better communication and coordination among diverse teams.","Jordan Dubié","Chief Product Owner, Thales",{"text":3277,"config":3278},"Read story",{"href":3279,"dataGaName":3280,"dataGaLocation":3256},"/customers/thales/","thales case study",{"cardImage":3282,"logo":3286,"text":3290,"button":3291},{"altText":3283,"config":3284},"geo-events",{"src":3285},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1757960663/r5njhxug7at2hkoddy4x.png",{"altText":3287,"config":3288},"mis-logo-blue-transparent",{"src":3289},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1754018718/gljeqt4iiyxqu5hevgru.png","From months to days: MIS accelerates support for disaster victims with GitLab",{"text":3277,"config":3292},{"href":3293,"dataGaName":3294,"dataGaLocation":3256},"/customers/mckenzie-intelligence-services/","MIS case study",{"cardImage":3296,"logo":3300,"text":2146,"button":3304},{"altText":3297,"config":3298},"kantoor",{"src":3299},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1757961639/nnfgechxco7qzshsnuc7.jpg",{"altText":3301,"config":3302},"cube-logo",{"src":3303},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1754018682/am9woaqg4fssdi17llr3.png",{"text":3277,"config":3305},{"href":3306,"dataGaName":3307,"dataGaLocation":3256},"/customers/cube/","cube case study",{"heading":89,"config":3309,"cards":3310},{"dataGaName":91,"dataGaLocation":3256},[3311,3328,3342],{"cardImage":3312,"logo":3316,"quote":3320,"button":3324},{"altText":3313,"config":3314},"siemens-cover-image",{"src":3315},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1757961628/vztoizwxe28xmbqxecat.jpg",{"altText":3317,"config":3318},"siemens-color-logo",{"src":3319},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1754018726/gvkvducefyvku3jzn2bc.png",{"text":3321,"author":3322,"role":3323},"We really try to bring the open source culture in, and so far, we really succeeded. With CI/CD, we have one and a half million builds every month. The whole culture has completely changed.","Fabio Huser","Software Architect at Siemens Smart Infrastructure, Siemens",{"text":3277,"config":3325},{"href":3326,"dataGaName":3327,"dataGaLocation":3256},"/customers/siemens/","siemens case study",{"cardImage":3329,"logo":3333,"text":3337,"button":3338},{"altText":3330,"config":3331},"nvidia",{"src":3332},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1757961625/omtyh4aopgab4obiugrt.jpg",{"altText":3334,"config":3335},"nvidia-color-logo",{"src":3336},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1754018720/jozpx3g2byckplozupr7.svg","How GitLab Geo supports NVIDIA’s innovation",{"text":3277,"config":3339},{"href":3340,"dataGaName":3341,"dataGaLocation":3256},"/customers/nvidia/","nvidia case study",{"cardImage":3343,"logo":3347,"text":3351,"button":3352},{"altText":3344,"config":3345},"iron-mountain",{"src":3346},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1757961615/f12rf9cettrj8qpchwug.png",{"altText":3348,"config":3349},"iron-mountain logo",{"src":3350},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1745517944/okxhs17wk5ubfpttlra2.png","Iron Mountain drives DevOps evolution with GitLab Ultimate",{"text":3277,"config":3353},{"href":3354,"dataGaName":3355,"dataGaLocation":3256},"/customers/iron-mountain/","iron mountain case study",{"heading":69,"config":3357,"cards":3359},{"dataGaName":3358,"dataGaLocation":3256},"financial-services",[3360,3373,3386],{"cardImage":3361,"logo":3364,"quote":3367,"button":3369},{"altText":3362,"config":3363},"ally-financial-logo",{"src":1134},{"altText":3362,"config":3365},{"src":3366},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1754018666/afbjqydmuoccgc8ry4gj.png",{"text":1162,"author":1163,"role":3368},"Executive Director and CIO of Consumer, Commercial Banking & Invest, Ally Financial",{"text":3277,"config":3370},{"href":3371,"dataGaName":3372,"dataGaLocation":3256},"/customers/ally/","ally case study",{"cardImage":3374,"logo":3377,"text":3381,"button":3382},{"altText":3375,"config":3376},"airwallex",{"src":1015},{"altText":3378,"config":3379},"airwallex logo",{"src":3380},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1754018664/yvkhis15iwnducgkiyp2.png","Global fintech company Airwallex meets customer needs faster with GitLab",{"text":3277,"config":3383},{"href":3384,"dataGaName":3385,"dataGaLocation":3256},"/customers/airwallex/","airwallex case study",{"cardImage":3387,"logo":3391,"text":3395,"button":3396},{"altText":3388,"config":3389},"goldman",{"src":3390},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1757961612/cw5seropodn5nsrr4gs6.jpg",{"altText":3392,"config":3393},"goldman-sachs logo",{"src":3394},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1751663183/ijoh3vyhqusfdywqqwqs.svg","Goldman Sachs improves from 1 build every two weeks to over a thousand per day",{"text":3277,"config":3397},{"href":3398,"dataGaName":3399,"dataGaLocation":3256},"/customers/goldman-sachs/","goldman-sachs case study",{"heading":290,"config":3401,"cards":3403},{"dataGaName":3402,"dataGaLocation":3256},"public-sector",[3404,3420,3434],{"cardImage":3405,"logo":3409,"quote":3412,"button":3416},{"altText":3406,"config":3407},"intuitive-machines",{"src":3408},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1757961623/dmcr2ftve7khol77cjja.jpg",{"altText":3406,"config":3410},{"src":3411},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1755887550/fabv3ums3ucm5ppuhbsy.png",{"text":3413,"author":3414,"role":3415},"We built a spacecraft from scratch in five years. If we hadn’t adopted GitLab, we could not have done that. The lander would not have flown — not in the timeframe we were working on and with the number of people we had on the team.","James Blakeslee","Software Lead, Intuitive Machines",{"text":3277,"config":3417},{"href":3418,"dataGaName":3419,"dataGaLocation":3256},"/customers/intuitive-machines/","intuitive-machines case study",{"cardImage":3421,"logo":3425,"text":3429,"button":3430},{"altText":3422,"config":3423},"sigma-defense",{"src":3424},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1757961618/kqpnqesmrvitvucrbfwz.jpg",{"altText":3426,"config":3427},"sigma-defense logo",{"src":3428},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1754018732/wlzg2c2qgx75hcssk9qg.png","Sigma Defense uses GitLab to speed software delivery to US Navy",{"text":3277,"config":3431},{"href":3432,"dataGaName":3433,"dataGaLocation":3256},"/customers/sigma-defense/","sigma-defense case study",{"cardImage":3435,"logo":3439,"text":3443,"button":3444},{"altText":3436,"config":3437},"lockheed-martin",{"src":3438},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1757961635/cdhu9espptaqys8pvb5w.jpg",{"altText":3440,"config":3441},"lockheed-martin logo",{"src":3442},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1745517945/zbnsprmeoavupjkmexhk.png","Lockheed Martin saves time, money, and tech muscle with GitLab",{"text":3277,"config":3445},{"href":3446,"dataGaName":3447,"dataGaLocation":3256},"/customers/lockheed-martin/","lockheed-martin case study",{"componentName":3449,"componentContent":3450},"CustomersLogoGridCarousel",{"config":3451,"partners":3453},{"rowsPerPage":3452,"paginated":199},4,[3454,3461,3466,3471,3476,3481,3484,3488,3492,3496,3501,3505,3510,3513,3516,3519],{"altText":3455,"config":3456},"airbus logo",{"href":3457,"src":3458,"dataGaName":3459,"dataGaLocation":3460},"/customers/airbus/","https://res.cloudinary.com/about-gitlab-com/image/upload/v1754018664/l6rzgyy6ndjsuvzk6uso.png","Airbus logo","body",{"altText":3462,"config":3463},"deutsche-telekom logo",{"href":3464,"src":3465,"dataGaName":3462,"dataGaLocation":3460},"/customers/deutsche-telekom/","https://res.cloudinary.com/about-gitlab-com/image/upload/v1754018685/mvwmgv7o1ue3sidqfp4o.jpg",{"altText":3467,"config":3468},"hackerone logo",{"href":3469,"src":3470,"dataGaName":3467,"dataGaLocation":3460},"/customers/hackerone/","https://res.cloudinary.com/about-gitlab-com/image/upload/v1751663579/nwhpv6y6yiiq9u5lqjsv.png",{"altText":3472,"config":3473},"nasdaq logo",{"href":3474,"src":3475,"dataGaName":3472,"dataGaLocation":3460},"https://www.youtube.com/watch?v=sT85nT9X2mM/","https://res.cloudinary.com/about-gitlab-com/image/upload/v1751663476/bnmptnzb08a2zc27vwlf.svg",{"altText":3477,"config":3478},"ubs logo",{"href":3479,"src":3480,"dataGaName":3477,"dataGaLocation":3460},"/blog/ubs-gitlab-devops-platform/","https://res.cloudinary.com/about-gitlab-com/image/upload/v1755887586/hzkzigbpkzwsdwlsmswh.svg",{"altText":3482,"config":3483},"siemens logo",{"href":3326,"src":3319,"dataGaName":3482,"dataGaLocation":3460},{"altText":3485,"config":3486},"hilti logo",{"href":3487,"src":3114,"dataGaName":3485,"dataGaLocation":3460},"/customers/hilti/",{"altText":3489,"config":3490},"fujitsu logo",{"href":3491,"src":2779,"dataGaName":3489,"dataGaLocation":3460},"/customers/fujitsu/",{"altText":3493,"config":3494},"fanatics logo",{"href":3495,"src":2734,"dataGaName":3493,"dataGaLocation":3460},"/customers/fanatics/",{"altText":3497,"config":3498},"haven logo",{"href":3499,"src":3500,"dataGaName":3497,"dataGaLocation":3460},"/customers/haven-technologies/","https://res.cloudinary.com/about-gitlab-com/image/upload/v1751663568/ohuqczwcofa5niecf7si.png",{"altText":3502,"config":3503},"deakin-university logo",{"href":3504,"src":2244,"dataGaName":3502,"dataGaLocation":3460},"/customers/deakin-university/",{"altText":3506,"config":3507},"dunelm logo",{"href":3508,"src":3509,"dataGaName":3506,"dataGaLocation":3460},"/customers/dunelm/","https://res.cloudinary.com/about-gitlab-com/image/upload/v1755887538/ra29bxrf84ctppz6lr1d.svg",{"altText":3511,"config":3512},"nvidia logo",{"href":3340,"src":3336,"dataGaName":3511,"dataGaLocation":3460},{"altText":3514,"config":3515},"goldman logo",{"href":3398,"src":3394,"dataGaName":3514,"dataGaLocation":3460},{"altText":3517,"config":3518},"iron mountain logo",{"href":3354,"src":3350,"dataGaName":3517,"dataGaLocation":3460},{"altText":3520,"config":3521},"credit-agricole logo",{"href":3522,"src":3523,"dataGaName":3520,"dataGaLocation":3460},"/customers/credit-agricole/","https://res.cloudinary.com/about-gitlab-com/image/upload/v1754018680/gvggjnudffk63z5vzxas.png",{"componentName":3525,"componentContent":3526},"CustomersCardsAndStatsTabs",{"heading":3527,"button":3528,"config":3531,"tabs":3532,"ctaCard":3665},"Organizations of all sizes trust GitLab",{"text":3214,"config":3529},{"href":3216,"dataGaName":3217,"dataGaLocation":3530},"customers organization size",{"purpleBackground":199},[3533,3571,3619],{"heading":280,"config":3534,"cards":3535,"quote":3558},{"dataGaName":283,"dataGaLocation":3530},[3536,3544,3552],{"cardImage":3537,"heading":2540,"text":2542,"button":3541},{"altText":3538,"config":3539},"dunelm",{"src":3540},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1757960131/madhyxykohxxomjc75n1.png",{"text":3277,"config":3542},{"href":3508,"dataGaName":3543,"dataGaLocation":3530},"dunelm case study",{"cardImage":3545,"heading":1462,"text":1464,"button":3548},{"altText":3546,"config":3547},"bab-cover-image",{"src":1465},{"text":3277,"config":3549},{"href":3550,"dataGaName":3551,"dataGaLocation":3530},"/customers/bab/","bendigo and adelaide bank case study",{"cardImage":3553,"heading":3555,"text":3337,"button":3556},{"altText":3330,"config":3554},{"src":3332},"Nvidia",{"text":3277,"config":3557},{"href":3340,"dataGaName":3341,"dataGaLocation":3530},{"logo":3559,"heading":3115,"text":3562,"author":3142,"role":3563,"stats":3564,"button":3568},{"altText":3560,"config":3561},"hilti",{"src":3114},"GitLab is bundled together like a suite and then ships with a very sophisticated installer. And then it somehow works. This is very nice if you're a company which just wants to get it up and running.","Head of Software Delivery, Hilti",[3565,3566,3567],{"metric":3132,"text":3133},{"metric":2163,"text":3135},{"metric":2842,"text":2840},{"text":3277,"config":3569},{"href":3487,"dataGaName":3570,"dataGaLocation":3530},"hilti case study",{"heading":3572,"config":3573,"cards":3575,"quote":3606},"Mid-market",{"dataGaName":3574,"dataGaLocation":3530},"mid-market",[3576,3587,3595],{"cardImage":3577,"heading":3581,"text":3582,"button":3583},{"altText":3578,"config":3579},"thezebra-heading",{"src":3580},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1757961633/hlbklbrtv9bxsiozjp6o.jpg","The Zebra","How The Zebra achieved secure pipelines in black and white",{"text":3277,"config":3584},{"href":3585,"dataGaName":3586,"dataGaLocation":3530},"/customers/thezebra/","the zebra case study",{"cardImage":3588,"heading":1989,"text":1991,"button":3591},{"altText":3589,"config":3590},"conversica",{"src":1992},{"text":3277,"config":3592},{"href":3593,"dataGaName":3594,"dataGaLocation":3530},"/customers/conversica/","conversica case study",{"cardImage":3596,"heading":3600,"text":3601,"button":3602},{"altText":3597,"config":3598},"moneyfarm-cover-image-july",{"src":3599},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1757961620/qik6wsejy7ztphunau1g.jpg","Moneyfarm","Moneyfarm deploys faster using fewer tools with GitLab",{"text":3277,"config":3603},{"href":3604,"dataGaName":3605,"dataGaLocation":3530},"/customers/moneyfarm/","moneyfarm case study",{"logo":3607,"heading":2967,"text":3610,"author":2994,"role":3611,"stats":3612,"button":3616},{"altText":3608,"config":3609},"hackerone",{"src":3470},"GitLab is helping us catch security flaws early and it's integrated it into the developer's flow. An engineer can push code to GitLab CI, get that immediate feedback from one of many cascading audit steps and see if there's a security vulnerability built in there, and even build their own new step that might test a very specific security issue.","Head of Infrastructure, HackerOne",[3613,3614,3615],{"metric":2982,"text":2983},{"metric":2985,"text":2840},{"metric":2987,"text":2988},{"text":3277,"config":3617},{"href":3469,"dataGaName":3618,"dataGaLocation":3530},"hackerone case study",{"heading":285,"config":3620,"cards":3622,"quote":3652},{"dataGaName":3621,"dataGaLocation":3530},"small-business",[3623,3632,3643],{"cardImage":3624,"heading":2869,"text":2871,"button":3628},{"altText":3625,"config":3626},"glympse-case-study",{"src":3627},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1757961092/rz9vsjqbew2adw80t1ki.jpg",{"text":3277,"config":3629},{"href":3630,"dataGaName":3631,"dataGaLocation":3530},"/customers/glympse/","glympse case study",{"cardImage":3633,"heading":3637,"text":3638,"button":3639},{"altText":3634,"config":3635},"nebulaworks",{"src":3636},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1757961613/wlg5shr2zkrvuzriewo5.jpg","Nebulaworks","How Nebulaworks replaced 3 tools with GitLab and empowered customer speed and agility",{"text":3277,"config":3640},{"href":3641,"dataGaName":3642,"dataGaLocation":3530},"/customers/nebulaworks/","nebulaworks case study",{"cardImage":3644,"heading":112,"text":3647,"button":3648},{"altText":114,"config":3645},{"src":3646},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1757961626/lmbnbn2j6hyutgceubhu.jpg","With just one year under its belt, Remote is improving global employment with GitLab SCM and CI/CD.",{"text":3277,"config":3649},{"href":3650,"dataGaName":3651,"dataGaLocation":3530},"/customers/remote/","remote case study",{"logo":3653,"heading":2824,"text":3656,"author":2849,"role":3657,"stats":3658,"button":3661},{"altText":3654,"config":3655},"fullsave-log",{"src":2823},"GitLab is an all-in-one solution that offers clarity and helps to improve the whole team’s efficiency.","Chief Technology Officer, FullSave",[3659,3660],{"metric":1034,"text":2840},{"metric":2842,"text":2843},{"text":3277,"config":3662},{"href":3663,"dataGaName":3664,"dataGaLocation":3530},"/customers/fullsave/","fullsave case study",{"text":3666,"config":3667,"button":3669},"Learn how GitLab for Enterprises can help your team ship secure code faster and drive business results.",{"icon":3668},"IncreaseThin;",{"text":117,"config":3670},{"href":282,"dataGaName":3671,"dataGaLocation":3530},"enterprise learn more",{"componentName":3673,"componentContent":3674},"CustomersIndustrySection",{"heading":3675,"tabs":3676},"Loved by users. Recognized by analysts.",[3677,3684],{"heading":3678,"config":3679,"text":3683},"G2 Leader in DevSecOps",{"icon":3680,"dataGaName":3681,"dataGaLocation":3682,"showBadges":199},"RibbonCheckAlt2","g2 leader in devsecops","badge section","GitLab ranks as a G2 Leader across DevSecOps categories",{"heading":3685,"config":3686,"text":3683,"button":3689,"cards":3694},"Industry Analyst Research",{"icon":3687,"dataGaName":3688,"dataGaLocation":3682},"DocPencilAlt","industry analyst research",{"text":117,"config":3690},{"href":3691,"dataGaName":3692,"dataGaLocation":3693},"/analysts/","industry learn more","customers badge",[3695,3704,3713,3719],{"text":3696,"image":3697,"config":3701},"The 2019 Forrester Wave™: Cloud-Native Continuous Integration Tools",{"altText":3698,"config":3699},"forrester logo",{"src":3700},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1751335786/lo2jfhxnf4eopwpfvsdd.svg",{"href":3702,"dataGaName":3703,"dataGaLocation":3693},"/press/releases/2019-09-20-gitlab-named-cloud-native-continuous-integration-tools-leader/","The 2019 Forrester Wave",{"text":3705,"image":3706,"config":3710},"2022 Gartner® Magic Quadrant for Enterprise Agile Planning Tools",{"altText":3707,"config":3708},"gartner logo",{"src":3709},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1751663315/iomamzsmpgw6k2k0hukt.svg",{"href":3711,"dataGaName":3712,"dataGaLocation":3693},"/press/releases/2021-04-27-gitlab-positioned-leader-gartner-magic-quadrant-enterprise-agile-planning-tools/","2022 gartner magic quadrant for enterprise agile planning tools",{"text":3714,"image":3715,"config":3717},"2022 Gartner® Magic Quadrant™ for Application Security Testing",{"altText":3707,"config":3716},{"src":3709},{"href":3702,"dataGaName":3718,"dataGaLocation":3693},"2022 gartner magic quadrant for application security testing",{"text":3720,"image":3721,"config":3723},"2021 Gartner® Market Guide for Value Stream Delivery Platforms",{"altText":3707,"config":3722},{"src":3709},{"href":3724,"dataGaName":3725,"dataGaLocation":3693},"/press/releases/2021-11-03-gitlab-inc-named-a-representative-vendor-in-new-gartner-market-guide/","2021 gartner market guide for value stream delivery platforms",{"componentName":3727,"componentContent":3728},"CustomersFullWidthCta",{"config":3729,"heading":3730,"image":3731,"button":3735},{"purpleBackground":199},"Learn how GitLab solves some of today’s toughest challenges",{"altText":3732,"config":3733},"customers link",{"src":3734},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1757959492/rsihx9p6va1pl8esrvyl.jpg",{"text":3214,"config":3736},{"href":3216,"dataGaName":3217,"dataGaLocation":3460},"content:en-us:customers:index.yml",{"_path":3739,"content":3740,"config":3792,"_id":3793},"/en-us/customers/intuitive-machines",{"name":3741,"logo":3742,"hero":3743,"heroImage":3744,"benefits":3745,"industry":3756,"employeeCount":3027,"location":3757,"solution":913,"stats":3758,"headline":3766,"summary":3767,"quotes":3768,"content":3771},"Intuitive Machines","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745517943/pd7pl28wbxdkrtpbmim3.png","Intuitive Machines enables historic Moon landing with GitLab","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518420/lsn4rixyfpdra7ppieyv.jpg",[3746,3749,3753],{"metric":3747,"config":3748},"Enables critical collaboration",{"icon":909},{"metric":3750,"config":3751},"Pipelines offer quality assurance",{"icon":3752},"MonitorPipeline",{"metric":3754,"config":3755},"Speeds development",{"icon":902},"Science and Technology","Houston, Texas",[3759,3761,3764],{"value":1588,"metric":3760},"increase in release cadence",{"value":3762,"metric":3763},"99%","reduction in downtime",{"value":2508,"metric":3765},"decrease in pipeline execution time","Founded in 2013, Intuitive Machines has evolved from a think tank into a space exploration company that provides space infrastructure and services required to commercialize the Solar System.","In 2024, working under a NASA contract, it became the first U.S. venture in 50 years — and the first commercial organization — to land a spacecraft intact on the Moon. Named one of Time magazine’s 100 Most Influential Companies of 2024, Intuitive Machines is at the forefront of lunar exploration.",[3769],{"quoteText":3413,"author":3414,"authorTitle":3770,"authorCompany":3741},"Software Lead",[3772,3774,3777,3780,3783,3786,3789],{"text":3773},"When [Intuitive Machines](https://www.intuitivemachines.com/) won a $77 million contract from NASA in 2019 to build, launch, and land a spacecraft near the south pole of the Moon, the company’s software development team knew they only had five years to build all of the code they would need to communicate with, navigate, control, and fly the vehicle. And they couldn’t do it with a fragmented, time-consuming toolchain. They needed an end-to-end DevSecOps platform to create and deploy secure software faster, hit their deadlines, and become the first U.S. venture to land on the Moon since the famed Apollo missions in the early 1970s. They partnered with GitLab, and together they made history.",{"header":3775,"text":3776},"Preparing for Moon launch drives GitLab adoption","Confident in their chances at winning NASA’s lunar lander contract in 2019, Intuitive Machines adopted GitLab months before receiving the official confirmation, so they would be prepared to hit the ground running.\n\n“The Moon lander project was easily an order of magnitude larger than anything we had ever done,” says James Blakeslee, software lead for Intuitive Machines. “We had a clean sheet so we had the opportunity to start from scratch. Looking at the software team and what we had to do, we knew we needed a platform that could handle all of our software challenges.”\n\nHe adds that it was important to have a single application where all of their 40 to 50 developers could work, gain visibility, and [collaborate](https://about.gitlab.com/blog/5-ways-collaboration-boosts-productivity-and-your-career/) on shared projects. Everyone on their team needed to have the ability to drop in on any project and pitch in on whatever work needed to be done. “The whole team needed a platform with the same look and feel no matter what project or software process they were working on,” says Blakeslee. “And GitLab’s platform gave us that collaborative flexibility and it had the tools we needed already built into it. We went all in.”",{"header":3778,"text":3779},"The race to build a spacecraft from the ground up","Aside from using some legacy frameworks the company already had in place, Intuitive Machines was faced with building all of the software for the lander, named Odysseus or “Odie.” That meant building systems for ground control; simulation; in-flight needs, like navigation and communications; and landing functions.\n\n“The reason the spacecraft works is because we tested the heck out of it with simulation tens of thousands or hundreds of thousands of times before the mission flew,” says Blakeslee. “And if the software in the control center doesn't work, you can't see the telemetry from the spacecraft and you can't talk to it. That would leave the operators blind. All of that is critical to the mission,” he adds. “All of that critical software was built with GitLab. We couldn’t have done it without the platform.”\n\nOdysseus lifted off on February 15, 2024. It did not carry a human crew but did ferry commercial scientific payloads, including technology for radio observations, stereo cameras, and navigation doppler lidar. It landed on the Moon seven days after launch, joining only Russia, the U.S., China, India, and Japan as part of a small, elite group that has marked this achievement.\n\n“We built a spacecraft from scratch in five years. If we hadn’t adopted GitLab, we could not have done that. The lander would not have flown — not in the timeframe we were working on and with the number of people we had on the team,” says Blakeslee.",{"header":3781,"text":3782},"Making software fixes on the fly with CI pipelines","Getting the spacecraft off the ground was not the end of the DevSecOps team’s job.\n\nThe first flight of any spacecraft is considered experimental, with engineers expecting to find and triage issues after launch. For Odysseus, “There were certainly things that came up in flight — Easter eggs — despite all the rugged testing that we did,” says Blakeslee. “That meant we had to patch software in flight. The deadlines were tighter. The stakes were higher. There was a lot more tension.”\n\nDue to timelines set by orbital mechanics and thermal constraints, there were specific deadlines for sending patches to the lander, both in flight and on the Moon. To quickly create and deploy those patches — including fixes for laser range finders, communications, and navigation — they relied heavily on GitLab’s continuous integration (CI) pipelines to ensure the patches weren’t introducing any defects into the system.\n\nThe CI pipelines enable the teams to scrutinize the software and [run quality-assurance checks](https://about.gitlab.com/blog/efficient-devsecops-workflows-with-rules-for-conditional-pipelines/) at a speed that they couldn’t do manually, according to Blakeslee. Intuitive Machines’ developers were able to create their own regression, integration, quality assurance, and acceptance tests that run in the pipelines. All of these tests gave them insights into the code that was changed, and ensured that the patches hadn’t broken anything, were compatible with ground software, and actually fixed the problems they were meant to resolve.\n\n“We vetted it all in the CI pipelines,” says Blakeslee, noting that they experienced a 20x decrease in pipeline execution time with GitLab. “You have to introduce good patches to the spacecraft. As you can imagine, if you introduce bad patches, it can be game over. It could absolutely end the mission, so you have to have something that vets them. GitLab did that for us.”\n\nThose CI pipelines also helped the DevSecOps teams create patches for problems that were caused when the spacecraft unexpectedly landed at an angle on the Moon, leading to critical communication challenges. The teams had to quickly develop multiple software patches, verify them using the CI pipelines, and restore the communication systems promptly, ultimately sending the patches a quarter of a million miles to successfully get the lander functioning again.",{"header":3784,"text":3785},"Planning ahead for next lunar lander—and a lunar terrain vehicle","With the fixes successfully uploaded into the lander’s systems, Odysseus operated on the lunar surface for seven days, the expected length of the mission. Now with a successful lunar mission in the books, Intuitive Machines is focused on launching a second lander in late 2024. Because their development process worked so well for Odysseus, Blakeslee says they plan to use the same setup.\n\n“We have less than a year between lunar missions, so getting ready is only possible if we build on what we've already constructed,” he says. “This next spacecraft is an evolution of the first mission so we won't change tools and certainly don't plan to start over with the DevSecOps platform. We’re going to stick with what works.”\n\nIntuitive Machines, hoping their lunar work will continue beyond the two landers, is one of three companies NASA has chosen to conduct year-long studies focused on developing a preliminary design and prototype for a lunar terrain vehicle (“LTV”). This LTV is set to be part of the Artemis missions, which will return humans to the Moon. NASA will choose one or more of the three companies to build a LTV, and then test its performance and safety. The vehicle is expected to be able to work for at least 10 years on the lunar surface in extreme temperatures, carry two astronauts, and use a robotic arm. The first Artemis mission is set to launch in 2029.\n\n“If NASA ends up selecting us to build the LTV, we certainly will build the systems with GitLab because it has worked so well for us,” says Blakeslee. “We’d just scale up the DevSecOps group that we have now. We can't argue against the results of landing on the Moon for the first time for the U.S. in more than 50 years. So I plan to continue to use the ecosystem we used to do that.”",{"header":3787,"text":3788},"Using artificial intelligence to accelerate development","Once the second lunar lander has made it to the Moon’s surface, the company’s DevSecOps teams can pause long enough to evaluate how they’re using GitLab and add more platform features, such as taking advantage of [GitLab runners](https://about.gitlab.com/blog/how-to-automate-creation-of-runners/) to help manage the increasing size of their teams and the workloads on their pipelines.\n\nAnother thing Blakeslee says they’re looking forward to using is the artificial intelligence features in [GitLab Duo](https://about.gitlab.com/gitlab-duo/).\n\n“The AI revolution is totally upon us now and using GitLab Duo seems like a natural advancement for us,” he says. “I think it will help [not just with code suggestions and code completion](https://about.gitlab.com/the-source/ai/how-to-put-generative-ai-to-work-in-your-devsecops-environment/), but with [answering questions about vulnerabilities and code](https://about.gitlab.com/the-source/ai/understand-and-resolve-vulnerabilities-with-ai-powered-gitlab-duo/). We’re always looking for ways to improve not just speed but the overall development experience.”\n\n“AI is really an accelerant for development,” Blakeslee adds. “You’ve got to keep up with it if you want to continue to be competitive. That’s why GitLab Duo is on my radar.”",{"header":3790,"text":3791},"GitLab a mission-critical part of lunar success","There was a 52-year-year gap between the Apollo mission in 1972 and when Intuitive Machines successfully landed Odysseus. And this first U.S. commercial lunar landing was a historic milestone — one that put Intuitive Machines on the map in the space exploration industry.\n\n“Everything we were working on was aggregated into one very specific event and we didn’t have a lot of margin for error,” says Blakeslee. “Unless we had really good software quality assurance and automation around that assurance, we couldn’t have made it happen. I have no doubt in my mind that if I went back in time and picked other development tools, our software would have been late and broken, and we probably wouldn't have flown.”\n\n“We absolutely could not have built a spacecraft in five years without GitLab. It helped us make history,” he adds. “That made a material benefit to the success of our business.”",{"template":950,"size":40,"region":102,"industry":79},"content:en-us:customers:intuitive-machines.yml",{"_path":3795,"content":3796,"config":3839,"_id":3840},"/en-us/customers/inventx",{"name":3797,"logo":3798,"hero":3799,"heroImage":3800,"benefits":3801,"industry":89,"employeeCount":2657,"location":3808,"solution":975,"stats":3809,"headline":3819,"summary":3820,"quotes":3821,"content":3827,"contributors":1281},"Inventx","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745517989/jeeajkfbtouuforov8q2.png","How GitLab decreased deployment times from 2 days to just 5 minutes for Inventx AG","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518445/kjmqjv3ecf0n867ooeqy.jpg",[3802,3804,3806],{"metric":961,"config":3803},{"icon":963},{"metric":965,"config":3805},{"icon":967},{"metric":969,"config":3807},{"icon":971},"Chur, Switzerland",[3810,3813,3816],{"value":3811,"metric":3812},20,"releases per day. Up from 4 releases per year",{"value":3814,"metric":3815},5,"minute deploys. Down from 2 days.",{"value":3817,"metric":3818},"10-60","minute bug fixes","Inventx simplified pipelines and increased operational efficiency with GitLab CI/CD.","Inventx AG was looking for a solution to simplify customer pipelines and reduce toolchain complexity.\n",[3822],{"quoteText":3823,"author":3824,"authorTitle":3825,"authorCompany":3826},"We're detecting bugs very, very fast and they're also fixed very fast. They can be fixed in maybe 10 minutes to one hour. So bugs are fixed very quickly and also automatically fixed in the production environment. This is a great value.\n","Louis Baumann","DevOps Engineer","Inventx AG",[3828,3831,3833,3836],{"header":3829,"text":3830},"Swiss IT services provider for leading financial institutions","Inventx AG is a Swiss IT partner for leading financial and insurance service providers. Inventx provides information technology, consulting, and application management services for Switzerland’s prominent financial and insurance organizations. The independent IT company offers individual solutions, the highest quality security, and data protection for its customers.\n",{"header":999,"text":3832},"As a multinational corporation, Airbus Intelligence needs tools that can help their team collaborate and work more efficiently across the globe. The Intelligence business wanted to avoid the common challenges of many global companies: distributed teams and disconnected toolchains that cause workflow inefficiency and slow production. An improved workflow that could break through these challenges, make teams more efficient, and foster communication was a high priority. Logan Weber is a software automation engineer at the Web Factory. Finding a better developer workflow was one of his core missions, and the Web Factory’s agility makes the team an ideal testing ground for new tools and technologies. For Logan, it was important that any tools they adopt share a similar dedication to innovation. “We’re in the midst of a digital transformation,” Logan said. “We want to join forces with partners who know what they’re doing and can keep up with us.”\n\nOne of the Web Factory team’s big challenges was that their processes just weren’t efficient enough, which led to delayed releases and lost time in development. Developers could spend at least a full day on the production setup, and too much time was being spent on simple tasks that should have been automated. Developers were frustrated with these manual and lengthy processes that stopped them from focusing on code. With a new tool the Web Factory team also hoped to avoid communication breakdowns between teams. After spending time on the production setup, developers would sometimes realise that the final product didn’t correspond to the initial request, which would then lead to additional efforts. “We’d have to create a bug to modify this error. But it wasn’t a bug, it was just a lack of communication,” Logan explained.\n\nThe Web Factory team tested several tools in the search for the right developer workflow. Because the Web Factory team already used Jira, they decided to test other Atlassian products, such as Bitbucket for version control and Bamboo for CI. Unfortunately, BitBucket and Bamboo didn’t offer a user-friendly experience, and both tools lacked some of the functionalities for their needs. The Web Factory team used Jenkins on old projects, but found it too complicated to maintain. They also wanted to be able to store their deployment script processes as code.\n",{"header":3834,"text":3835},"Simplifying customer complexity","Inventx had experience using GitLab for source code management. In order to simplify workflow, they started using GitLab for CI/CD. “We redesigned the whole pipeline and we're just using GitLab and GitLab runners now. It's all centralized into GitLab and that makes it very easy to troubleshoot. We have a very good overview over all the steps and the customers are also very satisfied with the solution. This really helped us to simplify this task,” said Louis Baumann, DevOps engineer.\n\n\nInventx created a package service for customers. This is a container platform that includes storage, monitoring, logging services, with the whole CI/CD construct running GitLab. The teams no longer need several physical servers to run pipelines. GitLab has allowed them to minimize their toolchain workflow and context switching between tools. “Using GitLab has reduced complexity enormously, and we accelerated  all our workflow processes. It offers us a great overview of all the processes running for one product. And it simplifies the whole toolchain,” according to Baumann.\n",{"header":3837,"text":3838},"Faster builds, increased deployments","With GitLab, developers are now able to own their own code. “GitLab enables our developers to directly deploy to test environments, to run integration tests on our test environment automatically, and also to deploy some nightly builds to our test environment and test them there, automatically,” Baumann said.\n\n\nDeveloper production has increased, due to being able to release code on their own. According to Baumann, the team previously was releasing  about four times a year. Now, they’re releasing approximately 20 times a day. “Everything is now contained in GitLab, in one centralized place and  there is one pipeline running where the customer has a great overview of all the different pipelines that were executed,” Baumann said. “If a shot fails, [the customer] can retry at the pipeline, rerun, and has all locks collected on one central project. This is really, really a great value for us and for our customer.”\n\n\nEngineers are developing on their local machines. Most of the code is written in .NET Core, but they’re starting to write some features in Golang. Teams are using Visual Studio Code as ID, and are deploying using GitLab pipelines to the test environment or the environment from the local machines. The teams execute GitLab runner on Kubernetes; and build their own deployment containers; containing all the functionalities to deploy and manage their resources on Kubernetes.\n\n\nEngineers are able to detect bugs earlier in the software lifecycle because they’re deploying smaller releases, faster. “We're detecting bugs very, very fast and they're also fixed very fast. They can be fixed in maybe 10 minutes to one hour. So bugs are fixed very quickly and also automatically fixed in the production environment. This is a great value,” Baumann added.\n\n\nGitLab is allowing the teams to have more control, broader visibility, better ability to plan with improved governance. With less tools in the pipelines, customers now have streamlined services.\n",{"template":950,"size":40,"region":106,"industry":91},"content:en-us:customers:inventx.yml",{"_path":3842,"content":3843,"config":3883,"_id":3884},"/en-us/customers/iron-mountain",{"name":3844,"logo":3350,"hero":3351,"heroImage":3845,"benefits":3846,"industry":89,"employeeCount":3855,"location":3856,"solution":913,"stats":3857,"headline":3864,"summary":3865,"quotes":3866,"content":3871},"Iron Mountain","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518421/jnf3ihqvksetnf4v7fc3.png",[3847,3850,3852],{"metric":3848,"config":3849},"Reduced complexity",{"icon":1302},{"metric":2354,"config":3851},{"icon":1142},{"metric":3853,"config":3854},"Improved visibility",{"icon":1526},"25,000+","Boston, Massachusetts",[3858,3861],{"value":3859,"metric":3860},"$150k","in approximate cost savings per year",{"value":3862,"metric":3863},"20 hrs","saved in onboarding time per project","Iron Mountain has embraced Agile methods — and that has led the data governance giant to GitLab CI/CD.","The platform speeds pipeline creation and takes over administrative chores so that developers can focus on development.\n",[3867],{"quoteText":3868,"author":3869,"authorTitle":3870,"authorCompany":3844},"GitLab has provided us with the foundation and platform to enable our scaled Agile framework. We are able to collaborate within our Enterprise IT teams and our key stakeholders.\n","Hayelom Tadesse","Vice President of Enterprise Technology",[3872,3874,3877,3880],{"header":7,"text":3873},"Iron Mountain Incorporated is a global leader in innovative storage, data center infrastructure, asset lifecycle management and information management services. Founded in 1951 and trusted by more than 225,000 customers worldwide, Iron Mountain helps customers CLIMB HIGHER™ to transform their businesses.\n\nThrough a range of services including digital transformation, data centers, secure records storage, information management, asset lifecycle management, secure destruction, and art storage and logistics, Iron Mountain helps businesses bring light to their dark data, enabling customers to unlock value and intelligence from their stored digital and physical assets at speed and with security, while helping them meet their environmental goals.\n",{"header":3875,"text":3876},"Taming fragmented tooling to gain a single view of DevOps","Iron Mountain’s architecture and platform group had a goal to implement an overall strategy to support the use of cloud managed services. The group began evaluating SaaS-based integration platforms, which they hoped could address challenges such as fragmented open source tooling, gaps that blocked development and operations communications, heavy administrative burdens, and difficulties with efficiently securing complex pipeline deployments. Existing on-premises Jira software incurred management complexity in the form of plugin troubleshooting, and with Veracode security software, teams were only able to discover coding issues late in the development cycle, causing resource-intensive rework. In addition, operations needed to support teams’ increasing adoption of new Kubernetes development methods. Iron Mountain’s technical leadership concluded that an appropriate cloud services solution was needed to support developers’ challenges.\n",{"header":3878,"text":3879},"GitLab Ultimate SaaS empowers developers while reducing complexity","Iron Mountain chose [GitLab Ultimate on Google Cloud](/partners/technology-partners/google-cloud-platform/){data-ga-name=\"google cloud\" data-ga-location=\"customers content\"} to solve these challenges, and is now running 240 automated cloud deployments on GCP for Google Kubernetes Engine (GKE) workloads. GitLab CI/CD allows teams to save time and boost efficiency with automation while also supporting better security assurance via up-front security scanning such as dynamic application security testing (DAST) and static application security testing (SAST).\n\nGitLab supports Iron Mountain’s goal to “shift security left” — placing more security responsibility in the hands of developers and empowering teams to find security flaws earlier in the process.\n\nGitLab also serves as a complete, cohesive orchestration environment that simplifies management while meeting developers’ needs as they build new Kubernetes environments to support cloud and multi-cloud architecture. This single solution reduces complexity and supports a future-proof, community-driven roadmap that aligns with Iron Mountain’s tech planning. Iron Mountain sees GitLab as an important part of Enterprise Architecture and Platforms’ enablement of Agile methods and helpful to the company’s evolution to DevOps. GitLab Ultimate SaaS does the maintenance, so developers can focus on development.\n",{"header":3881,"text":3882},"Building a governance model with GitLab","With GitLab Ultimate SaaS, Iron Mountain has been able to reduce the costs associated with infrastructure management while also securely increasing production velocity. The company has cut the number of on-premises virtual machines (VMs) by nearly half, saving more than $60,000 per year in maintenance costs and more than $90,000 per year in labor.\n\n“GitLab has provided us with the foundation and platform to enable our scaled Agile framework,” adds Hayelom Tadesse, Iron Mountain’s vice president of enterprise technology. “We are able to collaborate within our Enterprise IT teams and our key stakeholders.”\n\nEpics in GitLab provide a way for Iron Mountain teams to organize and track issues according to a strategic theme. Team members can employ features within epics to create a governance model for development that supports large, multiyear initiatives.\n\nIron Mountain Vice President of Technology Jason Monoharan says GitLab — the company — has a roadmap and community spirit that aligns with best Agile practices. “To me, the vision that GitLab has in terms of tying strategy to scope and to code is very powerful. Also, I appreciate the level of investment they are continuing to make in the platform as they continue to work on it,” he says. Monoharan adds that GitLab’s team has collaborated closely with Iron Mountain teams to define priority features.\n\nAt Iron Mountain, GitLab’s single pane of glass helps teams to understand the demands on their capacity, and allows them to focus on priority work in order to speed secure delivery of innovative services — all while ensuring the security of pipelines and improving productivity.\n",{"template":950,"size":44,"region":102,"industry":91},"content:en-us:customers:iron-mountain.yml",{"_path":3886,"content":3887,"config":3933,"_id":3934},"/en-us/customers/jasper-solutions",{"name":3888,"logo":3889,"hero":3890,"heroImage":3891,"benefits":3892,"industry":89,"employeeCount":3903,"location":3904,"solution":913,"stats":3905,"headline":3913,"summary":3914,"quotes":3915,"content":3920,"contributors":1281},"Jasper Solutions","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745517989/p9dcy1e0ir9nhyutdn3n.svg","How Jasper Solutions offers “DevSecOps in a box” with GitLab","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518445/dmrzhgakurd1vkitzcg0.jpg",[3893,3897,3900],{"metric":3894,"config":3895},"Higher customer satisfaction",{"icon":3896},"Access",{"metric":3898,"config":3899},"ROI and RTO increased",{"icon":1247},{"metric":3901,"config":3902},"Hundreds of work hours saved annually",{"icon":967},"87","NY, VA, HI, GA, IA",[3906,3908,3910],{"value":1750,"metric":3907},"Reduction in cycle time",{"value":2666,"metric":3909},"Increase in deployment frequency",{"value":3911,"metric":3912},"90%-95%","Of projects on budget and on time","Jasper builds client-specific solutions using GitLab SCM, CI, and CD","With GitLab as their single stack software for CI, CD, and SCM, Jasper teams no longer worry about pipeline failures\n",[3916],{"quoteText":3917,"author":3918,"authorTitle":3919,"authorCompany":3888},"If a certain feature is not available, the ability to have a discussion with GitLab in the open and to put it on a road map so we can tell a customer that you can start using the existing platform and the features and functionality and within three months we will offer this specific feature to acknowledge your need. There is no other single product in the industry that does that.\n","Andy Patel","CEO and Owner",[3921,3924,3927,3930],{"header":3922,"text":3923},"Empowering the tactical edge for the public sector","[Jasper Solutions](https://www.jaspersolutions.com/) is a software development company that provides a broad range of business and technology services. Jasper offers clients worldwide access to enhanced workflow performance with the goal of aligning IT objectives with business objectives. The diverse customer range includes federal, state, and local government agencies, as well as several commercial enterprises. Jasper specializes in advanced analytics for data management, governing public or private cloud computing, and cyber security.\n\nOne of the leading solutions that Jasper provides enables organizations with tactical edge. “Tactical edge by definition is any individual or any operation that’s a field operation where no network connectivity or any network intermittent connectivity is provided, and primarily the field operations can consist of anything from logistics, to cyber, to information gathering, to an ISR capability,” according to [Andy Patel](https://www.linkedin.com/in/anshuman-andy-patel-35a48a/), CEO and Owner of Jasper Solutions.\n\nJasper Solutions offers constantly updated evolutionary data in the form of “DevSecOps in a box,” which enables operations at the tactical edge and gives the ability to modify any application to fit an environment and update intermittently when a network is established. Public sector clients, including war fighters, airmen, Marines, sailors, and other sectors of military service rely heavily on this service. “The ability to have the most recent updated information at the tactical edge can save a life or cause a loss of battalion,” Patel said.\n",{"header":3925,"text":3926},"Too many tools causing too many failures","Over the past five years, Jasper has been working with traditional pipelines, which included tools from Atlassian, BitBucket, Jira, Jenkins, and SonarQube. Developers provided a variety of pipelines to Jasper customers to enable their development. Jasper kept running into challenges with broken pipelines caused by single tool updates. Each time an upgrade was available for one tool, feature, or function, the pipeline would break and the development team would spend more time fixing the pipeline than actually developing code for customers.\n\n“We used to use a lot of tools and the biggest challenge that we had was that we were more worried about when the pipeline was going to break and how to actually fix the pipeline or roll it back so we could continue to do development and then introduce the additional features and functionalities by each different product in order to get it fully configured and fully tested,” Patel said. “A lot of times the development and test environment would have various different test packages with different vendors.”\n\nJasper’s teams spent years working with variations of different tools to develop their products to empower customers to work at the tactical edge and each one of them failed or didn’t meet requirements. According to Patel, nine out of 10 times the field operations did not have the latest and greatest tools to address their needs. “For a long, long time we could not put a solution together simply because we did not find tools that would work to fit specific customer requirements,” Patel said.\n\nIn order to develop “DevSecOps in a box,” Jasper needed a platform that deploys easily, offers code management, has security awareness, and ideally, is all in one tool. A single platform would allow the team to [focus on development](/stages-devops-lifecycle/), rather than on constant pipeline failures caused by updates from multiple tools. Not only would this capability help team members, it would also improve customer satisfaction with better products delivered at a faster rate.\n",{"header":3928,"text":3929},"Transparency provides competitive edge over 260 tools","Jasper adopted GitLab after testing more than 260 other tools. Jasper teams have been using GitLab for the past three and a half years. For the first two years, GitLab was only used internally for development. GitLab became part of the external service after the team saw how easily GitLab enabled deployments. “Knowing and understanding GitLab’s capability, the feature and functionality, the constant updates to add additional feature functionality and the ease of usability by end users to work the pipeline really enabled my internal team at Jasper to use the GitLab pipeline to build our internal development, maintain our applications, and now build our customer applications as well,” Patel said.\n\nAccording to Patel, GitLab’s transparency of the platform set it apart from the competition. Not only is the usability of tools transparent, but GitLab’s roadmap is transparent. “From a value proposition perspective, especially in the [DevSecOps](/solutions/application-security-testing/){data-ga-name=\"devops\" data-ga-location=\"body\"} space where it’s ever evolving and constantly changing, the ability to discuss a specific problem or a gap that GitLab currently does not offer and actually put it on a road map, no other company does that while being completely transparent. And, at the same time, addressing the entire stack of CI, CD and SCM,” Patel said.\n\nGitLab offers every feature, functionality, and benefit that the customers can take advantage of. GitLab is now their single stack software for CI, CD, and SCM. The pipeline gets updated from one end to the other, so teams no longer worry about pipeline failures. “With GitLab, you have the entire pipeline as a single track software to address all of the CI, CD, SCM functionality. So when we do one single upgrade, the entire pipeline gets upgraded with all of the new features and functionalities and 99.9% of the time we’re not breaking the pipeline and we can still address customers’ software development needs and focus on the application lifecycle rather than worry about our pipeline,” Patel said.\n",{"header":3931,"text":3932},"GitLab is the default for “DevSecOps in a box”","Jasper has reduced cycle time by 30% since introducing GitLab more than three years ago. Deployment frequency has accelerated by 25% because the pipelines are not breaking. “The ability to deliver our products with constant updates certainly increases. The ROI and the RTO times have increased, and the value proposition for the last three periods, year-over-year, have certainly increased because we’re providing a better value proposition from delivery, from execution, and also from a management perspective,” Patel said.\n\nGitLab is used to build internal and external products, so the pipeline remains the same. Ninety percent to 95% of project releases are on budget and on time. Some features and functionalities may change depending on a specific need, but between the internals of the organization, as well as the customers, GitLab is the solution. “Having a pipeline that doesn’t break, that’s roughly 350 man hours a year that we save on average for each individual product of ours, if not more,” according to Patel.\n\nFor the past year and a half, Jasper has been building solutions for customers using GitLab and in early 2020, Jasper became a GitLab partner. By December 2019, Jasper had finished the prototype architecture for “DevSecOps in a box” and was rolling it out to customers. “GitLab is by default on every box that we deploy. It is offered as a base solution. The rest of the components and open source software are all complimentary to fit around the DevSecOps scenario in the box,” Patel said. Each customer, from Marine to airman, has specific requirements, so GitLab is the base solution and additional capabilities are added to the overall toolkit accordingly. The “DevSecOps in a box” enables [multicloud deployments](/topics/multicloud/){data-ga-name=\"multicloud\" data-ga-location=\"body\"} for customers, including Azure, AWS, Google, IBM and Oracle Cloud.\n\nJasper is saving between 33%-37% annually since adopting GitLab for SCM, CI, and CD. “If we were purchasing individual tools, plus maintenance and upgrades on those specific tools, and add each one of them up individually and do a price comparison side-by-side to GitLab and if you do a ROI model, the amount of money that we save is tremendous,” Patel added.\n\nSince rolling out “DevSecOps in a box,” customers have been eager to test it out. “We have roughly 35 customers who have been currently working to take a delivery. We have four successful customers who already have it and they cannot stop raving about it. We are working on roughly additional 22 to 23 customers who have heard about it or have seen the capabilities and are interested,” according to Patel.\n",{"template":950,"size":36,"region":102,"industry":91},"content:en-us:customers:jasper-solutions.yml",{"_path":3936,"content":3937,"config":3982,"_id":3983},"/en-us/customers/keytradebank",{"name":3938,"logo":3939,"hero":3940,"heroImage":3941,"benefits":3942,"industry":69,"employeeCount":3952,"location":3953,"solution":975,"stats":3954,"headline":3962,"summary":3963,"quotes":3964,"content":3969,"contributors":1281},"Keytrade Bank","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745517991/ftotmto1ezify1mdnjfy.svg","Keytrade Bank centralizes its tooling around GitLab","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518446/gcw2bgsxjhjetbzflx4b.jpg",[3943,3946,3948],{"metric":3944,"config":3945},"Improved code management",{"icon":2598},{"metric":1524,"config":3947},{"icon":1195},{"metric":3949,"config":3950},"Improved customer satisfaction",{"icon":3951},"ValuesAlt","250","Belgium",[3955,3957,3959],{"value":3452,"metric":3956},"tools replaced by GitLab",{"value":1538,"metric":3958},"jobs executed daily",{"value":3960,"metric":3961},500,"projects since adoption","Keytrade Bank improved version control, CI/CD, and cross-company collaboration with GitLab.\n","Keytrade Bank adopted GitLab for code management, version control, and CI/CD, replacing four tools and improving workflow efficiency.\n",[3965],{"quoteText":3966,"author":3967,"authorTitle":3968,"authorCompany":3938},"GitLab allows us to have a common tool between Dev and Ops. DevOps is really a mentality, and you really try to put it in place within the company, so that people fit into that culture. GitLab really allows it because it's a common solution between these two teams, which we didn't have before. It really simplified the workflow at that level.","Nicolas Pepinster","DevOps and Cloud Engineer",[3970,3973,3976,3979],{"header":3971,"text":3972},"Online financial institution","\n\nKeytrade Bank is the Belgian market leader in online banking and trading, offering a full range of products and services on its digital platforms. It is part of the Crédit Mutuel Arkéa Group. At [Keytrade Bank](https://www.keytradebank.be/) consumers can find everything they want from a bank (current accounts, savings accounts, cards, mortgage loans, trading and investment possibilities, etc.) without ever setting foot in one. The bank helps its clients reach total independence in managing their banking and investment transactions, 24/7.",{"header":3974,"text":3975},"Managing too many tools","\n\nKeytrade Bank was using several different tools within the workflow chain from development to production. On top of that, the teams had created internal scripts for specific needs. With various tools in place, the teams were constantly context switching from one tool to another. Each tool had its own problems and the experts of those tools spent too much time managing and maintaining them. These siloed tools resulted in lots of manual processes, lots of blackboxes, and a lack of visibility across the workflow.\n\nManagers were also lacking the ability to audit work, in terms of who was responsible for which parts of a project and how and when it was happening. It is very important for management to understand what everyone is working on and it was nearly impossible with the existing level of visibility across the toolchain. “We would also have had a lot more finger pointing internally between Dev and Ops, trying to establish what's going on and where the problem is really coming from. Now, it's much easier to identify the problems and know how to solve them,” according to Niels Peto, DevOps and Cloud Engineer. The team was looking for a way to solve these problems and to avoid errors in communication, both internally and with customers. Customer communication is a top priority and Keytrade Bank was looking for the best solution to provide customers with superior service.",{"header":3977,"text":3978},"One platform, lots of features","\n\n“We have tried other suppliers before, but none of them had the support and level of automation of GitLab,” Peto said. GitLab provides developers with a [single solution](/topics/single-application/) that provides several features. “With GitLab, we really have a solution for the development part to the production part. It allows us to do exactly what we did before, or even more because it offers more features, which is really great and that is the main reason for our change,” said Nicolas Pepinster, DevOps and Cloud Engineer. “GitLab is constantly developing and often bringing new features, which we are fully satisfied with.”\n\nThe teams were using Nexus for artifact management presently and are reviewing how GitLab registry could fully replace this tool in the future. In addition, teams were previously using OpenShift container registry and are now using the integrated GitLab registry to store their container images using an AWS S3 backend. GitLab has enabled them to offer an integrated single solution and reduce toolchain complexity.",{"header":3980,"text":3981},"Version control, visibility, and collaboration","\n\nKeytrade Bank now uses GitLab for its Bank Assembly platform. Each team at Keytrade Bank works on different products supplied by the bank using their own set of applications. Bank Assembly has been built from scratch with the aim to provide a transversal platform based on several tools, and they specifically chose GitLab for the center of the platform. The Bank Assembly has a set of built-in pipelines. Teams can use what they need in the blocks because they've created all the ymls in the repository and the applications make e-clouds out of the ymls. It is easy to switch from one version to another because it all goes through GitLab.\n\n“All the teams are starting to be embedded in the Bank Assembly platform, and so we use GitLab as a central point for everything CI/CD, infrastructure, on-premise integration, and AWS,” according to Pepinster. Keytrade Bank installed [GitLab server on AWS](https://docs.gitlab.com/ee/install/aws/) using omnibus. They configured an external PostgreSQL with Aurora RDS. For GitLab runners, teams deployed them both on-premises and in AWS. On AWS, GitLab runners are EC2 instances that spawn new EC2 spot-instances when they pick up a job from GitLab server. It enables teams to handle loads efficiently without thinking about the capacity of the infrastructure. As GitLab runners are deployed in dedicated per feature team AWS accounts, they can easily adjust the setup according to their needs.\n\nKeytrade Bank applications are deployed in AWS mainly on EKS using GitLab. Teams also use Lambda to deploy a simple dashboard showing some crucial information about their applications. As for the other technologies, GitLab is used to deploy Lambda and Terraform configuration related to it. Since adopting GitLab, managers are able to properly audit workflows. “We can now see who does what, and when, which was not the case before. We have a lot of auditors who come to the bank, and it is very important for our management to be able to have all this information - it is now very easy for us,” Pepinster said.\n\nGitLab is also used by the Contact Management Development team. They are responsible for customer management and are the main communication channel with customers. This team is an extremely important element for the bank because there are no physical branches. Keytrade Bank is integrating GitLab with Jira in order to allow the business to control the complete software delivery lifecycle from Jira. In Jira, they developed a workflow with a set of statuses and transitions that a task moves through during its lifecycle. A new branch will trigger a transition to move the task from \"open\" all the way through to “code to be reviewed.” Triggering this transition automatically opens a new merge request in GitLab, using the source branch created before. Review is done in GitLab by other developers and the result of the merge request (either close or merged) triggers another Jira transition.\n\nThe same process happens for deployment: Only authorized users can trigger the transition \"to be deployed in prod.\" This creates a Git tag and triggers the corresponding pipeline to release an application in production. Keytrade Bank's newest project, PSD2, is a set of APIs that must be exposed publicly according to a European standard. PSD2 was created directly with GitLab from its inception. The project uses cloud, on-premises, AWS, and Terraform, and all the tools are managed by GitLab. PSD2 has around 10 microservices, two third parties on the cloud, and one on-premises tier. “The idea is to be able to reuse what has been done for Belgium for future projects. For example, for the implementation in Luxembourg. The PSD2 project was the first big project we used GitLab for and it went really well from development to production,” Pepinster said.\n\nGitLab is the foundation for communication, collaboration, and workflow efficiency at Keytrade Bank. As the project expands, GitLab will continue to be the hub for code management, version control, and continuous integration and deployment.",{"template":950,"size":44,"region":106,"industry":71},"content:en-us:customers:keytradebank.yml",{"_path":3985,"content":3986,"config":4030,"_id":4031},"/en-us/customers/kiwi",{"name":3987,"logo":3988,"hero":3989,"heroImage":3990,"benefits":3991,"industry":89,"employeeCount":3999,"location":4000,"solution":913,"stats":4001,"headline":4009,"summary":4010,"quotes":4011,"content":4017,"contributors":1281},"Kiwi","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745517993/vyykaqbedxxy73xuwoed.svg","How Kiwi.com transformed its workflow with GitLab and Docker","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518447/snwse6oa6hiixu5giwjc.jpg",[3992,3995,3997],{"metric":3993,"config":3994},"Increased operational efficiency",{"icon":1020},{"metric":1843,"config":3996},{"icon":950},{"metric":965,"config":3998},{"icon":2598},"2,000+","Brno, Czech Republic",[4002,4004,4007],{"value":978,"metric":4003},"Average builds per month",{"value":4005,"metric":4006},10,"Minute deploys",{"value":1308,"metric":4008},"Adoption rate","GitLab’s ease of integration allows Kiwi.com to use containers, manage collaboration, and boost deployment.","GitLab provides Kiwi.com with CI stability, ease of integration for containers, and source control management.\n",[4012],{"quoteText":4013,"author":4014,"authorTitle":4015,"authorCompany":4016},"I haven't seen any platform where it's as easy to use CI for automating everything as it is in GitLab.\n","Alex Viscreanu","Technical Team Lead","Kiwi.com",[4018,4021,4024,4027],{"header":4019,"text":4020},"Virtual Global Supercarrier","Kiwi.com is an online travel-tech company that offers travel itineraries to customers globally. Its proprietary algorithm - Virtual Interlining - allows users to combine flights and ground transportation from more than 800 carriers, including many that do not normally participate in offerings. All the connections are covered by the leader in the travel industry, Kiwi.com’s Guarantee, which protects the customers from missed connections caused by delay, schedule change, or cancellation.\n",{"header":4022,"text":4023},"Inadequate delivery system, CI, and source control","After [Kiwi.com](https://www.kiwi.com/us/) evolved from the startup phase, they started a plan to unify their systems. Firstly, there was no consistency between how different teams deployed their services, mainly because Docker wasn’t an essential part of the workflow. Secondly, the historical information of how that software was developed was in disparate silos and not documented properly.\n\nKiwi.com didn’t have continuous integration or delivery systems in place. “The release process was long and even rolling back wasn’t an easy task. Everything was done manually,” Alex Viscreanu, Technical Team Lead at Kiwi.com said. “There was no automation at all.”\n",{"header":4025,"text":4026},"Choosing a unified platform","The development team was initially working with different software platforms, but found that running shell commands wasn’t a good experience for them. Neither tool had proper support for containers, which was a priority. They tested GitLab and discovered that it offered the most well-integrated platform. “When we tried GitLab and we saw how well CI/CD was integrated with everything and that we could use CI/CD for automatically merging code, trusting our checks, and not worrying about all the things, it was like a no brainer,” Viscreanu said.\n",{"header":4028,"text":4029},"Integrating with Docker, Kubernetes, and Terraform for CI success","The first big issue that GitLab solved was the easy [integration with Docker](https://about.gitlab.com/blog/docker-in-docker-with-docker-19-dot-03/), allowing the team to leverage containers as the main way to package software. Previously, they hadn’t worked in containers, but with GitLab CI, they started using them everywhere. “Once we had that in place and we had an easy way to verify the code and automate the deployment, everything was so well integrated that we could trigger actions directly from GitLab” Viscreanu said. “Right now we have automated deployment, automated dependency maintenance, automated dependency scanning, automated dependency license scanning, automated everything.”\n\n With GitLab’s automation in place, Kiwi.com now averages:\n\n - 4,000 commits per day\n - 1,500 deployments per month\n - 47,000 tests per month\n - 5,000 MRs per month\n\n When containers became well established in the company, Kiwi.com went through different container platforms, most of which ended up limiting the scalability of their services. After dealing with those limitations, and creating workarounds to fit their use case, they didn’t want to invest more effort into products that weren’t going to be developed or be relevant any longer. Developers were looking for a solution that would consistently manage their resources and enable them to build tooling around it. The main reason for this, according to Viscreanu, is “Sanity. There is no way that you can keep track of all these tools when you are a big company if you don’t automate them and unify things.”\n\n GitLab’s integration with Kubernetes has made their work noticeably simpler, mainly because of how well integrated it is with the rest of the solution. [Viscreanu](https://www.youtube.com/watch?v=W1biIw0uM-4) and his team are also pushing a lot of infrastructure as code, using Terraform in GitLab CI. It allows them to deploy, create, modify, and lead infrastructure pieces without having to do it manually. “If it’s not in CI and it’s not in GitLab, then changes shouldn’t be done,” Viscreanu added.\n\n Keeping everything in CI means having a record of any modifications and provides a single source of truth. “At the beginning I think that CI/CD was the main feature and I think that even right now it’s still the most beloved feature for us. We’re using Git as the source of truth, which allows us to prevent having everything distributed and everything maintained by the teams themselves and then forgotten somehow,” Viscreanu said.\n\n Prior to GitLab, the deployment process was slow because there was no certainty that the code that was pushed was working. At that point, the only way to check the code was to deploy and learn after the fact. Now, despite the increase in services, employees, projects, microservices, and overall expansion of the company, the deployment is succinct with CI. Reaffirming their confidence in GitLab “Right now with CI, even if we don’t catch everything, we really trust it, at least for the critical paths. And with CD and approaches like rolling releases, even if the release has issues, we are able to react fast, before it affects all our customers,” Viscreanu said.\n",{"template":950,"size":44,"region":106,"industry":91},"content:en-us:customers:kiwi.yml",{"_path":4033,"content":4034,"config":4082,"_id":4083},"/en-us/customers/knowbe4",{"name":4035,"logo":4036,"hero":4037,"heroImage":4038,"benefits":4039,"industry":89,"employeeCount":4049,"location":4050,"solution":913,"stats":4051,"headline":4060,"summary":4061,"quotes":4062,"content":4069,"contributors":1281},"Knowbe4","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745517996/syj0scocuqi45yimagdx.svg","Security provider KnowBe4 keeps code in-house and speeds up deployment","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518447/vf5uzygilfxxfuojm1wb.jpg",[4040,4043,4046],{"metric":4041,"config":4042},"Easy integration",{"icon":2105},{"metric":4044,"config":4045},"Consolidating tools saves costs",{"icon":1477},{"metric":4047,"config":4048},"Standardized platform",{"icon":1852},"850","Clearwater, FL",[4052,4055,4058],{"value":4053,"metric":4054},"5+","Production deploys per day for any given application",{"value":4056,"metric":4057},"20+","Development environment deploys per day",{"value":1308,"metric":4059},"AWS self-managed GitLab","KnowBe4 integrated GitLab to help with the company’s trajectory towards growth, scalability, and success","KnowBe4 removes its multi-toolchain and goes “all in” with GitLab for increased deployment speed\n",[4063,4067],{"quoteText":4064,"author":4065,"authorTitle":4066,"authorCompany":4035},"There's literally no other solution that does everything that GitLab does.\n","Alex Callihan","VP of platform engineering",{"quoteText":4068,"author":4065,"authorTitle":4066,"authorCompany":4035},"The GitLab migration in general is one of our largest successes. Of the primary implementations that Site Reliability Engineering has brought to engineering at KnowBe4, the choice to move the department to GitLab ranks up there as one of the best.\n",[4070,4073,4076,4079],{"header":4071,"text":4072},"Standout software security training company","KnowBe4, Inc. is the provider of the world’s largest security awareness training and simulated phishing platform. [KnowBe4](https://www.knowbe4.com/) helps manage the ongoing problems of social engineering with on-demand, interactive training for tens of thousands of organizations worldwide. It was ranked highest in ‘Ability to Execute’ and ‘Completeness of Vision’ on the 2019 Gartner Magic Quadrant for Security Awareness CBT.\n",{"header":4074,"text":4075},"Toolchain complexity caused delays in innovation and releases","Members of KnowBe4’s engineering team were using three separate tools in their deployment toolchain. One for code management, another for code testing, and a third for code deployment. With three solutions in use, all of their work was spread out in different places. While each tool had its own value set, the lack of integration among them caused additional work and stress for users. “Deploys would go off and trigger jobs in multiple different tools. Tests would trigger in one location, the deployments in another. Context switching was constant, and due to everything running concurrently, you never achieved the correct continuous pipeline,” says Alex Callihan, VP of Platform Engineering at KnowBe4. “Tests had the potential to fail after a deploy already succeeded. This was a problem. With GitLab, we were able to consolidate this process into a single tool and ensure the pipeline was executed in order.”\n\nThe team also was looking to reduce the costs associated with operating three platforms per toolchain. With their code testing tool, each concurrent test capacity incurred an additional cost, so teams couldn’t scale as much as they wanted without considering the financial burden that comes with adding capacity. “With our old code testing tool, we had to provision to our maximum. So if we ever needed to run 50 concurrent tests, we were forced to pay for 50 all day, every day. Our cost was approximately $50 per concurrent test per month for 50 concurrent tests, even though outside of our core business hours the tests were rarely needed to that magnitude,” says Matthew Duren, Principal Site Reliability Engineer.\n\nKnowBe4 was looking to consolidate to one tool that could provide end-to-end visibility. If the team no longer had to to spend time context switching between various tools, deployment speed could soar automatically. Other priorities for a new toolset included being able to:\n\n* Be self-managed\n* Reside in AWS\n* Integrate with Jira, Docker, and other tools as needed\n* Scale their Git solution in tandem with their employee and service growth\n",{"header":4077,"text":4078},"Success even before the POC ended","Duren and Callihan had previously used GitLab’s free version. Their experience and understanding of the platform was a driving factor in bringing GitLab to stakeholders.\n\nThe pair was eager for the rest of the company to understand the scope of the platform’s capabilities. In order to do that, they chose to do a proof of concept with a single product from their project list. The team was obligated to deliver the product in one month. “We happened to pick one product that we had to ship in a month. We shipped it on GitLab while we were still in the trial period,” Callihan said.\n\nFor stakeholders, an important aspect was ensuring security by keeping code in-house, which GitLab enabled them to do. “As our company has grown, being compliant across multiple standards has been a key goal of our development and infosec teams. GitLab’s tooling for security and ability to host within our own infrastructure was a big selling point to get approval for the POC.” Callihan says.\n",{"header":4080,"text":4081},"Operational efficiency, built-in security, and increased deployments","GitLab is at the heart of KnowBe4’s software development lifecycle. A developer will first open a feature branch off of master in GitLab. From there, they can deploy an on-demand development environment leveraging GitLab pipelines. When the development environment is determined verified working by QA, the developer opens a merge request to master. All commits then run test pipelines until that merge request is approved and ultimately merged. After merge, a pipeline is started to build and release the Docker image to AWS. After the release, a deployment stage kicks off [leveraging Terraform](/topics/gitops/gitlab-enables-infrastructure-as-code/){data-ga-name=\"terraform\" data-ga-location=\"body\"} to roll-in the latest image into production. All of this is orchestrated by GitLab runners deployed in AWS with full logging and visibility. Production now deploys five or more times per day for any given application. Development environments deploy 20 or more times per day for any given application. Hundreds to thousands of test jobs run every day across all applications.\n\nThe teams have standardized the development lifecycle for more than 60 microservices. “Due to that standardization, the simplicity of starting new projects or troubleshooting existing ones is incredibly easy. We all know how projects will build, release, and ship regardless of codebase or design,” Callihan says. “With a healthy mix of Docker, Terraform, and GitLab in GitLab pipelines, we’ve got a system in place that is super efficient.” They’ve also lowered time to production by allowing multiple concurrent test pipelines and with deploying and auto-scaling their own runners.\n\nGitLab’s continuous integration helps prevent bugs before code hits production. Security modules are built into the test pipelines and count as failed tests, which then cancel pipelines, protecting against deploying any vulnerable code.\n\nSince KnowBe4 already had a modern architecture in place, GitLab was able to help the company ship faster and solve unique use cases. All the teams now collaborate within the same tooling whether for code reviews, pipelining, or code ownership. The adoption was straightforward, given the simplicity of the tool and GitLab YMLs were fully embraced by all teams.\n\n“Moving test, build, and deployment tooling into the application repositories themselves has given developers the opportunity to build and manage their own deployment pipelines, reducing the responsibility of the SRE team to simply review and approve the developers’ changes,” Duren says. “By making this relatively straightforward adjustment, we are able to deploy changes much more frequently than we otherwise would have been able to do. We removed a huge bottleneck, which sped up our development lifecycle and improved continuity between our team and the rest of R and D.”\n",{"template":950,"size":40,"region":102,"industry":91},"content:en-us:customers:knowbe4.yml",{"_path":4085,"content":4086,"config":4128,"_id":4129},"/en-us/customers/lely",{"name":4087,"logo":4088,"hero":4089,"heroImage":4090,"benefits":4091,"industry":89,"employeeCount":1743,"location":1305,"solution":975,"stats":4100,"headline":4108,"summary":4109,"quotes":4110,"content":4115,"contributors":1281},"Lely","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745517997/rvzohvpkeri3vom8c9ub.svg","How Lely replaced three tools with GitLab to maximize efficiency","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518448/neqpzayibtec67obdr9i.jpg",[4092,4095,4098],{"metric":4093,"config":4094},"Fewer tools to maintain",{"icon":1738},{"metric":4096,"config":4097},"Easy adoption",{"icon":2598},{"metric":1293,"config":4099},{"icon":1895},[4101,4103,4106],{"value":4102,"metric":3956},"3",{"value":4104,"metric":4105},"171","groups using GitLab",{"value":4107,"metric":1312},"1,278","Lely, a Dutch robotics manufacturer specializing in dairy farm automation, uses GitLab for better collaboration and less toolchain maintenance.","Lely adopted GitLab for improved collaboration with built-in code reviews and continuous integration.\n",[4111],{"quoteText":4112,"author":4113,"authorTitle":4114,"authorCompany":4087},"For a software engineer, everything is there, so the developers feel more empowered. All their work information is in one overview.\n","Kees Valkhof","Configuration Manager",[4116,4119,4122,4125],{"header":4117,"text":4118},"An innovator in agricultural robotics","Since 1948, Lely has been an international family business in the agricultural sector. [Lely](https://www.lely.com/us/about-lely/){data-ga-name=\"lely\" data-ga-location=\"body\"} specializes in robotic equipment and innovative solutions for dairy farmers in more than 45 countries. The company offers dairy automation to make farmers’ lives easier and help farms operate more efficiently. Lely’s services include robots that milk and feed, and stable cleaners that can operate independently. Lely’s inventions and automated systems produce healthier and more sustainable farms.\n",{"header":4120,"text":4121},"Adopt Git and do more with fewer tools","The development team at Lely was using Subversion (SVN) for [version control](/topics/version-control/){data-ga-name=\"version control\" data-ga-location=\"customers content\"}. However, the team was looking to move to Git because it is “easier to use Git correctly,” according to Kees Valkhof, configuration manager at Lely. The SVN repository was messy and lacked transparency, which created confusion around where data was stored.\n\nThe development team had to manually write scripts to ensure that reviews worked correctly and in order for engineers to do merge requests correctly in SVN. Developers were also using Review Board for code reviews, which required maintenance in order to continually integrate it with SVN. Having to open up a separate tool to perform code reviews meant that sometimes new code was getting deployed without ever being properly reviewed. With developers using multiple tools, there was little visibility into the status of projects. The maintenance and integration required to keep the developers up and running was taking up too much time and slowed throughput.\n\nLely developers were looking for a modern solution to replace their legacy tooling, including their homegrown SVN server, TeamCity, and Review Boards. Ideally, the solution would be an integrated, automated, singular platform that the developers could adopt quickly. The development team wanted to continue to innovate and consolidate the toolchain to become more productive. “We want to use as few tools as possible, and we want to stay on the same tool that everyone can use,” Valkhof said.\n\nBy replacing these older tools, the Lely team hoped they could continue to innovate internally, just as they innovate for their clients. The team had three requirements for any new tools:\n\n  1. **A Git workflow**: With SVN being outdated and unable to do what teams needed, Git adoption would be a top priority.\n\n  2. **Simple, all-in-one solution**: To reduce maintenance, teams wanted one solution that could do multiple tasks and integrate with Grafana dashboards.\n\n  3. **Easy adoption**: The tool(s) would need to be intuitive with a low barrier to entry for all team members to adopt quickly and efficiently.\n",{"header":4123,"text":4124},"Developers collaborating in one tool","A Lely development team working in the Czech Republic had installed GitLab via open source and was using it internally. GitLab received very positive feedback from the Czech team’s experience. Valkhof and his team reviewed GitLab and decided to purchase Premium in order to roll it out to the rest of the development team. “If you already have a working system, then I don’t have to figure out how it works,” Valkhof said.\n\n[GitLab’s built-in continuous integration](/solutions/continuous-integration/){data-ga-name=\"continuous integration\" data-ga-location=\"customers content\"} and code reviews gave developers greater visibility. “What I liked in GitLab when I started using it is the build system is integrated and the review system is integrated,” Valkhof said. “We don’t have to log with a whole other system.”\n\nGitLab’s complete DevOps platform, delivered as a single application, means developers spend less time managing tools and won’t have to cobble together Python code just to visualize data. With the Grafana dashboard and GitLab integration, teams know exactly what’s in the workflow process.\n",{"header":4126,"text":4127},"A unified DevOps workflow with less maintenance","Lely’s operations team is now managing fewer tools. “My maintenance became easy because I had to maintain fewer servers. And I didn’t have to maintain the connections,” Valkhof said. GitLab helps support collaboration within Lely services and between management and development. “[Collaboration] is better than what we had with Subversion. Now it’s much easier to review changes because the button to click and the information that we have is for an entire process or standard boards,” Valkhof said. “We can involve the managers with our process that we defined ourselves.”\n\nGitLab’s overview pages show test schedules, confidence results, and competency fields. This gives developers the visibility into the status of a project and, moreover, how if that project status directly impacts their workflow. “Before that, we never had good insights into the impact. The overview page of the emergent list contains usual information and we didn’t have that. So it’s basically a dashboard full of useful information for the developer, which is helpful,” Valkhof added.\n\nGitLab’s single application makes it easier to onboard new developers because Valkhof doesn’t have to train them on multiple tools. GitLab is designed to be very intuitive, so onboarding happens a lot faster. “They almost immediately know how to use it. And the few that don’t, I can help in just minutes,” Valkhof added. GitLab helped the team move to Git, adopt better practices around code review and testing, and empowered developers. “GitLab has allowed us to do more complex projects while simplifying how we visualize and track progress,” Valkhof said.\n",{"template":950,"size":40,"region":106,"industry":91},"content:en-us:customers:lely.yml",{"_path":4131,"content":4132,"config":4193,"_id":4194},"/en-us/customers/lockheed-martin",{"name":4133,"logo":3442,"hero":3443,"heroImage":4134,"benefits":4135,"industry":4145,"employeeCount":4146,"location":4147,"solution":913,"stats":4148,"headline":4157,"summary":4158,"quotes":4159,"content":4164},"Lockheed Martin","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518422/c4xcs1xhskaw0flb1s6f.jpg",[4136,4139,4142],{"metric":4137,"config":4138},"Easy adoption experience",{"icon":902},{"metric":4140,"config":4141},"Simplified toolchains",{"icon":1852},{"metric":4143,"config":4144},"Streamlined software sharing",{"icon":1295},"Defense and Aerospace Manufacturing","114,000","Bethesda, Maryland, U.S.",[4149,4152,4155],{"value":4150,"metric":4151},"80x","faster CI pipeline builds",{"value":4153,"metric":4154},"1,000s","of Jenkins servers retired",{"value":1402,"metric":4156},"less time spent on system maintenance","The world’s largest defense contractor uses GitLab’s end-to-end DevSecOps platform to shrink toolchains, speed production, and improve security.","[Lockheed Martin Corp.](https://www.lockheedmartin.com/), an American aerospace, defense, information security, and technology giant, has adopted GitLab’s single, end-to-end DevSecOps platform to more efficiently, securely, and quickly develop and deploy software for thousands of their programs, ranging from satellite platforms and aerospace systems to ground control software and maritime surface and subsurface software.\n",[4160],{"quoteText":4161,"author":4162,"authorTitle":4163,"authorCompany":4133},"By switching to GitLab and automating deployment, teams have moved from monthly or weekly deliveries to daily or multiple daily deliveries.\"\n","Alan Hohn","Director of Software Strategy",[4165,4168,4172,4175,4178,4181,4184,4187,4190],{"header":4166,"text":4167},"Achieving mission needs with speed and flexibility","Based in Bethesda, Maryland, Lockheed Martin has approximately 116,000 employees worldwide, with more than 370 facilities. The company is principally engaged in the research, design, development, manufacture, integration, and sustainment of advanced technology systems, products, and services. The majority of the company's business is with the U.S. Department of Defense and U.S. federal government agencies. In the aeronautics industry alone, Lockheed Martin had $26.7 billion in sales in 2021.\n\nLockheed Martin’s customers depend on the company to help them overcome their most complex challenges and to stay ahead of emerging threats by providing the most technologically advanced solutions. Their engineering teams need speed and flexibility to meet the specific mission needs of each customer, while using shared expertise and infrastructure to ensure affordability.\n",{"title":4169,"config":4170},"AWS re:Invent 2023 - Lockheed Martin case study",{"url":4171},"https://www.youtube.com/embed/Q1OSyxYkl5w?si=z1vqIWgXC7JobF2x",{"header":4173,"text":4174},"Toolchain complexity","Lockheed Martin has a history of using a wide variety of DevOps tools — everything from ClearCase to Jenkins, Dimensions, Redmine, and Bitbucket. Each program or product line at the company had its own toolchain. Rarely was one like another, with team members simply picking tools they were familiar with.\n\nThat led to uneven efficiencies and results.\n\nAlan Hohn, director of software strategy at Lockheed Martin, said the quality of a team’s development and deployment environment often was based on how lucky the DevOps team happened to be. Well-funded programs, or those with forward-leaning leadership, might have had high-quality automation for everything from testing to continuous deployments, while other programs might only have had a build server to run compiles. And in the worst cases, programs might not have had any automation at all, creating more hands-on work, using team members’ time, and increasing the chance of missed problems.\n",{"header":4176,"text":4177},"Increasing collaboration","To add to the challenge, software development teams at Lockheed Martin had made numerous attempts to set up code repositories that would allow developers to reuse code across programs — but these repos were rarely, if ever, used because they were never incorporated into the multitude of environments where teams were actually developing the software. That meant developers, without a solid collaboration environment, were always starting from scratch and the code in the repositories simply “sat and rotted,” says Hohn.\n\nOnce Lockheed Martin widely adopted GitLab’s platform, software sharing and reuse easily became part of their day-to-day operations.\n\n“Having GitLab has completely changed the way we approach reusable software because the place where we develop software is also the place that other people can share, contribute, and participate in that development,” says Hohn. “Now, all of our programs have access to a high-quality software development environment.”\n\nThis development environment translates directly to benefits for Lockheed Martin’s customers. One team working on a program for the U.S. Department of Defense was able to reduce build times from 12 hours to 4 hours through the use of GitLab pipelines with containerized builds. This enabled the program to run 16 builds per night, rather than four, increasing test frequency and software quality. Overall, build success went from 60% to 90%. As a result, the customer is receiving new capabilities sooner and with better quality.\n",{"header":4179,"text":4180},"Creating continuity","One of the most significant challenges Lockheed Martin faced in driving collaboration between programs and across the entire business is that their software resided in many different systems, with differing security requirements. GitLab, together with Lockheed Martin’s Software Factory, enables the company to modularize their software so reusable components can be shared in globally accessible environments, while teams can still maintain tight control over software components that are mission-critical or have security constraints.\n\nA key feature of Lockheed Martin’s Software Factory is that it provides a common GitLab CI configuration YAML and common CI container images that are pre-configured to work with their other software development tools.\n\nTeams have to maintain separate environments for security reasons, so their configuration needs to be able to work in different hosting environments for image registries and associated tools. They also often need to sustain particular versions of their software for years, since sometimes it’s deployed into operational environments where it can’t be frequently updated.\n\nTo take on these challenges, Hohn’s team created a catalog of common pipelines for popular programming languages with modules for security scanning, container image builds, and semantic versioning. The pipeline catalog allows developers to use the same YAML source file in multiple environments without having to make modifications. The catalog also makes it possible to create a historic build using a specific version of a pipeline and guarantees version consistency.\n\nBefore adopting GitLab, Lockheed Martin had made a few attempts to build a common set of pipelines, but they ended up only supporting a few users and were overly prescriptive. It wasn’t enough.\n\nWith GitLab as the foundation for their pipeline catalog, Lockheed Martin has been able to create pipeline templates that can be reused in multiple environments, including disconnected networks. That saves time and effort, and ensures continuity among projects. Now, pipeline updates are simpler, and sophisticated testing and release management are easier and more efficient.\n\n“Now, we can be confident changes to our pipelines are automatically and thoroughly tested, and we can easily support both fast-moving development teams and risk-averse teams that are maintaining mission-critical capabilities,” says Hohn. “Our new approach, built on some key GitLab CI features, has helped us find the right balance of commonality and customization.”\n\nLockheed Martin now serves 2,500 pipelines per minute through the common pipeline catalog.\n",{"header":4182,"text":4183},"Delivering scale","Because rapid adoption of GitLab created the need for a more scalable solution, Lockheed Martin, GitLab, and Amazon Web Services (AWS) worked together to automate and optimize Lockheed Martin's code deployment across the enterprise. The solution started with a well-architected review of the design between the three companies. AWS then helped to automate and optimize the Lockheed Martin GitLab deployment for the CI/CD environment by delivering Infrastructure as Code (IaC) to deploy the environment in two hours, instead of the several hours it had taken previously.\n\nThe AWS team also established workflows to deliver a fully automated, highly available Disaster Recovery architecture for GitLab that is compliant and scalable. This enabled a consistent process that runs without manual intervention. AWS also supported load balancing to auto-scale the deployment process based on developer demand for pipeline runs and user traffic so developers are not waiting on deployments to execute. Pre-migration testing was performed to establish baselines, followed by post-migration testing to measure performance and scalability gains in delivering faster deployments.\n\nAdditionally, monitoring and security controls were implemented to comply with Lockheed Martin’s security policies. As a result, the team was able to deliver operational efficiencies with the number of build requests waiting to be processed dropping from 200 to zero, and reducing time for code deployment across the enterprise. This effort showcased how large enterprises with thousands of software developers can build and deploy automated, scalable, and resilient code pipelines in the cloud using platforms such as GitLab by leveraging AWS best practices.\n",{"header":4185,"text":4186},"Going with GitLab","Lockheed Martin didn’t need to do a formal evaluation of GitLab’s platform before deciding to go with it. The company’s DevOps teams have, over the years, used a multitude of tools on the market, so they understood the capabilities and benefits they would get from GitLab. For instance, GitLab’s built-in continuous integration capability was a “killer feature,” according to Hohn.\n\nAnd the company has gone in big with GitLab. Today, they have approximately 64,000 projects on the GitLab Platform — some legacy projects have been migrated to GitLab, and others were initiated on the platform.\n\nLockheed Martin hasn’t rid itself of all of its toolchains but the company has greatly reduced them, cutting complexity, cost, and workload.\n\n“We recognize that there are going to be programs where the customer wants to own the development environment and they want a specific tool,” explains Hohn. “We want to get to the point, and what we’re achieving, is people don't even consider standing up their own toolchain. They just use GitLab because they know that it works.\n\n“Have we erased all traces [of toolchains]? No,” adds Hohn. “But it’s so small it’s not significant to us.”\n\nFor instance, before widely adopting GitLab, the company was using Jenkins for CI servers – thousands of instances of Jenkins across the organization. That’s no longer the case.\n\n“Everybody had to maintain a different installation. We’ve collapsed that down to mostly GitLab,” says Hohn. “There are still Jenkins instances out there but they’re a small fraction of the number there were three years ago.”\n",{"header":4188,"text":4189},"Saving time and effort","Those reduced toolchains are saving the company time, muscle, and money, so that it can continue to innovate and deliver affordable solutions to their customers.\n\n“For teams that had independent environments, they had to dedicate about 20 hours a week and 80 hours a month just to keep the system running,” says Hohn. “On a team of 12 people, that’s dedicating at least half a person. We reduced that by something like 90%. They’re now spending a couple of hours of a person’s time. That’s multiplied across a lot of teams. As a corporation with more than 10,000 software engineers, we can say we’re saving hundreds or thousands of hours a year.”\n\nHaving all of those projects on GitLab’s single platform means legacy programs that might have previously, on average, delivered to testing monthly and to operations quarterly, now are delivering to testing every six days and to operations every 26 days, Hohn notes.\n\n“It's very typical that we're seeing monthly deliveries turn into weekly,” he adds. “We're seeing quarterly deliveries turn into monthly. I mean, that scale of changes is very common.”\n\nThat time savings means the company can respond to customer requests more confidently and reliably.\n\n“We serve a lot of customers and we have a lot of software development activities,” says Ian Dunbar-Hall, senior software engineer at Lockheed Martin. “GitLab allows a team to go from zero to a repository and a full CI pipeline, totally self-service, in 30 minutes, rather than the 40 hours, minimum, that it used to take.”\n",{"header":4191,"text":4192},"Improving security","Since Lockheed Martin works with the Department of Defense and federal agencies, the company builds systems that are critical to national security. That means creating secure software is integral to both Lockheed Martin and its customers. A challenge for any company using toolchains is that it’s easy to miss an update because of the sheer size and complexity of the chain. Now with GitLab, they don’t have to worry about using tools that haven’t been updated because with a single, end-to-end platform, an update only has to be done once and every instance is covered.\n\nAnd with defense and security-focused customers, compliance is a critical issue for Lockheed Martin. That’s easier to manage now that the company uses GitLab's compliance framework to enforce software quality, and automation to make releases and dependency management more efficient and faster.\n\nUsing a single platform also means teams are getting a standardized set of automated security capabilities — from cutting-edge analysis tools to vulnerability scanning and security automation — seamlessly built in. Before using GitLab, teams didn’t all have the best security tools and there was no standardized way of handling security practices. Now with Lockheed Martin’s common pipeline catalog, teams also are using off-the-shelf pipelines that already have best-in-class security built in. “Now that we have a more common approach, it's much easier for teams to leverage a common way of doing software build, test, and security scans, which raises the level of quality of the products that we create,” says Hohn.\n\nAnd with GitLab, teams no longer need security experts, who could be difficult for every team to find, to configure various tools. Best-in-class security already is built in, according to Hohn.\n\n“Today, it is extremely common to have sophisticated security scanning capabilities as part of all of our pipelines because the effort involved to add that to the pipelines is so much smaller,” says Hohn. “Teams now are aware of the security posture of the code they're writing in a way that they weren't before. That enables conversations about the security of our software that were not taking place the old way.”\n\nThe company is still using some third-party, legacy security tools, but teams are using GitLab’s platform to make it easier to integrate them all. “It’s a great complement,” says Jeff Daniels, Director Automations and Applications. “It's easier now that we have GitLab, which increases our security posture and quality.”\n\nLockheed Martin is looking to continue to grow with GitLab. DevOps teams will migrate even more of their projects over to the DevSecOps platform and expand from there. “We hope to see growth in the number of projects using security and software supply chain functionality, including compliance pipelines and dashboards,” says Hohn.\n",{"template":950,"size":44,"region":102,"industry":79},"content:en-us:customers:lockheed-martin.yml",{"_path":4196,"content":4197,"config":4244,"_id":4245},"/en-us/customers/mckenzie-intelligence-services",{"name":4198,"logo":4199,"hero":3290,"heroImage":4200,"benefits":4201,"industry":4210,"employeeCount":4211,"location":4212,"solution":975,"stats":4213,"headline":4220,"summary":4221,"quotes":4222,"content":4226},"McKenzie Intelligence Services","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745517946/kcowf6555k1iq65yszso.png","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518423/qfcsjrdc3khwcwpzea56.png",[4202,4204,4207],{"metric":969,"config":4203},{"icon":902},{"metric":4205,"config":4206},"No tool integration time",{"icon":1852},{"metric":4208,"config":4209},"Improved productivity",{"icon":1385},"Technology consulting","35","London, UK",[4214,4216,4218],{"value":2666,"metric":4215},"of technology budget saved",{"value":2666,"metric":4217},"increase in MR speed",{"value":1857,"metric":4219},"decrease in deployment time","McKenzie Intelligence Services (MIS) collects and analyzes critical data to help global insurance companies accelerate economic recovery after both natural and man-made disasters.","Focused on providing post-event intelligence, the company helps get aid to people and businesses when they need it most. By adopting GitLab’s end-to-end DevSecOps platform in 2018, MIS has dramatically cut the time it takes to get critical information to insurers — enabling them to accelerate payouts to people in crisis, while protecting sensitive data.",[4223],{"quoteText":4224,"author":4225,"authorTitle":2850,"authorCompany":4198},"Our insurance company customers need to respond to disaster victims as fast as possible. With our GEO platform, which we built with GitLab, they have the data they need to help people in days, instead of months or even years.","Andre Nita",[4227,4229,4232,4235,4238,4241],{"text":4228},"Founded in London in 2011, [McKenzie Intelligence Services](https://mckenzieintelligence.com/) has 27 employees. The company’s NATO- and military-trained analysts provide detailed evaluations of hurricanes, wildfires, tornadoes, earthquakes and other catastrophic events, monitoring situations from as far afield as Ukraine to Yemen.\n\nUsing its Global Events Observer (GEO) platform, built with [GitLab’s DevSecOps platform](https://about.gitlab.com/free-trial/devsecops/), the company conducts risk and damage assessments worldwide. With GEO, MIS formulates insights into potential risks and offers data-driven recommendations that help insurers expedite claims processing and disaster response efforts. GEO’s capabilities extend beyond natural disasters — government agencies and multi-national corporations also rely on GEO to assess evolving geopolitical situations.",{"header":4230,"text":4231},"GEO with GitLab: A secure platform for disaster intelligence","GEO is the heart of MIS. Covering the globe, it maps all natural and man-made catastrophes. The platform can obtain, and study, images from the entire path of a hurricane, for instance, down to the damage done to an individual house. The organization’s intelligence analysts use GEO, and the data — such as aerial and satellite imagery — it brings in and stores, to plot risk before a storm rolls through, study wind speeds, fire damage and storm surges during the storm, and then assess the damage after.\n\nThe system handles between 100 gigabytes and one terabyte of data per catastrophe, while holding tens of hundreds of terabytes of data total. Given the sensitive nature of this information and its global reach, their system must meet rigorous security standards and comply with various regulations across multiple countries. MIS can meet both of those critical needs because GEO was built, and is continually updated, with GitLab.\n\n“It’s our only product, so it is definitely critical to the company,” says Andrei Nita, chief technology officer of McKenzie Intelligence Services. “The majority of our revenue comes from GEO so it has to be a really well-run, efficient, and secure product. That’s why we use GitLab.”\n\nThe system was built top to bottom with the DevSecOps platform, using GitLab’s CI/CD pipelines, automated security features, and the GitLab Docker registry and containers. They also store their entire code base in GitLab.",{"header":4233,"text":4234},"Accelerating economic recovery to natural disaster victims","With the strength of GEO, the organization is able to gather, analyze, and then feed that information to major insurance companies around the world at top speed. That means those insurers can then take care of their customers faster, easing disaster victims’ suffering.\n\nFor example, MIS used GitLab to create scripts that automate collecting disaster data to populate their GEO ecosystem. Instead of manually searching for data about the exact path of a tornado, GEO can automatically grab and organize that data, saving analysts a significant amount of time and effort. The scripts also enable them to pinpoint data collection geographically, giving specific customers exacting information and filtering out anything they don’t need.\n\nNita notes that previously it took months, sometimes even years, for an insurance company to get the information it needed to make individual claim payouts, which enable people to rebuild their homes, and rebuild their lives.\n\n“But with observed data from GEO, we can get the insurers the information — actionable and trusted information — they need in 24 to 72 hours after the event,” he says. “Our insurance clients need to respond to disaster victims as fast as possible. With GEO, they have the data they need to help people in days, instead of months or even years. That makes a difference in people’s lives. They need help right away. Say there’s a flood, they might no longer have a home to go back to. They need their insurance company to be able to help them.”\n\nNita adds that delivering needed data and insights within three days is a major selling point for MIS’s service. The ability to provide imagery and one-by-one kilometer grids with detailed assessments and damage ratings is critical to their overall business success.",{"header":4236,"text":4237},"Cutting an inefficient toolchain, speeding releases","This dramatic acceleration in disaster response didn't just benefit MIS clients — it also transformed how their own teams work. Before adopting GitLab, MIS had used an inefficient mix of five different DevOps tools that caused difficult onboarding, fragmented workflows, the need for a variety of support teams, slow deployment processes, and problems maintaining collaboration across distributed teams. By [eliminating that toolchain](https://about.gitlab.com/blog/battling-toolchain-technical-debt/) with a single, end-to-end platform, the organization has not only made their team’s jobs easier, they’ve also been able to launch releases every two weeks, instead of quarterly or even less frequently. And it enables them to more easily meet client requests, particularly those that are stipulated as part of their contracts.\n\n“With the toolchain we had before, I think a lot of people were kind of confused about where things were being done and if projects were ready. It affected our delivery schedule,” says Nita. “It resulted in very little value being created with the technology. That meant we were slow to respond to customer requests. It was a drag on the company. That’s no longer a problem.”\n\nCutting that toolchain and working on a single platform is even [more important for a small business](https://about.gitlab.com/blog/five-essential-business-benefits-a-devops-platform-gives-smbs/) trying to get a lot of work done with fewer hands. “That’s 100% true,” adds Nita. “The problem was that a majority of a developer’s time had been spent on integrating and connecting one disparate tool to the other. And if there was a problem, finding out which tool was causing it. With a single platform, though, everything is already connected and integrated by design. Our development team is only seven people — that’s 20% of our company. We’re a small team with a small budget. We need an advantage that enables us to function as a much bigger team.”\n\nTo speed and ease those deployments even more, Nita says they will consider adopting [GitLab Duo](https://about.gitlab.com/gitlab-duo/), a suite of AI-powered features that assist across the entire software development lifecycle.",{"header":4239,"text":4240},"Collaborating across teams with a single platform","For MIS, the ability to collaborate quickly and effectively is crucial when monitoring disasters and delivering critical data to insurers. Before adopting a single application, even their small team struggled to work cohesively — the mix of tools created barriers between analysts tracking storm damage, developers building data collection tools, and teams working directly with insurance companies.\n\nNow using a unified platform, the organization has seen a dramatic [increase in collaboration](https://about.gitlab.com/blog/5-ways-collaboration-boosts-productivity-and-your-career/) that directly impacts their disaster response capabilities. This includes not only work between DevSecOps team members, but also between developers and other teams, like those in product, customer support, and client solutions, who sometimes write their own simple scripts or SQL queries in GitLab. Together, they now can all rapidly implement changes that help get aid to people faster.\n\n“Sometimes they start writing some scripts, but then they get stuck. Because they’re all on the same platform, they can easily tag someone to help them,” says Nita. “The engineers can just jump in, see the latest commit or merge request, and get them squared away. That kind of cross collaboration saves everyone so much time and, ultimately, makes everything seamless.”",{"header":4242,"text":4243},"Easing compliance and increasing security","Using a unified platform also makes it easier and faster to make their software secure, according to Nita. Being able to take advantage of  automated security features, like static application security testing (SAST), dependency scanning, secret detection, and vulnerability reporting within merge requests, was one of the reasons he has been so happy using GitLab. “Having those automated tools built in has so much value for us,” he adds.\n\nAnd that value extends into their [regulatory needs](https://about.gitlab.com/blog/meet-regulatory-standards-with-gitlab/).\n\nBecause of GitLab’s automated security features, along with standardization and documentation tools, MIS is more easily able to remain compliant, while working with major insurance companies based around the world — with many requiring different standards specific to individual countries. The company has to manage potentially hundreds of different laws and regulations.\n\n“We have very strict regulations to meet,” says Nita. “The ecosystem that we need to operate in must be very secure. But when we tell companies that we use GitLab — with its CI/CD, its registry, its security and documentation tools — we don’t get any follow-up questions about our compliance abilities, which is helpful because generally it takes ages to get signoff from major enterprises.\n\n“We had a client recently who said it generally takes them several months to close the regulatory process, but we managed to close it within a few weeks,” he adds. “That’s key. That affects our business.”\n\nGitLab's single DevSecOps platform has revolutionized McKenzie Intelligence Services' operations by delivering the critical trifecta of speed, security, and compliance. The platform's automated security features, standardization tools, and streamlined workflows not only enable the company’s small development team to transform three-month release cycles into rapid two-week deployments, but to also ensure software security, and seamless compliance with global regulations. This technological foundation allows MIS to focus on their expertise — helping insurance companies worldwide accelerate disaster recovery efforts.",{"template":950,"size":36,"region":106,"industry":91},"content:en-us:customers:mckenzie-intelligence-services.yml",{"_path":4247,"content":4248,"config":4291,"_id":4292},"/en-us/customers/moneyfarm",{"name":3600,"logo":4249,"hero":3601,"heroImage":4250,"benefits":4251,"industry":4262,"employeeCount":4263,"location":4264,"solution":975,"stats":4265,"headline":4271,"summary":4272,"quotes":4273,"content":4278},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1745517947/jqrjskjsuyp5izp0xjxj.png","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518423/sa7fnkqefjajro2qgdsl.jpg",[4252,4256,4260],{"metric":4253,"config":4254},"Tighter feedback loops",{"icon":4255},"Release",{"metric":4257,"config":4258},"Faster pipelines",{"icon":4259},"GitlabPipelineAlt",{"metric":1293,"config":4261},{"icon":1295},"Finance","130","UK and Italy",[4266,4268],{"value":1807,"metric":4267},"faster CI/CD pipelines",{"value":4269,"metric":4270},"2x","more deployments","Moneyfarm wanted to help its small team be as efficient as possible, but its existing continuous delivery solution was cumbersome to manage.","With GitLab, the online wealth management firm now has happier developers — and those happier developers are producing more code and deploying more value to customers.\n",[4274],{"quoteText":4275,"author":4276,"authorTitle":4277,"authorCompany":3600},"It's easy to underestimate the developer's feelings about the tool. Developers like using GitLab. They didn't like what we were using before. That helps us all over the different metrics we have.\n","Nicholas Faulkner","Director of Engineering",[4279,4282,4285,4288],{"header":4280,"text":4281},"A European online financial management platform","Moneyfarm is an online wealth management company with offices in the United Kingdom and Italy. “We are a digital wealth manager, and of course, our mission is to make sure that people can build and manage their wealth in a hassle free way and get advice from experts like us,” explained Emanuele Blanco, CTO of Moneyfarm. Blanco’s team wants to support flawless customer service and believes continuous delivery is the way to achieve it. “We want to use and strengthen our continuous delivery capability. We believe in delivering small chunks of value, in releasing incremental software.”\n\nBut [Moneyfarm](https://www.moneyfarm.com/) doesn’t have a huge team and wants to be as efficient as possible, all the while supporting offices in two countries and making the most out of its continuous delivery philosophy. “To do all of that, we need to have a tech organization coupled with a process and a platform that allows us to do what we need to do,” Blanco said.\n",{"header":4283,"text":4284},"Too much babysitting","Moneyfarm had an existing continuous delivery platform, Concourse CD, and everything was running on Amazon Web Services (AWS). The Concourse solution worked, but required a tremendous amount of time and attention to keep it up and running. Almost as frustrating, “it was costing us quite a lot of money in terms of our AWS bill,” according to Nicholas Faulkner, director of engineering. Concourse was self-hosted but Faulkner says it was “very temperamental. It took people full time to manage it and we weren’t interested in investing (that much time) into it.”\n\nThe complex nature of Moneyfarm’s CD platform also created another issue: There was no possibility of self-service. Stakeholders started to treat the platform team like they were outsourced service providers, a situation that simply wasn’t going to work over the long haul.\n\nAnd, finally, Moneyfarm just needed to a solution that worked with its “not so big team” rather than against it. “For us the advantage of (moving to) a software as a service solution is that we can focus our people on what matters the most for us,” Blanco said.\n",{"header":4286,"text":4287},"GitLab Premium makes CD nearly hands free","Moneyfarm was already familiar with GitLab because the team was running the self-managed version internally on its private network. In January 2020, Blanco and Faulkner and team began the process of transferring all their code from Concourse to GitLab in the cloud. The team has integrated GitLab into AWS deployment with a custom script that runs in the pipeline and releases the container into production. Their migration is complete and the team has moved between 80 and 1000 pipelines related to their most important tasks over to GitLab. The full migration to GitLab took about four months to complete.\n\nThe move to GitLab “made things a little bit simpler because it’s one less tool to manage,” Blanco says. Moneyfarm’s value proposition is clear, he says: “We deliver value when we put software in front of our customers. Having the infrastructure and a tool that (operates) seamlessly means developers can just focus on building features and making code that works. We have a tool that supports that in production (now) and it made a difference.”\n\nWith GitLab, Moneyfarm has:\n  * Shrunk the cycle time between idea and production from 45 minutes down to 13.5 minutes\n\n  * Improved the working relationships between developers and stakeholders\n\n  * Enabled greatly enhanced developer self-service\n\n  * Achieved predictable timing in the deployment process\n\n  * Doubled the number of deployments from 18 deploys per week to 35 per week\n\n  * Increased code production\n\nThere is also, quite simply, less time spent waiting. “With GitLab we go from a developer’s keyboard to a customer environment much faster,” Faulkner said. “It used to be the case that developers were sitting watching a progress bar on Concourse with a stakeholder standing behind them. I don’t remember that happening since we’ve moved to GitLab.”\n\nBut there are also other, less concrete outcomes. Improved collaboration has led to brainstorming conversations the likes of which the Moneyfarm team had never seen before. “Conversations that wouldn’t have happened before are now happening and this, in turn, spreads knowledge, and that in turns helps us to have a better understanding of the tool and how to use it better,” according to Blanco.\n\nAnd finally, the Moneyfarm team was pleasantly surprised to find the cost of GitLab is roughly the same as what was spent on self-hosting and local management of the previous tool. The GitLab bonus, though, is that it doesn’t require a dedicated staff to manage and maintain it.\n",{"header":4289,"text":4290},"Happy developers = better code and faster deployments","Although Moneyfarm has seen a number of concrete benefits from the shift to GitLab, one in particular was relatively surprising. “Our developer’s happiness shot to the sky when we migrated to GitLab. Everybody was satisfied that we have a new solution because everybody felt it was a breath of fresh air and quite easy to understand,” Blanco said. “This definitely made our developers happier.”\n\nDeveloper happiness matters because happy developers simply do better work, according to Blanco. “You need to keep your developer experience at a high level because that’s the only way you really can deliver value fast. GitLab has played … a significant part in helping us increase our developer experience.”\n\nOne obvious way the developer experience has improved is that things are moving more quickly. Their previous CI/CD solution took between 35 to 45 minutes to get from commit to staging, Faulkner said, but [GitLab comes in reliably](/solutions/continuous-integration/){data-ga-name=\"continuous integration\" data-ga-location=\"customers content\"} at just 13.5 minutes. The process is faster and more reliable and that translates to less context-switching and an increased ability to focus on a single task.\n\n“Before, developers would effectively have to pick up another task while waiting,” Faulkner said. “Now people can be much more focused on keeping on the same task and getting it through production.”\n\nThat focus translates into deployments that are twice as frequent as before and increased code production. “I definitely can tell you we spend less time worrying about the CD tool and worrying about the idiosyncrasies. Sometimes the CD tool was down or somebody had to restart it – now we don’t think about that anymore,” Blanco said. “I can see a kind of correlation between the fact that we’re producing more code, deploying more value, and the fact that we are using GitLab.”\n",{"template":950,"size":40,"region":106,"industry":71},"content:en-us:customers:moneyfarm.yml",{"_path":4294,"content":4295,"config":4331,"_id":4332},"/en-us/customers/mpei",{"name":4296,"logo":4297,"hero":4298,"heroImage":4299,"benefits":4300,"industry":65,"employeeCount":4307,"location":4308,"solution":913,"headline":4309,"summary":4310,"quotes":4311,"content":4317,"companySize":1281,"region":1281,"contributors":1281,"stickyBenefits":4330},"Moscow Power Engineering Institute","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745517999/r3nkpl3wgu0jlnhec2ik.svg","Moscow Power Engineering Institute powers forward with GitLab-infused teaching","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518448/mqbvxfb7cokyfsdzxgja.jpg",[4301,4303],{"metric":1893,"config":4302},{"icon":1895},{"metric":4304,"config":4305},"Improved project management",{"icon":4306},"Enablement","13,000 students","Moscow, Russia","AI and math instructors at the Moscow Power Engineering Institute adopted GitLab to overcome workflow issues that hindered students’ moves to new DevOps methods.","Moscow Power Engineering Institute’s (MPEI) Department of Applied Mathematics counts on GitLab to organize student learning, with state-of-the-art DevOps processes.\n",[4312],{"quoteText":4313,"author":4314,"authorTitle":4315,"authorCompany":4316},"GitLab helps us to measure the performance of each student. It provides timely feedback\n","Andrey Efanov","Teaching Asst. and PhD student, Applied Mathematics and Artificial Intelligence Dept.","MPEI",[4318,4321,4324,4327],{"header":4319,"text":4320},"Preparing students for technical achievement","The National Research University “Moscow Power Engineering Institute” is a public university that offers training in power engineering, electrical and radio engineering, information technology, and related fields. The institute’s history is marked by profound technical achievement, such as being among the first to take radio images of the Venus surface and the dark side of the Moon. Within [MPEI](https://mpei.ru/lang/en/Pages/default.aspx){data-ga-name=\"MPEI\" data-ga-location=\"body\"} Department of Applied Mathematics, there has long been a special focus on research and teaching in the evolving fields of parallel programming and artificial intelligence — work that is evolving rapidly as cloud, Kubernetes, and microservices gain greater use.\n",{"header":4322,"text":4323},"MPEI looks to CI/CD pipelines to meld student efforts into cohesive whole","As they looked to grow researchers’ and students’ technical capabilities, MPEI educational leaders grew concerned. Software project complexity was increasing. New design paradigms such as containers and microservices were emerging. There were signs that assorted largely manual processes showed stress. Additionally, processes varied widely in methods applied. “Everybody used their own method,” said Andrey Efanov, teaching assistant and Ph.D. student in MPEI's Applied Mathematics and Artificial Intelligence Department. An essential requirement was support for capable CI/CD pipelines that could organize individual members into cohesive groups, Efanov added. It was beneficial generally to invite a large group into curated projects to participate. At times, however, there was a need to manage students’ visibility into each other’s projects. In this regard, tools such as Travis CI, GitHub, Moodle, and Google Classroom were found to be suboptimal. Able role-based access was a must.\n",{"header":4325,"text":4326},"Teachers and students alike gain insight into workflow","To expand innovation and enhance learning, the MPEI educators decided they needed an open-source DevOps platform they could flexibly apply to coursework and project work alike. GitLab met the MPEI Math and AI Department’s objectives in terms of highly granular role-based access control, integration, collaboration, and DevOps agility. By providing advanced planning capabilities in the form of milestones, epics, and boards, student project management is significantly enhanced. A GitLab group graph displays a useful visual history of repository work, which assures teachers and students a good understanding of general workflow. These group graphs include data on pushed events, opened and closed issues, and total number of contributions. From students’ perspectives, they gained greater insight into the development process. GitLab helped the department meet its requirement to automate the verification processes of student work, according to Efanov.\n",{"header":4328,"text":4329},"GitLab supports learning while doing, aids Kubernetes learning curve","Today, GitLab provides exceptional project visibility, and helps ongoing management of student work. It allows increased collaboration between students, and prepares them for industry careers deploying state-of-the-art CI/CD pipelines. GitLab group and subgroup hierarchies have become a part of the department’s organizational structure. There are now four learning and infrastructural services fully managed by just two staff engineers using GitLab IaC integration with Kubernetes: keycloak, wiki, a discord bot and a self-made online judge.\n\nMoreover, the GitLab environment simplifies Kubernetes development for beginners, who can make simple Helm child charts from templates to create services ready to deploy, Efanov said. “GitLab helps us to measure the performance of each student and it provides timely feedback. Sometimes, at the end of the term, a student would come up with some huge problems with which they had struggled for a long time,” he continued. “GitLab’s visibility means we can always ask what problems they face, if they are okay with them, or whether they need help with them.” While the institute provides important theoretical knowledge to students, the GitLab environment helps them expand that with practical experience in methods used by industry experts for creating better software.\n",{"benefits":1281},{"template":950,"size":44,"region":106,"industry":67},"content:en-us:customers:mpei.yml",{"_path":4334,"content":4335,"config":4370,"_id":4371},"/en-us/customers/nebulaworks",{"name":3637,"logo":4336,"hero":3638,"heroImage":4337,"benefits":4338,"industry":89,"employeeCount":4347,"location":4348,"solution":2108,"headline":4349,"summary":4350,"quotes":4351,"content":4356,"stickyBenefits":4369},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1745517947/ilfknqbmru09zrd0mc30.png","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518424/l6neb85nzcj4ubqq08ra.jpg",[4339,4341,4345],{"metric":1524,"config":4340},{"icon":1195},{"metric":4342,"config":4343},"Simplified workflow",{"icon":4344},"Monitor",{"metric":1893,"config":4346},{"icon":1295},"15","Irvine, CA","Nebulaworks adopted GitLab, eased tool maintenance and overhead, and achieved CI organization.","The engineering consultancy organization adopted GitLab for source code management (SCM), continuous integration and delivery (CI/CD), and issue tracking, and increased connection with the marketing team in the process.\n",[4352],{"quoteText":4353,"author":4354,"authorTitle":4355,"authorCompany":3637},"When we adopted GitLab, we went all in, because it simplified a lot of the day-to-day maintenance. We don't have a lot of time to deal with the platform where we're storing our code. It frees us up to do things that are either internal to the engineering team or to focus on customer interactions.\n","Rob Hernandez","CHIEF TECHNOLOGY OFFICER",[4357,4360,4363,4366],{"header":4358,"text":4359},"Consultancy by engineers for engineers","Nebulaworks is a software engineering consultancy firm that provides customers with innovative solutions for development and delivery processes. The organization prides itself around working with its customers to create high-performing engineering teams where members are inspired to collaborate openly, incentivized to gather new knowledge and skills, and are fulfilled by solving complex problems simply.\n\n[Nebulaworks](https://www.nebulaworks.com/about/) was founded in 2014 by two engineers who saw a need to challenge the status quo of software development and IT Ops services delivery in large enterprises. Different from many of the consulting firms and Global SI’s of the time, Nebulaworks was built to solve the complex challenges of the enterprise IT engineer. A consulting and SI firm, built for engineers by engineers.\n",{"header":4361,"text":4362},"Three tools too many","Nebulaworks was looking for a platform that provided remote repositories to empower teams to collaborate — regardless of location. The development team was previously using a self managed instance of a git repository and a separate issue board software for issues and tracking. They wanted to increase productivity and focus their engineering efforts on development that would impact the business, rather than dealing with the daily administrative tasks just to keep the system online.\n\nThe organization had self-managed continuous integration service that was backed by Kubernetes. This was not an ideal solution due to the administrative overhead and caused more work for the engineers who were using the system.\n\nNebulaworks was maintaining a total of three internal tools for the course of several years. It was a full-time job for an engineer to manage and maintain the tools, which reduced time for software engineering. On top of that, having data and user permissions in various places caused a lot of context switching, which was time-consuming and inefficient.\n",{"header":4364,"text":4365},"One platform, many functionalities","Before renewing the license for the existing three internal, self-managed tools, Rob Hernandez, Chief Technology Officer, and his team researched other platforms. When they demoed GitLab, they mirrored an existing project, fit it for the CI portion to test, and then wrapped all the issue tracking and board structures. Hernandez found that GitLab’s level of organization and the ability to provide a hierarchy of different projects stood out against competitors.\n\n“Realizing that we could even have all the issues rolled up to the top-level GitLab group was really cool. We wouldn’t be able to do that with our existing self-managed git service,” Hernandez said. “Going through the tool in the demo, that was great. And realizing that with the hierarchy we could have subgroups, and we could break those subgroups into how we organize projects for a given customer.”\n\nGitLab offered the team a singular platform for CI integration, code management, collaboration, and issue tracking without the need to layer any tools. Nebulaworks is able to provide customers with a collaborative and transparent experience. A focus on a transparent relationship reduces cost for everyone by enabling faster resolution of issues, and reduces risk by creating trust and enabling both sides to plan and execute accordingly. With GitLab, Nebulaworks was able to truly focus on deliverables instead of performing updates and toolchain maintenance.\n",{"header":4367,"text":4368},"CI, code management, and customer success","GitLab breaks down silos as a centralized platform for collaboration, helping to drive the company forward. The team now has a simplified workflow, including issues that are close to the code, end-to-end visibility, easily integrated CI, and no more context switching between tools.\n\nNebulaworks fully replaced its internal, self-managed git stack with GitLab. “We went as far as to define all of our resources in GitLab (repositories, groups, permissions, etc.) using Terraform. That way, GitLab gets changed just like any other piece of code – submit a MR, apply it and merge it,” Hernandez said. “It’s really cool to see new hires add their permissions on the first day via a MR and that’s the way it should be. There’s no other way for someone to make a change within our GitLab Nebulaworks group.”\n\nNebulaworks selected GitLab Gold, because the SaaS capabilities allowed the team to shut down some on-prem machines and gain the benefits of a hosted offering. GitLab is powering their [deployments across Amazon Web Services (AWS)](/blog/from-monolith-to-microservices-how-to-leverage-aws-with-gitlab/){data-ga-name=\"deployments across AWS\" data-ga-location=\"customers content\"}, specifically their container workloads running on top of Amazon EKS clusters.\n\nBy moving to SaaS, the team is able to optimize its efficiencies by leveraging the GitLab infrastructure, and to focus on delivering better products to customers. “We’re not worrying about security patches or upgrading to new versions for new features. All of those things are taken care of by GitLab,” Hernandez said. “Now we are focusing on enabling our engineering team as a whole, across all the services and functionality that we need. Gitlab allows us to focus on that instead of focusing on maintenance.”\n\nBecause the engineering team works with many different tools with different clients, they need to focus on the statement of work. The team measures success against what gets delivered and the time it takes to deliver, which requires a dependable tool that can work with a variety of other tools. “With GitLab, we release every two weeks to production. That’s a business need. That’s how we want to do it. It’s easy for us. It’s low stress. We correctly test things, let them bake in the development and staging capacity, before they get out to production,” Hernandez said.\n\nThe engineering team at Nebulaworks is not the only one using GitLab. To help improve coordination between marketing and the engineering group, the content marketing team [collaborates in GitLab](/topics/version-control/software-team-collaboration/){data-ga-name=\"collaborates in gitlab\" data-ga-location=\"customers content\"}. The company had planned on creating content for the engineering consultancy and GitLab provided a simple way to work closely with the engineering team to create quality content. Both teams use GitLab issues and boards to communicate and content is added to the website in merge requests.\n\n“When we decided to invest in content marketing, we knew we had to figure out a solution that would allow marketing and engineering to work seamlessly together. The simplicity of GitLab’s features made that possible for us,” said Anne Lin, Marketing and Brand Manager. “The marketing team quickly adopted the engineering team’s workflow using issue tracking, kanboards, and merge requests to collaborate on content production. By leveraging the same workflow, the two teams were able to generate trust and visibility into each other’s work.”\n\nUsing GitLab means that the teams can work asynchronously. Working from home is optional at Nebulaworks. As the company has adopted the work from home lifestyle, they’ve been able to collaborate easily. “We have not missed a beat. How we collaborate with our customers, how we work with our customers, how we work on projects, that workflow has not changed,” said Patrick Collins, VP, Sales and Customer Success. “It’s been a huge success having this process in place, going to a large group coming into the office, now 100% remote.”\n",{},{"template":950,"size":36,"region":102,"industry":91},"content:en-us:customers:nebulaworks.yml",{"_path":4373,"content":4374,"config":4415,"_id":4416},"/en-us/customers/new10",{"name":4375,"logo":4376,"hero":4377,"heroImage":4378,"benefits":4379,"industry":69,"employeeCount":1150,"location":4388,"solution":913,"stats":4389,"headline":4396,"summary":4397,"quotes":4398,"content":4402,"contributors":1281},"New10","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518001/lkz8lquokr8zmubgkeon.svg","How New10 deploys 3 times faster with GitLab","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518449/blkggbp6mxawulyssqqm.jpg",[4380,4382,4385],{"metric":1521,"config":4381},{"icon":902},{"metric":4383,"config":4384},"Accelerated releases",{"icon":1734},{"metric":4386,"config":4387},"Built-in security scanning",{"icon":967},"Netherlands",[4390,4391,4394],{"value":1807,"metric":1032},{"value":4392,"metric":4393},0,"context switching",{"value":2508,"metric":4395},"shorter cycle times","New10 wanted a solution that could provide version control and code ownership for engineers to deploy quickly and safely.","New10 found startup success using GitLab as a single platform for source code management (SCM) and continuous integration and delivery (CI/CD), and GitLab's Amazon Web Services (AWS) integration.\n",[4399],{"quoteText":4400,"author":4401,"authorTitle":1267,"authorCompany":4375},"GitLab is really helping us in our very modern architecture, because you're supporting Kubernetes, you're supporting serverless, and you are supporting cool security stuff, like DAST and SAST. GitLab is enabling us to have a really cutting edge architecture.\n","Kirill Kolyaskin",[4403,4406,4409,4412],{"header":4404,"text":4405},"Growing FinTech start-up","New10 is a digital financial lender based in the Netherlands offering loans to small and medium-sized enterprises. [New10](https://new10.com/) is 100% a subsidiary of ABN AMRO Bank N.V., combining the speed and innovation capacity of a startup with the expertise and security of a bank. The FinTech startup helps entrepreneurs to accelerate business growth with fully digital financial services.\n\nThe whole lending process, from application phase to officially signing, happens within 15 minutes. Entrepreneurs can secure a financing offer with clear terms and conditions via a professional and efficient digital process. In just three years, New10 has provided loans to more than 2,500 happy customers with an average customer satisfaction score of nine.\n",{"header":4407,"text":4408},"Getting started swiftly and securely","Three years ago, New10 was established by a small group of highly motivated professionals, most of whom had backgrounds in engineering with banks or other financial organizations. The engineers had a variety of software platform knowledge, but none had previously worked with GitLab. From the inception of the company, the engineers wanted a solution that was developer-friendly and scalable. Ideally, the solution would allow developers to own their own code, creating quick deployment turnaround times.\n\nAs a startup, it was crucial for the company to bring value to enterprises as soon as possible while maintaining high standards. The main requirement was to have Git functionality integrated together with CI/CD, essentially avoiding context switching to increase workflow efficiency. New10’s affiliation with ABN AMRO Bank requires strong security and privacy regulation compliance. The company has always placed protection at the forefront and a solution that focuses on high-level security would offer another level of assurance.\n",{"header":4410,"text":4411},"All-in-one workflow efficiency","New10’s engineers had experience with several other platforms, but they adopted GitLab from inception in order to get up and running quickly. GitLab’s all-in-one solution allows developers to work efficiently without any context switching, unlike other tools.\n\n“If you have to go to your data center, you have to buy servers, the servers have to be shipped, you install some kinds of Jenkins on the servers, you configure it, and then you can start developing, only then can you start to produce. With GitLab, you really cut the time in configuration, cut the time to what is crucial for you to deliver,” said Kirill Kolyaskin, CTO.\n\nNew10’s engineers own their own code with GitLab’s [version control system](https://about.gitlab.com/topics/version-control/) and CI/CD. “It’s not only Git and CICD, Infrastructure as a code and application security is also owned by the developer. It’s really bringing ownership and power into the hands of people who write the code. This is the main competitive advantage and deal breaker when I’m using GitLab. No one else does it in the market,” according to Kolyaskin.\n",{"header":4413,"text":4414},"Fast deployments, increased releases, supported engineers","With CI/CD properly in place and incorporating GitLab’s best practices, changes are made directly to the code in real time. The deployment is altered immediately, allowing developers to deploy three times faster than they previously were able to. Having an enhanced and integrated source control management tool has improved efficiencies amongst developers. The solution provides the opportunity to work asynchronously, and integrates with several other tools.\n\nGitLab integrates with Slack, which allows notifications and improves workflow. New10 also plugs GitLab into its data analytics tool, Tableau. This integration allows data from GitLab to give visibility of the business acceleration to stakeholders. New10’s engineers are thriving in a DevOps culture. The engineers are able to release new features and new products because they no longer need to maintain deployments. The deployment to production release time went from two times per month to two times per day, with GitLab directly supporting this success.\n\nGitLab closely [integrates with AWS](https://about.gitlab.com/partners/technology-partners/aws/) and this integration has delivered great value for New10. They run all their production workloads in AWS, including loan administration, risk calculation, customer information and analytical services. “It’s a great cloud native integration for us,” added Kolyaskin. New10 uses GitLab runners for testing and quality assurance purposes, and these runners are hosted on Kubernetes clusters. Their engineers are empowered to run static and dynamic tests on their code. The data is provided to a developer during the merge request, saving team members from security checks in various departments and then looping back to developers. “GitLab helped us in our initiative to kind of shift security left. We have a shorter feedback loop on security and we can fix problems in code before they are even deployed,” Kolyaskin said.\n\nNew10’s level of security has always been “like Fort Knox,” according to Kolyaskin. With GitLab, teams are able to maintain a high level of security faster and at an inexpensive rate. “GitLab is really helping us in our very modern architecture, because you’re supporting Kubernetes, you’re supporting serverless, and you are supporting cool security stuff, like DAST and SAST. GitLab is enabling us to have a really cutting edge architecture.”\n\nGitLab’s technical account managers are engineers who understand and recognize the importance of solving problems and work tirelessly to solve any issues that New10 has come across. “What’s really important for me, and why I really respect and love GitLab, is that when we are struggling with something, I see a lot of effort from GitLab to do it better for us. Our software engineers appreciate that,” Kolyaskin said.\n\nNew10 appreciates that GitLab is a technology-oriented company, with an engineering focus, as opposed to a business focus. “When I’m working with GitLab, I just open your road map and then I think, ‘Yeah, this would be a roadmap if I were in charge’ … Really GitLab is supporting us by your way of working.”\n",{"template":950,"size":36,"region":106,"industry":71},"content:en-us:customers:new10.yml",{"_path":4418,"content":4419,"config":4458,"_id":4459},"/en-us/customers/nvidia",{"name":3555,"logo":4420,"hero":3337,"heroImage":4421,"benefits":4422,"industry":89,"employeeCount":4431,"location":4432,"solution":975,"stats":4433,"headline":4438,"summary":4439,"quotes":4440,"content":4445},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1745517948/bzwcbp5gudplrzc1rv9r.svg","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518425/kq0osjfh8nf2mies7nyr.jpg",[4423,4426,4428],{"metric":4424,"config":4425},"Increased scalability",{"icon":1636},{"metric":4041,"config":4427},{"icon":2105},{"metric":4429,"config":4430},"More upgrades, more frequently",{"icon":971},"11,000+ employees","More than 50 offices worldwide",[4434,4436],{"value":4435,"metric":2661},"51%",{"value":3762,"metric":4437},"uptime","GitLab Geo helps NVIDIA’s development teams to stay secure and highly communicative.","NVIDIA’s distributed teams rely on Geo for stability and security.\n",[4441],{"quoteText":4442,"author":4443,"authorTitle":4444,"authorCompany":3555},"Without GitLab, we'd be wasting engineering time with lots of individual little servers being managed around the world. We would probably have a lot more headaches and still be suffering with scalability problems.\n","Patrick Herlihy","Configuration Management Specialist, NVIDIA",[4446,4449,4452,4455],{"header":4447,"text":4448},"A pioneer in supercharged computing","NVIDIA is known for creating the world’s first graphics processing unit (GPU) in 1999, which changed the face of computer gaming.\n\nSince then, [NVIDIA](https://www.nvidia.com/en-us/) has grown to be a global leader in visual computing, artificial intelligence, data centers, deep learning, and gaming platforms. The company strives to provide the latest GPU technology for mobile computing, automotive services, medical devices, and gaming on a massive scale. Its GPUs are widely used in the world’s leading public cloud datacenters.\n",{"header":4450,"text":4451},"Staying secure, scalable, and seen","NVIDIA has more than 50 offices worldwide with more than 13,000 employees, requiring numerous software applications. Creative freedom is expected. “I think we consider it a competitive advantage that we don't mandate from the top when it comes to tools and things. We let groups organically figure out how they want to best operate,” said Patrick Herlihy, configuration management specialist at NVIDIA.\n\nEncouraging staff to use the best tool for business responsibilities brings a variety of challenges. Security and transparent communication are integral parts of keeping business momentum moving forward. “We'd be wasting a lot of NVIDIA engineering time with lots of individual little servers being managed around the world,” Herlihy said. “We need something more modern, with a modern workflow and features and things,” said Kevin Sage, SCM manager.\n\nThe company strategy allows teams to use any platform or tool that they prefer. If a tool becomes accepted by a majority, a plan is then put in place to layer in support for the tool. “We have a very decentralized model here where groups kind of get to choose their own way of doing their own things for a while. And then eventually they'll grow big enough, where that becomes unworkable and then they'll come to the central groups, like us, to help them out and manage it for them,” Herlihy said. “So in a sense, it's kind of a marketplace for ideas, and a lot of people are choosing GitLab. If they're given an open choice, they seem to choose GitLab.”\n",{"header":4453,"text":4454},"Keeping dispersed teams on the same page","GitLab’s Community Edition was introduced at NVIDIA in much the same way. While GitLab was introduced internally in 2016, the overall acceptance rate has skyrocketed and is now fully supported. As the tool was utilized by additional people, it became clear that GitLab’s integration capabilities, scalability, and ease of use are elements that not all other tools share. “GitLab is the only Git server that really gives us those capabilities. I think that's been a huge thing for us as the administrators,” Sage said.\n\nGitLab Geo is especially critical to enable distributed teams to work efficiently and effectively. [GitLab Geo](https://docs.gitlab.com/administration/geo/){data-ga-name=\"geo\" data-ga-location=\"customers content\"} reduces the time — and stress — it takes for NVIDIA’s distributed development teams to clone and manage projects. “GitLab has continually gotten better with scalability. It's gotten more ability to spread among more nodes. With Geo, within one data center, we can now scale ... We have a bunch of nodes running and sharing the load, and it's all invisible to the users, and it's continued work there to make it scale better, be more fault-tolerant, more high availability,” Sage said. “We're now doing zero downtime upgrades, I mean all that stuff has been really great improvements in the product that makes it easier to run and manage in a large deployment.”\n\nGitLab Geo is empowering NVIDIA to easily span the globe and provide services for their international teams. Utilizing GitLab Geo’s read-only mirrors, the company is able to keep data close to users — instead of having them waste hours waiting for large repos to be pulled down to work on them.\n\nThe end goal is to provide developers with a dedicated, scalable, experience — and prevent users from hitting all of the servers at once. The company is also in the process of establishing additional facilities and GitLab Geo with High Availability capabilities is helping teams be prepared for any disaster recovery needs and maintain their uptime capabilities.\n\nGitLab also provides a level of transparency that other tools do not. “The fact that you're so transparent in your development process is huge. It helped me come up to speed relatively quickly. But, also I’m able to understand how the product works internally and be able to actually fix things myself,” Herlihy said.\n",{"header":4456,"text":4457},"Transparency breeds innovation","The goal is to have uptime at 100% and the development teams have found that with GitLab. “For about the last six months, I would say, it's been pretty close to 100% ... for the [GitLab HA](https://docs.gitlab.com/ee/administration/reference_architectures/) model to actually never have downtime which is pretty impressive,” Herlihy said. “On the Geo side, there's more usage than I thought.”\n\nGitLab’s transparency in communication — and even failures — has created a safe environment for NVIDIA’s development teams. It is no secret that software isn’t reliable 100% of the time. However, GitLab is quick to point out issues, and even faster at fixing them. “When you have a problem, we can get it fixed. You know, we can get help, we don't have to wait three years for someone in the community to decide to submit a patch,” Sage said. “Good support has been a really big deal for us.”\n\n[GitLab’s openness](https://handbook.gitlab.com/handbook/values/){data-ga-name=\"openness\" data-ga-location=\"customers content\"} has been appreciated in a company culture capacity as well. Not just in the way that the tool is managed, but how clear communication improves processes — both internally and for the customer. “We've had senior directors who are using GitLab as an example of why we want transparency, and how to use transparency, and how much it helps people,” Sage said. “The way you guys handle that kind of stuff is actually being noticed by our senior management, and they’re guiding us that we should try and copy some of that with our internal applications and tools too.”\n\nNVIDIA’s next big step with GitLab is pushing forward with disaster recovery planning strategies. “Disaster recovery is our plan using Geo. So, that should be an easy cut over ... we are trying to make it a lot easier to not so much have automated failover, but make the disaster recovery part of Geo work really easily,” Herlihy said.\n",{"template":950,"size":44,"region":102,"industry":91},"content:en-us:customers:nvidia.yml",{"_path":4461,"content":4462,"config":4510,"_id":4511},"/en-us/customers/paessler",{"name":4463,"logo":4464,"hero":4465,"heroImage":4466,"benefits":4467,"industry":4477,"employeeCount":4478,"location":4479,"solution":4480,"stats":4481,"headline":4490,"summary":4491,"quotes":4492,"content":4497,"contributors":1281},"Paessler","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518003/uttyottdzejmrhvl3wbr.svg","Paessler AG switched from Jenkins to GitLab and ramped up to 4x more releases","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518450/af0g908t8dj2yc4ltq4i.png",[4468,4471,4474],{"metric":4469,"config":4470},"Improved stability",{"icon":1845},{"metric":965,"config":4472},{"icon":4473},"CodeAlt2",{"metric":4475,"config":4476},"Accelerated deployment",{"icon":902},"Network Software","201-500","Nuremberg, Germany","[GitLab Starter](https://about.gitlab.com/pricing/)\n",[4482,4484,4487],{"value":1402,"metric":4483},"of QA self-served",{"value":4485,"metric":4486},"120x","speed increase",{"value":4488,"metric":4489},15,"releases per day","Paessler AG is the company behind PRTG Network Monitor, an award-winning Unified Monitoring Solution. Helping IT professionals monitor their entire infrastructure around the clock, PRTG monitors all systems, devices, traffic and applications of your IT infrastructure.","Helping customers monitor their entire IT infrastructure 24/7, Paessler AG keeps up with this fast-moving field with GitLab for version control and continuous delivery.\n",[4493],{"quoteText":4494,"author":4495,"authorTitle":4496,"authorCompany":4463},"Every branch gets tested, it’s built into the pipeline. As soon as you commit your code, the whole process kicks off to get it tested. The amount of effort involved in actually getting to the newest version that you’re supposed to be testing, whether you’re a developer or a QA engineer, is minimized immensely.\n","Greg Campion","Senior Systems Administrator",[4498,4501,4504,4507],{"header":4499,"text":4500},"Providing round-the-clock monitoring for the enterprise","Paessler AG’s [PRTG Network Monitor](https://www.paessler.com/prtg) is used by enterprises and organizations of all sizes and industries across more than 170 countries. With customers as diverse as London’s National Theatre, Fulham Football Club, universities, and healthcare networks, PRTG constantly monitors IT infrastructure, alerting administrators to problems with bandwidth, applications, networks, databases, and more, all before users are even aware of an issue.\n",{"header":4502,"text":4503},"Instability and erratic performance","In offering an all-encompassing monitoring service, it’s critical that PRTG moves fast to keep up with developments in every space. Paessler migrated their development of PRTG from Mercurial to GitLab primarily for version control purposes. A combination of a cumbersome, 7GB repository (the initial commit took place 20 years ago) and some bad practices (the absence of LFS in Mercurial means they had their binaries as part of the repository) led to major stability issues that made pulling, pushing and merging all work inconsistently.\n\n“There were times where it just stopped working; you couldn’t pull and push anymore and you didn’t really know why,” said Konstantin Wolff, Infrastructure Engineer (PRTG Development).\n",{"header":4505,"text":4506},"Modern version control and unprecedented QA automation with GitLab","This instability prompted Paessler to seek out a Git solution. “A lot of people used Git at the company and just knew that it was faster, better, and what everybody else is using nowadays,” said Greg Campion, Senior Systems Administrator. “It’s also harder now to train somebody to use Mercurial because Git is so prevalent. So, when you hire a developer, they probably know Git but they may not know Mercurial.”\n\nAfter testing a number of version control systems, they chose GitLab for “the whole package.” Adopting Git restored stability and helped Paessler ramp up their release cycle from three major releases a year to continuous delivery and monthly releases. But arguably the greatest outcome of their switch to GitLab has been the unanticipated effect on QA automation.\n",{"header":4508,"text":4509},"Stability, more frequent releases, and 120x boost for QA tasks","Greg noticed the functionality and potential of GitLab pipelines, and adopted them for the cloud team he works on, and it’s since caught on all over the organization.\n\n“Before we had our build pipeline running with Jenkins,” explained Konstantin. “So, we have a develop, release, and master branch, which is finally released to the public. Every time you build a branch of those three, the outcome would have been installs on several VMs and then our test automation started in a separate process. At the end of the process you got an email that it worked, it didn’t work, where it failed, and stuff like that.”\n\nThis sequential process, with feedback only available at the end, was only triggered automatically on the dev, release and master branches. A QA engineer had to perform some tasks to make this happen, around 10 minutes, 6-7 times a day. If other branches needed testing they’d have to build them locally and run a test locally.\n\nThe situation now could not be more different with the use of GitLab: “Every branch gets tested,” said Greg. “It’s built into the pipeline. As soon as you commit your code, the whole process kicks off to get it tested. Then you can go to the branch’s review app and have a running version of PRTG that you’ve just checked in code for, that’s already also been tested.” What this means in practice is higher quality control for their product and a significantly tighter feedback loop between developers and QA.\n\n“The amount of effort involved in actually getting to the newest version that you’re supposed to be testing, whether you’re a developer or a QA engineer, is minimized immensely.” The QA engineer’s tasks – about an hour a day in total – have been slashed to 30 seconds, a 120x speed increase.\n\nThis automation really pays dividends when something is wrong: if the tests fail, the pipeline fails, so the developer already knows something has gone awry, instead of waiting to hear that from QA. This immediate feedback now has developers at Paessler self-serving 90 percent of their QA.\n\nWhile it’s sometimes a challenge to drive widespread adoption of a new tool within an organization, the uptake of GitLab CI/CD at Paessler has been remarkable. “It really started catching on when people just saw our pipelines,” Greg said. “We actually had an internal learning session that was basically, ‘You show us yours, and we’ll show you ours.’ Everybody showed off their pipelines just to see what they’re capable of, what people are doing with them, to get new ideas and stuff like that. It was actually a pretty successful, interesting session.”\n\n“GitLab is being used like crazy. And now that there’s a bunch of cool stuff going on in it, everybody wants to jump on the bandwagon.”\n",{"template":950,"size":40,"region":106,"industry":91},"content:en-us:customers:paessler.yml",{"_path":4513,"content":4514,"config":4556,"_id":4557},"/en-us/customers/paessler-prtg",{"name":4515,"logo":4464,"hero":4516,"heroImage":4517,"benefits":4518,"industry":89,"employeeCount":2657,"location":4479,"solution":975,"stats":4527,"headline":4536,"summary":4537,"quotes":4538,"content":4543,"contributors":1281},"Paessler PRTG","How Paessler deploys up to 50 times daily with GitLab Premium","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518450/qlq0acudcuqztsxmk8k4.jpg",[4519,4522,4524],{"metric":4520,"config":4521},"Accelerated feedback cycles",{"icon":902},{"metric":1524,"config":4523},{"icon":1195},{"metric":4525,"config":4526},"Faster pipeline builds",{"icon":1734},[4528,4531,4534],{"value":4529,"metric":4530},"75%","reduction in build time",{"value":4532,"metric":4533},"20-50","deployments per day",{"value":3037,"metric":4535},"decrease in runtime","Paessler upgraded to GitLab Premium after success with Starter.","Paessler found success with GitLab and quickly discovered that adopting Premium would offer accelerated deployments and efficient workflows.\n",[4539],{"quoteText":4540,"author":4541,"authorTitle":4542,"authorCompany":4515},"When the PRTG pipeline ran, including test automation so we could release, we were between 45 minutes to almost an hour, depending on how the tests behaved. Now, we just build PRTG with our test automation and it's 15 minutes.","Konstantin Wolff","Architect, Paessler",[4544,4547,4550,4553],{"header":4545,"text":4546},"Worldwide monitoring solution","Founded in 1997 in Nuremberg, Germany, Paessler provides IT infrastructure services for over 200,000 companies worldwide. Paessler’s PRTG Network Monitor is an all-in-one solution that helps IT professionals easily and effectively monitor their infrastructure. [PRTG](https://www.paessler.com/prtg) is a powerful business solution that monitors all the systems, devices, traffic, and applications within an IT infrastructure.\n",{"header":4548,"text":4549},"Success with GitLab Starter","Paessler previously migrated the development of PRTG from Mercurial to GitLab primarily for SCM. PRTG used GitLab Starter to restore stability, accelerate release times, and improve software quality.\n\nWith the swift success of Starter, PRTG development teams looked to access the additional features that GitLab offers. The development teams use Jira for ticketing and merger, and they wanted a simplified Jira integration.\n\nThe team needed a tool to monitor all of the pipelines, to view which deployments were running, and to see which have passed and which have failed, and they became interested in GitLab’s operations dashboard. End-to-end transparency would give the teams a better understanding of projects and deployments to improve the overall workflow performance.\n",{"header":4551,"text":4552},"Faster pipelines with simplified toolchains","Greg Campion, Cloud Engineer, and Konstantin Wolff, Architect, approached their managers about upgrading to GitLab Premium. Because the price point was minimal and developers could work in a more simplified toolchain at a faster rate, PRTG’s IT leadership quickly approved the request.\n\nThe deployment of the microservices for their cloud offering PRTG Hosted by Paessler was really long, because they used Terraform, Troposphere, and Serverless and ran many integration tests against resources at AWS that took time to create and destroy. Since adopting GitLab Premium, all these pipelines have been made to run concurrently, and runtime of the testing and deployment has decreased by more than 66%. “The longest pipelines were an hour. The worst one we had took an hour and a half. By using multiple concurrent runners that were able to run scripts to check the status of other jobs and things like that, we dropped that time down to 20 minutes for the really bad pipelines,” Campion said.\n\nPremium offers an unparalleled level of support from GitLab. However, PRTG has only needed to use GitLab support once in two years. “During an upgrade, something went wrong with the Postgres and the support team solved it within the hour. So that was really great,” Campion said.\n",{"header":4554,"text":4555},"Transparent workflow, accelerated deployments, happy developers","Since adopting Premium, there isn’t a single developer working at Paessler who isn’t using GitLab. Every developer, part of the marketing team, and anyone who writes code works on the over 700 projects within GitLab.\n\nAll of PRTG’s components were previously built in a single large pipeline, so it was split in order for every component to become its own project with different pipelines chained together. With [Premium](/pricing/premium/){data-ga-name=\"premium\" data-ga-location=\"customers content\"}, they now have one central repository which uses triggers from every component to notify the central pipeline, eliminating pipeline dependence. “This way we have far more flexibility than before when every push created this big pipeline, which then took half an hour to run through. We considerably shortened the feedback cycle for developers using that approach. And the pipeline graphs help us visualize the whole picture,” Wolff said.\n\nThe central repository has helped to organize the process flow and speed up pipeline times. “When the PRTG pipeline ran, including test automation so we could release, we were between 45 minutes to almost an hour, depending on how the tests behaved. Now, we just build PRTG with our test automation and it's like 15 minutes,” Wolff said.\n\nEach group within PRTG is now individually responsible for building their specific projects. Instead of rebuilding each time, developers control their own builds and simply add to the overall puzzle. This modularization process is only possible through multi-project pipelines.\n\nWith GitLab Starter, deployments were up to 15 times daily, an improvement from Mercurial. Since adopting Premium, deployments are now between 20 to 50 a day. “We migrated 22 microservices in one day and the migration consisted of running unit tests twice on each repository, integration tests twice on each repository and deployment to three different [AWS environments](/partners/technology-partners/aws/){data-ga-name=\"aws environments\" data-ga-location=\"customers content\"}. So each one of them, when I say we make a deployment, that's every single one of those,” Campion said.\n\nDevelopers now have access to the features that they need to work with Jira seamlessly. Teams now have visibility into the workflow and can view the status of projects within PRTG. Furthermore, developers are pleased with how things are working. “It's very, very rare to get any kind of a compliment, but if nobody's complaining about it, that's like a round of applause,” Campion said.\n",{"template":950,"size":40,"region":106,"industry":91},"content:en-us:customers:paessler-prtg.yml",{"_path":4559,"content":4560,"config":4599,"_id":4600},"/en-us/customers/parimatch",{"name":4561,"logo":4562,"hero":4563,"heroImage":4564,"benefits":4565,"industry":2656,"employeeCount":2114,"location":4573,"solution":975,"stats":4574,"headline":4580,"summary":4581,"quotes":4582,"content":4587,"contributors":1281},"Parimatch","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518004/nko47sprks3kdvewwaha.png","How Parimatch scores big with GitLab","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518451/vkfuzhtivquea87t551v.jpg",[4566,4568,4571],{"metric":1893,"config":4567},{"icon":1895},{"metric":4569,"config":4570},"Intuitive user interface",{"icon":1629},{"metric":3993,"config":4572},{"icon":1191},"Cyprus",[4575,4578],{"value":4576,"metric":4577},"57%","User growth in one year",{"value":4529,"metric":4579},"Fewer tools","Parimatch, a gaming platform designed for football fans to bet on matches, adopted GitLab to eliminate toolchain maintenance","Learn how GitLab Premium helps Parimatch enhance visibility, collaboration, and integration management\n",[4583],{"quoteText":4584,"author":4585,"authorTitle":4586,"authorCompany":4561},"We chose GitLab because it’s the industry standard and a good open-source project for any development process\n","Anatolii Kovalenko","Senior DevOps Engineer",[4588,4591,4594,4597],{"header":4589,"text":4590},"A gaming platform dedicated to football fans","Parimatch is a popular platform football fans use to bet on matches. With a rich 25-year history, it's known for providing leaderboard competitions, boosted odds, and cash-back incentives to encourage fans to join in the fun of betting before and during matches. Created by football fans, Parimatch strives to provide fans with a unique and engaging experience.\n",{"header":4592,"text":4593},"Complex integration management and insecure infrastructure","Like many scaling organizations, Parimatch struggled to increase operational efficiency while managing and maintaining multiple tools. Developers used a variety of tools according to their personal preferences, so the team lacked a cohesive, standard workflow. They also lacked the ability to collaborate easily without having a singular solution in place.\n\nThe team also spent a significant amount of time maintaining a complicated toolchain and combating context switching as they moved from one application to the next. The time spent on maintenance pulled developer focus away from feature development and slowed velocity.\n\nIn addition to workflow difficulties, Parimatch also experienced a unique regulation challenge. As an organization that operates in the gaming industry and handles financial information, Parimatch has to adhere to strict security and compliance requirements. Its previous infrastructure didn’t meet the company's stringent regulations.\n\nIn the past, the development team was able to get by using legacy tools, like Jenkins and TeamCity, but an enhanced focus on modernizing tools, maintaining compliance, and simplifying the development workflow inspired them to seek a new solution.\n",{"header":4595,"text":4596},"A single application simplifies integrations and increases collaboration","In assessing the team’s needs, Parimatch’s ideal solution called for a single application that enabled multiple integrations, features that created a secure infrastructure, and an open-source foundation.\n\nWhen considering options, the team immediately dismissed GitHub based on cost and infrastructure incompatibility. They also decided Jenkins was too complex and clunky for their needs. Team members had been using GitLab Free for several years and expressed satisfaction with its features and and their experience with it, so they moved 458 developers onto the GitLab platform.\n\nFully adopting GitLab easily solved the integration issue that had been frustrating the team for quite some time. “We chose GitLab because it makes it easy to maintain multiple integrations in one place. If teams prefer different tools, they can continue to use them seamlessly without struggling with complex workflows or context switching. Some developers prefer Jira, and GitLab provides a simple integration to satisfy those contributors,” says Anatolii Kovalenko, Senior DevOps Engineer.\n\nGitLab’s features meet Parimatch’s commitment to [compliance and security](/solutions/application-security-testing/){data-ga-name=\"compliance and security\" data-ga-location=\"body\"}, and the team appreciates that they can manage their own instance. Developers have been happy with GitLab’s user-friendly user interface (UI). “GitLab is the best wrapper for Git, and the web interface is very intuitive. In comparison with Jenkins, GitLab has a much nicer UI,” Kovalenko said.\n\nUsing GitLab, Parimatch increased operational efficiency and collaboration across the entire software development lifecycle.\n",{"header":3993,"text":4598},"Parimatch has experienced an increase in collaboration as teams across the software development lifecycle embraced GitLab. “Many teams use GitLab, including developers, IT, security, and DevOps engineers. Everyone can cooperate efficiently with each other to meet their needs. Every team has its own criteria on how to deliver value, and now we can answer questions in a single place,” Anatolii explains. Because many teams now are using GitLab, there is an increase in visibility and communication, which makes for a stronger application.\n\nAnatolii says GitLab has positively impacted the team’s ability to maintain stability and ship high-quality code. “If something goes wrong, GitLab offers a simple fix. For example, if we deployed the wrong ratio of our services to the server, we can see the history, read the commit message, and identify the author to roll back commits.”\n\nThe move to GitLab also resulted in a new deployment strategy: GitOps. This framework enables the team to enhance collaboration on infrastructure changes, deliver rapidly, and reduce risk. Using GitLab, Parimatch is able to drive infrastructure automation and benefit from integrated [CI/CD pipelines](/solutions/continuous-integration/){data-ga-name=\"ci/cd\" data-ga-location=\"body\"}.\n\nParimatch has increased collaboration, simplified integrations, and strengthened operational efficiency. “GitLab, for us, is one source of truth,” Anatolii shared.\n",{"template":950,"size":40,"region":106,"industry":91},"content:en-us:customers:parimatch.yml",{"_path":4602,"content":4603,"config":4647,"_id":4648},"/en-us/customers/potato-london",{"name":4604,"logo":4605,"hero":4606,"heroImage":4607,"benefits":4608,"industry":89,"employeeCount":4617,"location":4618,"solution":2454,"stats":4619,"headline":4627,"summary":4628,"quotes":4629,"content":4634,"contributors":1281},"Potato","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518005/tuqmh9czutnnpjqecp7v.png","How Potato uses GitLab CI for cutting edge innovation","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518452/diq0yyulvif3sxwzz1fx.jpg",[4609,4611,4614],{"metric":1847,"config":4610},{"icon":1734},{"metric":4612,"config":4613},"Less tool maintenance",{"icon":1852},{"metric":4615,"config":4616},"Monthly cost savings",{"icon":1247},"80","London and San Francisco",[4620,4622,4625],{"value":1308,"metric":4621},"of projects in GitLab",{"value":4623,"metric":4624},"6,000","deployments in 6 months",{"value":4626,"metric":1312},856,"Potato was looking for a continuous integration (CI) solution that would allow developers and designers to collaborate effectively and ensure total workflow visibility   on one robust platform.","Potato adopted GitLab as a single platform for CI and workflow efficiency.",[4630],{"quoteText":4631,"author":4632,"authorTitle":4633,"authorCompany":4604},"One of the major benefits of GitLab is the ability to keep the whole development workflow in a single tool.","Alessandro Artoni","Tech Community Lead",[4635,4638,4641,4644],{"header":4636,"text":4637},"Cross-functional web development","Potato is a digital product development studio that builds complex, scalable web applications with offices in London and San Francisco. [Potato](https://p.ota.to/) works collaboratively with its clients and often invites them into the development process to improve transparency and communication. Potato provides clients with cross-functional teams that can research and validate a business or product idea before full market launch. In addition, its talented teams design, test, and build innovative digital products for leading brand names.\n",{"header":4639,"text":4640},"Too many tools, not enough functionality","Over the last few years, Potato has transformed itself from an engineer- and development-focused company to a more well-rounded product development company. Team members have transitioned to product leads, designers, delivery leads, and coaches that weren’t historically company roles. In making this update, the teams discovered that they needed a software tool that is more suitable for the entire product development lifecycle, rather than just code hosting.\n\nPotato’s London studio was using Codebase for its code hosting needs. However, it was missing a merge request workflow. “When we were using Codebase, we had to write basically git commit hooks and various scripts to keep everything updated. We couldn't always store the code in Codebase for various client reasons. And so we had all kinds of glues and stuff to keep things working together,” said Luke Benstead, Technology Director, Potato. Sprint planning involved a lot of cumbersome manual planning such as post-it notes on actual whiteboards. They also didn’t have CI, so they were running tests locally which delayed the development process.\n\nWith Codebase, the teams didn’t have an effective method to conduct code reviews, so they used a variety of different tools for clients. Each developer had their own approach — some would follow the commits in a feature branch to review them individually and others would use the command line to create a big diff file and review that. In any instance, giving feedback was difficult and developers were frustrated.\n\nPotato was looking for a way to decrease the number of disparate tools and improve [project management workflows](https://docs.gitlab.com/topics/autodevops/){data-ga-name=\"project management\" data-ga-location=\"customers content\"}. It also wanted a platform that could cater to other teams, like the UX and design teams, in order for developers and designers to use one centralized system for issue tracking. On top of that, they were looking for a way to incorporate CI to improve the quality and speed with which teams could build, test, and ship features. “The biggest negative of our previous environment was the lack of advanced features such as CI/CD support,” said Alessandro Artoni, Technology Community Lead, Potato.\n",{"header":4642,"text":4643},"CI support for all teams","The development team researched a variety of CI platforms that could provide first-class support for Agile-oriented issue tracking and a flexible permissions system, which would allow them to include external stakeholders on a project-by-project basis. It was also very important that the tool integrate with [Google Cloud Platform](/partners/technology-partners/google-cloud-platform/){data-ga-name=\"google cloud platform\" data-ga-location=\"customers content\"}. GitLab checked all the boxes. “GitHub was too focused on developers and we wanted a solution that was also for the designers and the delivery team,” Benstead added.\n\nBecause the design team struggled to be effective using Codebase, Potato did an internal survey with various tools and the decision was made that designers would use Asana and the developers would use GitLab. “It quickly became clear that having two separate issue tracking solutions didn't work very well, so the designers moved across to GitLab as well. And then from that point on, we've used GitLab as our default tool for everything,” Benstead said.\n\nNow, Potato uses GitLab for all the code hosting and issue tracking needs for a majority of the projects and sprint planning efforts. Some projects use GitLab heavily for CI and some projects use it for release planning.\n",{"header":4645,"text":4646},"Integrated CI, GCP, and customer relations","Potato now has the [robust CI](/solutions/continuous-integration/){data-ga-name=\"continuous integration\" data-ga-location=\"customers content\"} support that it previously didn’t have. “Having everything under one roof and under one issue tracker definitely simplifies the end-to-end process of developing a product so we can track everything,” Benstead said. Projects are more consistent with the ability to merge and automate the development process.\n\nThe sprint planning process involves the entire team and is now seamless because the development, CI, and deployment pipeline are all combined on one platform. The workflow process is transparent and simplified. “I think the visibility of that and the fact that everyone can see what's happening and where everything is has definitely simplified the whole development workflow of a product. Definitely compared to all the disparate tools we were using before,” Benstead said.\n\nPotato is now able to give clients full visibility of the application development within GitLab. This transparency has enabled Potato to build better relationships with clients and vendors because everyone can contribute to the issues and discussions are no longer dependent on emails. “It's a lot easier to build that type of relationship with a tool like GitLab,” Artoni added.\n\nEighty to 90% of Potato’s projects are now on GCP and teams leverage CI as part of their workflow. “We almost always use Google App Engine Standard Environment, so it's very easy to integrate deployment pipelines to that environment and link back to the environment for a client's test or for internal teams to test, as well as having to hold automatic testing running in the meantime,” Artoni said.\n\nPotato has also reduced the number of tools used across the company and mitigated the need to write and maintain integrations for different tools. “Previously we had to maintain tools to make all these different systems work together, which is no longer the case now. That's another significant source of saving money,” according to Artoni.\n\nThe teams can count on higher quality merge requests thanks to integrated CI. They have improved collaboration within their own teams, as well as with clients. Overall, the workflow capabilities have surpassed what teams could previously accomplish, with over 6,000 deployments in the past six months. “We've definitely improved the quality and efficiency of the products we're building because we can leverage all the tools of GitLab, and we've definitely improved the efficiency of our teams,” Benstead added.\n",{"template":950,"size":36,"region":106,"industry":91},"content:en-us:customers:potato-london.yml",{"_path":4650,"content":4651,"config":4695,"_id":4696},"/en-us/customers/radiofrance",{"name":4652,"logo":4653,"hero":4654,"heroImage":4655,"benefits":4656,"industry":2358,"employeeCount":2601,"location":4666,"solution":1250,"stats":4667,"headline":4675,"summary":4676,"quotes":4677,"content":4682,"contributors":1281},"Radio France","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518006/xsdficohc8jkuqq12tr0.svg","Radio France deploys 5x faster with GitLab CI/CD","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518453/njkdptblohzbo2vhb2ww.jpg",[4657,4660,4662],{"metric":1521,"config":4658},{"icon":4659},"ClipboardTestAlt",{"metric":1732,"config":4661},{"icon":2451},{"metric":4663,"config":4664},"Year-over-year cost savings",{"icon":4665},"Money","Paris, France",[4668,4669,4672],{"value":2985,"metric":1032},{"value":4670,"metric":4671},"70%","annual cost savings",{"value":4673,"metric":4674},"82%","decrease in cycle time","Radio France adopted GitLab CI to minimize context switching and accelerate deployments.","Radio France adopted GitLab CI/CD after success with code management.\n",[4678],{"quoteText":4679,"author":4680,"authorTitle":4681,"authorCompany":4652},"That was the main goal that we had - to reunify multiple tools into a single one and make it really easy for developers to deploy to production. We were at 10 per day before the migration. Now with GitLab, we do 50 deployments per day in production, which is way more efficient than when we had to switch between GitLab and Jenkins.\n","Julien Vey","Operational Excellence Manager",[4683,4686,4689,4692],{"header":4684,"text":4685},"French public radio broadcaster","Radio France is a French public service radio broadcaster serving seven stations throughout the country. Radio France designs, builds, and operates websites, mobile applications, APIs, podcasts, voice assistant skills, and audio streaming platforms.\n",{"header":4687,"text":4688},"Configuration issues and context switching","Radio France was using GitLab for Git and Jenkins for the production builds, product images, and all the deployments. Developers were constantly switching between GitLab for source code and Jenkins for all the production builds. The teams at Radio France wanted a way to merge the two technologies in order to avoid constant context switching. Ideally, developers wanted a single solution that could be used for code management and deployment.\n\nThere were also configuration issues with Jenkins. All of the jobs were configured by the CI/CD team, so developers couldn’t make any changes with production deployments. Developers wanted to be able to own their own code without having to wait for permissions from the CI/CD team.\n\n“We wanted developers to manage their own way of deploying to production. Each team, each project, they don’t have the same culture. We deploy websites. We deploy APIs. We deploy a lot of things. We don’t all have the same challenges,” said Julien Vey, Operational Excellence Manager.\n\nAccording to Vey, Jenkins is a very static workflow. Developers were unable to customize their projects or add new functionalities easily. The new solution they needed would also have to provide easy integration, customizable jobs, and offer new features without an excessive amount of management.\n",{"header":4690,"text":4691},"One solution for code management and CI/CD","Since teams were already happily using GitLab for [source code management](https://about.gitlab.com/solutions/source-code-management/), they didn’t have to look far for a solution that also provides [CI/CD](https://about.gitlab.com/solutions/continuous-integration/). Developers quickly moved everything into a GitLab pipeline in order to start deploying code to production in one place.\n\nRadio France has a lot of teams working on a lot of different projects. Each team manages their own set of services — some teams are up to 20 services. Each service is now in its own GitLab project.\n\n“We just used the CI/CD part of GitLab because we already had GitLab that just works. We are embedded within the tools so that we don’t have to switch to other tools for [deployment]. The main thing that we like about GitLab is working in a single tool,” Vey stated.\n",{"header":4693,"text":4694},"Faster deployments, improved collaboration","Radio France’s technology stack includes PHP, React, NodeJS, Svelte, Golang, RabbitMQ, and PostgresQL. All their applications are running on a microservice architecture, built on top of Kubernetes. The teams run multiple instances of GitLab runners, which allows them to perform upgrades without interruption. GitLab is running in a virtual machine on AWS, [using Terraform and Ansible to manage it](https://about.gitlab.com/topics/gitops/gitlab-enables-infrastructure-as-code/). They use Kops to manage Kubernetes clusters on top of AWS. They are able to manage multiple instance groups that match AWS auto scaling groups.\n\nGitLab CI has enabled Radio France to add tests to their websites, including lighthouse, UI, and web bottle tests that they previously were unable to implement with Jenkins due to both cost and time management challenges.\n\nPreviously, the teams were using two instances of 64G full time with Jenkins runners, which cost approximately $1,100 monthly. With GitLab, teams are using between one to eight spot instances, but only for about 10 hours a day at a cost of about $300 a month. “This makes a cost savings of 70% on our CI/CD costs,” Vey added.\n\n“The great benefit of GitLab is that before we were going from five or six minutes for just deploying production. Now, when the build is already done with GitLab, I think it only takes 20 seconds to deploy on any environment,” Vey said. This created an 82% reduction in cycle time over the team’s previous deployments using Jenkins.\n\nOverall workflow and collaboration has improved since they made the switch from Jenkins, allowing developers to manage the platform less and customize features more than they previously could. “With Jenkins, it was a very static workflow. We couldn’t customize it the way we wanted. It was really hard to add new functionalities,” Vey said. “Now with GitLab, we have huge flexibility and we can make the platform available for people to use without thinking a lot, just deploy it and people can use new features.”\n\nEach team is responsible for its own pipeline now. Developers can decide if, how, and when they want to deploy to production. Radio France has implemented all the tooling that is required for a developer to make their own choice.\n",{"template":950,"size":44,"region":106,"industry":91},"content:en-us:customers:radiofrance.yml",{"_path":4698,"content":4699,"config":4755,"_id":4756},"/en-us/customers/red-sea-global",{"name":4700,"logo":4701,"hero":4702,"heroImage":4703,"benefits":4704,"industry":4715,"employeeCount":4716,"location":4717,"solution":4718,"stats":4719,"headline":4727,"summary":4728,"quotes":4729,"content":4742},"Red Sea Global","https://res.cloudinary.com/about-gitlab-com/image/upload/v1761242184/ppnn3ef4hclnta7sf0sh.png","Red Sea Global powers vision with AI-driven speed and security from GitLab\n","https://res.cloudinary.com/about-gitlab-com/image/upload/v1761242314/mkv84uqea2xy0gglywn6.jpg",[4705,4709,4712],{"metric":4706,"config":4707},"Speeding code development with AI",{"icon":4708},"Eyebrow",{"metric":4710,"config":4711},"Delivering better products faster",{"icon":1852},{"metric":4713,"config":4714},"Reduced security and compliance risks",{"icon":239},"Real Estate","7,000+ ","Riyadh, Saudi Arabia","GitLab Ultimate and GitLab Duo Enterprise",[4720,4722,4724],{"value":1402,"metric":4721},"reduction in MTTR",{"value":1402,"metric":4723},"reduced developer onboarding time",{"value":4725,"metric":4726},"900%","increase in feature delivery","As a cornerstone of Saudi Arabia's Vision 2030 initiative, Red Sea Global focuses on responsible development through partnerships with global innovators.","The company develops luxury regenerative tourism destinations that combine sustainability with world-class hospitality, from premier resorts to personalized customer experiences. “We are the technical arm of Red Sea Global, supporting the company's technical innovation and sustainability goals,“ said Zakaria Alsahafi, Director of Solution Development and Integration at Red Sea Global. “We know all eyes are on us. That's why we need to be able to deliver fast and always bring something new to the market.\"",[4730,4734,4738],{"quoteText":4731,"author":4732,"authorTitle":4733,"authorCompany":4700},"At Red Sea Global, technology is not just a support function — it is a catalyst for transformation. GitLab has enabled us to move with AI-driven speed while ensuring the highest levels of security and compliance. This foundation allows us to innovate with confidence, deliver value to our customers faster, and set new benchmarks for how technology can power regenerative tourism and beyond.\"","Sultan Moraished","Group Head of Technology & Corporate Excellence",{"quoteText":4735,"author":4736,"authorTitle":4737,"authorCompany":4700},"We have built a piece of software that is reshaping our customer experience. It has become a key business driver. We built it faster, more efficiently, and more collaboratively because we are all in with GitLab.\"","Mohamed ElFayomy","Associate Director for Automation and Integration",{"quoteText":4739,"author":4740,"authorTitle":4741,"authorCompany":4700},"Automation has become more than just a process for us — it acts like a co-worker. By extending automation into IT services, we've been able to scale, secure, and simplify operations, freeing our teams to focus on higher-value work.\"","Ammar Alsanani","Senior Specialist for Automation and Integration",[4743,4746,4749,4752],{"header":4744,"text":4745},"From growth opportunities to strategic transformation","As Red Sea Global's development organization expanded, leadership evaluated ways to optimize its approach. Each team had adopted tools that worked well individually, including Bitbucket, Jenkins, GitHub, and Nexus, but the organization was ready to scale more strategically. \n\nLeaders wanted to improve coordination between teams working on related projects and consolidate tool management across the expanding organization. They also aimed to accelerate new developer onboarding with standardized processes, unify security practices to meet enterprise standards, automate manual processes to increase velocity, and implement systematic compliance documentation to meet ambitious delivery goals. \n\n“We recognized that standardization would improve our teams' effectiveness,\" said Alsahafi. “We wanted to get everyone working together in a single DevSecOps platform that could support our growth.” Red Sea Global adopted GitLab Ultimate to consolidate its entire software development lifecycle.\"",{"header":4747,"text":4748},"Accelerating development with AI-powered features","Red Sea Global's teams quickly embraced GitLab Duo AI capabilities as a core part of their development approach. “Our developers were excited about using AI from the start, and they keep giving us ideas for other ways we can use it,” notes Alsahafi. \n\n“Duo isn't just making us faster, it's making us more efficient and productive,” says Alsahafi. “It's helping us analyze our code, solve problems, and even onboard new developers with greater speed and confidence.”\n\n**GitLab Duo now supports multiple critical functions across the teams' development lifecycle:**\n- **Code Development** with autogenerated unit tests, context-aware code suggestions, and intelligent refactoring guidance.\n- **Quality Assurance** with automated merge request summaries, bug triage assistance, and AI-powered root cause analysis.\n- **Security Operations** with vulnerability explanation, remediation recommendations, and continuous monitoring of dependency risks.\n- **Troubleshooting** with rapid diagnosis of build failures, environment drift, and integration errors.\n- **Project Documentation** with AI-generated technical documentation, architectural summaries, and knowledge sharing across teams.\n- **Developer Onboarding** with context-aware guidance that explains unfamiliar codebases and accelerates new engineers' productivity.",{"header":4750,"text":4751},"Extending Automation to Operations Activity","Red Sea Global extended its automation journey far beyond software development into IT operations. Today, routine service requests that once required manual coordination are delivered through automated, governed workflows that ensure speed, security, and consistency. \n\nFrom provisioning infrastructure and configuring environments to managing employee access and day-today operational changes, processes are now executed automatically once approvals are in place. Every action follows clear governance policies, is performed securely, and leaves a full audit trail for transparency. \n\nThe impact has been transformative. What previously demanded significant manual effort is now completed in minutes, at scale, and with far greater reliability. By applying automation principles to IT services, Red Sea Global has dramatically increased efficiency, reduced risk, and freed teams to focus on higher-value work.",{"header":4753,"text":4754},"Comprehensive Results Across the Organization","These improvements delivered measurable results across the organization. Feature delivery increased by 90% within the first quarter, while deployment time reduced from weeks or months to days. Project delivery now consistently meets 3-month targets with zero project cancellations due to missed deadlines since implementation.\n\n**Platform Consolidation Benefits:**\n- Eliminated GitHub, Bitbucket, Jenkins, and Nexus entirely\n- Single source of truth for 160+ active projects \n- Streamlined tool management and maintenance\n- Reduced context switching for developers\n\n\n**Improved Team Collaboration:**\n- 20+ engineering teams now work in a unified environment \n- Elimination of tool management overhead \n- Enhanced visibility across all project phases\n\n\n**Enhanced Development Capabilities:**\n- Unit test coverage jumped from 10% to 98%\n- Automated security scanning integrated into pipelines\n- GitLab Duo AI assistance for code generation and review \n- Comprehensive compliance documentation and tracking\n\n\"From the first month with GitLab, we saw improvements,\" Alsanani shared. \"GitLab is the framework that brings all our teams and projects together. That's helping our business because we've greatly reduced our time to market. It makes us more agile and more competitive.\" \n\nRed Sea Global plans to expand its GitLab implementation with organization-wide compliance dashboards, fully automated security processes, and GitLab Duo access for all engineering teams. \n\nFor an organization supporting Saudi Arabia's tourism development goals, this technological foundation provides the speed, security, and collaboration needed to deliver high-quality experiences in the luxury travel sector.",{"template":950,"size":44,"region":106,"industry":91,"showInResults":6},"content:en-us:customers:red-sea-global.yml",{"_path":4758,"content":4759,"config":4801,"_id":4802},"/en-us/customers/remote",{"name":112,"logo":4760,"hero":4761,"heroImage":4762,"benefits":4763,"industry":89,"employeeCount":4772,"location":112,"solution":2053,"stats":4773,"headline":4781,"summary":4782,"quotes":4783,"content":4788},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1745517949/nxfflxztnkohb9r0d8u1.svg","How Remote meets 100% of deadlines with GitLab","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518426/xz6woikubtbcf6bqavbn.jpg",[4764,4767,4770],{"metric":4765,"config":4766},"Quick iterations",{"icon":971},{"metric":4768,"config":4769},"Zero context switching",{"icon":2553},{"metric":1843,"config":4771},{"icon":1845},"10",[4774,4776,4778],{"value":1308,"metric":4775},"Deadlines met",{"value":1308,"metric":4777},"Focus on product",{"value":4779,"metric":4780},"3,795","Code pushed in the last three months","Remote uses GitLab as a single source of truth, iterating fast from ideation to delivery.","With just one year under its belt, Remote is improving global employment with GitLab SCM and CI/CD.\n",[4784],{"quoteText":4785,"author":4786,"authorTitle":4787,"authorCompany":112},"Within a year, we never had a case of not meeting a deadline because we had to spend time working on the CI pipeline or something related to the tooling. That has never been the case.\n","Marcelo Lebre","Co-founder And CTO",[4789,4792,4795,4798],{"header":4790,"text":4791},"Solving global employment","Remote is a global organization that provides a platform to employ anyone anywhere in the world. The company started just one year ago completely from scratch with the goal to reform the way global employment works. [Remote](https://remote.com/) helps to place employees with full-time working roles, as opposed to contract or freelance positions like most remote opportunities. It creates a solution to employ people in different countries, acting as a global employer of records.\n",{"header":4793,"text":4794},"Avoiding multi-toolchains and unnecessary costs","A startup is a challenge in and of itself, but being a startup with the premise of global organizational employment is an even bigger ambition. The company is dependent upon productivity and they wanted a tool that would provide operational efficiency and enhanced product delivery. Remote is a lean team and when they expand, they’ll need a tool that will scale with them.\n\nBecause Remote depends on communication worldwide, the development team needed a tool for source code management and continuous integration. “There is one underlying need or requirement that I have for the projects that I manage and Remote isn’t an exception. It is that from the ideation step to the delivery, it needs to be as smooth as possible and as fast as possible,” said Marcelo Lebre, co-founder and CTO of Remote. “Any deviation to this sort of stream by any measurement, even if it’s very small, is very costly to the whole company and to the people themselves because it translates into waste and waste is inefficiency.”\n\nLebre and his team have all had previous experience working with multi-toolchains and understand the added amount of time, cost, and work needed. With multiple tools, smaller startups usually have to manually code, test, and deploy or wire it all together explicitly. A developer’s time would be spent configuring and managing the various tools. If one tool breaks, it negatively impacts the whole system, sidetracking the engineering team.\n",{"header":4796,"text":4797},"Building a startup with GitLab","Building [speed with a startup](https://about.gitlab.com/solutions/startups/) usually requires a variety of software tools. According to Lebre, “Every small startup had to use a plethora of tools. They had to use things like Codeship, Trello, Basecamp, Asana, or Jira … We’ve used them all together to make sure that you could ship something, and iteratively, because otherwise what I saw in smaller startups was that they would have to do all the things by hand.”\n\nMembers of the Remote team had previously used GitLab and came to the conclusion to use the platform once again fairly quickly. “To be honest, when we started Remote it was already a no-brainer. I have been using GitLab for many years already. So I mean, there’s no competition there,” Lebre said. The threshold to get started with other tools was much higher because it meant picking out individual tools for individual services. Since the team was comfortable with GitLab, it helped get the start-up moving faster than had they chosen another platform.\n",{"header":4799,"text":4800},"Operational efficiency, on-time deliveries, and zero maintenance","From the very inception, Remote has used GitLab. The entire small company is using the platform, both developers and non-developers, with the intention to expand and maintain GitLab as the infrastructure. For now, Remote has one software in one location and focuses on quick iterations.\n\nThe issues used in GitLab are the single source of truth and because team members are all remote, this keeps everyone in the loop. Almost zero time is spent managing the tool with the ability to link directly between the issues to code and the pipeline allows a continuous visibility and workflow. “GitLab has made it easier to be a remote company because we document everything and make sure all our code and product is visible in GitLab,” Lebre said. “Through GitLab, we have full observability over our delivery speed and iteration process so that we can optimize where we need to.”\n\nThe development team has eliminated the [need for a multi-toolchain](https://about.gitlab.com/customers/knowbe4/) by using GitLab for SCM and CI/CD. “We pride ourselves for not making people overwork. Engineering is a craft, I believe in that, and making people work overtime reduces the quality of that craft,” Lebre said. “If I use four tools to do the same as I do with GitLab, it means that the team is spending time managing those tools and jumping off and on from those tools. So either we work more hours, or we ship less. Those two options are not something that I looked forward to as a manager.”\n\nRemote developers spend 100% of their time working directly on the product. Lebre and his team appreciate the transparent end-to-end platform, negating any possibility of being blindsided by an issue, which has allowed them to meet deadlines 100% of the time. In the last three months, the team has shipped over 540 merges to production and engineers have updated code 3,795 times. “I can say that GitLab and the full suite has been an enabler, and never a problem we had to fix,” Lebre said.\n",{"template":950,"size":36,"region":114,"industry":91},"content:en-us:customers:remote.yml",{"_path":4804,"content":4805,"config":4846,"_id":4847},"/en-us/customers/siemens",{"config":4806,"name":4807,"logo":4808,"hero":4809,"heroImage":4810,"benefits":4811,"industry":89,"employeeCount":3855,"location":4819,"solution":4820,"stats":4821,"headline":4828,"summary":4829,"quotes":4830,"content":4833},{"hideGitlabLogo":199},"Siemens","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745517951/m6l8veud9alpk60bhjsu.png","How Siemens created an open source DevOps culture with GitLab","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518426/rkwyekumeiverghtfp9u.jpg",[4812,4814,4817],{"metric":1574,"config":4813},{"icon":902},{"metric":4815,"config":4816},"Cost and time savings",{"icon":1247},{"metric":1293,"config":4818},{"icon":1385},"190 Countries","GitLab Free",[4822,4825],{"value":4823,"metric":4824},"40,000+","GitLab users",{"value":4826,"metric":4827},"6.4M+","builds per month","Siemens uses GitLab for improved developer efficiency and customer satisfaction.","Siemens transformed its collaboration and organizational workflow with GitLab SCM, CI/CD, and DevOps.\n",[4831],{"quoteText":3321,"author":3322,"authorTitle":4832,"authorCompany":4807},"Software Architect at Siemens Smart Infrastructure",[4834,4837,4840,4843],{"header":4835,"text":4836},"Worldwide innovation pioneer","Siemens was founded in 1847 as a “backyard machine shop” in Berlin, Germany. Siemens AG (Berlin and Munich) is a global technology powerhouse that has stood for engineering excellence, innovation, quality, reliability, and internationality for more than 170 years. Active around the world, the company focuses on intelligent infrastructure for buildings and distributed energy systems and on automation and digitalization in the process and manufacturing industries.\n\n[Siemens](https://www.siemens.com/global/en.html) brings together the digital and physical worlds to benefit customers and society. Through Mobility, a leading supplier of intelligent mobility solutions for rail and road transport, Siemens is helping to shape the world market for passenger and freight services. Via its majority stake in the publicly listed company Siemens Healthineers, Siemens is also a world-leading supplier of medical technology and digital health services.\n\nIn addition, Siemens holds a minority stake in Siemens Energy, a global leader in the transmission and generation of electrical power that has been listed on the stock exchange since September 28, 2020. In fiscal 2019, which ended on September 30, 2019, the Siemens Group generated revenue of €58.5 billion and net income of €5.6 billion. As of September 30, 2019, the company had around 295,000 employees worldwide on the basis of continuing operations.\n",{"header":4838,"text":4839},"Large-scale company with large-scale needs","With over 20,000 developers, Siemens is divided into multiple organizations acting within different domains, mainly focused on business-to-business initiatives. According to Fabio Huser, Software Architect, the challenge was, “How do we build a DevOps culture around this really fractured federalistic company structure?”\n\nSiemens needed a DevOps platform that offered collaboration, transparency, and proper code management to achieve their goal: A community for employees around the world, and a single source of truth for code. In order for a tool to be successful, Siemens required developers to have a collaborative mindset, full stack engineering knowledge, experience as an open source contributor, and a scalable platform that can be used to build upon itself. The vision for an improved workflow included the ability to collaborate on code and share it within minutes, speed up time to market, empower people to own their own code, and set the technological foundation for future business models.\n",{"header":4841,"text":4842},"Adopting open source first","A small team within Siemens adopted GitLab in 2013 for collaboration and version control to develop Linux based embedded devices. In a typical grassroots approach, the team opened the platform for the whole company and scaled it up to over 40,000 users. The DevOps platform provides a place for different teams to work on the same project with the ability to share code within minutes and to collaborate easily across the world.\n\n“The open source world comes up with new tools every week. But at the end of the day, we really try to solve it like a human issue. We want to collaborate, and the tool is just a secondary thing after all,” Huser said. “Thanks to GitLab, we found a tool which facilitates this ideology. It's all about the people behind it and to maintain this idea and also have this community spirit within Siemens, you really need to establish such a community.”\n\nIn 2015, the code.siemens.com team shifted its focus to DevOps CI/CD, calling its specific workflow style “junkyard computing” in the early days to enable integration builds for open source components. “Thanks to the ease of use of the GitLab runner, you can set up new machines in a matter of minutes,\" according to Huser. \"If you have old machines laying around and you have a good enough set up in terms of network, you can literally set up new runners, new capabilities in a minute. It's quite cost effective.”\n",{"header":4844,"text":4845},"Code, collaboration, and community","Today, code.siemens.com has its [IT infrastructure on AWS](/blog/from-monolith-to-microservices-how-to-leverage-aws-with-gitlab/){data-ga-name=\"infrastructure on aws\" data-ga-location=\"customers content\"}. There is no longer a need for “junkyard computing” because code.siemens.com is a fully established service with a large in-house developer community provided by the Siemens IT organization.\n\nThe infrastructure evolved to a highly tuned and sophisticated setup, with a large amount of EC2 instances all managed as [Infrastructure as Code](/topics/gitops/infrastructure-as-code/){data-ga-name=\"infrastructure as code\" data-ga-location=\"customers content\"}. SaaS solutions such as S3, RDS, ElastiCache, EFS, and ELB are used as well, since those can be replaced by standard open source solutions to minimize vendor lock-in. GitLab is hosted on AWS, also the supporting services such as GitLab CI runners, monitoring, logging, crash reporting and more.  Siemens has exceeded over 38 million CI builds since adopting GitLab. “If you're part of Siemens you have different repositories you can collaborate with. We really try to bring the open source culture in and so far, we really succeeded. With CI/CD we have one and a half million builds every month. The whole culture has completely changed,” Huser said.\n\nWith GitLab, Siemens saves both time and money because there is no need to maintain local patches or manually update fixes. The code.siemens.com team follows an ‘upstream first’ workflow. “We go without patches. We only deploy upstream versions, nothing else. If we want to have new features, we contribute them to GitLab. We do not patch our instance,” said Roger Meier, Principal Key Expert and Service Owner of code.siemens.com from Siemens IT. “As soon as they are merged upstream, we will deploy the next version. So we ship every month. We do about four production deployments per month.”\n\nThe code.siemens.com platform is managed by a team of just eight people distributed across four countries in a highly agile fashion. All team members are committed to the open source way of working. They are coaching, supporting, and guiding the internal developer community, on top of managing the whole infrastructure and application. They use GitLab day by day to manage all their activities. All team members contribute and/or maintain several open source projects, while providing a reliable service for the wider Siemens developer community to increase developer happiness.\n\nCollaboration happens throughout the entire organization with over 40,000 GitLab users and the potential to expand. GitLab helps Siemens ensure scalability internally and with customer development opportunities. “Our customers and our developers just want to have a reliable service that is running all the time,” Meier added.\n\nSiemens teams heavily contribute to GitLab with over 150 merged MRs in GitLab. In addition, Huser and Meier are [GitLab Heroes](https://contributors.gitlab.com/docs/previous-heroes){data-ga-name=\"heros\" data-ga-location=\"customers content\"} and were selected as [GitLab MVPs](https://contributors.gitlab.com/docs/notable-contributors){data-ga-name=\"mvps\" data-ga-location=\"customers content\"}. The teams not only use the DevOps platform, but they pride themselves with being so knowledgeable that they don’t use a support team from GitLab. “Since the beginning, we were talking about all our ideas and to have our roadmap visible for all the people within the company. You have to walk the talk, that's key. Of course, focus on your customers: for developers, from developers,” Meier said.\n",{"template":950,"size":44,"region":106,"industry":91},"content:en-us:customers:siemens.yml",{"_path":4849,"content":4850,"config":4902,"_id":4903},"/en-us/customers/sigma-defense",{"name":4851,"logo":4852,"hero":3429,"heroImage":4853,"benefits":4854,"industry":290,"employeeCount":4864,"location":4865,"solution":913,"stats":4866,"headline":4875,"summary":4876,"quotes":4877,"content":4881},"Sigma Defense","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518007/ea3y7qwzjrrzxio642vr.png","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518453/co5ozf9ydaqmoawrkxkp.jpg",[4855,4857,4860],{"metric":1293,"config":4856},{"icon":909},{"metric":4858,"config":4859},"Increased project visibility",{"icon":1526},{"metric":4861,"config":4862},"Broadened access to talent pool",{"icon":4863},"Handshake","900","Perry, Georgia",[4867,4870,4872],{"value":4868,"metric":4869},"97%","reduction in time to fix bugs",{"value":1402,"metric":4871},"reduction in software factory setup cost",{"value":4873,"metric":4874},"98%","reduction in onboarding time","Sigma Defense is a leading technology company serving the Department of Defense (DoD), and civilian organizations, providing ground, air, and space-based systems and services, like communications, intelligence, and reconnaissance.","The company’s pivotal move to make GitLab the center of its DoD-focused DevSecOps environment, called [Black Pearl](https://about.gitlab.com/blog/u-s-navy-black-pearl-lessons-in-championing-devsecops/), helped them tame software factory sprawl, boost collaboration, and expand access to a wider talent pool, while dramatically increasing production speed.",[4878],{"quoteText":4879,"author":4880,"authorTitle":4277,"authorCompany":4851},"If there’s a vulnerability in a critical system on a Naval ship, we can’t wait two years to fix it. It’s essential to national security that we do it in days, if not hours. GitLab is fundamental to how we do that.","Josh Metheney",[4882,4884,4887,4890,4893,4896,4899],{"text":4883},"Based in Perry, GA, [Sigma Defense](https://sigmadefense.com/about-sigma/) has approximately 800 employees, with more than a dozen locations around the globe. The company builds and deploys command and control software for the U.S. Navy’s Aegis system, autonomy software for unmanned vehicles, and communication systems for F-18 supersonic aircraft.\n\nSigma Defense’s customers depend on them to quickly, efficiently, and securely provide them with software and systems that are critical to U.S. national security. The organization is tasked with building advanced solutions that stay ahead of emerging threats, and accelerate information collection and sharing for faster decision-making and better mission outcomes.",{"header":4885,"text":4886},"Solving software factory sprawl","Before Sigma Defense first adopted GitLab early in 2021, the company was weighed down with a growing sprawl of software factories, an umbrella term for DevOps tools and processes, the people who use them, the buildings they work in, and even the ships, planes, and unmanned vehicles the software works in. For each new project the company began working on, a new software factory had to be spun up with team members choosing their own tools, which created a costly duplication in time, infrastructure, and investment. It also meant [silos](https://about.gitlab.com/blog/too-many-toolchains-a-devops-platform-migration-is-the-answer/) were repeatedly popping up across the organization, prohibiting different teams from working together and sharing a common place for reusable code to live—bridling their productivity, efficiency and speed.\n\nSigma Defense, working with the Navy’s IT services team, PEO Digital, created the DevSecOps environment, Black Pearl, to eliminate that duplication and the silos and complexities that came along with it. [GitLab’s AI-powered, end-to-end DevSecOps platform](https://about.gitlab.com/) is at the heart of that new environment, dismantling silos, fueling collaboration, and speeding software development and delivery—all while more easily and efficiently meeting compliance regulations.\n\nGitLab, in essence, gives Black Pearl its DevSecOps capabilities and a single platform to power its pipelines and tools. Automated security scanning is conducted, and software planning, development, testing, documentation, and deployment all occur within GitLab. By using GitLab, DevSecOps teams from across Sigma Defense now can work together on projects, visualize progress and bottlenecks, help create efficiencies, and speed secure software to deployment.\n\nAfter adopting GitLab, the organization saw benefits in both time and money. For instance, the time it takes to set up software factories was cut from about six months to three to five days. As for the cost of software factory deployments, that was slashed 90%, going from about $4 million to $400,000.\n\n“GitLab is the core of our DevSecOps capabilities. It’s where we go to develop, deliver, and work together. It’s where we get things done,” says Josh Metheney, director of engineering at Sigma Defense, noting that they upgraded from GitLab Premium to GitLab Ultimate in 2022. “GitLab and DevSecOps are synonymous at Sigma Defense and are critical to the success of Black Pearl and the Sigma Defense team.”",{"header":4888,"text":4889},"Deploying critical software goes from 3 months to 3 days","Black Pearl, with GitLab at its core, has become pivotal to creating and deploying mission-critical software systems onboard U.S. Naval ships. When ships are at sea for months at a time, the Navy needs to be able to continuously update their software systems, fixing vulnerabilities, adding capabilities, and responding to feature needs.\n\n“The legacy approach to software updating was basically like cutting a hole in the ship, pulling out racks of hardware, and dropping in new ones,” says Metheney. “Now with GitLab, it is much easier to update the software, push it through the CI/CD pipeline up into the cloud and down to the ship onto the existing hardware.”\n\nFor the Naval project, the DevSecOps team simply took Black Pearl and built project-specific processes on top of it. “If there’s a vulnerability in a critical system on a Naval ship, we can’t wait two years to fix it,” he adds, noting that with GitLab, the time it takes for discovery and remediation of bugs has gone from months to days. “It’s fundamental to national security that we do it in days, if not hours. GitLab is fundamental to how we do that.”",{"header":4891,"text":4892},"Boosting collaboration and visibility","A multitude of software factories, and the silos that came along with them, had caused a lot of challenges and headaches for Sigma Defense and the broader DoD. For example, without a common environment that all teams could use—and a platform to power it—DevSecOps team members had no way to come together to support each other and work jointly on projects, sharing ideas, experiences, and best practices. Now with GitLab as the foundation of Black Pearl, there are far fewer pockets of people duplicating efforts, and collaboration has become the norm. DevSecOps team members from across the country can collaborate, expediting projects and dramatically increasing efficiencies.\n\n“[Collaboration](https://about.gitlab.com/blog/5-ways-collaboration-boosts-productivity-and-your-career/) was a fundamental problem,” says Metheney. “Now we have one place for everyone to work, and all the data and capabilities are in one place. One of the powers of GitLab is that everyone and everything — the codes, the builds, the scans — are in one place. Now our people, even if they’re not in the same building or the same state or even the same division of the Navy, can work together—easily.”\n\nWith Sigma Defense’s DevSecOps teams working in Black Pearl’s GitLab-powered environment, they now also have [visibility into projects](https://about.gitlab.com/blog/three-steps-to-optimize-software-value-streams/) and workflows that they never had before. Without having to wait weeks or months for project reports to come in, teams are able to make real-time decisions about priorities and deployments. And with insight from GitLab analytics and dashboards into where bottlenecks are happening, they can jump in, fix problems, and move projects forward.",{"header":4894,"text":4895},"Broadening access to a strong talent pool","Before adopting GitLab and creating Black Pearl, silos meant that project team members had to be physically located in the same geographic area. There was no way for them to collaborate unless they were sitting in the same building. That dramatically narrowed the talent pool.\n\nWith GitLab, everything from project planning, development, and code and security scanning all are done in one environment that is accessible to team members using Black Pearl in any geographic location. “Regardless of what building or state they’re in, they can work together in GitLab,” says Edward Anderson, executive vice president of Innovative Mission Solutions at Sigma Defense. “We can bring in external people with new ideas and new approaches to reinvigorate the community and production—without concern for where they’re located. Now we have more opportunities for innovation.”\n\nWith GitLab, Sigma Defense has expanded the areas where developers working for the company can be located from two locations to anywhere across the nation.  As a result, the company is able to offer a broader and richer pool of talent to its customers.",{"header":4897,"text":4898},"Easing compliance efforts","Working so closely with the DoD means the software that Sigma Defense develops must be fully [compliant](https://about.gitlab.com/blog/meet-regulatory-standards-with-gitlab/) with government laws, regulations, and standards, like the National Institute of Standards and Technology's  Secure Software Development Framework (SSDF). A significant benefit of using GitLab is that they now are better, and more easily, prepared to meet those regulations, avoiding making expensive software modifications, struggling to find needed project documentation, and potentially losing contracts because of compliance failures.\n\nA major piece of [being compliant](https://about.gitlab.com/blog/meet-regulatory-standards-with-gitlab/) is being able to predictably and consistently supply the needed information to prove it. Metheney says they have a leg up with that because working on GitLab’s end-to-end platform means all of their information—whether it’s data on security scans running in necessary pipelines, automated security practices, or approvals on merge requests—all can be found, and aggregated, in one place.\n\n“Being able to visualize, enforce, and report on compliance is something GitLab enables us to do,” says Metheney. “Before we were using different tools so scan results might be here or there. Sometimes they’d be put into a spreadsheet and that would get emailed around. Now we have one place where we're collecting and organizing all of that data. It’s incredibly helpful to have everything in one spot so we have one source of truth.”",{"header":4900,"text":4901},"Expanding their use of GitLab and Black Pearl","Metheney notes that since they’ve found success with GitLab-powered Black Pearl at the center of their DevSecOps capabilities, they are looking to expand use of it to U.S. intelligence agencies and across the DoD. Black Pearl, for instance, has been granted Authority to Operate by the Navy and the U.S. Marine Corps through reciprocity. Sigma Defense is working with the Army to deliver the same capabilities.\n\nEarly in 2024, the company launched Sigma Software Studio, a DevSecOps platform, which also has GitLab at its center. It is aimed at expanding Sigma Defense’s footprint into civilian agencies, as well.\n\n“With GitLab at its core, Black Pearl is a critical piece of our software development,” says Anderson. “It’s a core value prop. When we see an opportunity that involves software development, we know they should just use the platform and then they can skip the hard, repetitive parts of software development and move right to the creative part.”",{"template":950,"size":40,"region":102,"industry":79},"content:en-us:customers:sigma-defense.yml",{"_path":4905,"content":4906,"config":4947,"_id":4948},"/en-us/customers/signicat",{"name":4907,"logo":4908,"hero":4909,"heroImage":4910,"benefits":4911,"industry":89,"employeeCount":4920,"location":4921,"solution":975,"stats":4922,"headline":4927,"summary":4928,"quotes":4929,"content":4934,"contributors":1281},"Signicat","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518007/uu3itzdt6a2wom0oddfz.png","Signicat reduces deploy time from days to just minutes","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518454/hgbaejhxc3agwil1qhvs.jpg",[4912,4915,4917],{"metric":4913,"config":4914},"Rapid pipeline deployment",{"icon":4259},{"metric":1293,"config":4916},{"icon":1295},{"metric":4918,"config":4919},"Easy scalability",{"icon":1636},"400+","Trondheim, Norway",[4923,4925],{"value":3960,"metric":4924},"daily builds",{"value":4269,"metric":4926},"increase in developer team","Quick development and deployment of reliable identity services was a must-have at Signicat.","The company turned to GitLab Premium SaaS to power onboarding and drive collaboration.\n",[4930],{"quoteText":4931,"author":4932,"authorTitle":4933,"authorCompany":4907},"The ability to react to change quickly is extremely valuable for a scaling company like ourselves. We are seeing a lot of collaboration around GitLab CI/CD and pipelines.\n","Jon Skarpeteig","Vice President for Cloud Architecture",[4935,4938,4941,4944],{"header":4936,"text":4937},"A market-leading European digital identity solutions provide","[Signicat](https://www.signicat.com/) is a market-leading European digital identity solutions provider that has aggressively extended its capabilities, both organically and through acquisitions, to create a full line of identity management tooling, including identity proofing solutions, a suite of electronic signature solutions, and advanced authentication. Clients, partners and customers include Fortune 500 banks and financial services, government and health services, payments, insurance and other industries. While supporting more than 30 national identity methods, Signicat enables digital transformation in regulated and unregulated industries.\n\nThe company’s software services focus on essential use cases, including trustworthy digital onboarding and reboarding, identity verification and authentication, risk and compliance management, and fraud detection. Capabilities have been expanded, just as the threat surfaces of modern B2B and B2C applications have expanded. This is particularly crucial as clients focus their efforts on better knowing, identifying, and protecting their customers, especially during the COVID-19 pandemic. Advanced use of cloud-native software development methods underlies Signicat’s efforts to meet the evolving needs for ever-better digital identity technologies and building a trusted digital world.\n",{"header":4939,"text":4940},"Achieving rapid, secure deployment while improving service deliveries","The challenge Signicat faced were manual processes which needed to be automated, and fragmentation across tooling in different teams. Signicat also needed a solution to continually expand as the business grew, which called for an exceptionally cohesive integration architecture — one that must adhere to the strictest standards of governance and compliance. The need to continue promoting collaboration across diverse working teams was also important. It was important to know the status of work, and which person or team could help on specific code dependencies.\n\nDevelopment leaders looked for an overarching platform that allowed them to move quickly, and to, in effect, accomplish more with less. What they needed was a DevOps platform that future-proofed them and aligned with their ambitious roadmap. To get there, they went with GitLab to achieve rapid, dependable, development cycles and scalable performance through various peaks of operations.\n",{"header":4942,"text":4943},"Scalability, visibility, and enhanced integration","GitLab Premium SaaS, ideally suited for scaling organizations and multi-team use, is used to improve the developer experience, while enhancing productivity. Developers are onboarded quickly, enabling them to get important workloads up and running. Scalable, reliable, and predictable build timetables also help fine-tune operations. GitLab enables integration with a variety of static application security testing and other popular third-party tools, which is especially crucial to a company that routinely adds to its technology portfolio via an aggressive acquisition strategy. The platform provides visibility into project status, and supports cross-team communications. This has given developer teams more empowerment and autonomy, which had been another key objective for Signicat. Improvements in visibility also took the form of fine-grained code documentation, used for audits as part of necessary certifications and verifications. The platform also meshed well with the company’s move to containerization of software services.\n",{"header":4945,"text":4946},"Huge gains in deployment times and culture alignment","GitLab provides developer teams a platform for reliable, scalable and predictable build times. Collaboration, resourcing and planning have improved as well. “A positive thing we are seeing is in terms of GitLab support. Instead of having to set aside resources internally, we can direct our internal users to GitLab support” added Jon. One of the most noticeable and dramatic improvements since adopting GitLab is that Signicat’s deployment time has dropped from days to just minutes. It has significantly changed not only their speed to deployment but it has supported Signicat with the ability to be agile and deliver more continuously. GitLab’s dedication to transparency and openness in its technology roadmap is a notable plus for planning, according to Jon Skarpeteig, Signicat’s Vice-President for Cloud Architecture. “The push from the company perspective is towards containerizing everything. That is one of the reasons why GitLab was a good fit for us. It really solves containers in a very elegant way” he explains. That transparent GitLab roadmap matches Signicat’s own roadmap, providing an integrated system for source code management, continuous integration and continuous delivery of key services – including Docker and Kubernetes.\n\n“GitLab’s open culture has served us well. There is an openness about what is coming and how things get prioritized,” said Skarpeteig, adding that GitLab support is another benefit. GitLab’s support resources for Signicat’s internal developers’ free up development managers’ time. In addition, GitLab’s software supports the team’s ability to quickly react to change; which is extremely valuable for a company in rapid growth at the same time it is at the center of important trends in modern commerce and technology.\n",{"template":950,"size":40,"region":106,"industry":91},"content:en-us:customers:signicat.yml",{"_path":4950,"content":4951,"config":4997,"_id":4998},"/en-us/customers/sopra-steria",{"name":4952,"logo":4953,"hero":4954,"heroImage":4955,"benefits":4956,"industry":89,"employeeCount":4969,"location":4666,"solution":975,"stats":4970,"headline":4977,"summary":4978,"quotes":4979,"content":4984,"contributors":1281},"Sopra Steria","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518008/gdsqsjegskgyrg8fugep.svg","How GitLab became the cornerstone of digital enablement for Sopra Steria ","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518455/vlc1ypam1xkdcs9wgk0p.jpg",[4957,4961,4965],{"metric":4958,"config":4959},"Built-in security and compliance",{"icon":4960},"ComplianceAndSecurity",{"metric":4962,"config":4963},"Collaborative user experience",{"icon":4964},"CollaborationAlt3",{"metric":4966,"config":4967},"Improved software quality",{"icon":4968},"PencilCode","45,000 employees",[4971,4972,4975],{"value":978,"metric":4824},{"value":4973,"metric":4974},6,"Minutes for a full software build",{"value":4392,"metric":4976},"Developer time spent setting up CI/CD","In the midst of a digital transformation, Sopra Steria adopted GitLab as its DevOps platform of choice\n","Sopra Steria's digital transformation uses GitLab for operational efficiency, built-in security, and cloud-ready DevOps.\n",[4980],{"quoteText":4981,"author":4982,"authorTitle":4983,"authorCompany":4952},"Going into full automated DevOps is key for a software group like ours. Our GitLab instance is the cornerstone of what we call the digital enablement platform internally, which is really the means to enable our team to do cloud native development in a full automated DevOps mode.","Yves Nicolas","Group CTO Office",[4985,4988,4991,4994],{"header":4986,"text":4987},"A distinguished IT services group","\nSopra Steria is a European leader in consulting, digital services, and software development. With more than 50 years of experience, [Sopra Steria](https://www.soprasteria.com/) provides IT integration and solutions, consulting services, application implementations, technical support, and various outsourcing operations for users and applications. Their broad customer base includes leading companies from  aerospace, government, financial services, retail, transportation, utilities, and insurance sectors.",{"header":4989,"text":4990},"Steadily evolving with Git","\nSopra Steria has had several years of success using Apache Subversion (SVN) and had experienced no standout problems with the software workarounds that were in place. However, the development team felt that they needed to evolve and embrace more innovation in order to create a more progressive and robust roadmap, keeping up with competitive technologies.\n\nIn 2017, several team members were using Git independently for various projects and it became clear there was an internal need for a Git platform. “I guess the main challenge was to make sure that inside the organization we had a full-fledged Git platform that was suitable for DevOps and that all the projects would use it because we were beginning to see projects massively moving from SVN to Git as the software management system,” said Yves Nicolas, Group CTO Office, Sopra Steria. The goal was to evolve before any outstanding challenges took place and move to a consolidated, cloud-ready DevOps tool.\n\n“It was really the fact that in the state of the software development we were in three years ago, with a group of 40,000 people, about half of them were committing code. We really wanted and we needed to have a proper unified accessibility for everybody in a Git managed software platform. That's what we wanted to achieve,” Nicolas said.",{"header":4992,"text":4993},"Operational efficiency, open source, and CI are priority","\nThe team wanted a Git platform that was available to anybody in the group with credentials, using only their SSO from Sopra Steria. “It was the main requirement. The idea was that if you want to have access to one platform to share code and do some demo with usability, we want to test how it goes,” Nicolas said. “For that, it was more like testing. It was more demonstration and internal code. At the beginning, it was not necessarily for the code we provide to our customers or the code we develop for our customers.”\n\nThe teams did a comparison between Microsoft VSTS, GitHub, and GitLab. They quickly eliminated Microsoft VSTS because it was not possible to search code inside the environment. The ability to reuse code from one team to another was a necessity.\n\nGitLab was chosen over GitHub for three main reasons. (In no particular order...) One reason was cost. “The entry point for GitLab enterprise was way below what GitHub was asking for GitHub enterprise at that time,” Nicolas said.\n\nThe second reason was that GitLab has an [open source](/solutions/open-source/) version of its code and several groups already had installed a GitLab open source instance and were managing their source code with that. “We had a very good knowledge about GitLab administration inside the group. We felt a little more comfortable with that. It was easier to find people who could help us in setting up the project,” Nicolas said.\n\nThe third reason was GitLab's built-in continuous integration orchestrator. “I thought it was a very, very clever idea to have that directly inside the platform to have a complete environment where you could actually fully build, in a continuous integrated way, the software we are managing,” Nicolas said.",{"header":4995,"text":4996},"Happy developers, automated services, built-in security","\nSopra Steria began adopting GitLab in March of 2017 and by June there were about 1,000 users. Today, there are more than 9,000 team members connected. Developers are happy with this transition, which eased worry about potential turnover within the company. “One of our main challenges is keeping our best developers,\" said Nicolas. \"We want to make sure they stay with a good environment. The fact that it was obvious that this was a good environment for them to stay and have good things to say was very well perceived by the business units, the people who are actually selling to our customers over vertical business units.”\n\nSopra Steria includes more than 40,000 people, so teams using GitLab vary from one extreme to the other. Some teams are very advanced in maturity around DevOps and software development. Teams working in the company's banking software edition group are using GitLab CI, working in microservices, using templates, and developing pipelines rapidly. Other teams have very little previous knowledge of Git and have only a small amount of continuous integration in their current projects. “What's interesting is that we have found that whatever the level of the team is at in the actual knowledge of these environments, GitLab is very user-friendly to use that,” Nicolas said.\n\nThe GitLab platform has helped to establish a digital transformation culture throughout Sopra Steria. “We have been able to have advanced teams work in advance and take full-fledged advantage of the GitLab CI, and then spread their knowledge so that all the teams, even the less advanced ones, which are kind of new to Git, migrating their projects from SVN to Git, can take advantage right now with the GitLab CI environments. It is really impressive,” Nicolas said.\n\nGitLab's flexible hosting options allow Sopra Steria's large network to use a variety of cloud integrations, including Azure, AWS, and GCP. “This is kind of transparent. The way it clogs into the cloud environment is that from the GitLab instance and using the continuous integration and continuous deployment pipelines, we are deploying from GitLab to any kind of cloud at any kind of level,” Nicolas said.\n\nPrior to GitLab, security checks were done manually, requiring time and effort. Security testing is now implemented in project templates and no longer needs manual effort for each and every test. “They don't have to worry anymore about how to set up a test -- this security test makes them use it.  Sometimes they would've even skipped some tests.” Nicolas said. “Because it's easier for the user now, they have taken it for granted. It's no effort for the team, so that results in better quality software.”\n\nDevelopers have gone from having to set up their own planning processes and services that they need to roll out within their software projects, to now having these steps already formatted for them. GitLab has simplified its overall workflow and improved collaboration between teams. According to Nicolas, “It is very often confirmed by the teams that using GitLab has significantly reduced the time they needed for both setup and managing the whole software build environment and the continuous integration chain. This reduction is probably the one that is the best thing to the bottom line.”\n\nSopra Steria and GitLab have had a successful working relationship for about three years. With GitLab's release updates, Sopra Steria continues to appreciate the unified platform. “It has been confirmed over the years with the inclusion of all the DevOps related features that GitLab is a unique platform for every DevOps tool in some way,” said Nicolas.",{"template":950,"size":44,"region":106,"industry":91},"content:en-us:customers:sopra-steria.yml",{"_path":5000,"content":5001,"config":5045,"_id":5046},"/en-us/customers/surf",{"name":5002,"logo":5003,"hero":5004,"heroImage":5005,"benefits":5006,"industry":1530,"employeeCount":2657,"location":5015,"solution":975,"stats":5016,"headline":5025,"summary":5026,"quotes":5027,"content":5033,"contributors":1281},"SURF","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518010/cuvjewbrgxxkudq9pvib.svg","How SURF increased deployment speed by 1,400%","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518456/lugvjh943kjmogfobkak.jpg",[5007,5010,5013],{"metric":2045,"config":5008},{"icon":5009},"Merge",{"metric":5011,"config":5012},"Faster deployment time",{"icon":2836},{"metric":1293,"config":5014},{"icon":1895},"Amsterdam",[5017,5020,5023],{"value":5018,"metric":5019},"93%","decrease in deploy times",{"value":5021,"metric":5022},25,"min to create a product environment cluster",{"value":4269,"metric":5024},"more MRs daily","Dutch research cooperative SURF was looking for a single source of truth for the entire organization to help them improve their IT processes and better organize projects.","With GitLab, SURF found versatility and user management features that other solutions didn't provide — allowing SURF to deliver solutions to research and education communities much faster.\n",[5028],{"quoteText":5029,"author":5030,"authorTitle":5031,"authorCompany":5032},"Because of CI/CD, development and operations teams have a framework of co-operation. This is probably the highest value GitLab has introduced in our teams.\n","Giuseppe Gianquitto","Cloud Lead Architect","Research and Development Services",[5034,5037,5039,5042],{"header":5035,"text":5036},"IT supporting science research","Formed in 1974, SURF is a cooperative association that supports the national scientific and educational communities and institutions in the Netherlands and their worldwide partners like CERN. Within the field of research, SURF provides IT solutions, platforms, and architectures for data management, analytics, and computation to its members.\n\n\n[SURF](https://userinfo.surfsara.nl/) supports over one hundred institutions between medical research centers, universities, research institutes and space exploration centers across the nation. Driving innovation together. That is the mission of SURF. Together with the institutions, SURF ensures that the education and research community has access to the finest and newest Information and Communication Technologies (ICT) facilities for top research and talent development.\n",{"header":2629,"text":5038},"SURF was previously using several tools in a very scattered environment. Each team was using different platforms in various ways, including SBC, GitHub, and GitLab CE. With so many different on-premises installations per group, developers were disconnected from one another and lacked the ability to truly collaborate.\n\n\nSURF needed a solution that could act as the single source of truth for the entire organization. Teams needed one solution for user management and granular repository access. The goal was to provide an improvement of processes, an overall organization of projects, and enhanced user management capabilities.\n",{"header":5040,"text":5041},"More than a version control system","SURF was previously using GitLab primarily as a Git tool. As they researched tools for version control, they discovered that GitLab Premium offers versatility and user management features that other solutions don’t provide.\n\n\nSURF adopted GitLab Premium as a versioning platform to run on premises. Teams started by using GitLab for version control and then formed a step-by-step process for [CI adoption](/topics/ci-cd/implement-continuous-integration/).\n",{"header":5043,"text":5044},"Increased deployment, code management, and IaC","Deployment times have decreased tremendously, allowing SURF to deliver solutions to research and education communities much faster. “We are coming from a place where you buy the hardware, you rock it, you plug it, you install the operating system. From this, we moved directly to deployment using GitLab CI for infrastructure as a code. Deploys went from two weeks to one day. So it took two weeks to deploy a cluster. Now it can take one day if it's a really, really complex case. That's the worst case scenario,” said Giuseppe Gianquitto, cloud lead architect, Research and Development Services.\n\n\nWorkflow is simplified not only because of the [GitLab Flow](/topics/version-control/what-is-git-workflow/), but also because of CI/CD templates, which empowers teams to leverage Infrastructure as Code (IaC) and deploy complex systems in a streamlined and repeatable fashion. “GitLab is the backbone of our deployments, from data analytics to IoT distributed platforms. We rely on GitLab to rapidly create complex solutions,” said Machiel Jansen, head of Scalable Data Analytics group.\n\n\nThe Research and Development Services unit within SURF designs and deploys Kubernetes clusters as IaC with applications spread across dozens of repositories using a modular and pluggable design and with GitLab as the backbone. “We deploy Kubernetes clusters for our developers. So those clusters, they come up with everything ready for the developer to create an application, production-ready for the final user. Now, the entire process for us to the product cluster is less than 25 minutes,” said Gianquitto. “From the moment that the developer says, ‘I need a new cluster, because I need to go into production with the municipality of Amsterdam or with a project for CERN,’ the environment is ready within 25 minutes.”\n\n\nGitLab runners are responsible for authenticating to the cloud environment, and typically run Terraform and Ansible deployments to set up the required infrastructures and applications. Over 20 Kubernetes clusters and over 300 nodes are serving universities and institutes with complex workloads.\n\n\nThe microservices running on those Kubernetes clusters, from internal platforms to the end services, are designed across GitLab repositories. Creating, scaling, and deleting those applications and infrastructures is entirely driven by GitLab CI. “Our DevOps teams can provision production-ready solutions within minutes, from Kubernetes to multi-cloud and multi-tier complex hybrid cloud infrastructures. GitLab CI/CD in synergy with Terraform gives us all we need to provide our researchers and data scientists with reliable and re-usable tools,” Gianquitto said.\n\n\nSURF now has a single platform for Git, version control, code management, IaC, and CI/CD. Developer throughput has increased and cross-functional relationships have improved. “Mostly because CI/CD, development and operations teams have a framework of cooperation. This is probably the highest value GitLab has introduced in our teams,” Gianquitto said.\n",{"template":950,"size":40,"region":106,"industry":87},"content:en-us:customers:surf.yml",{"_path":5048,"content":5049,"config":5092,"_id":5093},"/en-us/customers/sva",{"name":5050,"logo":5051,"hero":5052,"heroImage":5053,"benefits":5054,"industry":89,"employeeCount":5062,"location":5063,"solution":4820,"stats":5064,"headline":5072,"summary":5073,"quotes":5074,"content":5079,"contributors":1281},"SVA","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518011/bihapvuozcrcevmjywql.svg","How SVA enhanced business agility workflow with GitLab","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518457/wodl0me5ogvpghqdi1hc.jpg",[5055,5057,5059],{"metric":1843,"config":5056},{"icon":1845},{"metric":1293,"config":5058},{"icon":1295},{"metric":5060,"config":5061},"Improved source code management",{"icon":2598},"1,400","Wiesbaden, Germany",[5065,5067,5070],{"value":5066,"metric":4824},510,{"value":5068,"metric":5069},110,"GitLab groups",{"value":5071,"metric":1207},"1,571","SVA was looking for a platform to improve central code management and workflow CI.","SVA's application and infrastructure development teams adopted GitLab for internal and external source code management (SCM), DevOps, and continuous integration and delivery (CI/CD).\n",[5075],{"quoteText":5076,"author":5077,"authorTitle":5078,"authorCompany":5050},"GitLab is easy to use. Our system engineers onboarded very fast. You don't have to explain every feature. It is very intuitive.\n","Stefan Gärtner","Head of Competence Center CICD",[5080,5083,5086,5089],{"header":5081,"text":5082},"Systems integration leader","System Vertrieb Alexander GmbH (SVA) is a leading systems integration company founded in 1997. Based in Germany, [SVA](https://www.sva.de/index.html) provides a combination of quality IT products with consultation know-how for custom solutions for all industries. The company offers expertise in data center infrastructure, IT platforms, virtualization technologies, software development, applications in general and business intelligence.\n",{"header":5084,"text":5085},"Improving CI and central code management","SVA has different lines of business, and all vendors and services are divided into nine distinct areas. The focus of one department is Agile IT and software development, which includes DevOps and CI/CD.\n\nThe applications and infrastructure development teams were looking for a solution that could improve their CI workflow and help them organize and manage code. SVA was looking for a quickly accessible tool to boost collaboration and code quality for their system engineers.\n",{"header":5087,"text":5088},"Collaboration, transparency, open source community","SVA uses Jira for issues and Kanban boards in their workflow and both continue to be extremely useful. The team reviewed different products and after some analysis, the team found that GitLab was the best option for their particular use case. Jira and GitLab integrate easily, so SVA adopted GitLab's Community Edition for their field engineers.\n\nSeveral SVA system engineers had previous experience using GitLab and were familiar with its features. Many SVA customers have also used GitLab and the engineers now implement it into customer environments. Now, the teams also use GitLab to [deploy Kubernetes](/solutions/kubernetes/) clusters.\n\n\"If one team wants to look at what the other team is doing or wants to reuse some Ansible playbooks or some code snippets or anything, this is the central point of collecting these things. It's also where they can develop and improve code,\" said Sarah Mueck, Head of Business Line Agile IT and Software Development at SVA.\n",{"header":5090,"text":5091},"Internal and external knowledge","SVA has over 500 active GitLab users. Every engineer is now connected to others in an open source environment. The teams use GitLab as a version control system and also for test automation. \"We try to make everything public or most things public. We try to connect every system engineer to each other, like an open source community,\" said Stefan Gärtner, Head of Competence Center CICD at SVA.\n\nSystem engineers use [GitLab CI](https://about.gitlab.com/solutions/continuous-integration/) for most of their reports and projects. On top of that, GitLab is used in areas that the team hadn't expected. \"We don't use it only as a version control system. I think it's a benefit of GitLab that we are doing test automation now more than before,\" Gärtner added.\n\nAs a consultant company, SVA needs to be able to adapt to the customer environment. By adopting GitLab internally, consultants now have a broader understanding of how their customers work. \"That's why we also adopted GitLab internally. Not just for the purpose of what it's used for, but also as a learning curve for our employees that they use it and know how to use it. So if they come to a customer who's using this as well, then they know what they're doing,\" Mueck added.\n\nGitLab mirrors the technical company structure, and teams work together within specific projects or repositories. Cross-group work can happen easily within the tool because of the level of transparency. Collaboration happens easier now with one centralized tool in place.\n",{"template":950,"size":40,"region":106,"industry":91},"content:en-us:customers:sva.yml",{"_path":5095,"content":5096,"config":5135,"_id":5136},"/en-us/customers/synchrotron-soleil",{"name":5097,"logo":5098,"hero":5099,"heroImage":5100,"benefits":5101,"industry":5111,"employeeCount":5112,"location":5113,"solution":913,"headline":5114,"summary":5115,"quotes":5116,"content":5121,"companySize":1281,"region":1281,"contributors":1281,"stickyBenefits":5134},"Synchrotron SOLEIL","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518013/iymvuvjq9bfnrhqrwxnx.png","GitLab accelerates innovation and improves efficiency for Synchrotron SOLEIL","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518457/lyyitdhzhfmovnx22aft.jpg",[5102,5106,5109],{"metric":5103,"config":5104},"Faster testing",{"icon":5105},"MonitorTest2",{"metric":5107,"config":5108},"Easier collaboration",{"icon":1895},{"metric":3853,"config":5110},{"icon":1195},"Education and Research","358","France","Synchrotron SOLEIL, the French national synchrotron facility, wanted to improve developer productivity and make it easier for a wide array of internal and external users to collaborate.","With GitLab, the facility is enabling researchers to access the insights they need to make breakthrough discoveries.\n",[5117],{"quoteText":5118,"author":5119,"authorTitle":5120,"authorCompany":5097},"GitLab increased the visibility of the information shared within the Agile development team. Project management combined with issue tracking on the code was very useful for us.\n","Idrissou Chado","Head of Management Information Systems",[5122,5125,5128,5131],{"header":5123,"text":5124},"The French site for synchrotron radiation research and application","A synchrotron is a large machine (about the size of a football field) that accelerates electrons to almost the speed of light. As the electrons are deflected through magnetic fields they create extremely bright light. The light is channeled down beamlines to experimental workstations where it is used for explorative research and applied in industry. Located in Saint Aubin, Essonne, [SOLEIL](https://www.synchrotron-soleil.fr/en) is the French national synchrotron light source, a very large research facility. SOLEIL, an acronym for “Optimized Light Source of Intermediate Energy to [LURE](https://www.synchrotron-soleil.fr/en/about-us),” functions as a laboratory and experimental place for scientists from France and abroad. SOLEIL’s mission is to run research programs using synchrotron radiation, to develop state-of-the-art instrumentation on the beamlines, and to make those available to the scientific community.\n\nSOLEIL, a unique tool for both academic research and industrial applications across a wide range of disciplines including physics, biology and chemistry, is used by over 4,500 researchers per year within the international community. The facility is a public entity employing about 358 people, founded by the CNRS and the CEA, and partner of the Paris-Saclay University. SOLEIL is preparing for an upgrade of the facility in order to offer new capabilities for research. The electron accelerators and the beamlines, from the source down to experimental workstations, will be deeply refurbished and improved, including the whole IT systems and infrastructure. The atmosphere of collaboration carries over to software development, which is open source, with contributions from the internal team and external developers.\n",{"header":5126,"text":5127},"Systems getting in the way of collaboration","SOLEIL uses a variety of different types of software, including some commercial off-the-shelf software for Human Resources, back-office financials, project management and tracking issues. It also develops software for its own needs, such as its most important application the SUN set, which manages the scientific proposals submitted to and realized at SOLEIL or in collaboration with other scientific laboratories and facilities. The team was in the process of migrating this application from PHP to Java and wanted to accelerate the process while maintaining strict quality standards for the code. But SOLEIL had no standard for version control.\n\n“We were maintaining too many systems, including CVS [Concurrent Versions System] and SVN [Apache Subversion] and GitLab to do the same thing,” says Idrissou Chado, head of management information systems at SOLEIL. The situation was confusing — less than ideal for developer productivity. Developers were using Agile software development practices, consisting of five steps: plan requirements, develop product, test software (automatic non-regression tests as well as manual testing), deliver iteration, and incorporate feedback. The team needed to improve code version control and governance. They needed a common repository for source code written by SOLEIL staff (scientists and developers). And the team wanted to improve its software development lifecycle (SDLC).\n\nToward both goals, the first order of business was to migrate to an integrated DevOps platform. “We needed to improve our development project management, particularly in the framework of external collaboration,” recalls Chado. “It was too time-consuming to use CVS and SVN, and they were not up to date so there was no way to manage tasks or develop in a collaborative way.\" Source code was spread out on a number of systems, including GitHub, GitLab, and on the individual developers’ local computers. There was no option not to upgrade the tooling without the prospect of wasted time and money and reduced quality of the code. And not being able to collaborate with ease was affecting the motivation of the developers because it was too cumbersome to track the evolution of the code. Chado led a multi-stakeholder working group endorsed by SOLEIL’s IT Department to search for a collaborative platform that followed an open-source philosophy and had all the tools in one place (including code versioning and CI/CD integration). The working group decided to do a proof of concept project on GitLab. “By doing that, we found that GitLab was very user-friendly,” Chado says. “We didn’t go too much deeper because the feedback we got about GitLab from the developers and users was very good.”\n",{"header":5129,"text":5130},"Active projects take off in GitLab","The SOLEIL team considered GitHub and BitBucket but decided to progress with GitLab due to the alignment with open source and the transparent philosophy which was in keeping with their mission. They tested GitLab for a few months and determined from this pilot that GitLab was the right choice as it offered a single DevOps platform, robust workflow, and security capabilities such as pushing issues from external testing applications into GitLab on specific project and user profiles. After GitLab got good reviews from the development team, Chado elected to migrate to GitLab Starter for its unified version control system and a variety of other functions. The team now uses GitLab Ultimate. After starting with 134 active users and roughly 74 projects, the team’s use of GitLab has rapidly grown to 270 users and more than 250 projects.\n",{"header":5132,"text":5133},"A window into developer activities","Immediately after the migration, GitLab provided much better visibility into the work done by developers. Having a unified view in the GitLab dashboard was a major step up, says Chado. “GitLab increased the visibility of the information shared within the Agile development team,” he adds. This was especially important during the migration of the SUN set also called SOLEIL Digital User office tool from PHP to Java. “Project management combined with issue tracking on the code was very useful for us,” says Chado. Collaboration is still paramount, because the researchers and scientists come from within and outside SOLEIL.\n\n“Now, with the help of GitLab, we are able to take charge and collaborate on code with internal and external users. This is very useful for us because it makes our life much easier,” says Chado. Testing is another major improvement under GitLab. Previously, it took roughly one week for a developer to test the code manually. “Now, by doing that automatically and putting that into GitLab, testing is much easier and faster,” says Chado. A sure sign the developers have embraced GitLab: There will soon be 500 new projects moved on the GitLab. Says Chado, “The work is ongoing and GitLab has been adopted very quickly and we are happy with that.”\n",{"benefits":1281},{"template":950,"size":40,"region":106,"industry":87},"content:en-us:customers:synchrotron-soleil.yml",{"_path":5138,"content":5139,"config":5187,"_id":5188},"/en-us/customers/thales",{"name":5140,"logo":3271,"hero":5141,"heroImage":3267,"benefits":5142,"industry":5152,"employeeCount":5153,"location":5154,"solution":913,"stats":5155,"headline":5163,"summary":5164,"quotes":5165,"content":5169},"Thales","Using GitLab, Thales revolutionizes in-flight entertainment with personalized experiences",[5143,5146,5149],{"metric":5144,"config":5145},"Fewer outages",{"icon":1477},{"metric":5147,"config":5148},"Greater collaboration",{"icon":1895},{"metric":5150,"config":5151},"Easing compliance requirements",{"icon":4960},"Aerospace, Defense, & Security","81,000+","Meudon, France",[5156,5158,5161],{"value":1031,"metric":5157},"faster software updates",{"value":5159,"metric":5160},"40x","faster project setups",{"value":1402,"metric":5162},"reduction in build infrastructure costs","Thales is a global technology leader that designs, builds, and delivers products and systems for the aerospace, defense, and security and digital identity industries. The company turned to GitLab in 2018 to replace a toolchain of outdated DevOps tools with a single DevSecOps platform that would enable their teams to collaborate quickly and more efficiently to deliver innovative and secure software to its customers. That speed and dependability enables them to differentiate themselves from their competitors.","With more than 81,000 employees in 68 countries, [Thales](https://www.thalesgroup.com/) builds systems ranging from communication-delivery satellites to air traffic management, nose-to-tail aircraft connectivity, and in-flight services for major air carriers. Thales' managers, who wanted to remain ahead of their competitors, needed to break down thousands of work silos so their more than 5,000 DevSecOps team members could collaborate, speeding the development and delivery of innovative software. To do that, they turned to GitLab.\n",[5166],{"quoteText":5167,"author":3274,"authorTitle":5168,"authorCompany":5140},"With GitLab, we went from a completely isolated situation to a collaborative environment that enables better communication and coordination among diverse teams.\n","Chief Product Owner",[5170,5173,5175,5178,5181,5184],{"header":5171,"text":5172},"Elevating in-flight entertainment by making it personal","Thales provides in-flight entertainment systems on more than 2,300 aircraft across 80 airlines, serving more than 1.6 million passengers per day. To take in-flight entertainment (IFE) to a new level, Thales built a groundbreaking system, dubbed FlytEDGE, designed to offer passengers a personalized experience based on their individual preferences. Unlike traditional IFE systems, FlytEDGE is a cloud-based solution focused on bringing operational flexibility, in order to quickly deploy new applications and services onboard. These new services will tailor passenger experience by intelligently recommending content, providing personalized journey information, like luggage tracking and directions to connecting gates, or even allowing passengers to stream their favorite shows and movies using their own streaming subscriptions.\n\nThales built, delivered and will operate the FlytEDGE system, which won a prestigious 2024 Crystal Cabin Award recognizing in-flight innovations, on GitLab's end-to-end DevSecOps platform. Adopting GitLab in 2018, empowered Thales to streamline their software development processes, [improving collaboration](/blog/5-ways-collaboration-boosts-productivity-and-your-career/), and ensuring [robust security measures](/blog/securing-your-code-on-gitlab/).\n\nUsing GitLab has enabled Thales teams to better collaborate because they were all using the common platform, gaining visibility into projects, sharing documentation, and gaining the ability to pitch in and work together. And while also relying on GitLab's CI/CD pipelines to build, test, and deploy gave them efficiency and speed, using automated features, specifically for merge requests, also gave them a solid boost.\n\nWith FlytEDGE, airlines will be able to do a bi-weekly software update on in-service aircraft, which is a frequency 20 times faster than with traditional IFE systems. That speed is a key differentiator for Thales.\n\nThe IFE system relies on cloud-based content management, using providers like Amazon Web Services. This ensures the most popular entertainment options, including live sporting events, are available on every plane, using digital distribution and intelligent content curation.\n\n“By using [GitLab's platform](/), we were able to build FlytEDGE much faster and much more securely than we would have been able to without it,” Dubié. “The platform empowered our developers to create a piece of software that is not only critical to our overall business but will transform the way people are entertained inflight. We are happy to partner with GitLab to redefine the travel experience.”\n\n“Before GitLab, everything was disparate,” says Jordan Dubié, chief product owner of Thales' Software Factory, an environment of tools, processes, and best practices to accelerate software production. “That made it impossible to modify our software without understanding different systems. Now, people can contribute to a common system so it's not a problem. And we can scale better.”\n\nAll of this is important to Thales' overall business since in-flight entertainment is a major source of revenue for the company, and it could help them capture more business from airlines that want to digitize their on-board experience and maximize their own customer experience.\n\nFlytEDGE is being beta tested in 2024, operating on four aircraft flying domestically in the U.S. Then the system is expected to be operating at scale by the end of 2026.",{"text":5174},"\u003Cdiv style=\"padding:56.25% 0 0 0;position:relative;\">\u003Ciframe src=\"https://player.vimeo.com/video/1095091943?badge=0&autopause=0&player_id=0&app_id=58479\" frameborder=\"0\" allow=\"autoplay; fullscreen; picture-in-picture; clipboard-write; encrypted-media; web-share\" style=\"position:absolute;top:0;left:0;width:100%;height:100%;\" title=\"Thales | Customer Story\">\u003C/iframe>\u003C/div>\u003Cscript src=\"https://player.vimeo.com/api/player.js\">\u003C/script>",{"header":5176,"text":5177},"Streamlining an out-dated, cumbersome toolchain","One of the main reasons Thales migrated to GitLab is because their teams were being slowed down by a [cumbersome toolchain](/blog/too-many-toolchains-a-devops-platform-migration-is-the-answer/) made up of long-out-dated, overly customized legacy tools that left members of the development, security and operations teams constrained and working in silos. It also meant developers and security team members were left to handle many tasks, like compliance processes, manually, which took up precious time and energy. The company has trimmed its toolchain by replacing Bitbucket, Jenkins, and Atlassian's Confluence.\n\nTo get out of that situation, Thales turned to GitLab's full platform, replacing legacy tools like BitBucket, Jira, and Jenkins. The company still uses a few distinct security tools but they now use them in conjunction with GitLab and its own security capabilities.\n\n“We had challenges with our old tools that were so old that we were not even able to maintain or upgrade them anymore,” says Dubié. “We were stuck in the past and team members, especially new hires, were saying it was weird we were using these old tools. They wanted something different, something better.”",{"header":5179,"text":5180},"Breaking down silos and fostering global collaboration","Dubié notes that with teams switching over to GitLab's platform, they were able to centralize their work in one common platform, remove old collaboration barriers, and enable team members to work together, regardless of where they were physically located around the world.\n\n“We used to have a different software team for every different business entity,” he adds. “We had different teams in Bordeaux, Toulouse, Valence, and Paris — on completely separate platforms, using tools that hadn't been updated in three or four years. That was a major obstacle to collaboration and led to inconsistent development environments.”\n\nWith different teams unable to work together — for instance, sharing best practices and helping others solve problems they'd already faced — the company suffered from sporadic and slow release cadences, limiting the efficiency of their software delivery pipeline. “In terms of functionality, we were way behind in the market,” says Dubié. Now, that has all changed. Thales notes they eliminated what once was a “heavy backlog” of software updates because their continuous improvements now are eight times faster than before they used GitLab.\n\nAnd GitLab-based efficiencies also have given Thales one day extra per month, per person of development time. With 5,000 DevSecOps team members onboard, that is a lot of saved time.\n\nUsing a single platform has enabled Thales to rectify this troublesome fragmentation, pull developers together to share information and workloads, and create a whole new level of agility and productivity across projects and geographic locations.\n\n“With GitLab, we went from a completely isolated situation to a collaborative environment that enables better communication and coordination among diverse teams,” Dubié adds. “That has allowed us to overcome those previous barriers, improving our productivity and our ability to build and deploy software.”",{"header":5182,"text":5183},"Increasing speed and security with automation","Olivier Flous, senior vice president of Engineering & Digital Transformation at Thales, notes that it's critical to the company to be able to continuously upgrade their software to ensure they maintain a high level of security. “Speed has become essential to our businesses,” he says. “That means we need to continuously adapt our software and our processing, and that means we need to be able to deliver faster and to deliver continuously. That's a revolution and that's where GitLab, of course, plays a key role for us.”\n\nUsing the platform also has enabled Thales to take advantage of automation, whether it involves security, CI/CD pipelines, documentation, or compliance processes. “Having GitLab's platform has allowed us to really embrace automation,” says Dubié. “It's been key to not just adding shortcuts to so many different workflows but to freeing up our developers from repetitive, manual tasks so they can focus on being innovative. It also has improved the overall developer experience.\n\n“We're betting everything on automation,” he adds.\n\nThales has set up a lot of automation around its [CI/CD pipelines](/blog/how-to-keep-up-with-ci-cd-best-practices/), which has added consistency and reliability, as well as speed and efficiency, giving them faster release cycles and reducing their time-to-market.\n\nBy setting up standardized, shared automation tools, such as [GitLab Runners](/blog/how-to-automate-creation-of-runners/) that execute jobs in a defined pipeline, team members are able to spin up projects faster, get to work on them, and move through the entire software development lifecycle more efficiently.\n\nThe company also is relying on the platform's automated security capabilities, such as secret detection, software composition analysis, static application security testing, and dynamic application security testing. Thales's teams also are able to use GitLab with other tools, giving them a flexibility they didn't have before. Dubié also notes that having security testing already in place whenever a new merge request is opened gives them a new confidence and enables them to create and deploy secure software more easily and efficiently. And by saving them from having to do more frequent audits, it saves them both time and money.\n\n“Having all of these automated security features integrated on GitLab  ensures that all of our teams and projects have the same high level of protection, giving us early vulnerability detection, continuous monitoring, and scalability,” says Dubié, noting that they also use GitLab's Trust Center, an interactive portal that provides compliance and assurance credentials and documentation.\n\n“It has really impressed a lot of our team members that they now have the ability to move so fast in the pipelines,” he adds. “They were accustomed to it being a complex and slow setup, and now it's not. We went from days of setting up an environment to just a couple of minutes or hours.”\n\nThough Thales hasn't yet adopted GitLab Duo, a suite of AI-powered features that organizations use to develop and deploy secure software faster, Dubié says team members are eager to start using it. “We are looking closely at GitLab's AI roadmap and the AI capabilities in Duo because it will be key to our future,” he adds. “There's a lot of interest because we know it will streamline our development and delivery, helping us find, analyze, and fix bugs.”",{"header":5185,"text":5186},"Meeting compliance needs with GitLab","Using GitLab's automation has helped Thales not only effortlessly [meet compliance requirements](/blog/meet-regulatory-standards-with-gitlab/), but prove that they are doing it, as well. Since Thales works in the highly regulated defense, space and transportation industries, the company has to meet an ever-changing list of mandates, such as ISO 27001, an international information security standard. GitLab helps Thales  stay compliant by offering tools that automatically ensure the proper setup of development environments, set up guardrails around data locations, tag data, and keep track of information, like vulnerabilities found and fixed.\n\n“Throughout the company, we have multiple levels of data sensitivity so remaining compliant is a complex operation. GitLab helps us do that,” says Dubié. “It's not just about meeting mandates but being able to prove, on a moment's notice, that you're doing what needs to be done. It's easy to impress someone sometimes, but we need to be able to show proof of our compliance every time. Now we have the processes and documentation to do that.”\n\nDubié notes that Thales, which is building nearly all of its new software with GitLab, is still working to fully automate their compliance system but says they are well on their way. The company also is looking ahead to digitizing their avionics work, and they'll be relying heavily on GitLab to do that since the platform's user interface makes it easy for team members, specifically those who are not developers, to more easily understand and use configuration management. That brings a sense of confidence across teams and departments.\n\n“Our collaboration with GitLab is based on mutual respect and has been very fruitful for us,” says Flous. “We listen to what they tell us, in terms of their vision and in terms of software craftsmanship that we can integrate into our workflow. Thales is a very large company and our mission is to build a future we can all trust. And we're doing that by partnering with GitLab.”",{"template":950,"size":44,"region":106,"industry":91},"content:en-us:customers:thales.yml",{"_path":5190,"content":5191,"config":5235,"_id":5236},"/en-us/customers/the-last-mile",{"name":5192,"logo":5193,"hero":5194,"heroImage":5195,"benefits":5196,"industry":65,"employeeCount":4211,"location":5204,"solution":913,"stats":5205,"headline":5215,"summary":5216,"quotes":5217,"content":5222,"companySize":1281,"region":1281,"contributors":1281},"The Last Mile","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518014/pojlzts5yjjcdgydnaxn.png","With GitLab, TLM students forge path to DevOps and independence\t","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518458/ez7dzyynhnuo5bb9ztou.jpg",[5197,5199,5201],{"metric":1843,"config":5198},{"icon":950},{"metric":1293,"config":5200},{"icon":1295},{"metric":5202,"config":5203},"Streamlined project management",{"icon":2553},"San Francisco, CA",[5206,5209,5212],{"value":5207,"metric":5208},33,"students pre-cloud-GitLab per year",{"value":5210,"metric":5211},150,"students with-cloud-GitLab per year",{"value":5213,"metric":5214},"133 to 1,500","student project growth with GitLab","The Last Mile supports incarcerated students with learning services and in-house support staff with scalable infrastructure, while ensuring compliance and security.  GitLab meets the group’s needs to provide its constituents a collaborative, real-world DevOps environment.","Improve fidelity of incarcerated student DevOps learning experience, while streamlining in-house project execution collaboration.\n",[5218],{"quoteText":5219,"author":5220,"authorTitle":5221,"authorCompany":5192},"GitLab benefits our students because it is a real-world platform. That is invaluable.\n","Sydney Heller","Executive Director",[5223,5226,5229,5232],{"header":5224,"text":5225},"The Last Mile builds in-prison education path to DevOps skills","Formed in 2010, [The Last Mile (TLM)](https://thelastmile.org) is an organization dedicated to breaking the cycle of mass incarceration affecting individuals, families and communities across the United States, by making coding and other educational and career-training opportunities available to incarcerated and justice-impacted individuals. The non-profit organization supports 24 classrooms across six states, has served 974 students and counting since 2010, and has aided 379 Returned Citizens who have successfully rejoined society. Education programs include the United States’ first in-prison coding bootcamp. Another educational offering by The Last Mile is the new Audio and Video Production Program, currently offered in TLM classrooms in CA and IN. The mission to provide software training depends in great part on The Last Mile’s Engineering and Education teams. Team members support students with learning services and support staff with technological infrastructure, while ensuring compliance and security.\n",{"header":5227,"text":5228},"Prepare students for DevOps outside prison walls, with in-house project collaboration","The Last Mile’s Web Development Program began with its first very low-tech coding bootcamp in San Quentin State Prison in California in 2014. As the program evolved it became increasingly clear that centrally managed resources were important to success. Students’ individual repositories had some benefit, but did not provide students with a representative view of what a software developer’s work really looked like. Without remote repositories and real-life technical collaboration, the support of modern DevOps workflows was inadequate. TLM tried different tools for version control, including Bitbucket and GitHub. Moving between different project tools limited productivity.\n\nFor internal project management, the company used Monday.com across departments.  But it became clear that there was difficulty in getting everyone across the company on the same page. It was difficult, for example, for someone in the marketing department to view the progress and development of important new classroom features, or what kind of lead times were anticipated. These issues presented themselves at the same time that a significant expansion of The Last Mile Programs was anticipated.\n\nThe Last Mile wanted one solution, a DevOps platform, to solve both of these challenges. TLM investigated the use of GitLab for Scaled Agile portfolio planning and project management features, including use of Project Issue and Group Issue Boards and CI / CD pipelines to deliver auditable and repeatable infrastructure as code, to support a growing number of learning locations and to better track how processes moved through the organization. The organization also expanded its use of GitLab to support remote repositories for students.\n",{"header":5230,"text":5231},"GitLab Ultimate imbues DevOps process, promotes collaboration","Today, The Last Mile leverages GitLab to cover elements needed both for outside client training and for in-house project management. Such work spans from student on-boardings, to special systems access, to its infrastructure-as-code state-management store. Meanwhile, inside The Last Mile organization, GitLab now provides tooling that supports comprehensive workflow coordination across the entire company. For students, GitLab provides the basis for dedicated curricular resources, including sandbox and branching activities and dedicated remote instruction lesson plans. Students gain hands-on experience in DevOps processes and Agile methods. And, GitLab furthers The Last Mile’s efforts to support more locations, and more students.\n",{"header":5233,"text":5234},"Real-world platform strengthens Returned Citizen programmer skills","With GitLab Community Edition in place, student developers learn how to address challenges, conceptualize solutions, and gain counseling of others that may have developed other approaches to similar problems. This grounds their experience in an essential part of modern collaborative DevOps methods. For teams within The Last Mile, GitLab Ultimate creates a visible and accessible single source of truth, that allows all parties to take part in project oversight. That vastly improves the in-house collaboration, according to Tulio Cardozo, IT manager, The Last Mile. “The reality — before GitLab — was a lot of emails, a lot of other tools. It was a lot of really hard attempts at trying to get everybody on the same page,” Cardozo said. “But once we rolled out GitLab, we use it absolutely for everything.”\n\nHe said GitLab supported company-wide efforts to promote project transparency and collaboration.  “It really felt natural to be able to have one unified platform, where anybody can see every single bit of merge requests, and what’s going into code deployment. Anybody can be in the loop,” he said.  “That really helps to have the entire company thinking about what we're delivering as a platform.” Fully leveraging GitLab during reentry means, when a student goes through the program and is released, they can have access to an export of their GitLab group with all of their GitLab projects. They can then import that into a personal, online GitLab account, and along with their programming foundation, embark on a programming career.\n\nGitLab is an integral part of The Last Mile’s holistic program, and a part of an education that is based on an open-source ethos, Cardozo indicated. “This is the same thing as in open-source software, if you will. It's like open-source life building,” Cardozo said. GitLab has worked closely on webinars and seminars with The Last Mile, to fully immerse students in open source as a way of developing skills and aligning with The Last Mile’s objectives to support not just the tools but also the human aspect.” he added. ‘Training that has high-fidelity to actual open-source DevOps methods is crucial’, adds The Last Mile Executive Director Sydney Heller.\n\n“GitLab benefits our students because it is a real-world platform. Being able to leverage GitLab means that, regardless of the fact that they are incarcerated, they are getting real world experience using tools that millions of people use on the outside,” Heller said. “That is invaluable.”\n",{"template":950,"size":36,"region":102,"industry":67},"content:en-us:customers:the-last-mile.yml",{"_path":5238,"content":5239,"config":5281,"_id":5282},"/en-us/customers/thezebra",{"name":3581,"logo":5240,"hero":3582,"heroImage":5241,"benefits":5242,"industry":89,"employeeCount":5253,"location":5254,"solution":913,"stats":5255,"headline":5259,"summary":5260,"quotes":5261,"content":5268},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1745517952/kmbocohvcmshrupgvtdt.svg","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518427/zjppqrhidfxqy1qoinuy.jpg",[5243,5247,5250],{"metric":5244,"config":5245},"Enhanced CI/CD",{"icon":5246},"IncreaseThin",{"metric":5248,"config":5249},"Less software maintenance",{"icon":1302},{"metric":5251,"config":5252},"Improved developer workflow",{"icon":2598},"350","Austin, TX",[5256,5258],{"value":3037,"metric":5257},"fewer tools",{"value":4269,"metric":1032},"The Zebra adopted GitLab to replace GitHub and Jenkins for source code management, CI/CD, and security.","The Zebra, an online insurance comparison site, adopted GitLab for SCM, CI/CD, and SAST and DAST.\n",[5262,5266],{"quoteText":5263,"author":5264,"authorTitle":5265,"authorCompany":3581},"The biggest value (of GitLab) is that it allows the development teams to have a greater role in the deployment process. Previously only a few people really knew how things worked, and now pretty much the whole development organization knows how the CI pipeline works, can work with it, add new services, and get things into production without infrastructure being the bottleneck.\n","Dan Bereczki","Sr. Software Manager",{"quoteText":5267,"author":5264,"authorTitle":5265,"authorCompany":3581},"We've gone from deploying once a week, to twice a week. We're getting to a place where we're getting comfortable with our testing verification. We'll be at continuous deployment hopefully by the end of the year and be able to deploy at will.\n",[5269,5272,5275,5278],{"header":5270,"text":5271},"Insurance in black and white","The Zebra was established to provide customers with a simplified way to compare insurance providers. Established in 2012, The Zebra is an online insurance comparison shop that researches car insurance options and delivers the best rates available. [The Zebra](https://www.thezebra.com/about/) has recently expanded into homeowners and renters insurance.\n",{"header":5273,"text":5274},"Too many plugins without any advantages","The Zebra was using GitHub as its repository and Jenkins for deployments. The teams were also using Terraform to deploy to AWS. The number of Jenkins plugins created an overwhelming amount of management work. On top of that, the variety of plugins caused security vulnerabilities because some tools were no longer supported or too fragile to update in the deployment environment.\n\n“The biggest problem that we were having was that we were using Jenkins to do our deploys before GitLab. We put enough plugins into that. It was so fragile that nobody wanted to touch it,” said Dan Bereczki, Sr. Software Manager. “Anybody that did try to touch it broke it, and then deploys were down for half a day or a day to try to fix things, or keep things all upgraded.”\n\nTeams wanted to improve the existing CI/CD process, but that meant adding plugins to Jenkins, further complicating the existing level of maintenance. The Zebra needed a new solution that would integrate testing and security, as well as allow for deploys to a [variety of different platforms](/partners/){data-ga-name=\"different platforms\" data-ga-location=\"customers content\"}.\n",{"header":5276,"text":5277},"A fast migration with zero plugins","The Zebra researched a variety of platforms to replace the existing plugins and ease management stress. They adopted GitLab because it provides an enhanced repository without having to manage plugins. Moreover, the CI/CD capabilities were the selling point.\n\nOn top of that, the teams were eager to adopt GitLab because it offers features that other solutions don’t offer, like built-in security. “People realized how much more control they had of their processes, and how easy it was to make the transition. We got the migration done in under three months,” Bereczki said. Ninety-five percent of Jenkins code was migrated over in that time, and they have since completely moved off of Jenkins and GitHub.\n\nAll six of the application development teams and even a few other teams outside of development are using GitLab. “Now instead of one or two people who understand the intricacies of Jenkins and can fix the things that are problematic, everybody knows how to work with the GitLab pipeline,” Bereczki said. The teams went from using 3 tools — GitHub, Codeship CI, and Jenkins Deploy — to using only [GitLab CI/CD](/solutions/continuous-integration/){data-ga-name=\"continuous integration\" data-ga-location=\"customers content\"}, fully integrated and fully automated.\n",{"header":5279,"text":5280},"One platform, many solutions","With GitLab, The Zebra can now focus on moving towards continuous deployment because teams can deploy at will, without waiting for other schedules. All of the development teams have a greater role in the deployment process because they understand how the CI pipeline works and can work within it. On top of that, the infrastructure is no longer a bottleneck for deployment.\n\nThe workflow usually begins with a request from marketing. From there, it becomes a technical brief which gets broken into a set of JIRA tickets and then assigned to the appropriate team. It then gets worked on, code gets generated and goes into the GitLab repository. Then, the team will use the GitLab CI/CD pipeline to get it deployed in the development environment. Terraform is used to implement infrastructure as code to ensure configuration changes are maintained throughout the test and deployment process.\n\nTeams use Amazon EKS with RDS. Traffic routing is initially handled by Cloudflare, then internal Elastic Load Balancing. When developers need to connect The Zebra services to outside, third-party services they use Amazon Virtual Private Cloud. “We don’t want systems where it’s this black box that nobody knows how it works. We’re slowly getting rid of that,” Bereczki said.\n\nGitLab has enabled cross-functional relationships between the development teams because now they own their own code all the way into production. Developers can understand each step to deployment and can work through any issues and make changes without worrying about disrupting other parts of the workflow.\n\n[GitLab SAST and DAST](/solutions/application-security-testing/){data-ga-name=\"sast and dast\" data-ga-location=\"customers content\"} makes it easier for compliance for SOC2 Type 1 certification and now the teams are in the middle of SOC2 Type 2 certification. It has also provided additional testing and security measures reducing their risk. “The biggest impact is, we’ve got a whole bunch of vulnerabilities that we didn’t even know were there, that we’re dealing with right now. We’re remediating those,” Bereczki states. They have eliminated all identified Criticals and Highs on four projects so far. “The nice thing about it is that, since it’s part of the pipeline now, we won’t be playing catch up for when we schedule a penetration test, or when we run some quarterly or biannual tests,” added Bereczki.\n",{"template":950,"size":40,"region":102,"industry":91},"content:en-us:customers:thezebra.yml",{"_path":5284,"content":5285,"config":5326,"_id":5327},"/en-us/customers/trek10",{"name":5286,"logo":5287,"hero":5288,"heroImage":5289,"benefits":5290,"industry":89,"employeeCount":5301,"location":5302,"solution":975,"headline":5303,"summary":5304,"quotes":5305,"content":5312,"contributors":1281,"stickyBenefits":5325},"Trek10","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518014/rwayjqbmyszyodn6zfnd.svg","Trek10 provides radical visibility to clients","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518459/weibdfbxf7qggepie5jv.png",[5291,5295,5298],{"metric":5292,"config":5293},"Increased client feedback",{"icon":5294},"AnnouncementAlt",{"metric":5296,"config":5297},"Real-time client visibility",{"icon":1526},{"metric":5299,"config":5300},"Seamless collaboration",{"icon":1385},"25-49","South Bend, Indiana, USA","Professional services company Trek10 needed to bridge the gap between developers and clients by having everything visible in one application.","With GitLab, Trek10 is able to deliver full transparency throughout the development cycle.\n",[5306,5310],{"quoteText":5307,"author":5308,"authorTitle":5309,"authorCompany":5286},"Essentially, we look at GitLab as a building block, and we just build whatever we need on top of it. Whether it's a wiki or a custom integration, GitLab helps create an engineering culture.\n","Jared Short","Director of Innovation",{"quoteText":5311,"author":5308,"authorTitle":5309,"authorCompany":5286},"Because GitLab hasn't broken for us in the past two and a half years, we auto update every day.\n",[5313,5316,5319,5322],{"header":5314,"text":5315},"Trek10 modernizes software solutions to support clients","An increasing demand for cloud native applications has left some organizations struggling to compete in a changing landscape. Without the teams, tools, or expertise to build cloud applications, organizations find themselves adrift in a sea of serverless solutions. How can organizations modernize their technology when they are not equipped with the knowledge or time to build, design, and support solutions?\n\n[Trek10](https://www.trek10.com), a professional services company, combines comprehensive consulting with specialized technical skills to build and manage serverless applications, enabling enterprises to migrate to cloud native architectures. Trek10 customizes solutions to offer clients massive scalability, heavy automation, and low operating costs. Clients who collaborate with Trek10 have the option to select among various offerings, ranging from building and operationalizing applications and systems on AWS to a 24/7 managed service to oversee and respond to incidents.\n\nBy working with clients to determine a service offering that meets their specific needs and goals, Trek10 ensures that organizations have cutting-edge solutions to tackle business demands.",{"header":5317,"text":5318},"Clients require visibility and collaboration","As organizations worked with Trek10 to develop customized cloud solutions, the need to create a transparent process became imperative as clients asked for updates. The team struggled with balancing the demands of building, designing, and meeting with clients to provide progress reports. Specializing in custom solutions, Trek10 encourages clients to offer feedback throughout the development lifecycle.\n\nWhen clients collaborated on projects to make decisions, the Trek10 team made adjustments, causing changes in timelines and budgets. The team tried several list-based todo apps to track progress, but there was always discrepancies and lag time between reality and the tools due to the overhead required from the developers. While the Trek10 team highly valued client collaboration to create custom solutions, the lack of visibility into how decisions altered original plans resulted in miscommunication and friction when closing out a project.\n\nInformation was spread across different tools, causing transparency and collaboration issues, and Trek10 needed to bridge the gap between developers and clients by having everything visible in one application.",{"header":5320,"text":5321},"GitLab for project management fosters collaborative partnerships","Jared Short, Director of Innovation, and the Trek10 team tested several tools in hopes of solving the transparency and collaboration conundrum. While some applications offered visibility, clients did not feel comfortable navigating through difficult UIs, so the team continued to struggle. Trek10 searched for a single application that brought value to both developers and clients. Specifically, the team looked for a way to tie issues more closely with code, since developers and clients were not contributing to a single conversation.\n\nLooking for an end-to-end solution, Trek10 selected GitLab to deliver full transparency throughout the development cycle. The team creates separate groups within projects and develops applications with full visibility to clients, paving the way for seamless collaboration after reviewing a repository or [review app environments](https://docs.gitlab.com/ci/review_apps/){data-ga-name=\"review app environments\" data-ga-location=\"customers content\"}.\n\n“We invite the clients and their developers, and project managers to collaborate with us, and we try to have as much visibility as possible,” explains Short. Exposing executive summaries, documentation, and spend reports offers clients real-time visibility into the development lifecycle. “With wikis, clients can easily find the information they want, helping them to quickly answer their own questions,” observes Short.\n\nThe decision to use GitLab has had a significant impact on both development and culture, with Short remarking, “Essentially, we look at GitLab as a building block, and we just build whatever we need on top of it. Whether it's a wiki or a custom integration, GitLab helps create an engineering culture.”\n\n\"At Trek10, an Amazon Web Services Advanced Consulting Partner and MSP Partner, we run many of our business and technology          operations on GitLab. This includes everything from collaboratively developing internal software, laying out and managing           clients projects, to documentation via wikis and management of deployments via GitLab CI. All of our GitLab Infrastructure          runs within our own Virtual Private Cloud in AWS (VPC). We use GitLab CI to build, test and deploy AWS infrastructure.              Whether it be containers on Fargate and ECS, or serverless solutions with Lambda and API Gateway, GItLab and its integrated         CI help us seamlessly and securely manage deployments across many AWS accounts on a daily basis for our clients as well as          our own practice,\" Short continued.",{"header":5323,"text":5324},"Increased visibility accelerates developer velocity","By moving to GitLab, Trek10 increased developer velocity, improved client relationships, and fostered trust and transparency. Review apps have created a direct link between developers and clients, increasing communication and allowing them to seamlessly collaborate in an improved development flow. “The concept of review apps is powerful, because developers can work within their own environment, while QA can test the features in isolation. Showing progress to executives with review apps has been a valuable component in increasing developer velocity,” says Short.\n\nClients have positively responded to the comprehensive wikis and issues, which Short says is a reassuring source of information for clients, since “they know that they have a place to go and immediately see everything.” Furthermore, the ability to collaborate directly with developers allows clients to maintain an active role in the development lifecycle.\n\nTrek10 uses GitLab as the core piece of an end-to-end solution for full transparency. As Short explains, “GitLab is a cohesive experience. We keep building off GitLab, because it works well when everybody lives in this little world that we created. If you adopt the philosophy and understand it, then it works.”\n\nUsing GitLab as a project management application helps Trek10 focus on innovating solutions for its clients. “Our business runs on GitLab. It’s a central point of our operations,” Short proclaims. After using GitLab, Short emphatically believes in the application, revealing, “Because GitLab hasn't broken for us in the past two and a half years, we auto update every day.”\n\nCommitted to visibility and collaboration, Trek10 uses GitLab to speed up development, strengthen client relationships, and create innovative solutions.",{"benefits":1281},{"template":950,"size":36,"region":102,"industry":91},"content:en-us:customers:trek10.yml",{"_path":5329,"content":5330,"config":5373,"_id":5374},"/en-us/customers/trendyol",{"name":5331,"logo":5332,"hero":5333,"heroImage":5334,"benefits":5335,"industry":61,"employeeCount":5345,"location":5346,"solution":975,"stats":5347,"headline":5354,"summary":5355,"quotes":5356,"content":5360,"companySize":1281,"region":1281,"contributors":1281},"Trendyol","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518016/bexphe6d35gk4nd3kfda.png","Trendyol boosts developer productivity with GitLab","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518459/xnr4e3zyrv014gbvuppp.jpg",[5336,5338,5342],{"metric":2210,"config":5337},{"icon":1738},{"metric":5339,"config":5340},"Automated documentation creation",{"icon":5341},"Docs",{"metric":5343,"config":5344},"Easy AWS integration",{"icon":1473},"1,300 developers\n","Istanbul, Turkey",[5348,5350,5352],{"value":1750,"metric":5349},"Improvement in developer productivity",{"value":2260,"metric":5351},"Reduction in build times",{"value":2163,"metric":5353},"Faster to launch a new application via a single platform","Trendyol developer teams rely on GitLab to turbocharge software deployment, driving market expansion.\n","Speeding development and deployments with GitLab platform, Trendyol is able to expand business-critical online customer services.\n",[5357],{"quoteText":5358,"author":5359},"\"GitLab's features allowed us to speed up our production cycle, which accelerated our development and deployment process.\"\n","Cenk Civici, Chief Technology Officer, Trendyol",[5361,5364,5367,5370],{"header":5362,"text":5363},"Trendyol at forefront of Turkish e-commerce expansion","Headquartered in Istanbul, [Trendyol](https://www.trendyol.com) is the largest e-commerce company in Turkey, operating a research and development (R&D) center, a last-mile delivery system, mobile wallets, and a wide-ranging marketplace that offers everything from food to clothing, electronics, and cosmetics.  As part of its mission, the company exports Turkish products over various platforms to consumers around the world. The company is focused on making its mark by dependably serving more than 30 million shoppers and delivering more than 1 million packages every day. To get all of this done, the company uses natural language processing, machine learning, recommendation systems, and big data. State-of-the-art DevOps processes also are vital to achieving Trendyol's business strategy.\n",{"header":5365,"text":5366},"Adapting to change, tackling inefficiencies","As Trendyol has expanded its stable of services and platforms, its developer teams amassed a diverse and complex DevOps toolchain. This caused obvious inefficiencies. Learning and using multiple tools was time-consuming and ineffective for development teams, even slowing down developer onboarding just as the company needed to expand its developer ranks. It also ultimately slowed deployments. The company's DevOps managers needed to change all of that.\n\n\nIt was clear that using multiple tools, like BitBucket, Jenkins, and GitLab, couldn't continue. They needed one platform.  Because of compliance issues, it needed to be a CI/CD engine. To make all of this happen, Trendyol selected GitLab Premium for a  container-based, runner architecture, enabling faster and continuous deployments. The platform's simplicity was the primary deciding factor. “We knew we wanted to consolidate tools into a single tool so our development team could spend less time context-switching and learning new platforms, and more time improving our product,” said Cenk Çivici, CTO at Trendyol.\n",{"header":5368,"text":5369},"GitLab enables disaster recovery, high availability","Implementing GitLab Premium with OpenStack and the AWS Cloud Platform has provided Trendyol teams with high availability and disaster recovery. GitLab Premium has allowed software development teams to simplify operations and organize using a single resource. And advanced search capabilities have enabled critical collaboration. Now, as new developers start work at Trendyol, they are not faced with learning multiple tools and repeatedly shifting into different environments, according to Civici. “GitLab included all the processes needed to execute a project within a single platform,” he said, adding that GitLab is a “very mature on-premises solution.”\n",{"header":5371,"text":5372},"Faster development enables critical business strategy","Adopting the GitLab platform has meant a 30% improvement in developer productivity, which has translated into a dramatic market expansion. The developer experience is significantly enhanced with this standardization, providing a combined repository, registry, and CI/CD view for developers, along with reliable operations updates for DevOps managers.  New developer onboarding times have dropped from 10 days to eight days as a result of using a single, end-to-end platform and not a disparate toolchain. This high level of integration means GitLab can operate together with LDAP, JIRA, Slack, and similar applications. And streamlined integration with Kubernetes helps Trendyol teams accelerate the addition of new platform features and updates. “GitLab included all the processes needed to execute a project within a single platform,” said Civici.\n\n\nGitLab automation means developers are no longer burdened with many manual documentation tasks, while GitLab advanced search allows them to more easily reuse and share code. The platform also helps them learn from each other. For crucial pipeline configurations, GitLab's simple YAML-based processes ensure repeatable processes, while its container-based runner architecture easily handles 70 or more Kubernetes clusters. GitLab features, such as Service Desk and Issues, provide additional productivity. GitLab's priority support further assures 24/7 assistance for the vital infrastructure that powers production services. Trendyol's DevOps and platform teams now are successfully deploying infrastructure as code, and expanding resources into multiple data centers. And using GitLab, launching a new application has become 50% faster - now taking just one day when it used to take two.\n\n\nGitLab has become a key part of how the company creates a robust platform that drives its business strategy to become one of the largest e-commerce companies in the world, offering a full range of customer services.\n",{"template":950,"size":40,"region":106,"industry":63},"content:en-us:customers:trendyol.yml",{"_path":5376,"content":5377,"config":5423,"_id":5424},"/en-us/customers/university-of-cambridge",{"name":5378,"logo":5379,"hero":5380,"heroImage":5381,"benefits":5382,"industry":65,"employeeCount":5391,"location":5392,"solution":913,"stats":5393,"headline":5403,"summary":5404,"quotes":5405,"content":5410,"companySize":1281,"region":1281,"contributors":1281},"University of Cambridge","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518016/vnzqqh84qxelyh7refhj.png","University of Cambridge Information Services paves path to DevSecOps with GitLab","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518460/yvf6fin36xy7y6xixpw2.jpg",[5383,5385,5388],{"metric":2150,"config":5384},{"icon":1895},{"metric":5386,"config":5387},"Enables self-service",{"icon":1415},{"metric":5389,"config":5390},"Successful workflow implementation",{"icon":902},"24,450 students","Cambridge, UK",[5394,5397,5400],{"value":5395,"metric":5396},"500 to 4,000","Project growth",{"value":5398,"metric":5399},"100s to 50,000","Issue tracking growth",{"value":5401,"metric":5402},"0 to 12,700+","Merge request growth","University Information Services (UIS) is helping to drive improved collaboration across departments and evolve new processes along with new digital transformation initiatives.","The need to keep pace with a more rapid rate of versioning, as well as new demands of global research, led a leading university to explore DevOps software.\n",[5406],{"quoteText":5407,"author":5408,"authorTitle":5409,"authorCompany":5378},"Cloud native GitLab efforts aligned well with our internal deployment processes.\n","Dr Abraham Martin","Head of Development and Operations (DevOps)",[5411,5414,5417,5420],{"header":5412,"text":5413},"Leading Oxbridge University transforms its DevSecOps function","At the the Development and Operations (DevOps) Division within University Information Services (UIS) at the University of Cambridge, GitLab now serves as part of efforts to manage software builds and updates across a highly active and varied user base. The GitLab instance is maintained by the Development and Operations (DevOps) Division within University Information Services (UIS) at the University of Cambridge.\n\nIt has used GitLab as it works to achieve better visibility and collaboration in and among diverse academic and research programs. Such tooling is part of the effort to continually improve the educational and research capabilities of the institution. UIS provides University-wide services to staff and students with a wide scope of requirements. These range from Student Groups like the Cambridge University Robotics Lab or Cam FM, Cambridge and Anglia Ruskin Student Radio, to Research Groups like the Computational and Digital Archaeology Lab; the Cambridge Advanced Imaging Centre; Cancer Research UK, Cambridge Institute; and the Wolfson Brain Imaging Centre. UIS also supports academic services, including Moodle and student admissions systems that were stress tested during the Covid-19 pandemic. This all translates into a dynamic, ever-changing environment. The focus is on delivering internal services that display the same fit and finish that public-facing services present.\n",{"header":5415,"text":5416},"Fragmented tools led to inefficiencies and siloed teams","UIS faced a number of issues that led teams to explore new source code management options. It was difficult to keep up with the rapid pace of modern versioning, or gain adequate visibility into operations. Teams wanted to evolve new paths toward automated software development practices. Among the challenges identified by UIS was the deployment of software components that required separate and continual on-premises tool versioning. Also, development teams looked to ensure academic researchers' efforts to use more open data sets, and open-source software development, were supported. Add to this challenge the fact that different University departments were maintaining and using their own different tooling.\n\nOverall, a more unified approach to the process was desired. After a series of interviews with users, the group chose to upgrade from basic use of Git repository services, while ensuring reliable continuity for long-running research projects.\n",{"header":5418,"text":5419},"A robust code repository facilitates collaboration","GitLab was employed to help support production, staging and development for the group, as well as to achieve greater coherence for development and operations. GitLab's open-source lineage also fits within University of Cambridge's overarching goal to support open-source culture. “Having an institutionally supported git hosting service provides a useful way to share materials collaboratively with colleagues. Mirroring functionality lets me keep copies of open-source projects that I am using in corpora for research\" explains Professor Andrew Rice, Computer Science in The University of Cambridge Department of Computer Science and Technology.\n",{"header":5421,"text":5422},"A unified, optimized workflow","GitLab is used to integrate the varied parts of full-cycle DevOps over the array of the University's customer departments. In doing this, it allows the UIS team to focus on deploying a single tool that enables a broad range of development options. The software provides a unified platform for complex pipelines, including building, different types of testing, integration, and deployment. Agile responses to pressing pandemic challenges were among the successes for these projects. While the University had already started developing digital tooling to aid admission processes, the events of 2020 brought this into sharp focus. GitLab served as a central tool in adapting to the new normal. GitLab CI/CD tooling was instrumental in allowing daily and even hourly releases - some of which by necessity were continually adjusted to the changing demands of pandemic response. GitLab has supported the University to continue its focus on innovation and providing its stakeholder groups with one DevOps platform.\n",{"template":950,"size":44,"region":106,"industry":67},"content:en-us:customers:university-of-cambridge.yml",{"_path":5426,"content":5427,"config":5474,"_id":5475},"/en-us/customers/university-of-surrey",{"name":5428,"logo":5429,"hero":5430,"heroImage":5431,"benefits":5432,"industry":65,"employeeCount":5439,"location":5440,"solution":913,"stats":5441,"headline":5451,"summary":5452,"quotes":5453,"content":5461,"contributors":1281},"University of Surrey","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518017/y91rlj5vougczfnqcxmc.svg","The University of Surrey achieves top marks for collaboration and workflow management with GitLab","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518461/e4sysrnehdp7k35ransr.jpg",[5433,5435,5437],{"metric":1193,"config":5434},{"icon":1526},{"metric":1893,"config":5436},{"icon":1295},{"metric":1897,"config":5438},{"icon":1580},"4,000","UK",[5442,5445,5448],{"value":5443,"metric":5444},67,"Runners serving jobs from 150 projects",{"value":5446,"metric":5447},"2,300+","GitLab projects on its platform",{"value":5449,"metric":5450},"110K","Builds created by 830 active users","The University of Surrey is a leading research university dedicated to providing exceptional teaching and practical learning to over 17,000 students.","Learn how GitLab’s stable code repository fosters collaboration and visibility at the University of Surrey.\n",[5454,5457],{"quoteText":5455,"author":5456,"authorTitle":4496,"authorCompany":5428},"We like that GitLab is a platform that provides a one-point solution for many things. It's not just a repository; it has many features, including Wiki, Pages, analytics, a web interface, merge requests, CI/CD, and issue comments. You can collaborate in issues and merge requests. It's a nice package overall.\n","Kosta Polyzos",{"quoteText":5458,"author":5459,"authorTitle":5460,"authorCompany":5428},"GitLab does a really good job of visualizing the branch structure of a given Git repository, allowing me to quickly refer back to a previous version of code rather than checking out individual branches/hashes at a time.\n","Matthew Shere","Postgraduate research student",[5462,5465,5468,5471],{"header":5463,"text":5464},"A global community dedicated to education and research","The University of Surrey is a leading research university in England, UK focused on practice-based education. Founded in 1966, The University specializes in engineering, science, and sociology. [The University of Surrey](https://www.surrey.ac.uk) teaches over 17,000 students from around the world and strives to empower its student body for personal and professional success.\n",{"header":5466,"text":5467},"Inefficient file storage and lacking visibility","The Information Technology department at the University of Surrey faced a myriad of challenges in supporting researchers to store code in an on-premise [version control system](/topics/version-control/). The team had to balance the needs of academics who asked for an enhanced version control tool coupled with their own need to collaborate and iterate in a more efficient, modern way. A growing team accompanied a more complex infrastructure, and the previous method of using Subversion or storing files in folders or on storage locations did not support the IT team or academics.\n\n\"We were at a point where we had to collaborate and start doing DevOps the modern way. We had automation tools, infrastructure as code, quick cycles, and testing, but we had a growing team and collaboration wasn't easy to do,\" explains Kosta Polyzos, Senior System Administrator. Compounding the difficulties was the lack of an interface to easily provide visibility into work. It was becoming increasingly difficult for colleagues to keep track of progress and make informed contributions at the right place, to the right effect. Committed to increasing collaboration, the team set out to find a solution that offered reliability and a seamless single interface to coordinate work.\n",{"header":5469,"text":5470},"A stable, reliable code repository facilitates collaboration","Determining a solution required factoring in several unique considerations. The main request from all stakeholders was to have a stable code repository that enabled rapid collaboration. Because the University of Surrey has strict regulations regarding data, the team also needed an on-premise solution to ensure full compliance. Academics may not have strong Git skills, so the solution also needed to have a low barrier to entry for people to collaborate and support quick adoption.\n\nConsidering these factors, the team identified GitLab as the solution to increase collaboration and iteration across teams regardless of role. By starting on a free tier, the team was able to try out features, and when GitLab provided [free, unlimited licenses for academic institutions](/solutions/education/), every feature became available to them. \"This was very good news for us, because we have access to every GitLab feature. It doesn't mean that everyone will use all the extra features, but they're available to solve specific problems if someone needs a solution. I think it's a good thing for universities and their research communities,\" Polyzos said.\n\nGitLab has satisfied academics as well. As Polyzos explained, \"GitLab's GUI helps people understand what is going on by visualizing all things Git. I'm not sure people were particularly familiar with Git, but learning it through GitLab made it very easy to get people on board.\" As Oscar Mendez Maldonado, Research Fellow, explained, \"Having a university-hosted repository is crucial to ensuring access, safety, and reliability.” With GitLab, the team increased collaboration and was able to implement a streamlined workflow, bringing together contributors and breaking down silos.\n",{"header":5472,"text":5473},"A modern, flexible workflow","The University of Surrey has over 2,300 projects and 110,000 builds. These efforts are made possible by implementing a seamless workflow in which users create personal branches from issues and test solutions before merging into the main branch and deploying to the production line. This workflow has improved the way the team delivers their service and simplified their growing infrastructure. \"When it comes to operations, we wouldn't have been able to cope. GitLab's code repository and CI are the two main things that have enabled this for us,” Polyzos said.\n\nGitLab has helped the IT team write more and better code and create a DevOps model. \"This modern world of IT is not a single problem with a single solution. You need many tools in your toolchain. GitLab is a core tool with a central place in our toolchain. It has enabled us to further explore other tools and combine them,” Polyzos shared. \"GitLab helped us implement the workflow architecturally, and we can iterate and go through the workflow again and again to improve. It has also helped us better integrate testing into the workflow. Protected branches and merge approvals provide control over the flow of new code before CI/CD pushes out the changes. Basic syntax and linting errors have essentially disappeared, and logical errors are caught earlier in the workflow.”\n\nWhile the IT team has made use of GitLab's branching, testing, and coding capabilities, academics have incorporated GitLab in the teaching environment due to its GUI, which provides a simple code visualization to identify changes and authors. In a group assignment, professors find it useful to understand which students committed specific changes. \"Users appreciate the seamless interface - from setting up SSH keys to navigation - so that every little detail makes the user experience really enjoyable and effortless. Someone with no Git experience whatsoever doesn't feel intimidated by it,” Polyzos said.\n\nAs the IT team and academics tinkered with GitLab to discover the features that meet their needs, the usefulness of GitLab's applications development features has slowly spread throughout the University of Surrey. \"GitLab is a reliable tool and code repository first and foremost. It lubricates workflows in various ways and allows for collaboration internally as well as externally,\" Polyzos added.\n\nSome users have built custom Docker images by uploading files and setting GitLab runners to build the images for them, while others who require a website now use GitLab Pages. As Dean Roe, System Administrator Team Leader, said \"We are continually impressed at the rate at which GitLab expands its feature set in useful ways. The blog posts on gitlab.com do an excellent job of telling us and our users what fixes and new features we can expect in each new release. The process of bringing in updates is effortless too.\n\nBy using GitLab, the University of Surrey has increased collaboration, while developing higher quality code through a robust solution to deliver better software faster. \"We like GitLab, and the users like it. It's stable and trustworthy, and we're definitely going to continue using it.”\n",{"template":950,"size":44,"region":106,"industry":67},"content:en-us:customers:university-of-surrey.yml",{"_path":5477,"content":5478,"config":5524,"_id":5525},"/en-us/customers/us-army-cyber-school",{"name":5479,"hero":5480,"heroImage":5481,"benefits":5482,"industry":2050,"employeeCount":5492,"location":5493,"solution":913,"stats":5494,"headline":5503,"summary":5504,"quotes":5505,"content":5511,"contributors":1281},"U.S. Army Cyber School","How the U.S. Army Cyber School created “Courseware as Code” with GitLab","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518461/jbj8ween51iaqlgcywgb.jpg",[5483,5485,5488],{"metric":1293,"config":5484},{"icon":1895},{"metric":5486,"config":5487},"Enhanced CI integration",{"icon":2105},{"metric":5489,"config":5490},"Easy template creation",{"icon":5491},"ClipboardCheckAlt","200+","Fort Gordon, Georgia, U.S.",[5495,5498,5501],{"value":5496,"metric":5497},"36x","faster review cycles",{"value":5499,"metric":5500},"8,415","commits by students and contributors",{"value":4973,"metric":5502},"courses created using GitLab","The U.S. Army Cyber School wanted to build its software development using Git and continuous integration (CI) and found success with GitLab’s all-in-one solution.","The U.S. Army Cyber School created secure, collaborative coursework with GitLab continuous integration and delivery (CI/CD), DevOps, and source code management (SCM).\n",[5506],{"quoteText":5507,"author":5508,"authorTitle":5509,"authorCompany":5510},"Instead of having to teach people 10 different things, they just learn one thing, which makes it much easier in the long run.\n","Chris Apsey","Captain","U.S. Army",[5512,5515,5518,5521],{"header":5513,"text":5514},"The U.S. Army Cyber Center of Excellence","The [U.S. Army Cyber School](https://cybercoe.army.mil/Home/Schools/Cyber-School/) is responsible for the functional training and education of all U.S. Army 17 Series Soldiers. The U.S. Army Cyber School provides students with the required knowledge, skills, and abilities related to Defensive Cyberspace Operations (DCO), Offensive Cyberspace Operations (OCO), Electronic Warfare (EW), and cyberspace planning, integration, and synchronization.\n",{"header":5516,"text":5517},"Starting Git from scratch","After being established in 2014, the U.S. Army Cyber School at Fort Gordon was tasked with creating the school’s software development process from the ground up. There wasn’t a legacy system to manage or update, but at the same time, the school had nothing to work from — no instructors, no content, and no playbook to follow.\n\nAs the team started to create content for the program, the data was primarily created and stored on individual laptops. That approach quickly became problematic when the school experienced turnover and content was lost when individuals left the organization. Other early tactics included emailing around Zip files and whiteboarding, which resulted in an inefficient and exceedingly manual process. The school also lacked a way for the team to collaborate and track progress on their projects. Without a common repository for the team to contribute to, the school risked losing the valuable content they paid contractors to develop.\n\nTo address their growing challenges, the school drew inspiration from other teams doing software development and began their search for a Git-based solution for their unique situation. The goal was to empower the team with “Courseware as Code” and use DevOps principles like CI/CD to replace the traditional maintenance of content in documentation styles (presentations, word processing documents, spreadsheets, etc.) with markdown language and CI pipelines.\n\nCaptain Christopher Apsey and his team wanted one software tool that would allow developers to collaborate on a single corpus of information, a platform for students and staff to use Git and provide a way to [access CI pipelines](/blog/guide-to-ci-cd-pipelines/){data-ga-name=\"continuous integration\" data-ga-location=\"customers content\"}. They researched GitHub, Gogs, Node Kitten, and Gitea, and ultimately chose GitLab because it offered a variety of services that other platforms didn’t match, including integrated CI. With the collaborative capabilities of GitLab, coursework and certification assessments were established.\n",{"header":5519,"text":5520},"From a Zip drive to CI pipeline","The U.S. Army Cyber School uses their GitLab instance to administer and grade the programming exam, the first certification assessment for 17 Series Developers in the Army. The CI pipeline is used for grading exams, which is an interactive JavaScript website hosted on GitLab pages that summarizes test results. The process is actively being developed in order to streamline grading and certification through automation and collaboration.\n\nTo achieve a successful Courseware as Code deployment, nearly every piece of technical content the school has curated in GitLab has been written in markdown language. This includes student templates, course content, slide decks, and handouts. All of the content production has been CI driven and is completed in the same fashion as software development. Whenever someone makes a change to a document, it is recorded and stored within GitLab as the [single source of truth](/topics/version-control/){data-ga-name=\"single source of truth\" data-ga-location=\"customers content\"}.\n",{"header":5522,"text":5523},"SCM, CI/CD, and DevOps for career success","Through the implementation of GitLab’s automated workflow, the U.S. Army Cyber School has established coursework for multi-instructor, multi-contributor, location-disparate classes and has solved many of the limitations that they previously experienced. There have been six courses created using GitLab and over 4,000 merges between instructors and students.\n\nBecause everyone contributes within the central repository, no one leaves the school with government information, which had formerly been an exfiltration risk. The school is also benefiting from alumni who can contribute their knowledge from the field and provide real-time field updates. Graduates are encouraged to shape the learning material for current students by submitting merge requests directly into the course repositories.\n\nWith DevOps, SCM, and CI/CD firmly in place, all contributors work in a collaborative and transparent environment. Issues, boards, epics, and checklists are heavily used as data tools to increase student participation. These GitLab features allow instructors to easily track how students are progressing. Traditional documentation formats have been replaced with GitLab’s trackable project repositories. “We can now look and say, ‘Who’s doing what? Who’s value-added? Who’s being a team player, who’s slacking off?’ all within the GitLab commit history,” CPT Apsey said.\n\nExams are created using a group-level template with the seed from a student’s examination file. The exam template includes a merge request and issues, so when a new project is created the student has their own repository. “We add them as a developer to the repository and they make commits to any branches they want and merge them into develop or they can make commits straight to develop. It’s from that open MR where we have the conversation and grade,” said CPT Jessie Lass, Senior Developer, U.S. Army.\n\nReview cycle times previously took three years, but with GitLab’s asynchronous collaboration it now moves much faster. “In GitLab I’ve been able to tag people and then within a week get feedback. I wouldn’t say it’s a full formalized review cycle, but certainly from years down to months,” according to CPT Benjamin Allison, Cyberspace Operations Officer.\n\nUsing GitLab has not only improved the internal development of examinations, but it is also helping students become proficient in Git. “My hope is that these candidates, once we certify them, they’ll have had a little bit of exposure to what a healthy professional development workflow looks like. So when they show up onto a team, they’re actually ready to work,” CPT Jessie Lass said.\n",{"template":950,"size":40,"region":102,"industry":79},"content:en-us:customers:us-army-cyber-school.yml",{"_path":5527,"content":5528,"config":5567,"_id":5568},"/en-us/customers/uw",{"name":5529,"logo":5530,"hero":5531,"heroImage":5532,"benefits":5533,"industry":5542,"employeeCount":5543,"location":2706,"solution":975,"stats":5544,"headline":5550,"summary":5551,"quotes":5552,"content":5558,"contributors":1281},"University of Washington","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518019/ol6uucfcqwgx9bn5lgfe.svg","The Paul G. Allen Center for Computer Science & Engineering gains control and flexibility to easily manage 10,000+ projects","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518462/tw2tmlgvpcf0uwlj5rvk.png",[5534,5536,5538],{"metric":4424,"config":5535},{"icon":1636},{"metric":1893,"config":5537},{"icon":1295},{"metric":5539,"config":5540},"Greater flexibility",{"icon":5541},"Arrows","Public sector - University","1,500 users",[5545,5548],{"value":5546,"metric":5547},2000,"users suported by 1 engineer",{"value":978,"metric":5549},"projects hosted","The Paul G. Allen Center for Computer Science & Engineering (the Allen School) at the University of Washington (UW) is consistently ranked as one of the top computer science and computer engineering programs in the U.S.","Learn how GitLab has scaled to effectively host more than 10,000 projects, representing roughly 400 GiB of data, in one instance\n",[5553],{"quoteText":5554,"author":5555,"authorTitle":5556,"authorCompany":5557},"Over the past two years, GitLab has been transformational for our organization here at UW. Your platform is fantastic!\n","Aaron Timss","Director of Information Technology","CSE",[5559,5561,5564],{"header":5550,"text":5560},"The school is in the midst of a dramatic expansion as the demand for computer science degrees has never been higher. The Allen School currently consists of nearly 1,000 undergraduates, 250 PhD students, and 70 faculty members, who leverage version control and continuous integration tools to complete everything from class assignments to open source research and educational outreach projects. Aaron Timss, Director of Information Technology at the Allen School, leads a team of 20 software engineers and technical staff who are responsible for selecting and optimizing the tech stack that supports the school’s research, instructional, and development needs.\n",{"header":5562,"text":5563},"For years, the Allen School had been using Subversion (SVN) in conjunction with some homegrown scripts to support a flat, ad hoc version control system.","Faculty and students were getting frustrated with the slowness and workflow limitations of SVN, and having to rely on arcane Linux scripts to manage permissions on group directories and repositories. Fed up with SVN, they quietly turned to online Git repository managers, such as GitHub, to host their course assignments and collaborate on projects. But in some cases, students were inadvertently leaving their class assignments ‘public,’ violating university policy. The Allen School had world-facing open source projects. The critical requirement was to find a solution that provided federated login for external collaboration, while ensuring protections on sensitive projects, such as student coursework and unpublished research.\n\nFaced with these challenges, along with a rapidly growing user base, it was clear the Allen School IT team needed to find a solution that met both the collaboration and security requirements of their students and faculty. The team initially considered a number of self-managed options, including GitHub Enterprise. However, this platform didn’t provide an easy way for research teams to share and collaborate on their open source projects with external investigators or institutions. After some additional research, in the fall of 2014, the team decided to move forward with GitLab.\n",{"header":5565,"text":5566},"The Allen School has been using GitLab for more than two years and recently surpassed the milestone of their 10,000th project","Jason Howe, a software engineer on the school’s IT team, led the process of making GitLab available to the school’s students and faculty. Six months after rolling GitLab out, Howe authored provisioning tools on top of GitLab to enable faculty members to easily add students to course-specific projects. As more students started to use it as part of their class work, adoption climbed, and the number of projects on GitLab skyrocketed.\n\nIT staff noticed students had begun opting to host more of their personal development projects on the platform. And adoption by Allen School instructors jumped from the initial handful of early adopters to a few dozen. Other units within the university also began to be interested in using the platform. The IT team noted that it has been extremely pleased with GitLab’s ability to easily scale with the demands of their growing organization, and they appreciate GitLab’s fervor for further developing the platform and staying on top of security issues. Even as usage of GitLab continues to grow, Howe and the team still find the product easy to maintain. They spend just one to two days per quarter updating and maintaining the platform.\n\nThe Allen School’s students, faculty, and IT team are happy with their decision to choose GitLab. Howe sums up GitLab’s benefits in two words: control and flexibility. From an admin or systems perspective, GitLab gives the IT team the necessary controls to ensure that sensitive university research and students’ coursework are all easily manageable and kept safe. And in terms of flexibility, GitLab is open source, which makes it possible for the IT team to build unique SSO and provisioning tools against GitLab’s API.\n",{"template":950,"size":40,"region":102,"industry":67},"content:en-us:customers:uw.yml",{"_path":5570,"content":5571,"config":5616,"_id":5617},"/en-us/customers/veepee",{"name":5572,"logo":5573,"hero":5574,"heroImage":5575,"benefits":5576,"industry":81,"employeeCount":5585,"location":5586,"solution":2108,"stats":5587,"headline":5596,"summary":5597,"quotes":5598,"content":5603,"contributors":1281},"Veepee","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518021/ijbr5955xybcahg4fso0.svg","How Veepee accelerated deployment from 4 days to 4 minutes","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518463/effkt5rplyuv2c2p94xq.jpg",[5577,5580,5583],{"metric":5578,"config":5579},"Native CI integration",{"icon":2105},{"metric":5581,"config":5582},"Improved workflow",{"icon":2553},{"metric":4475,"config":5584},{"icon":902},"6,500","La Plaine Saint-Denis, France",[5588,5591,5594],{"value":5589,"metric":5590},"99.98%","Customer availability rate",{"value":5592,"metric":5593},"\u003C3","Months adoption time",{"value":3452,"metric":5595},"Minute deployment, down from 4 days","Veepee completely overhauled its central repository and increased deployment and security with GitLab.","GitLab Enterprise helped transform Veepee’s IT production with enhanced continuous integration (CI), automated testing, and expedited continuous delivery (CD) for improved process workflows.\n",[5599],{"quoteText":5600,"author":5601,"authorTitle":5602,"authorCompany":5572},"Veepee’s availability rates went to 99.98% due to the faster feedback cycle and accelerated triggers.\n","Antoine Millet","Head of IT Operations",[5604,5607,5610,5613],{"header":5605,"text":5606},"European e-commerce company","Veepee, formerly known as vente-privee.com, was founded in 2001 as an e-commerce company that specializes in flash online sales. Veepee creates daily sales events in partnership with leading brands, on a limited-time basis with specific products, sold at heavily discounted prices for industrial or promotional reasons.\n\nBased throughout Europe, \u003Ca href=\"http://www.veepee.com/\" target=\"_blank\">Veepee\u003C/a> represents the successful transformation of a long-established activity — clearance sales — through a revolutionary e-commerce model that has since been copied worldwide. vpTech, the Veepee Tech community, supports the business and the growth. The team handles more than 70 products using around 50 technos. As a European company spread in six different countries, they advocate feature teams that are flexible, autonomous, and multicultural.\n",{"header":5608,"text":5609},"Spreading the inner-source philosophy to improve overall delivery process","The year 2016 was a turning point for Veepee that included expanding the company throughout Europe. To get ahead of any upcoming issues, the vpTech team came with a strong promise: Align all Veepee legacies and adopt a modern and agile information system. To do so, the team grew up from 300 to 750 people.\n\nAt the beginning, vpTech faced several challenges with its initial release workflow. Each team worked within their own toolset, which made collaboration and contribution difficult. Teams were frustrated that they couldn’t easily access other’s code and had no way to successfully collaborate with others.\n\nAlso, with the previous workflow, deploying to production was a slow and tedious process. “It was not an ideal situation at all, as it was nearly impossible to release something fast — only emergency cases were free from the whole process,” explained Antoine Millet, Head of IT Operations at Veepee.\n\nvpTech was looking for a way to modernize its engineering infrastructure and enforce inner-source. At the same time, top management wanted to keep code and instances in house and stay off the cloud for the time being. CI integration was  a key requirement for the development teams.\n",{"header":5611,"text":5612},"GitLab and its complete toolsets","vpTech chose to fully reboot its tooling and workflow to modernize engineering tools within the company in order to allow teams to work in a singular environment with common tool sets and shared methodologies. vpTech researched and ended up adopting GitLab. “Three years ago, the biggest difference between GitLab and GitHub was the native CI integration. That's something we really needed at Veepee,” Millet said.\n\nThe team adopted GitLab rather quickly. The initial goal was to start with 300 licenses over the span of three years. However, developers gravitated toward the platform and demanded more within the first six months of the adoption period. Within a year, vpTech had over 1,000 licenses.\n\nvpTech set out with new technology and deployment initiatives. The first initiative was to get developers onboarded to GitLab and completely off of the previous workflow. The second was to explain and spread the inner-source philosophy: If you need something, contribute. The third was to ensure that if a deployment in production happens, testing occurs in the GitLab [CI pipeline](/topics/ci-cd/pipeline-as-code/) for visibility.\n",{"header":5614,"text":5615},"A new workflow, a changed culture","Engineering and product team workflow has improved significantly. If the team wants to change a form on the website, or introduce a new A/B test, they simply release code. If the test passes, they can deploy in production. “Before GitLab, it could take up to four days for a production deployment because we had to involve a lot of people. Right now, it's a few minutes without any human in the middle. It's fully automatic,” Millet said.\n\nThe technology and the deployment process with [GitLab CI](/solutions/continuous-integration/){data-ga-name=\"continuous integration\" data-ga-location=\"customers content\"} belong to the product team, so they are empowered with choices for how they deploy. “We produced the last component of the CI, the deploy part. We created tools for engineering which will automatically execute blue and green deployment for them to try everything through canary deployment. If it's validated, it’s deployed in production. That's the front workflow,” Millet added.\n\nThe site reliability engineering (SRE) team produced a lot of CI templates, which created a center of knowledge for the teams. If there is a new developer in the company, templates can be easily accessed in order to get started. “We have sets of linter for all languages pre-templated by the SRE team. Basically, you just choose that first component. In the middle, for the test, you put your own code because you know what you did, so the test part is for your team,” according to Millet. The deployment is templated for either Nomad and Kubernetes to get in production.\n\nIn the last three years since adopting GitLab, Millet has never received a single complaint about the platform. GitLab significantly changed the culture of a 16-year-old company by improving transparency, workflow, and developers’ time. “It took almost a year for people to adopt GitLab as it was a change of habit, change of the way to work. Now it's working really well. At this point, we have developed a tool named DevHub on top of GitLab to make statistics and give a full view for the top management,” Millet said.\n",{"template":950,"size":44,"region":106,"industry":83},"content:en-us:customers:veepee.yml",{"_path":5619,"content":5620,"config":5665,"_id":5666},"/en-us/customers/victoria-university",{"name":5621,"logo":5622,"hero":5623,"heroImage":5624,"benefits":5625,"industry":65,"employeeCount":5632,"location":5633,"solution":913,"stats":5634,"headline":5644,"summary":5645,"quotes":5646,"content":5652,"contributors":1281},"Te Herenga Waka—Victoria University of Wellington","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518022/r5yzwppnms4p2yfnmtpm.svg","GitLab advances open science education at Te Herenga Waka – Victoria University of Wellington","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518464/scasnefy6drh5rlodku4.jpg",[5626,5628,5630],{"metric":961,"config":5627},{"icon":963},{"metric":1524,"config":5629},{"icon":1526},{"metric":1843,"config":5631},{"icon":1845},"2,300","Wellington, New Zealand",[5635,5638,5641],{"value":5636,"metric":5637},35,"GitLab-enabled courses",{"value":5639,"metric":5640},"8,000+","projects across 2,212 groups",{"value":5642,"metric":5643},"768+","active users","Te Herenga Waka – Victoria University of Wellington’s School of Engineering and Computer Science needed a single, integrated solution to simplify processes and encourage adoption across all user groups.","GitLab enables software coursework and project management with a single, simplified solution for faculty and students.\n",[5647],{"quoteText":5648,"author":5649,"authorTitle":5650,"authorCompany":5651},"When I heard about GitLab Self-Managed, it was a very clear choice. It was really only GitLab that fulfilled the requirements I had within the engineering project management courses. That and GitLab being one single product.\n","Dr. James Quilty","Director Of Engineering","Te Herenga Waka – Victoria University of Wellington",[5653,5656,5659,5662],{"header":5654,"text":5655},"School of Engineering and Computer Science at New Zealand’s top-ranked research university","Te Herenga Waka – Victoria University of Wellington’s School of Engineering and Computer Science has been New Zealand’s innovation hub since the advent of the country’s first internet connection by Professor John Hine. The greater university, founded in 1897, is the island nation’s leading institution for research quality and intensity. In this tradition, the School, located within the University’s Faculty of Engineering, developed an expert-led curriculum with a focus on applied learning. The School’s Bachelor of Engineering (with Honors) degree holistically prepares students for real-world technology systems by offering career-minded coursework in project management and entrepreneurship.\n",{"header":5657,"text":5658},"Finding a single, compliant solution for all user groups","The School of Engineering and Computer Science’s comprehensive professional program had multiple systems for tracking contributions and content. Lecturers were using Blackboard, the school’s customized Wiki page, personal web pages and even Google Docs for course content. Students were typically given discretion to choose the system to use for their course work. “When I joined the School, my first job was to develop and deliver courses in engineering project management and professional practice. I quickly came to realise that the use of multiple was problematic because few of them provided the features required and there was a lot of unnecessary variability, which complicated both teaching and learning,” says Dr. James Quilty, Program Director for Engineering.\n\nOther staff agree. “My experience at another institution running the full Atlassian Stack was that the administration overhead was too high, and the tools were overkill for the size and scope of the work we were doing,” says Dr. Simon McCallum, Senior Lecturer. “I prefer to use professional project management tools, rather than tools that enable less transfer to the real environment.” Few of the previous tools provided proper version history or issue tracking, so collaboration wasn’t possible. Both students and lecturers lacked transparent insights into academic progress. Distributing information via PDFs and Word documents offered little benefit. “Information was fragmented across multiple files, multiple formats – sitting often on file systems, not necessarily under good version control,” says Dr. Quilty.\n\nThe previous environment’s biggest negatives included time lost on administration and the impact that had on the overall education of the students. “Time is the most precious commodity while teaching. The maximum percentage of time should be spent on things that affect student achievement. Admin tasks for the sake of it are wasteful and limit the capacity to create excellent learning environments,” says McCallum. To improve continuity in education and innovation, the engineering program needed a single, integrated solution to simplify processes and encourage adoption across all user groups. However, the university has strict intellectual property and confidentiality agreements which narrowed the School’s platform options. “I see GitLab as a critical source in open science. The ability to share code that has been created with an open license is great, and I appreciate that most people are nudged to open their projects by providing free hosting for open projects. This encourages more code and resources to be available for universities,” adds McCallum.\n",{"header":5660,"text":5661},"GitLab Self-Managed for on-premises hosting","Dr. Quilty acquainted himself with GitLab as a project management tool beginning in 2015. “My current role grew from the project management side of things, and it’s in that context of teaching engineering project management in a school that’s heavily focused on software engineering in particular, as well as electronics engineering, that I came into contact with GitLab as a product,” says Dr. Quilty. Previously, educators had remained solution-agnostic — using GitHub, Atlassian, Trello, Subversion, Blackboard, and Fronter. Many academics, including Dr. Quilty, allowed students to choose their own developer tools for project execution. Dr. Quilty soon understood that students often lacked the experience to identify appropriate software solutions, which led to disparate learning experiences. Dr. Quilty briefly explored GitHub as an alternative but preferred GitLab’s open DevOps platform.\n\nAs an organizational experiment, a small group of academics began using GitLab in 2017. Dr. Quilty notes, “I think everybody was using GitLab from that point on. It was a very rapid transition from 2018 onwards for course delivery right through from second year all the way through third to fourth year, as well as some people adopting it for their research.” The University ultimately chose GitLab for the Educational license for the professional suite of tools and onsite hosting. The program seamlessly implemented a single sign-on for GitLab and Mattermost (an open source, university-compliant chat service) to increase collaboration without complicating its toolchain. GitLab LDAP integration further simplified adoption.\n\nFor Dr. Quilty and the greater university, the open platform also served to reinforce academic values. Open source support was a key factor in aligning software with curriculum; other previously considered solutions, such as Microsoft Project, failed in this category. GitLab’s openness extended to project methodologies as well, allowing academics the freedom to teach agile planning without limiting the potential for future courses on other frameworks.\n",{"header":5663,"text":5664},"Empowering learning and open science education","Victoria University of Wellington’s engineering and computer science students now leverage GitLab for managing software projects. Both students and educators have gained transparency by tracking coursework with issues, boards, epics, and milestones — all hosted on a local instance of GitLab per university governance. GitLab is being used both as a tool to manage the content of the class and as a tool for students to use to develop their own content. Students can submit repositories as the submission for assignments. They can then check histories and better manage work with issues and boards.\n\n“I use it to manage the progress of students through the Master’s program,” says McCallum. “Each student is an issue in the service desk, this allows me to share any communication with them, with the supervisor, and provides a single location for all the communication that is shared with the supervisor.” With greater academic transparency came focused collaboration. Dr. Quilty praised the newly acquired processes resulting from the transformation: “When it came to reviewing the students’ work, particularly the reports that they had to generate or other documentation, they raised merge requests for the various chapters and then asked for me to go through and do approval. And since all of that was either Markdown or LaTeX, it was really quite good to be able to make comments, suggestions on the original code, have those all in the version control, and multiple connections. It was a really good way of managing that writing process, surprisingly so.”\n\nThe School of Engineering and Computer Science has seen rapid adoption of the platform. As of 2021, student users are up by more than 483% since 2017. The program has also added 34 GitLab-facilitated courses in that same timeframe. Over 2,000 groups at every level, from researchers and lecturers to undergraduates and postgraduates, contribute to more than 8,000 projects. GitLab has enabled a form of continuous learning at the School of Engineering and Computer Science. Students actively engage in problem-solving, using the platform to get real-time educational feedback. It also helps students prepare for working in a modern, engineering-oriented team environment\n\nUndergraduate teams working on electronics development have used GitLab to run automated tests of their designs by configuring their .gitlab-ci.yaml script to create a Docker container. The script runs the KiCad electronic design automation (EDA) suite in graphical user interface (GUI) mode to execute these tests. Postgraduate students have employed GitLab to set up hardware-in-the-loop testing with GitLab Runner. By copying and executing the embedded code from the repository to a microcontroller-based device under test, via USB-connection from a small Linux server executing GitLab Runner, the students ran automated tests and success/failure reports to streamline hardware and software co-development. With 30,000-plus issues and nearly 15,000 merge requests, it’s easy to see how the engineering program at Victoria University of Wellington has leveraged GitLab-led learning to power innovation.\n",{"template":950,"size":44,"region":110,"industry":67},"content:en-us:customers:victoria-university.yml",{"_path":5668,"content":5669,"config":5713,"_id":5714},"/en-us/customers/weave",{"name":5670,"logo":5671,"hero":5672,"heroImage":5673,"benefits":5674,"industry":89,"employeeCount":5682,"location":1305,"solution":975,"stats":5683,"headline":5693,"summary":5694,"quotes":5695,"content":5700,"contributors":1281},"Weave","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518024/frsk7lxnqbiqpqhaphex.png","GitLab delivers faster pipeline builds and improved code quality for Weave","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518464/rm89xrxrnmhojh3uhhgm.jpg",[5675,5677,5679],{"metric":4525,"config":5676},{"icon":1302},{"metric":1018,"config":5678},{"icon":1738},{"metric":5680,"config":5681},"Ensured compliance",{"icon":1526},"25",[5684,5687,5690],{"value":5685,"metric":5686},"23%","faster pipeline migration",{"value":5688,"metric":5689},"30x","faster pipeline deployments",{"value":5691,"metric":5692},"78x","increase in weekly microservice deployments","Weave, a Netherlands-based development consultancy, wanted to bring project management and development closer together in order to better help customers transform and innovate.","With GitLab, Weave has been able to create repeatable standard processes and establish a single source of truth covering the full software development lifecycle.\n",[5696],{"quoteText":5697,"author":5698,"authorTitle":5699,"authorCompany":5670},"GitLab enables us to really share a lot of pipeline configurations, and Helm charts. It may not be exactly required to develop a project, but it will make a project more stable and maintainable. Also, you are always up-to-date. GitLab is a big factor in how fast we can implement pipelines, and in improving the quality of code.\n","Dorian de Koning","DevOps Leader",[5701,5704,5707,5710],{"header":5702,"text":5703},"Helping customers transform and innovate","[Weave](https://weave.nl/){data-ga-name=\"weave\" data-ga-location=\"body\"} is a developer of innovative software technologies focused on microservices and cloud-native development. The company leverages open source tools, including Go, Docker, and Kubernetes. The company’s objective is not merely to build and help clients transform their businesses, but to enable clients to carry their own development work forward as well. As it is a young company, Weave embraces what is new. Still, according to Peter-Jan Karens, CTO and co-founder, Weave’s experienced teams prioritize application deployment timelines. “Everybody wants to work with exciting new technologies, but clients want working applications delivered on time,” he said. Among Weave customers are Mijndomein, MobyOne, sustainable energy provider EnergyZero, and the Government of the Netherlands.\n\nUse of open source methods ensures that clients' applications are not dotted with unpredictable dependencies that bind them to proprietary software use. Weave works to help clients with legacy backlog to navigate a new software development landscape. The goal is to enable customers of all sizes to develop new applications on the cloud in much the same way as an Uber, Google, or any big tech company might. “We are trying to put this in the hands of our customers,” Karens said.\n",{"header":5705,"text":5706},"Lacking project management and Agile capabilities","In expanding from the company’s original roots in PHP-oriented web development, Weave developers experimented with alternative ways of handling version control. But some processes were unstable, time consuming, and ‘messy.’ Speed of issue tracking, particularly, was found lacking, and the size of the hosting footprints was a drawback. Overall, Weave’s team concluded important portions of their existing tooling were not optimal for Agile development. Software alternatives for project management and software deployment were found at times to be little more than somewhat enhanced to-do lists, with rudimentary commenting. These had some use in project management, but were not truly a part of the actual development process. What was vitally needed, team members agreed, was closer coupling of project management and development. That meant integration tooling capable of handling issues, branches, merge requests, deployments, and pipelines.\n\nCrucially missing were effective project management features like comprehensive milestones, as well as burn-down charts that showed required work remaining. These traits were deemed crucial to delivering software on time and providing process transparency to clients. In their quest, Weave managers also set forth the goal to find such capability in open source software. As they confronted factors limiting their ability to enable customers’ pressing digital transformation requirements, Weave staff began increasingly to use GitLab open source software. As cloud application migrations became the common application pattern, the company began to deliberately move away from manual pipeline builds to automated GitLab deployments.\n",{"header":5708,"text":5709},"Kubernetes integration, CI/CD builds, and improved collaboration","The move to GitLab Premium coincided with expanded work with cloud and Kubernetes, and projects benefited from GitLab’s strong Kubernetes integration. As Weave implemented GitLab Premium, teams were able to dependably create repeatable standard processes and access a single source of truth covering the full software development lifecycle. Teams were enabled to quickly develop, test, and automate CI/CD pipeline builds to deploy to Kubernetes clusters. GitLab closely mirrored the company’s DevOps strategy, and provided a standard way to connect to the cloud and to deploy Kubernetes. “We really wanted not only to develop on Kubernetes, but also to deploy it through a CI/CD pipeline. And that was when we really started to see the benefits of GitLab,” said Karens. The migration of their GitLab instance to Google Kubernetes Engine (GKE) was “pretty smooth, frees up space and allows us to deploy more; really this migration aligns with our cloud journey and ensures we are at the forefront of innovation,” Karens added.\n\nAfter a brief time of experimentation, the software began to provide a capable template for repeatable deployment. Moreover, GitLab provided clients with transparency into activity, facilitating better communications all around. Weave leaders judge that use of GitLab today positively supports innovative development in small ways that in turn contribute to large and beneficial overall effect. Weave used GitLab to tighten compliance within the company. Yet, experience showed, it provided a natural environment within which developers could work.\n",{"header":5711,"text":5712},"Making digital transformation possible","In Weave’s experience, GitLab has dramatically improved the company’s Agile development program generally — and several key processes specifically. For example, the speed of pipeline migration to Google Cloud was boosted by 23%. This was accompanied by an estimated 30x decrease in developer time required to deploy pipelines. Meanwhile, Weave is now deploying 78x more microservices per week. “We have sprints with retrospectives [and] we want somehow to have these sprints supported in the software. Every development sprint is a milestone. We plan our issues, and then we can see how the sprint is progressing. This is super useful for us,” added Karens.\n\nCompliance helps ensure that high-quality projects are delivered on time, with guidelines for backend developers, front-end developers, and DevOps groups. A ready default pipeline repository ensures adherence to best practices. “With GitLab functionality and updates, we have insight into the process, which feels really nice,” according to Dorian de Koning, DevOps Leader at Weave. Finally, Weave is now better able to co-innovate with its clients via project collaborations based on GitLab. Team leaders have found that developers that work with other companies are familiar with GitLab style development, find it intuitive, and are able to be up and running on projects within just a few hours. In short, GitLab aligns with Weave's values and development philosophy.\n",{"template":950,"size":36,"region":106,"industry":91},"content:en-us:customers:weave.yml",{"_path":5716,"content":5717,"config":5767,"_id":5768},"/en-us/customers/worldline",{"name":5718,"logo":5719,"hero":5720,"heroImage":5721,"benefits":5722,"industry":69,"employeeCount":5733,"location":5734,"solution":4820,"stats":5735,"headline":5745,"summary":5746,"quotes":5747,"content":5754,"contributors":1281},"Worldline","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518024/qdpivt1jsfmitbc5rzfh.png","Worldline improves code reviews’ potential by 120x","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518465/piqob5z0rfigjft1hht2.jpg",[5723,5727,5730],{"metric":5724,"config":5725},"Easy code reviews",{"icon":5726},"MagnifyingGlassCode",{"metric":5728,"config":5729},"Increase in code quality",{"icon":5246},{"metric":5731,"config":5732},"Easier review/planning",{"icon":2553},"11,000 worldwide","Offices in Europe, Asia, and Latin America",[5736,5739,5742],{"value":5737,"metric":5738},"14,500","GitLab projects",{"value":5740,"metric":5741},"100,000+","merge requests",{"value":5743,"metric":5744},"1.4M","CI jobs executed in 1 year","Payment service provider Worldline was looking for a way to increase collaboration and reduce review cycle time in its development phase.","With GitLab, Worldline has decreased cycle time and improved release quality.\n",[5748,5752],{"quoteText":5749,"author":5750,"authorTitle":5751,"authorCompany":5718},"GitLab is the backbone of our development environment. Today we have 2,500 people working on that for us daily.\n","Antoine Neveux","Software Engineering- Kazan Team",{"quoteText":5753,"author":5750,"authorTitle":5751,"authorCompany":5718},"Because we’ve got lots of requests from our users ... most of our users are developers and they are enthusiastic about everything that is happening in the open source world. We’ve got lots and lots of people who are really aware of what GitLab is providing. They are using GitLab.com and they are all following the progress of what GitLab is doing.\n",[5755,5758,5761,5764],{"header":5756,"text":5757},"Powering billions of financial transactions annually","Worldline is the European market leader in the payment and transaction services industry. With innovation at the core of its DNA, Worldline core offerings include pan-European and domestic Commercial Acquiring for physical or online businesses, secured payment transaction processing for banks and financial institutions, as well as transactional services in e-Ticketing and for local and central public agencies.\n\nWorldline processes billions of financial transactions each year. Covering the entire payment value chain, the company’s technological experts create and operate digital platforms that handle the millions of highly critical transactions between a company, its partners, and its customers. The company focuses on three pillars of business: Merchant Services, Mobility & e-Transactional Services, and Financial Services.\n",{"header":5759,"text":5760},"Increasing speed and collaboration with the capabilities of Git","In 2014, the company was looking for a way to increase collaboration and reduce review cycle time in its development phase. One way was to use a chain consisting of many tools including Gerrit, ReviewBoard, CVS, Jenkins, and Subversion. For its branch management capabilities, Git was also used to improve the manual release process.\n\n“Our model required having to request the manual creation of an SVN repository which could take up to a week. And then we had to use that to work together and we were not doing any code reviews,” said Antoine Neveux, Software Engineering - Kazan Team, Worldline. “And some projects, when they were out of the scope for typical Jenkins jobs, were unable to use Continuous Integration.”\n",{"header":5762,"text":5763},"An easy-to-use solution encourages code reviews","To help overcome these challenges, Git capabilities were introduced into the development environment. Worldline started with a vanilla Git product, but it was quickly clear that it wasn’t going to meet the required needs.\n\n“We started using GitLab because we wanted to get an easy Git repository management system and because we wanted people to be able to use merge requests,” Neveux explained. “We wanted the ability to have more code reviews and to ease discussions between developers.”\n\nThe adoption of GitLab was quite successful and, within six months, over 1,000 users were active users. Developers explained that the adoption rate was high because GitLab is so easy to use. People actually felt encouraged to contribute code reviews with GitLab merge requests. Previous code review tools had 10-20 developers using them, while Worldline currently has 3,000 active users of GitLab — an adoption rate increase of 12,000 percent.\n",{"header":5765,"text":5766},"New projects, new opportunities","Worldline now hosts 14,500 projects on GitLab. It previously took 1-2 weeks to get a source code repo; now it takes a few seconds. The company is using GitLab’s CI and merge requests as well as GitLab Pages and Mattermost capabilities. They are also exploring deployments and integration with Kubernetes. Shared runners have helped increase developer acceptance. Before GitLab, Worldline had 15,000 Jenkins jobs running. When GitLab introduced CI, Worldline moved over because GitLab allows users to run continuous integration in separate containers. Now Worldline is running close to 80% of their CI through GitLab.\n\n“Thanks to GitLab CI we allow lots of new projects to come like C++ and .net projects or mobile projects thanks to the fact that people can bring their own runners. That is one of the biggest changes,” Neveux said.\n\nGitLab Pages has also improved the way Worldline communicates. Using a static website generator, creating a website from scratch is easy. “You can’t even believe how much of our website is created with Pages — and our documentation too actually,” Neveux explained. “People moved like all of the wikis and other things like this to GitLab Pages and so it is the standard for everyone to communicate. Everything is published through pages and it is starting to become collaborative, so that is one major change as well.”\n\nWorldline began using GitLab in 2014, and both companies have experienced incredible growth and change during this time. With the addition of Git at Worldline, users started looking at each other's code and then they started collaborating on each other’s projects. This was a big step for the organization and has changed how teams focus and work. Now the company is utilizing innersourcing practices and has people creating frameworks, tools, and best practices documents that they share within the company.\n",{"template":950,"size":44,"region":106,"industry":71},"content:en-us:customers:worldline.yml",{"_path":5770,"content":5771,"config":5812,"_id":5813},"/en-us/customers/zoopla",{"name":5772,"logo":5773,"hero":5774,"heroImage":5775,"benefits":5776,"industry":89,"employeeCount":5784,"location":5785,"solution":975,"stats":5786,"headline":5792,"summary":5793,"quotes":5794,"content":5799,"contributors":1281},"Zoopla","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518025/jsci15spz4skidvmjuta.png","How Zoopla deploys 700% faster with GitLab","https://res.cloudinary.com/about-gitlab-com/image/upload/v1745518466/epwrjmgusbtzddzswjzt.jpg",[5777,5780,5782],{"metric":5778,"config":5779},"Easy user interface",{"icon":1415},{"metric":4475,"config":5781},{"icon":971},{"metric":1524,"config":5783},{"icon":1526},"700","United Kingdom",[5787,5789],{"value":1804,"metric":5788},"faster lead time",{"value":5790,"metric":5791},"0%","change failure rate","Zoopla, the UK’s most comprehensive property destination, adopted GitLab for accelerated deployment and a unified workflow.","Zoopla uses GitLab Self-Managed Premium for version control, CI/CD, and improved developer collaboration.\n",[5795],{"quoteText":5796,"author":5797,"authorTitle":5798,"authorCompany":5772},"I personally absolutely love GitLab. And I would say multiple times, here internally, that I think your API is very sexy, in that respect, that it's really great to work with it. It's very intuitive.\n","Gustaw Fit","Engineering Lead",[5800,5803,5806,5809],{"header":5801,"text":5802},"Leading real estate portal","Zoopla is the United Kingdom’s most comprehensive property destination. [Zoopla](https://www.zoopla.co.uk/){data-ga-name=\"zoopla\" data-ga-location=\"body\"} provides millions of users with access to properties for sale and for rent, along with detailed valuation information on nearly 29 million UK homes, in one place. The website enables estate agencies and developers to promote properties they want to sell. On top of that, Zoopla uses detailed valuation software to allow for valuation of properties to be done automatically along with connecting homeowners with local agents if they want a more detailed valuation.\n",{"header":5804,"text":5805},"Managing too many tools without visibility","Zoopla developers were managing a number of tools for source control and running pipelines, primarily Jenkins and Apache Groovy. Between the lack of plugin support for Jenkins and the complexity of Groovy, the team was looking for a way to simplify the existing workflow. “Maintaining Jenkins, understanding Groovy, and creating complex builds that you can’t really easily package with the code, was a bit of a challenge,” according to Gustaw Fit, Engineering Lead. Zoopla was looking for an all-in-one solution in order to facilitate development management. The development team wanted “A tool that offers multiple points, you can store the source control, you can simply build a pipeline, it gives you a nice visual support and gives you reports, and then you can even do schedules. And you can do it without much thinking,” Fit said.\n",{"header":5807,"text":5808},"SCM, CI, and CD in one platform","According to Fit, Zoopla adopted GitLab Premium as a “strategic and primary tool” at the start of a big transformation project. The notable added value in their adoption decision was regarding DORA metrics and GitLab’s advanced API capabilities. “We tried using other build pipeline provider APIs, but they still have a very long way to go to get to a place where it’s easy to use,” Fit said. Another benefit of adopting GitLab is that now the team uses a single platform for continuous integration, deployment, and source control management. The robust workflow efficiency is the ideal solution they were searching for. On top of that, GitLab is becoming a market standard for engineers and developers. “[Engineers] basically come with a specific skill set, they will be expecting a certain set of tools. And [GitLab] is becoming a market standard, because it is very usable and user friendly,” Fit added.\n",{"header":5810,"text":5811},"Improved APIs, faster deploys, AWS integration","GitLab is now Zoopla’s primary tool for delivery, source control, APIs, and pipelines. The team also uses GitLab issues for the Request For Comments process — which would not have been adopted so rapidly if not for GitLab’s features supporting this use case. “When we moved to GitLab, we moved from a weekly process that we couldn’t properly measure, to a process that takes around 45 minutes now, but runs the same set of quality assurances in all of the deployments,” Fit said. “We still think about how we can make it smaller, and how we can measure it. So, that’s absolutely wicked.”\n\nZoopla uses deployment frequency, change failure rate, MTTR, and cycle time metrics. Since the transformation project, which included moving to GitLab and also using the platform that supports the project, teams have seen their metric numbers dramatically improve in all areas. “Without GitLab, we wouldn’t be able to measure them. So this would be the key point, and that’s also why I really like the way the API is designed. There’s a lot more that we can be doing with just the API, because without that, we wouldn’t be able to measure all of that stuff, because we wouldn’t know,” Fit added.\n\nGitLab was one of the key elements that allowed teams to improve deployment frequency for the key public websites from once per week to now once daily. On top of that, lead time went down from “five business days to just under two hours,” according to Fit. The change fail rate is trending from 40% towards a flat 0% rate as of now. “If we’re comparing our previous solution, Jenkins, it takes me around 15 minutes just to create the deployment pipeline. I can’t remember any other place, or any other tool where it is so simple and provides all of the additional benefits of GitLab. I’m a great fan of just storing the build configuration in code, as a configuration file,” Fit added.\n\nEngineers have started using GitLab features for integrating tests into pipelines. Though this is a possibility in other platforms, the simplicity of creating a pipeline in GitLab and then adding dependencies on the pipeline is unique to GitLab. “It gives you a very nice user interface, where you can just basically go in and see, especially if you’re a quality engineer. You can go in and see what failed in the console,” according to Fit. With GitLab, developers no longer need to click through multiple screens in order to view the data they need. This single process allows teams to measure DORA metrics and assess efficiencies. On top of that, the teams are moving towards a place where everything is standardised. Instead of having a tool that needs constant support and a lengthy learning curve, everyone knows how to use GitLab. Developers own and manage their own pipelines, without worrying too much about how it should work.\n\nDevelopers are able to execute the relevant discrete parts of the pipeline on their own and with little supervision. “Whether it’s rollback or standard deployment, I am really happy we have the GitLab pipelines,” Fit said. Zoopla started with Amazon Web Services (AWS) in 2011. Developers deploy GitLab to the cloud using AWS and have never had any issues with the integration. “The AWS integration works very well and is reliable. The teams are doing a massive move from the old architecture that Zoopla was using when they were a startup. Now, as a more mature company, Zoopla is becoming a more distributed architecture with GitLab as the driving force behind the upgrades and scaling efficiencies,” added Fit.\n",{"template":950,"size":40,"region":106,"industry":91},"content:en-us:customers:zoopla.yml",1761814442110]