[{"data":1,"prerenderedAt":538},["ShallowReactive",2],{"/en-us/the-source/authors/sharon-gaudin/":3,"footer-en-us":29,"the-source-banner-en-us":336,"the-source-navigation-en-us":348,"the-source-newsletter-en-us":376,"authors-en-us":387,"categories-en-us":419,"sharon-gaudin-articles-list-en-us":420},{"_path":4,"_dir":5,"_draft":6,"_partial":6,"_locale":7,"config":8,"seo":10,"content":12,"type":21,"slug":22,"_id":23,"_type":24,"title":11,"_source":25,"_file":26,"_stem":27,"_extension":28},"/en-us/the-source/authors/sharon-gaudin","authors",false,"",{"layout":9},"the-source",{"title":11},"Sharon Gaudin",[13,19],{"componentName":14,"type":14,"componentContent":15},"TheSourceAuthorHero",{"name":11,"headshot":16},{"altText":11,"config":17},{"src":18},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1751463475/h6j4nnvykzyfzgvl7txb.webp",{"componentName":20,"type":20},"TheSourceArticlesList","author","sharon-gaudin","content:en-us:the-source:authors:sharon-gaudin.yml","yaml","content","en-us/the-source/authors/sharon-gaudin.yml","en-us/the-source/authors/sharon-gaudin","yml",{"_path":30,"_dir":31,"_draft":6,"_partial":6,"_locale":7,"data":32,"_id":332,"_type":24,"title":333,"_source":25,"_file":334,"_stem":335,"_extension":28},"/shared/en-us/main-footer","en-us",{"text":33,"source":34,"edit":40,"contribute":45,"config":50,"items":55,"minimal":324},"Git is a trademark of Software Freedom Conservancy and our use of 'GitLab' is under license",{"text":35,"config":36},"View page source",{"href":37,"dataGaName":38,"dataGaLocation":39},"https://gitlab.com/gitlab-com/marketing/digital-experience/about-gitlab-com/","page source","footer",{"text":41,"config":42},"Edit this page",{"href":43,"dataGaName":44,"dataGaLocation":39},"https://gitlab.com/gitlab-com/marketing/digital-experience/about-gitlab-com/-/blob/main/content/","web ide",{"text":46,"config":47},"Please contribute",{"href":48,"dataGaName":49,"dataGaLocation":39},"https://gitlab.com/gitlab-com/marketing/digital-experience/about-gitlab-com/-/blob/main/CONTRIBUTING.md/","please contribute",{"twitter":51,"facebook":52,"youtube":53,"linkedin":54},"https://twitter.com/gitlab","https://www.facebook.com/gitlab","https://www.youtube.com/channel/UCnMGQ8QHMAnVIsI3xJrihhg","https://www.linkedin.com/company/gitlab-com",[56,83,155,223,285],{"title":57,"links":58,"subMenu":64},"Platform",[59],{"text":60,"config":61},"DevSecOps platform",{"href":62,"dataGaName":63,"dataGaLocation":39},"/platform/","devsecops platform",[65],{"title":66,"links":67},"Pricing",[68,73,78],{"text":69,"config":70},"View plans",{"href":71,"dataGaName":72,"dataGaLocation":39},"/pricing/","view plans",{"text":74,"config":75},"Why Premium?",{"href":76,"dataGaName":77,"dataGaLocation":39},"/pricing/premium/","why premium",{"text":79,"config":80},"Why Ultimate?",{"href":81,"dataGaName":82,"dataGaLocation":39},"/pricing/ultimate/","why ultimate",{"title":84,"links":85},"Solutions",[86,91,95,100,105,110,115,120,125,130,135,140,145,150],{"text":87,"config":88},"Digital transformation",{"href":89,"dataGaName":90,"dataGaLocation":39},"/topics/digital-transformation/","digital transformation",{"text":92,"config":93},"Application Security Testing",{"href":94,"dataGaName":92,"dataGaLocation":39},"/solutions/application-security-testing/",{"text":96,"config":97},"Automated software delivery",{"href":98,"dataGaName":99,"dataGaLocation":39},"/solutions/delivery-automation/","automated software delivery",{"text":101,"config":102},"Agile development",{"href":103,"dataGaName":104,"dataGaLocation":39},"/solutions/agile-delivery/","agile delivery",{"text":106,"config":107},"Cloud transformation",{"href":108,"dataGaName":109,"dataGaLocation":39},"/topics/cloud-native/","cloud transformation",{"text":111,"config":112},"SCM",{"href":113,"dataGaName":114,"dataGaLocation":39},"/solutions/source-code-management/","source code management",{"text":116,"config":117},"CI/CD",{"href":118,"dataGaName":119,"dataGaLocation":39},"/solutions/continuous-integration/","continuous integration & delivery",{"text":121,"config":122},"Value stream management",{"href":123,"dataGaName":124,"dataGaLocation":39},"/solutions/value-stream-management/","value stream management",{"text":126,"config":127},"GitOps",{"href":128,"dataGaName":129,"dataGaLocation":39},"/solutions/gitops/","gitops",{"text":131,"config":132},"Enterprise",{"href":133,"dataGaName":134,"dataGaLocation":39},"/enterprise/","enterprise",{"text":136,"config":137},"Small business",{"href":138,"dataGaName":139,"dataGaLocation":39},"/small-business/","small business",{"text":141,"config":142},"Public sector",{"href":143,"dataGaName":144,"dataGaLocation":39},"/solutions/public-sector/","public sector",{"text":146,"config":147},"Education",{"href":148,"dataGaName":149,"dataGaLocation":39},"/solutions/education/","education",{"text":151,"config":152},"Financial services",{"href":153,"dataGaName":154,"dataGaLocation":39},"/solutions/finance/","financial services",{"title":156,"links":157},"Resources",[158,163,168,173,178,183,188,193,198,203,208,213,218],{"text":159,"config":160},"Install",{"href":161,"dataGaName":162,"dataGaLocation":39},"/install/","install",{"text":164,"config":165},"Quick start guides",{"href":166,"dataGaName":167,"dataGaLocation":39},"/get-started/","quick setup checklists",{"text":169,"config":170},"Learn",{"href":171,"dataGaName":172,"dataGaLocation":39},"https://university.gitlab.com/","learn",{"text":174,"config":175},"Product documentation",{"href":176,"dataGaName":177,"dataGaLocation":39},"https://docs.gitlab.com/","docs",{"text":179,"config":180},"Blog",{"href":181,"dataGaName":182,"dataGaLocation":39},"/blog/","blog",{"text":184,"config":185},"Customer success stories",{"href":186,"dataGaName":187,"dataGaLocation":39},"/customers/","customer success stories",{"text":189,"config":190},"Remote",{"href":191,"dataGaName":192,"dataGaLocation":39},"https://handbook.gitlab.com/handbook/company/culture/all-remote/","remote",{"text":194,"config":195},"GitLab Services",{"href":196,"dataGaName":197,"dataGaLocation":39},"/services/","services",{"text":199,"config":200},"TeamOps",{"href":201,"dataGaName":202,"dataGaLocation":39},"/teamops/","teamops",{"text":204,"config":205},"Community",{"href":206,"dataGaName":207,"dataGaLocation":39},"/community/","community",{"text":209,"config":210},"Forum",{"href":211,"dataGaName":212,"dataGaLocation":39},"https://forum.gitlab.com/","forum",{"text":214,"config":215},"Events",{"href":216,"dataGaName":217,"dataGaLocation":39},"/events/","events",{"text":219,"config":220},"Partners",{"href":221,"dataGaName":222,"dataGaLocation":39},"/partners/","partners",{"title":224,"links":225},"Company",[226,231,236,241,246,251,256,260,265,270,275,280],{"text":227,"config":228},"About",{"href":229,"dataGaName":230,"dataGaLocation":39},"/company/","company",{"text":232,"config":233},"Jobs",{"href":234,"dataGaName":235,"dataGaLocation":39},"/jobs/","jobs",{"text":237,"config":238},"Leadership",{"href":239,"dataGaName":240,"dataGaLocation":39},"/company/team/e-group/","leadership",{"text":242,"config":243},"Team",{"href":244,"dataGaName":245,"dataGaLocation":39},"/company/team/","team",{"text":247,"config":248},"Handbook",{"href":249,"dataGaName":250,"dataGaLocation":39},"https://handbook.gitlab.com/","handbook",{"text":252,"config":253},"Investor relations",{"href":254,"dataGaName":255,"dataGaLocation":39},"https://ir.gitlab.com/","investor relations",{"text":257,"config":258},"Sustainability",{"href":259,"dataGaName":257,"dataGaLocation":39},"/sustainability/",{"text":261,"config":262},"Diversity, inclusion and belonging (DIB)",{"href":263,"dataGaName":264,"dataGaLocation":39},"/diversity-inclusion-belonging/","Diversity, inclusion and belonging",{"text":266,"config":267},"Trust Center",{"href":268,"dataGaName":269,"dataGaLocation":39},"/security/","trust center",{"text":271,"config":272},"Newsletter",{"href":273,"dataGaName":274,"dataGaLocation":39},"/company/contact/","newsletter",{"text":276,"config":277},"Press",{"href":278,"dataGaName":279,"dataGaLocation":39},"/press/","press",{"text":281,"config":282},"Modern Slavery Transparency Statement",{"href":283,"dataGaName":284,"dataGaLocation":39},"https://handbook.gitlab.com/handbook/legal/modern-slavery-act-transparency-statement/","modern slavery transparency statement",{"title":286,"links":287},"Contact Us",[288,293,298,303,308,313,318],{"text":289,"config":290},"Contact an expert",{"href":291,"dataGaName":292,"dataGaLocation":39},"/sales/","sales",{"text":294,"config":295},"Get help",{"href":296,"dataGaName":297,"dataGaLocation":39},"/support/","get help",{"text":299,"config":300},"Customer portal",{"href":301,"dataGaName":302,"dataGaLocation":39},"https://customers.gitlab.com/customers/sign_in/","customer portal",{"text":304,"config":305},"Status",{"href":306,"dataGaName":307,"dataGaLocation":39},"https://status.gitlab.com/","status",{"text":309,"config":310},"Terms of use",{"href":311,"dataGaName":312,"dataGaLocation":39},"/terms/","terms of use",{"text":314,"config":315},"Privacy statement",{"href":316,"dataGaName":317,"dataGaLocation":39},"/privacy/","privacy statement",{"text":319,"config":320},"Cookie preferences",{"dataGaName":321,"dataGaLocation":39,"id":322,"isOneTrustButton":323},"cookie preferences","ot-sdk-btn",true,{"items":325},[326,328,330],{"text":309,"config":327},{"href":311,"dataGaName":312,"dataGaLocation":39},{"text":314,"config":329},{"href":316,"dataGaName":317,"dataGaLocation":39},{"text":319,"config":331},{"dataGaName":321,"dataGaLocation":39,"id":322,"isOneTrustButton":323},"content:shared:en-us:main-footer.yml","Main Footer","shared/en-us/main-footer.yml","shared/en-us/main-footer",{"_path":337,"_dir":338,"_draft":6,"_partial":6,"_locale":7,"visibility":323,"id":339,"title":340,"button":341,"_id":345,"_type":24,"_source":25,"_file":346,"_stem":347,"_extension":28},"/shared/en-us/the-source/banner/the-economics-of-software-innovation-2025-08-18","banner","The Economics of Software Innovation","The Economics of Software Innovation—AI’s $750 Billion Opportunity",{"config":342,"text":344},{"href":343},"/software-innovation-report/","Get the research report","content:shared:en-us:the-source:banner:the-economics-of-software-innovation-2025-08-18.yml","shared/en-us/the-source/banner/the-economics-of-software-innovation-2025-08-18.yml","shared/en-us/the-source/banner/the-economics-of-software-innovation-2025-08-18",{"_path":349,"_dir":9,"_draft":6,"_partial":6,"_locale":7,"logo":350,"subscribeLink":355,"navItems":359,"_id":372,"_type":24,"title":373,"_source":25,"_file":374,"_stem":375,"_extension":28},"/shared/en-us/the-source/navigation",{"altText":351,"config":352},"the source logo",{"src":353,"href":354},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1750191004/t7wz1klfb2kxkezksv9t.svg","/the-source/",{"text":356,"config":357},"Subscribe",{"href":358},"#subscribe",[360,364,368],{"text":361,"config":362},"Artificial Intelligence",{"href":363},"/the-source/ai/",{"text":365,"config":366},"Security & Compliance",{"href":367},"/the-source/security/",{"text":369,"config":370},"Platform & Infrastructure",{"href":371},"/the-source/platform/","content:shared:en-us:the-source:navigation.yml","Navigation","shared/en-us/the-source/navigation.yml","shared/en-us/the-source/navigation",{"_path":377,"_dir":9,"_draft":6,"_partial":6,"_locale":7,"title":378,"description":379,"submitMessage":380,"formData":381,"_id":384,"_type":24,"_source":25,"_file":385,"_stem":386,"_extension":28},"/shared/en-us/the-source/newsletter","The Source Newsletter","Stay updated with insights for the future of software development.","You have successfully signed up for The Source’s newsletter.",{"config":382},{"formId":383,"formName":274,"hideRequiredLabel":323},1077,"content:shared:en-us:the-source:newsletter.yml","shared/en-us/the-source/newsletter.yml","shared/en-us/the-source/newsletter",{"amanda-rueda":388,"andre-michael-braun":389,"andrew-haschka":390,"ayoub-fandi":391,"bob-stevens":392,"brian-wald":393,"bryan-ross":394,"chandler-gibbons":395,"dave-steer":396,"ddesanto":397,"derek-debellis":398,"emilio-salvador":399,"erika-feldman":400,"george-kichukov":401,"gitlab":402,"grant-hickman":403,"haim-snir":404,"iganbaruch":405,"jason-morgan":406,"jlongo":407,"joel-krooswyk":408,"josh-lemos":409,"julie-griffin":410,"kristina-weis":411,"lee-faus":412,"ncregan":413,"rschulman":414,"sabrina-farmer":415,"sandra-gittlen":416,"sharon-gaudin":11,"stephen-walters":417,"taylor-mccaslin":418},"Amanda Rueda","Andre Michael Braun","Andrew Haschka","Ayoub Fandi","Bob Stevens","Brian Wald","Bryan Ross","Chandler Gibbons","Dave Steer","David DeSanto","Derek DeBellis","Emilio Salvador","Erika Feldman","George Kichukov","GitLab","Grant Hickman","Haim Snir","Itzik Gan Baruch","Jason Morgan","Joseph Longo","Joel Krooswyk","Josh Lemos","Julie Griffin","Kristina Weis","Lee Faus","Niall Cregan","Robin Schulman","Sabrina Farmer","Sandra Gittlen","Stephen Walters","Taylor McCaslin",{"ai":361,"platform":369,"security":365},{"allArticles":421,"visibleArticles":537,"showAllBtn":323},[422,461,496,516],{"_path":423,"_dir":424,"_draft":6,"_partial":6,"_locale":7,"config":425,"seo":427,"content":432,"type":456,"slug":457,"category":424,"_id":458,"_type":24,"title":428,"_source":25,"_file":459,"_stem":460,"_extension":28,"date":433,"description":429,"timeToRead":434,"heroImage":430,"keyTakeaways":435,"articleBody":439,"faq":440},"/en-us/the-source/platform/devops-teams-want-to-shake-off-diy-toolchains-a-platform-is-the-answer","platform",{"layout":9,"template":426,"author":22,"featured":6,"isHighlighted":6,"authorName":11},"TheSourceArticle",{"title":428,"description":429,"ogImage":430,"config":431},"DevOps teams want to shake off DIY toolchains. A platform is the answer","According to GitLab research, 64% of DevSecOps professionals say they want to consolidate creeping toolchains.","https://res.cloudinary.com/about-gitlab-com/image/upload/v1751463678/r0gawsvh4vcmgblpra58.png",{"ignoreTitleCharLimit":323},{"title":428,"date":433,"description":429,"timeToRead":434,"heroImage":430,"keyTakeaways":435,"articleBody":439,"faq":440},"2025-01-14","5 min read",[436,437,438],"DevOps teams face \"toolchain tax\" as multiple development tools create hidden costs. More than 78% of teams spend up to 100% of their time maintaining tools instead of coding, with most managing 6+ tools.","Nearly 64% of DevOps teams want to consolidate their toolchains due to monitoring issues and delays. The push is strongest in automotive (76.5%) and manufacturing (72%) sectors.","A single DevSecOps platform helps teams focus on code, rather than tool maintenance. Companies report improved efficiency, reduced costs, and better developer experience through consolidated toolchains.","A DevOps team’s biggest problem can start innocently enough: maybe one person wants to add a tool to automate deployment, and then someone else wants to add a tool for code review. More tools keep being added until suddenly teams are dealing with a tangled and complicated toolchain that is wasting more time and money than it was intended to save.\n\nThis [\"toolchain tax\"](https://about.gitlab.com/blog/avoiding-devops-tax-webcast/) - the hidden and insidious cost of using multiple development tools - begins gradually, but it can lead to serious bottlenecks in software production. Tools accumulate until teams find themselves managing a complicated chain that wastes more time and money than it saves, affecting their ability to meet customer needs and stay ahead of competitors.\n\nThat problem is becoming clear to DevOps professionals who are looking to shake off the shackles of a toolchain. [GitLab’s 2024 Global DevSecOps Survey](https://about.gitlab.com/developer-survey/) reveals the scale of this challenge and the pain point it’s creating. More than half of DevOps teams are juggling six or more tools in their development chain - and 13% of them are managing up to 14 different tools.\n\nThe workday cost of this complexity? DevOps professionals are spending up to three-quarters of their time just maintaining and integrating these tools instead of developing software. More than 78% report wasting between 25% to 100% of their time keeping their toolchain running.\n\nRespondents say that’s a problem.\n\nThe study showed that nearly 64% want to consolidate their (sometimes sprawling) toolchains because of challenges with monitoring, development delays, and unhappy developers. That percentage ticks up for a few industries. Respondents in the automotive industry clocked in at 76.5%, while more than 72% in manufacturing are looking to consolidate.\n\nAnd when respondents talk about how much of their responsibilities revolve around maintaining and/or integrating their DevOps toolchains, it’s clear why they want to cut back or eliminate them. According to the survey, about 20% reported that maintenance and integration take up to 24% of their time, with more than 40% saying it accounts for 25% to 49%, and more than 27% say it uses up 50% to 74% of their workday. That’s more than 78% of DevOps professionals saying they waste at least a quarter of their day keeping their toolchain running.\n\n“The everyday life of one of our developers was spread across many different services,” said Nadav Robas, DevOps & DevSecOps manager at [Agoda](https://about.gitlab.com/customers/agoda/), a major online travel booking platform headquartered in Singapore. “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.”\n\nIt all adds up to a lot of time spent doing things that aren’t directly developing and deploying software. It also means that DevOps team mates aren’t doing as much of what they love doing - being innovative and creative - which affects their work experience and happiness.\n\n## Eliminating the toolchain tax\n\nTeams clearly are tired of paying the toolchain tax. And now they’re ridding themselves of this problem by [adopting a full DevSecOps platform](https://about.gitlab.com/blog/eight-steps-to-prepare-your-team-for-a-devops-platform-migration/). That one move can create efficiencies, replace hands-on tasks with automation, shift security left, reduce costs, reduce aggravations, and drive critical advantages for both DevOps teams and the overall business.\n\n“I didn’t want them to be experts in individual tools,” said Robas. “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\nBeyond streamlining operations, a single platform also means companies aren’t paying licensing fees for multiple tools. To calculate what a company could save by replacing a toolchain, [use this ROI calculator](https://about.gitlab.com/calculator/roi/). [1]\n\nHaving a comprehensive platform that [boosts productivity](https://about.gitlab.com/blog/5-ways-collaboration-boosts-productivity-and-your-career/) while reducing costs is a superpower, especially in economically challenging times, because it can help deliver value to customers more quickly.\n\n## Decrease toolchain sprawl with GitLab\n\nA DevSecOps platform - like [GitLab’s single, end-to-end platform](https://about.gitlab.com/stages-devops-lifecycle/) - helps companies cut out the potentially costly integration work that comes with using various tools, and helps organizations create and release software faster, while increasing security and compliance. It’s a mixture of benefits that shorten cycle times and increases productivity, enabling teams to build software with velocity, trust, and visibility.\n\nAnd that creates value for customers.\n\n“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\nSee the [benefits that migrating](https://page.gitlab.com/resources-ebook-trading-diy-devops-for-a-single-platform.html) to an end-to-end GitLab platform can bring to your organization.\n\n[1] _Please note that ROI may vary depending on many factors, and the ROI calculator does not reflect actual results as results may vary._\n\n> #### Consolidate your complex toolchain\n>\n> Read our free guide to learn how to streamline your toolchain to avoid inefficiencies, decrease costs, and accelerate time to market.\n>\n> [Read the guide](https://page.gitlab.com/consolidate-toolchain-guide.html){class=\"button\"}",[441,444,447,450,453],{"header":442,"content":443},"How does GitLab help reduce toolchain complexity?","GitLab provides an end-to-end DevSecOps platform that consolidates services, offering teams a unified view of the software development lifecycle. This approach reduces toolchain sprawl, enhances security and compliance, and improves developer experience, boosting productivity and trust.",{"header":445,"content":446},"What is the \"toolchain tax,\" and how does it impact DevOps teams?","The \"toolchain tax\" refers to the hidden cost of managing and maintaining multiple tools in a software development toolchain. This complexity consumes up to 74% of DevOps professionals' time, leading to inefficiencies, delays, and reduced developer satisfaction.",{"header":448,"content":449},"How does a single DevSecOps platform improve efficiency?","A single DevSecOps platform eliminates the need for tool integration, automates manual tasks, shifts security earlier in the development lifecycle, and reduces costs. It enables teams to focus on innovation, shortens cycle times, and enhances productivity.",{"header":451,"content":452},"Why do DevOps teams want to consolidate their toolchains?","According to GitLab’s 2024 Global DevSecOps Survey, 64% of DevOps professionals want to consolidate their toolchains to reduce maintenance burdens, streamline workflows, improve monitoring, and enhance developer productivity by eliminating unnecessary context switching.",{"header":454,"content":455},"What are the financial benefits of adopting a comprehensive DevSecOps platform?","Replacing fragmented toolchains with a single platform reduces licensing fees for multiple tools and eliminates costly integration efforts. Organizations can calculate potential savings using ROI tools designed to assess the benefits of platform consolidation.","article","devops-teams-want-to-shake-off-diy-toolchains-a-platform-is-the-answer","content:en-us:the-source:platform:devops-teams-want-to-shake-off-diy-toolchains-a-platform-is-the-answer.yml","en-us/the-source/platform/devops-teams-want-to-shake-off-diy-toolchains-a-platform-is-the-answer.yml","en-us/the-source/platform/devops-teams-want-to-shake-off-diy-toolchains-a-platform-is-the-answer",{"_path":462,"_dir":424,"_draft":6,"_partial":6,"_locale":7,"config":463,"seo":465,"content":469,"type":456,"slug":492,"category":424,"_id":493,"_type":24,"title":466,"_source":25,"_file":494,"_stem":495,"_extension":28,"date":470,"description":467,"timeToRead":434,"heroImage":468,"keyTakeaways":471,"articleBody":475,"faq":476},"/en-us/the-source/platform/how-devops-and-platform-engineering-turbocharge-efficiency",{"layout":9,"template":426,"author":22,"featured":6,"sourceCTA":464,"isHighlighted":6,"authorName":11},"source-lp-the-ultimate-playbook-for-high-performing-devsecops-teams",{"title":466,"description":467,"ogImage":468},"How DevOps and platform engineering turbocharge efficiency","Platform engineering and DevOps work together to improve efficiency and productivity. One doesn’t replace the other.","https://res.cloudinary.com/about-gitlab-com/image/upload/v1751464549/dpw4yyb39ltxmagvuhvr.png",{"title":466,"date":470,"description":467,"timeToRead":434,"heroImage":468,"keyTakeaways":471,"articleBody":475,"faq":476},"2024-01-25",[472,473,474],"Platform engineering optimizes DevOps platforms, enhancing efficiency without replacing them.","DevOps provides the framework; platform engineering customizes for specific organizational needs.","Collaboration boosts development speed, security, and compliance in DevOps through platform engineering.","When it comes to platform engineering and DevOps, it’s not an either/or situation.\n\nTo be clear, platform engineering and DevOps are not the same thing. There’s a bit of confusion about the two practices. Does one replace the other? No. Can they work well together? Definitely.\n\nLet’s look at what platform engineering is and how it can work hand-in-hand with a DevOps platform.\n\n## DevOps and platform engineering: Differences and benefits\n\nYou’re likely pretty familiar with DevOps. It’s a methodology, along with a set of processes and tools, that integrates software developers with operations teams to increase efficiency, speed, and security. DevOps works most effectively on a single end-to-end platform, allowing teams to consolidate an often complex and confusing multitude of tools into a single, complete software development ecosystem.\n\nPlatform engineering, on the other hand, is an emerging approach to software development that accelerates production and deployment velocity by providing DevOps teams with a single self-service portal for tools and workflows. By making the day-to-day developer experience more efficient, platform engineering improves team performance, eases the cognitive load on developers, and makes software delivery scalable, faster, and repeatable.\n\nDevOps and platform engineering sound similar. They have similar goals. But think of it this way: DevOps, or a DevOps platform, acts as the framework for platform engineering. And platform engineering is a way to optimize, or turbocharge, a DevOps platform.\n\n## Why DevOps and platform engineering work well together\n\nOrganizations often adopt platform engineering after their software development teams have already migrated to DevOps. That’s because by using a DevOps platform, with tools and [automation](https://about.gitlab.com/blog/how-automation-is-making-devops-pros-jobs-easier/) already built in, platform engineers don’t have to integrate tools and build their own platform for their processes and methodologies to work on top of. They simply can optimize the single, end-to-end platform already set up for them, saving them a lot of time and labor.\n\nAs DevOps grows, there is an increasing call for platform engineers, a bleeding-edge role, in various job listings. A platform engineer, or team, is an extension of the DevOps team, tailoring the DevOps platform for the specific development, security, and compliance needs of specific organizations. Companies are looking for platform engineers with a myriad of skills - from experience with automation to infrastructure as code, cloud deployments, Kubernetes, and secure coding practices.\n\n“Using a DevOps platform is the perfect starting point for platform engineering,” says [Cailey Pawlowski](https://gitlab.com/cpawlowski), solutions architect at GitLab. “Both are focused on improving the development process and a developer’s experience. They work together.”\n\n## How platform engineers can optimize DevOps platforms\n\nPlatform engineering is focused on creating efficiencies and optimizations. That means platform teams help the business better serve its customers, stay ahead of competitors, and avoid costly and damaging security incidents.\n\nTo help their organizations get the most out of their DevOps platform, platform engineers can:\n- use and customize monitoring tools in the DevOps platform to find out when and why bottlenecks are happening, and then fix those problems\n- ensure teams aren’t missing out on tools, like [vulnerability scanning](https://about.gitlab.com/blog/remediating-vulnerabilities-with-insights-and-ai/) and access management, in the platform that will help their workflows\n- customize tools in the platform, such as finely tuned automation scripts for CI, to fit the organization’s specific needs\n- create a list of best practices and then ensure they’re being followed\n- set up and customize platform templates to standardize pipelines so developers don’t have to create new pipelines from scratch every time\n- build in pipeline efficiencies, such as custom code related to the organization’s infrastructure or a specific app\n- configure security and compliance policies to ensure that scans are run at specific times or points in the development process, or are triggered by certain events, such as a pipeline running against a branch\n- set up checks and balances for regulation enforcement\n- set up regular [security audits](https://about.gitlab.com/blog/what-you-need-to-know-about-devops-audits/)\n\n## How platform engineering helps DevOps teams\n\nBy setting up clear steps and guidelines, and by creating efficiencies throughout the software development lifecycle, platform engineers can have a great effect on the DevOps process, as well as on the team.\n\nHere are a few benefits:\n- increase development velocity by streamlining workflows\n- [improve collaboration](https://about.gitlab.com/blog/5-ways-collaboration-boosts-productivity-and-your-career/) by giving team members more time and energy to work together\n- make building secure software more efficient and consistent\n- ease regulatory compliance by setting up training, policies, and checks and balances\n- reduce team members’ cognitive load by using automated tools to reduce repetitive, hands-on work\n- minimize human error with automation\n- [make developers happier](https://about.gitlab.com/blog/why-hackerone-gets-love-letters-from-developers/) by easing manual tasks, giving them time and energy to do the creative, challenging work they enjoy\n\n“Platform engineering is about empowering developers,” says [Ayoub Fandi](https://gitlab.com/ayofan), staff field security engineer at GitLab. “It’s about enhancing what a DevOps platform already provides by making sure teams are using all of the tools available and by making the most of them. It’s literally having people dedicated to making developers’ jobs easier.”\n\nCheck out this video demo on how platform engineering works.\n\n\u003C!-- blank line -->\n\u003Cfigure class=\"video_container\">\n  \u003Ciframe src=\"https://www.youtube.com/embed/lwKOOq6XD9A?si=O2vIoCpgSwSvzRYh\" frameborder=\"0\" allowfullscreen=\"true\"> \u003C/iframe>\n\u003C/figure>\n\u003C!-- blank line -->",[477,480,483,486,489],{"header":478,"content":479},"What skills are needed for platform engineering within a DevOps environment?","Platform engineers require expertise in automation, infrastructure as code, cloud deployments, Kubernetes, and secure coding practices. They also need a strong understanding of DevOps tools and methodologies to effectively customize and optimize workflows for organizational needs.",{"header":481,"content":482},"How can organizations get started with platform engineering to enhance DevOps?","Organizations should begin by evaluating their existing DevOps platform and identifying bottlenecks in their workflows. From there, they can establish a platform engineering team to standardize pipelines, customize tools, and implement automation scripts, ensuring a smooth and efficient development lifecycle.",{"header":484,"content":485},"What are the key benefits of implementing platform engineering alongside DevOps?","Key benefits include increased development velocity, improved collaboration, enhanced security and compliance, reduced cognitive load for developers, and minimized human error through automation. By optimizing DevOps tools and processes, platform engineering empowers development teams to build secure software more efficiently.",{"header":487,"content":488},"Can platform engineering replace DevOps in software development?","No, platform engineering does not replace DevOps. Instead, it builds on the DevOps framework by providing self-service capabilities and standardizing pipelines. This helps developers focus on coding and innovation while ensuring security and compliance through automation and best practices.",{"header":490,"content":491},"How do platform engineering and DevOps complement each other?","Platform engineering enhances DevOps by optimizing tools and workflows within a unified platform, reducing cognitive load on developers, and increasing productivity. While DevOps provides the framework for continuous integration and delivery, platform engineering customizes and standardizes processes, making development more scalable and efficient.","how-devops-and-platform-engineering-turbocharge-efficiency","content:en-us:the-source:platform:how-devops-and-platform-engineering-turbocharge-efficiency.yml","en-us/the-source/platform/how-devops-and-platform-engineering-turbocharge-efficiency.yml","en-us/the-source/platform/how-devops-and-platform-engineering-turbocharge-efficiency",{"_path":497,"_dir":498,"_draft":6,"_partial":6,"_locale":7,"config":499,"seo":500,"content":504,"type":456,"slug":512,"category":498,"_id":513,"_type":24,"title":501,"_source":25,"_file":514,"_stem":515,"_extension":28,"date":505,"description":502,"timeToRead":506,"heroImage":503,"keyTakeaways":507,"articleBody":511},"/en-us/the-source/ai/5-ways-execs-can-support-their-devops-teams-with-ai","ai",{"layout":9,"template":426,"author":22,"featured":6,"sourceCTA":464,"isHighlighted":6,"authorName":11},{"title":501,"description":502,"ogImage":503},"5 ways execs can support their DevOps teams with AI","Learn how the AI capabilities within a DevSecOps platform can help teams boost productivity and collaboration.","https://res.cloudinary.com/about-gitlab-com/image/upload/v1751463727/lo1idgayu6d7ysofhlsn.png",{"title":501,"date":505,"description":502,"timeToRead":506,"heroImage":503,"keyTakeaways":507,"articleBody":511},"2023-12-14","8 min read",[508,509,510],"By automating routine tasks and providing tools like code suggestions, AI enhances developer efficiency and reduces stress, which can lead to higher job satisfaction and retention.","A strategic rollout of AI tools can free developers to focus on high-priority projects.","AI assists in summarizing code reviews and discussions, allowing team members to easily grasp and contribute to ongoing projects. This ultimately fosters a more collaborative and connected work environment.","Artificial intelligence (AI) is poised to radically improve the way DevSecOps teams build software. And IT leaders are positioned to help their teams maximize all the benefits that come with using AI - focusing on how the technology can add efficiencies, make developers’ jobs easier, and foster, rather than replace, human-to-human collaboration.\n\n“If developers have the right tools to get their jobs done efficiently, they’re happier and less stressed,” says Abubakar Siddiq Ango, developer evangelism program manager at GitLab. “And if developers are happier, less stressed, and less burned out, they’ll do their jobs better and they won’t be looking to leave for another job. So it means better productivity and retention. Big wins.”\n\n[AI capabilities built in an end-to-end DevSecOps platform](https://about.gitlab.com/gitlab-duo/) are about empowering developers and making their jobs easier. Think of AI as the next generation of automation, freeing developers to do the valuable work they love doing - writing innovative code.\n\nHere are five ways to help your DevSecOps teams use AI to transform the way they work:\n\n## 1. Boost developer confidence with AI training\n\nA few of the best things executives can do for their teams is to [automate routine tasks](https://about.gitlab.com/the-source/ai/how-ai-helps-devsecops-teams-improve-productivity/) and make solving problems faster and more efficient, because that makes developers’ jobs easier, more interesting, and less stressful. And that’s just the job for AI.\n\nBy employing AI tools - like [code suggestions](https://about.gitlab.com/blog/code-suggestions-improves-developer-productivity/), vulnerability summaries, and code explanations - developers are able to spend less time and mental energy on mundane, repetitive, and time-consuming tasks. And that takes a huge load off their backs and helps improve the quality of their work.\n\n“This is definitely going to improve developers’ jobs,” says Ango. “I’d say 70% of my time is spent on Googling this function or researching that. If I can get that understanding in seconds, instead of a few hours, I can spend all that time and energy actually writing code. AI does the mundane work so humans can spend their time on more important things.”\n\nTo get started with AI in a way that won’t simply add stress to DevSecOps team members, managers and executives should make sure their people have the training they need to feel comfortable with AI features. Actually, [our research](https://about.gitlab.com/developer-survey/2024/ai/) shows that nearly a third of respondents, 31%, are concerned they lack the appropriate skill set to employ AI or interpret AI output. Of course, training is always critical but with something as new as AI, leaders should take steps to ensure people begin using the technology with a lot of confidence and excitement.\n\n## 2. Work with teams to roll out AI strategically\n\nSpending less time on manual tasks means developers have more time to work on building features for the next project iteration or design the next big piece of software. It also means they have more time to return to projects that might have been pushed aside due to time constraints.\n\nBy using AI to generate code suggestions and explanations, or by using AI-powered root cause analysis to identify the cause of a problem, developers have more time to move projects forward and focus on bigger-picture needs.\n\n“I think executives and IT leaders need to understand that they’re helping people do more with AI,” says Karen Kwentus, senior solutions architect at GitLab. “These capabilities move repetitive tasks out of the way. When I’m developing, I’ve literally spent hours trying to figure out a problem. If AI can suggest code or summarize vulnerabilities so I don’t have to spend time doing that, that can save me hours. Then I’m suddenly doing more with the same amount of time.”\n\nAngo adds, “AI will lead to more efficiency in how developers can build software, secure software, and deploy software.”\n\nLeaders should stay current with what AI features are available and work with their teams to figure out what workflows to simplify first with AI. Where can AI be used to help developers lighten their load and make their work more efficient? Once an AI solution is in place and developers are seeing positive results, managers can work with their teams to see what projects or efforts have been delayed or back-burnered, and begin to prioritize getting that work back on track.\n\n## 3. Reinforce the importance of human-to-human collaboration\n\nOne of the major benefits of a DevSecOps platform is that it fosters a collaborative environment. By giving all team members - both within DevSecOps teams and throughout other departments in the company - visibility into the entire software development lifecycle, people from different teams are able to communicate about and help each other navigate around roadblocks and offer efficiency suggestions.\n\nAI capabilities support that.\n\n“When colleagues post comments about the code you’re building, it’s only helpful if you have time to take it in and absorb it all,” says Ango. “When someone asks for a review, AI can provide a summary of that request. And when people provide reviews, [AI can summarize those comments](https://about.gitlab.com/blog/merge-request-changes-summary-ai/) so it’s easier to understand what everyone is saying about your project. Instead of disconnecting people, AI better connects them.\"\n\nHe adds, \"Workflow is AI enabled. AI improved. Not AI replaced.”\n\nAI does more than automate tasks. It helps team members communicate, creating more opportunities for human-to-human collaboration. Leaders can serve their teams by fostering an environment that encourages communication and collaboration, and reminding people that AI is opening that door for them.\n\n## 4. Encourage teams to share security responsibility\n\nUsing AI-powered [vulnerability summaries](https://about.gitlab.com/blog/developing-gitlab-duo-use-ai-to-remediate-security-vulnerabilities/) makes securing code more efficient, less mentally consuming, and faster.\n\nFor example, if a developer pushes code and gets an alert that a SQL injection has been detected, they might not immediately understand how their code is being impacted. But with AI, it’s easy to get an explanation of what the vulnerability is, how it affects the code, and how it impacts the entire piece of software - as well as suggestions for how to fix it.\n\n“If AI can explain a vulnerability and suggest a fix, then that’s exactly what I want,” says Kwentus. “Developers and security teams are ultimately responsible for implementing the remediation, but they’ll benefit from actionable AI prompting, context, and explanation. With more information, a user can triage and correct the issue faster.”\n\nAs IT leaders play a significant role in ensuring that DevSecOps teams are using automated security and compliance testing and alerts, they have a similar responsibility to make sure teams are using security-related AI tools, like vulnerability summaries. Team members are increasingly understanding that security is a shared responsibility. That means correcting problems shouldn’t just be left to a security team taking on issues at the end of a project. Developers creating the code can make use of AI capabilities to explain problems that pop up and use suggestions to correct them as soon as they’re found.\n\n> Learn more about [how AI can help DevOps teams improve security](https://about.gitlab.com/the-source/ai/4-ways-ai-can-help-devops-teams-improve-security/) and [how to put generative AI to work in your DevSecOps environment](https://about.gitlab.com/the-source/ai/how-to-put-generative-ai-to-work-in-your-devsecops-environment/).\n\n## 5. Find AI champions in your teams\n\nExecutives should create time to talk with their teams about the AI capabilities in their DevSecOps platform, and how these tools can ease their workloads. “Let your teams know what your goals are,” says Kwentus. “Give them information. Talk about saving time and mental energy. Tell them about spending less time researching vulnerabilities and spending more time writing code. They didn’t get into this job to do all of these other tasks. They want to write code and this will give them more time for that.”\n\nAnd by relieving their workload and stress, developers will be happier in their jobs. And happier people lead to better retention, which leads to more stable DevSecOps teams and less work for executives.\n\n“Developers get stressed when they’re trying to get something done but they keep hitting bottlenecks,” says Ango. “Getting rid of those bottlenecks will decrease their stress and burnout. And that’s easier on everyone.”\n\nIT leaders should, of course, focus on openly communicating with their teams about AI capabilities in their DevSecOps platforms, explaining how the features can make their jobs easier, and making sure they have the training they need to use the tools efficiently and with confidence.\n\nLeaders can make this communication easier by finding and empowering influential people on their teams who are excited about using AI and who will act as champions to encourage others to use the technology. By giving team members not only the tools that will make their jobs easier, but also the knowledge of how to use them, and the encouragement to adopt them, developers are likely to be happier in their jobs.","5-ways-execs-can-support-their-devops-teams-with-ai","content:en-us:the-source:ai:5-ways-execs-can-support-their-devops-teams-with-ai.yml","en-us/the-source/ai/5-ways-execs-can-support-their-devops-teams-with-ai.yml","en-us/the-source/ai/5-ways-execs-can-support-their-devops-teams-with-ai",{"_path":517,"_dir":518,"_draft":6,"_partial":6,"_locale":7,"config":519,"seo":520,"content":525,"type":456,"slug":533,"category":518,"_id":534,"_type":24,"title":521,"_source":25,"_file":535,"_stem":536,"_extension":28,"date":526,"description":522,"timeToRead":527,"heroImage":523,"keyTakeaways":528,"articleBody":532},"/en-us/the-source/security/finserv-startup-constantinople-uses-devsecops-to-build-in-security","security",{"layout":9,"template":426,"author":22,"featured":6,"isHighlighted":6,"authorName":11},{"title":521,"description":522,"ogImage":523,"config":524},"FinServ startup Constantinople uses DevSecOps to build in security","With a DevSecOps platform, Constantinople has minimized security and compliance risks while maximizing efficiency.","https://res.cloudinary.com/about-gitlab-com/image/upload/v1751464713/jc0ceajcrsgteyhtaibf.png",{"ignoreTitleCharLimit":323},{"title":521,"date":526,"description":522,"timeToRead":527,"heroImage":523,"keyTakeaways":528,"articleBody":532},"2023-05-17","6 min read",[529,530,531],"Constantinople integrates security early using GitLab's DevSecOps Platform, ensuring software is secure from the start and compliant with industry standards.","The platform fosters collaboration across teams, creating a seamless environment where developers work together efficiently, avoiding overlap and errors.","By relying on GitLab's mature features, Constantinople enhances development efficiency, reducing toolchain complexity and focusing resources on product innovation.","Constantinople, a startup in the financial services space, is using GitLab’s DevSecOps Platform to incorporate security into their software development lifecycle from the very beginning, while also fostering critical, long-term collaboration across the business.\n\n“Security is a non-negotiable in our industry, and something neither we nor our clients will compromise on,” says Jeremy Smith, Vice President of Engineering at [Constantinople](https://www.cxnpl.com/), which has fewer than 70 employees and is based in Sydney, Australia. “By building in best practices through use of the DevSecOps platform from day zero, we are building a platform with [security baked in](/blog/its-time-to-put-the-sec-in-devsecops/). Trying to retrofit it in the future would not only leave us exposed until then, it also would result in a lesser end product.”\n\nBefore diving further into Constantinople’s story, here's a snapshot of what they’re doing and achieving with GitLab:\n- They’ve used GitLab to create a cloud-native backend platform, comprising six interconnected services, along with a mobile banking customer app.\n- Developers are deploying code 20 to 30 times per day.\n- The company is using automation built into the platform for more than a dozen processes, including testing, security scanning, and updating hosted API documentation.\n- The platform’s analytics and dashboards are continually displayed on a TV in the office for company-wide visibility.\n\nFor Macgregor Duncan, co-founder and co-CEO of Constantinople, it’s all about making sure security is at the forefront of everything they do.\n\n“Our customers entrust us to handle their most sensitive financial data and mission-critical operations. There is no margin for error,” he says. “As a result, we have treated security as a top priority from day one, building it into every aspect of our software lifecycle. GitLab’s DevSecOps Platform has been a key part of ensuring this. And as we continue to scale our business, we are placing more reliance on other platform features, like visibility, measurability, and collaboration.”\n\n## Starting out with a DevSecOps platform\nConstantinople delivers fully managed digital banking services to financial institutions. The venture capital-backed business, which was founded in 2022, is building a cloud-native operating platform and operational service software, along with customer-facing applications that each client bank can configure as its own.\n\nBy hosting customers directly on their platform and managing all operational aspects for their client banks, Constantinople is looking to radically simplify how banks operate.\n\nAll of this is being built with GitLab, using the [DevSecOps](/topics/devsecops/) Platform to create mission-critical software for everything from customer experience to transaction and lending products, digital servicing, and compliance solutions.\n\nFor Constantinople, [security](/blog/its-time-to-put-the-sec-in-devsecops/) needs to be part of every aspect of their software lifecycle now so they [don’t have to go back and fix vulnerabilities](/blog/devsecops-platforms-give-smbs-security-muscle/) when it’s more costly and time-consuming. Using GitLab’s DevSecOps Platform from the very beginning has been a key part of their startup strategy. They also want visibility, measurability, and collaboration to be part of their process at the earliest stages of their company.\n\n## Beginning with a security focus\nConstantinople, which uses the AWS cloud, is creating software and a multi-tenant platform that a number of banks will use, so strong security must be foundational. Moving security earlier in the software development lifecycle - all the way to the planning stages - is crucial. So is using [automated security testing](/blog/want-faster-releases-your-answer-lies-in-automated-software-testing/) to catch vulnerabilities when they’re created, instead of when software is about to be deployed. [Gaining those abilities](/the-source/security/how-to-strengthen-security-by-applying-devsecops-principles/) inside a single, end-to-end platform is the best way for Constantinople developers to make sure all of this happens.\n\n“Security is always front of mind for all of our developers, especially since we are working within a high-security industry,” says Smith. “A critical part of our secure software lifecycle is making it as easy as possible for developers to build secure code, and make sure any issues are quickly fixed, long before merge and release. By shortening our security feedback cycle, we have both happier developers, and a cleaner and more secure codebase.”\n\nIt’s key for Constantinople to not only offer its customers software that is [compliant](/blog/top-5-compliance-features-to-leverage-in-gitlab/) with industry and government regulations, but to ease the process for becoming and remaining compliant.\n\n“Compliance is obviously vital to any business operating within the regulated perimeter, especially financial services,” says Smith. “Automated compliance capabilities in the DevSecOps platform are a key differentiator for us, precisely because it makes the process easy, reliable, and repeatable.”\n\n## Creating an atmosphere of collaboration\nThe leadership team also is focused on building into their company - in development teams and across the entire business - an [atmosphere of collaboration](/blog/5-ways-collaboration-boosts-productivity-and-your-career/). They don’t want to wait until the number of employees has expanded from tens to hundreds or thousands, and then begin to try to convince people to work together. They want that happening right now, from the very beginning, so the collaboration mentality is part of the Constantinople experience that scales with the company.\n\n“[Collaboration](/blog/6-ways-smbs-can-leverage-the-power-of-a-devops-platform/) is absolutely critical,” says Smith, noting that about 80% of the company is directly responsible for delivering software products. “Without developers being able to collaborate, no complex system could be built because developers would tread on each other's toes and break each other’s work. While the software we build is at the heart of what we do, we’re so much more than just a software provider. With operations, compliance, and a multitude of other functions layered on top of the software, enabling multiple features to work together is key to us.”\n\nHe adds, “Having a group of self-driven developers each contributing seamlessly is like seeing a piece of art come together. Collaboration is the difference between a team that works and one that doesn’t.”\n\n## Getting started with GitLab’s platform\nConstantinople didn’t want to start with a complicated and costly bunch of DevOps tools strung together into an unwieldy toolchain. Developers and leaders wanted to launch the company using a full DevSecOps platform. They evaluated BitBucket, GitHub, and Snyk, but decided to go with GitLab Ultimate. This was largely because of its feature maturity as well as its [security](/blog/getting-started-with-gitlab-application-security/) and [CI/CD](/topics/ci-cd/) capabilities. Using a single application also means that they aren’t building a toolchain that would have their developers and engineers spending time integrating, updating, and maintaining a plethora of tools, instead of focusing on creating products, according to Smith.\n\n“We’ve been able to do all of our technical tooling within GitLab,” says Smith. “For a startup, especially, using a DevSecOps platform allows us to focus on building our product without all the overhead and risk that comes with trying to manage development and security in isolation. We can maximize the efficiency of, and minimize the rework for, both software and DevOps engineers.”\n\nAnd it’s working well for the company’s team of developers. Smith notes that everyone surveyed said they either “liked” or “loved” GitLab’s DevSecOps Platform.\n\n> **Next:** GitLab CISO Josh Lemos shares advice for [addressing the root cause of common security frustrations](https://about.gitlab.com/the-source/security/security-its-more-than-culture-addressing-the-root-cause-of-common-security/).\n","finserv-startup-constantinople-uses-devsecops-to-build-in-security","content:en-us:the-source:security:finserv-startup-constantinople-uses-devsecops-to-build-in-security.yml","en-us/the-source/security/finserv-startup-constantinople-uses-devsecops-to-build-in-security.yml","en-us/the-source/security/finserv-startup-constantinople-uses-devsecops-to-build-in-security",[422,461,496,516],1759347900867]