[{"data":1,"prerenderedAt":600},["ShallowReactive",2],{"/the-source/authors/brian-wald":3,"footer-en-us":32,"the-source-banner-en-us":402,"the-source-navigation-en-us":408,"the-source-newsletter-en-us":431,"authors-en-us":439,"categories-en-us":480,"brian-wald-articles-list-en-us":481},{"id":4,"title":5,"body":6,"category":6,"config":7,"content":9,"description":6,"extension":23,"meta":24,"navigation":25,"path":26,"seo":27,"slug":28,"stem":29,"testContent":6,"type":30,"__hash__":31},"theSourceAuthors/en-us/the-source/authors/brian-wald.yml","Brian Wald",null,{"layout":8},"the-source",[10,21],{"componentName":11,"type":11,"componentContent":12},"TheSourceAuthorHero",{"config":13,"name":5,"role":16,"bio":17,"headshot":18},{"gitlabHandle":14,"linkedInProfileUrl":15},"brianwald","https://www.linkedin.com/in/brianwald/","Head of Global Field CTO org","Brian Wald is Head of Global Field CTO org at GitLab. He leads a dynamic team of Field CTOs dedicated to transforming enterprise software development practices.",{"altText":5,"config":19},{"src":20},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1751463417/fugpbux9miqbdx3wewtu.jpg",{"componentName":22,"type":22},"TheSourceArticlesList","yml",{},true,"/en-us/the-source/authors/brian-wald",{"title":5},"brian-wald","en-us/the-source/authors/brian-wald","author","xMN9kqHPA7rbb_OhNCWA9tUGAPLCh9L7auCkxTtS0zs",{"data":33},{"text":34,"config":35,"items":40,"minimal":391},"Git is a trademark of Software Freedom Conservancy and our use of 'GitLab' is under license",{"twitter":36,"facebook":37,"youtube":38,"linkedin":39},"https://twitter.com/gitlab","https://www.facebook.com/gitlab","https://www.youtube.com/channel/UCnMGQ8QHMAnVIsI3xJrihhg","https://www.linkedin.com/company/gitlab-com",[41,99,175,256,334],{"title":42,"links":43,"subMenu":60},"Pricing",[44,50,55],{"text":45,"config":46},"View plans",{"href":47,"dataGaName":48,"dataGaLocation":49},"/pricing/","view plans","footer",{"text":51,"config":52},"Why Premium?",{"href":53,"dataGaName":54,"dataGaLocation":49},"/pricing/premium/","why premium",{"text":56,"config":57},"Why Ultimate?",{"href":58,"dataGaName":59,"dataGaLocation":49},"/pricing/ultimate/","why ultimate",[61],{"title":62,"links":63},"Contact Us",[64,69,74,79,84,89,94],{"text":65,"config":66},"Contact sales",{"href":67,"dataGaName":68,"dataGaLocation":49},"/sales/","sales",{"text":70,"config":71},"Support portal",{"href":72,"dataGaName":73,"dataGaLocation":49},"https://support.gitlab.com/hc/en-us","support portal",{"text":75,"config":76},"Customer portal",{"href":77,"dataGaName":78,"dataGaLocation":49},"https://customers.gitlab.com/customers/sign_in/","customer portal",{"text":80,"config":81},"Status",{"href":82,"dataGaName":83,"dataGaLocation":49},"https://status.gitlab.com/","status",{"text":85,"config":86},"Terms of use",{"href":87,"dataGaName":88,"dataGaLocation":49},"/terms/","terms of use",{"text":90,"config":91},"Privacy statement",{"href":92,"dataGaName":93,"dataGaLocation":49},"/privacy/","privacy statement",{"text":95,"config":96},"Cookie preferences",{"dataGaName":97,"dataGaLocation":49,"id":98,"isOneTrustButton":25},"cookie preferences","ot-sdk-btn",{"title":100,"links":101,"subMenu":132},"Platform",[102,107,112,117,122,127],{"text":103,"config":104},"Explore the platform",{"href":105,"dataGaName":106,"dataGaLocation":49},"/platform/","platform",{"text":108,"config":109},"Duo Agent Platform",{"href":110,"dataGaName":111,"dataGaLocation":49},"/gitlab-duo-agent-platform/","duo agent platform",{"text":113,"config":114},"CI/CD",{"href":115,"dataGaName":116,"dataGaLocation":49},"/solutions/continuous-integration/","ci/cd",{"text":118,"config":119},"Orbit Context Graph",{"href":120,"dataGaName":121,"dataGaLocation":49},"/gitlab-orbit/","orbit",{"text":123,"config":124},"Secrets Management",{"href":125,"dataGaName":126,"dataGaLocation":49},"/gitlab-secrets-manager/","secrets management",{"text":128,"config":129},"Why GitLab",{"href":130,"dataGaName":131,"dataGaLocation":49},"/why-gitlab/","why gitlab",[133],{"title":134,"links":135},"Topics",[136,140,145,150,155,160,165,170],{"text":113,"config":137},{"href":138,"dataGaName":139,"dataGaLocation":49},"/topics/ci-cd/","cicd",{"text":141,"config":142},"GitOps",{"href":143,"dataGaName":144,"dataGaLocation":49},"/topics/gitops/","gitops",{"text":146,"config":147},"DevOps",{"href":148,"dataGaName":149,"dataGaLocation":49},"/topics/devops/","devops",{"text":151,"config":152},"Version Control",{"href":153,"dataGaName":154,"dataGaLocation":49},"/topics/version-control/","version control",{"text":156,"config":157},"DevSecOps",{"href":158,"dataGaName":159,"dataGaLocation":49},"/topics/devsecops/","devsecops",{"text":161,"config":162},"Cloud Native",{"href":163,"dataGaName":164,"dataGaLocation":49},"/topics/cloud-native/","cloud native",{"text":166,"config":167},"AI for Coding",{"href":168,"dataGaName":169,"dataGaLocation":49},"/topics/devops/ai-for-coding/","ai for coding",{"text":171,"config":172},"Agentic AI",{"href":173,"dataGaName":174,"dataGaLocation":49},"/topics/agentic-ai/","agentic ai",{"title":176,"links":177},"Solutions",[178,183,188,193,198,203,208,213,218,223,228,233,238,241,246,251],{"text":179,"config":180},"DevOps modernization",{"href":181,"dataGaName":182,"dataGaLocation":49},"/assessments/devops-modernization-assessment/","devops modernization",{"text":184,"config":185},"Security modernization",{"href":186,"dataGaName":187,"dataGaLocation":49},"/assessments/security-modernization-assessment/","security modernization",{"text":189,"config":190},"AI modernization",{"href":191,"dataGaName":192,"dataGaLocation":49},"/assessments/ai-modernization-assessment/","ai modernization",{"text":194,"config":195},"Financial services",{"href":196,"dataGaName":197,"dataGaLocation":49},"/solutions/finance/","financial services",{"text":199,"config":200},"Public sector",{"href":201,"dataGaName":202,"dataGaLocation":49},"/solutions/public-sector/","public sector",{"text":204,"config":205},"Telecommunications",{"href":206,"dataGaName":207,"dataGaLocation":49},"/solutions/telecommunications/","telecommunications",{"text":209,"config":210},"Automotive",{"href":211,"dataGaName":212,"dataGaLocation":49},"/solutions/automotive/","automotive",{"text":214,"config":215},"Education",{"href":216,"dataGaName":217,"dataGaLocation":49},"/solutions/education/","education",{"text":219,"config":220},"Aerospace",{"href":221,"dataGaName":222,"dataGaLocation":49},"/solutions/aerospace/","aerospace",{"text":224,"config":225},"Enterprise",{"href":226,"dataGaName":227,"dataGaLocation":49},"/enterprise/","enterprise",{"text":229,"config":230},"Small business",{"href":231,"dataGaName":232,"dataGaLocation":49},"/small-business/","small business",{"text":234,"config":235},"Startups",{"href":236,"dataGaName":237,"dataGaLocation":49},"/solutions/startups/","startups",{"text":141,"config":239},{"href":240,"dataGaName":144,"dataGaLocation":49},"/solutions/gitops/",{"text":242,"config":243},"Software composition analysis",{"href":244,"dataGaName":245,"dataGaLocation":49},"/solutions/supply-chain/","software composition analysis",{"text":247,"config":248},"Value stream management",{"href":249,"dataGaName":250,"dataGaLocation":49},"/solutions/visibility-measurement/","value stream management",{"text":252,"config":253},"All solutions",{"href":254,"dataGaName":255,"dataGaLocation":49},"/solutions/","all solutions",{"title":257,"links":258},"Resources",[259,264,269,274,279,284,289,294,299,304,309,314,319,324,329],{"text":260,"config":261},"Install",{"href":262,"dataGaName":263,"dataGaLocation":49},"/install/","install",{"text":265,"config":266},"Quick start guides",{"href":267,"dataGaName":268,"dataGaLocation":49},"/get-started/","quick setup checklists",{"text":270,"config":271},"Docs",{"href":272,"dataGaName":273,"dataGaLocation":49},"https://docs.gitlab.com/","docs",{"text":275,"config":276},"University",{"href":277,"dataGaName":278,"dataGaLocation":49},"https://university.gitlab.com/","university",{"text":280,"config":281},"Demo Series",{"href":282,"dataGaName":283,"dataGaLocation":49},"/gitlab-technical-demo-series/","demo series",{"text":285,"config":286},"Demo Hub",{"href":287,"dataGaName":288,"dataGaLocation":49},"/demo-hub/","demo hub",{"text":290,"config":291},"Services",{"href":292,"dataGaName":293,"dataGaLocation":49},"/services/","services",{"text":295,"config":296},"Blog",{"href":297,"dataGaName":298,"dataGaLocation":49},"/blog/","blog",{"text":300,"config":301},"Community",{"href":302,"dataGaName":303,"dataGaLocation":49},"/community/","community",{"text":305,"config":306},"Customers",{"href":307,"dataGaName":308,"dataGaLocation":49},"/customers/","customers",{"text":310,"config":311},"Partners",{"href":312,"dataGaName":313,"dataGaLocation":49},"/partners/","partners",{"text":315,"config":316},"Events",{"href":317,"dataGaName":318,"dataGaLocation":49},"/events/","events",{"text":320,"config":321},"Newsletter",{"href":322,"dataGaName":323,"dataGaLocation":49},"/company/contact/#contact-forms","newsletter",{"text":325,"config":326},"What's new",{"href":327,"dataGaName":328,"dataGaLocation":49},"/whats-new/","whats new",{"text":330,"config":331},"All resources",{"href":332,"dataGaName":333,"dataGaLocation":49},"/resources/","all resources",{"title":335,"links":336},"Company",[337,342,347,352,357,362,367,372,377,381,386],{"text":338,"config":339},"About",{"href":340,"dataGaName":341,"dataGaLocation":49},"/company/","company",{"text":343,"config":344},"Jobs",{"href":345,"dataGaName":346,"dataGaLocation":49},"/jobs/","jobs",{"text":348,"config":349},"Press",{"href":350,"dataGaName":351,"dataGaLocation":49},"/press/","press",{"text":353,"config":354},"Handbook",{"href":355,"dataGaName":356,"dataGaLocation":49},"https://handbook.gitlab.com/","handbook",{"text":358,"config":359},"Leadership",{"href":360,"dataGaName":361,"dataGaLocation":49},"/company/team/e-group/","leadership",{"text":363,"config":364},"Investor relations",{"href":365,"dataGaName":366,"dataGaLocation":49},"https://ir.gitlab.com/overview/default.aspx","investor relations",{"text":368,"config":369},"Trust Center",{"href":370,"dataGaName":371,"dataGaLocation":49},"/security/","trust center",{"text":373,"config":374},"AI Transparency Center",{"href":375,"dataGaName":376,"dataGaLocation":49},"/ai-transparency-center/","ai transparency center",{"text":378,"config":379},"Sustainability",{"href":380,"dataGaName":378,"dataGaLocation":49},"/sustainability/",{"text":382,"config":383},"Diversity, inclusion and belonging (DIB)",{"href":384,"dataGaName":385,"dataGaLocation":49},"/diversity-inclusion-belonging/","Diversity, inclusion and belonging",{"text":387,"config":388},"Modern Slavery Transparency Statement",{"href":389,"dataGaName":390,"dataGaLocation":49},"https://handbook.gitlab.com/handbook/legal/modern-slavery-act-transparency-statement/","modern slavery transparency statement",{"items":392},[393,396,399],{"text":394,"config":395},"Terms",{"href":87,"dataGaName":88,"dataGaLocation":49},{"text":397,"config":398},"Cookies",{"dataGaName":97,"dataGaLocation":49,"id":98,"isOneTrustButton":25},{"text":400,"config":401},"Privacy",{"href":92,"dataGaName":93,"dataGaLocation":49},{"visibility":25,"title":403,"button":404},"The Intelligent Software Development Era: How AI is reshaping DevSecOps teams",{"config":405,"text":407},{"href":406},"/resources/developer-survey/","Get the research report",{"logo":409,"subscribeLink":414,"navItems":418},{"altText":410,"config":411},"the source logo",{"src":412,"href":413},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1750191004/t7wz1klfb2kxkezksv9t.svg","/the-source/",{"text":415,"config":416},"Subscribe",{"href":417},"#subscribe",[419,423,427],{"text":420,"config":421},"Artificial Intelligence",{"href":422},"/the-source/ai/",{"text":424,"config":425},"Security & Compliance",{"href":426},"/the-source/security/",{"text":428,"config":429},"Platform & Infrastructure",{"href":430},"/the-source/platform/",{"title":432,"description":433,"submitMessage":434,"formData":435},"The Source Newsletter","Stay updated with insights for the future of software development.","You have successfully signed up for The Source’s newsletter.",{"config":436},{"formId":437,"skeletonFieldCount":438,"formName":323,"hideRequiredLabel":25},1077,3,{"amanda-rueda":440,"andre-michael-braun":441,"andrew-haschka":442,"ayoub-fandi":443,"bob-stevens":444,"brian-wald":5,"bryan-ross":445,"chandler-gibbons":446,"cherry-han":447,"darva-satcher":448,"dave-steer":449,"ddesanto":450,"derek-debellis":451,"emilio-salvador":452,"erika-feldman":453,"george-kichukov":454,"gitlab":455,"grant-hickman":456,"haim-snir":457,"iganbaruch":458,"james-nyika":459,"jason-morgan":460,"jessie-young":461,"jlongo":462,"joel-krooswyk":463,"josh-lemos":464,"joshua-carroll":465,"julie-griffin":466,"kristina-weis":467,"lee-faus":468,"marco-caronna":469,"michelle-gill":470,"nathen-harvey":471,"ncregan":472,"rob-smith":473,"rschulman":474,"sabrina-farmer":475,"sandra-gittlen":476,"sharon-gaudin":477,"stephen-walters":478,"taylor-mccaslin":479},"Amanda Rueda","Andre Michael Braun","Andrew Haschka","Ayoub Fandi","Bob Stevens","Bryan Ross","Chandler Gibbons","Cherry Han","Darva Satcher","Dave Steer","David DeSanto","Derek DeBellis","Emilio Salvador","Erika Feldman","George Kichukov","GitLab","Grant Hickman","Haim Snir","Itzik Gan Baruch","James Nyika","Jason Morgan","Jessie Young","Joseph Longo","Joel Krooswyk","Josh Lemos","Joshua Carroll","Julie Griffin","Kristina Weis","Lee Faus","Marco Caronna","Michelle Gill","Nathen Harvey","Niall Cregan","Rob Smith","Robin Schulman","Sabrina Farmer","Sandra Gittlen","Sharon Gaudin","Stephen Walters","Taylor McCaslin",{"ai":420,"platform":428,"security":424},[482,524,566],{"id":483,"title":484,"body":6,"category":485,"config":486,"content":490,"description":492,"extension":23,"meta":516,"navigation":25,"path":517,"seo":518,"slug":520,"stem":521,"type":522,"__hash__":523,"date":491,"timeToRead":493,"heroImage":494,"keyTakeaways":495,"articleBody":499,"faq":500},"theSource/en-us/the-source/ai/your-enterprise-ai-stack-needs-air-traffic-control.yml","Your enterprise AI stack needs air traffic control","ai",{"layout":8,"template":487,"featured":488,"author":28,"sourceCTA":489,"isHighlighted":488,"authorName":5},"TheSourceArticle",false,"source-lp-enterprise-guide-to-agentic-ai",{"date":491,"title":484,"description":492,"timeToRead":493,"heroImage":494,"keyTakeaways":495,"articleBody":499,"faq":500},"2026-04-29","AI tools are multiplying faster than enterprise governance can keep up. Here's how platform orchestration supports innovation and security.","5 min read","https://res.cloudinary.com/about-gitlab-com/image/upload/v1776457632/llddiylsgwuze0u1rjks.png",[496,497,498],"AI tool sprawl is costing DevSecOps teams nearly a full workday every week. The AI point solutions drain productivity and create shadow AI risks faster than enterprise governance can resolve.","Vibe coding works for individuals but breaks down at enterprise scale, where legacy systems, compliance requirements, and non-deterministic AI outputs build, creating significant risk.","A platform approach acts as air traffic control for AI development, giving developers freedom to experiment while enforcing consistent security and compliance standards across the software lifecycle.","If you’re a CIO today, it might feel like you're walking a tight rope. On one hand your developers want to experiment with the latest AI coding tools. Every week brings a new model, agent, or tool promising unparalleled productivity gains. On the other hand, you have to weigh the security and compliance complications of adding a new tool. Which ones do you approve? And how do you make those decisions knowing that the landscape will look completely different in three months?\n\nTwo distinct approaches are emerging in response: \n\n1. Startups and small teams are optimizing for speed, rapidly adopting the tools that promise the fastest path to market.   \n2. Enterprises are focused on data privacy, sovereignty, and compliance, which are governance capabilities necessary to their operations.\n\nThe tension between these approaches creates a dilemma. You can’t keep changing your entire stack every few months, but standing still means falling behind competitors who are moving faster.\n\n## The challenges with AI point solutions\n\nWhen it comes to AI tools, there are too many, and DevSecOps professionals don’t have enough control over them.\n\n[Recent data](https://ir.gitlab.com/news/news-details/2025/GitLab-Survey-Reveals-the-AI-Paradox-Faster-Coding-Creates-New-Bottlenecks-Requiring-Platform-Solutions/default.aspx) shows that 60% of development teams use more than five tools for software development, and 49% use more than five AI tools. The cost of this fragmentation is staggering. DevSecOps professionals lose seven hours per week to disconnected workflows and context-switching between platforms.\n\nIn addition to lost productivity, organizations are struggling with shadow AI as more teams adopt AI tools under the radar of the IT team. This leads to a variety of governance and compliance issues from breaches of your intellectual property to customer data leaks. \n\nRestricting tool adoption seems like the obvious fix. Mandate a single approved stack and move on. But that approach fails in practice. Developers use the tools they prefer regardless of policy. Shadow IT has evolved into shadow AI, so how do you [govern the adoption of AI tools](https://selfcommunity.co/craft/software-development-enters-the-orchestration-era)? How do you decide who or what plays air traffic control?\n\n### Vibe coding from an enterprise perspective\n\nWith enough prompting, anyone can create functional code, translating business requirements into working applications through natural language. This makes programming so much more accessible to those without an engineering background, but 73% of organizations have already experienced significant problems with the [vibe coding approach](https://about.gitlab.com/the-source/ai/from-vibe-coding-to-agentic-ai-a-roadmap-for-technical-leaders/).\n\nLLMs are non-deterministic. The same prompt can produce different outputs, creating validation challenges that simply didn't exist with traditional development tools. AI can optimize the solution it’s given, but only humans can assess whether it's the right solution to the right problem.\n\nEnterprise development adds another layer of complexity. Pre-existing codebases spanning millions of lines, strict compliance requirements, legacy integrations, and layered security protocols all make AI less effective. A seemingly minor change in one line of code can ripple through interconnected systems in ways that even experienced developers struggle to predict.\n\n### The AI paradox: Creating bottlenecks it was supposed to eliminate\n\nAI helps developers write more code faster, which leads to more reviews, more tests to run, more surface area to protect, and more technical debt to manage. This is the scale trap or the AI paradox. AI accelerates one part of the development lifecycle while creating bottlenecks everywhere else. And as code complexity increases, the very speed and accuracy that made AI attractive in the first place begins to decline, creating a vicious cycle where teams move faster only to slow down.\n\n## Treating your platform as air traffic control\n\nThe governance crisis is real and getting worse. Seventy percent of organizations report that AI is making compliance management more challenging, not easier. No individual tool can solve this — point solutions lack the visibility and control needed to enforce consistent standards across the entire software development lifecycle. \n\nWhat’s needed is a platform that functions as an air traffic controller, ensuring every vehicle follows the rules while still allowing pilots to choose their preferred route.\n\nIn practice, this looks like:\n\n* **Single point of control**: Every piece of code, regardless of which AI tool generated it, flows through a unified platform that consistently applies your organization’s policies.  \n* **Comprehensive context**: The platform gives AI agents project plans, test suites, compliance checks, security scans, and the complete picture across your SDLC. With this context, agents have the full context to operate effectively.  \n* **Validated outputs at scale**: Non-deterministic AI outputs require consistent quality checks. A platform approach builds these validation loops into workflows, catching issues before they reach production.  \n* **Data privacy by design**: Enterprise data requirements are addressed at the platform level so your code and intellectual property stay under your control, not training models for someone else.  \n* **Provider-agnostic developer freedom (within guardrails)**: Developers use their preferred tools and experiment with new technologies, while the platform ensures everything meets enterprise standards.\n\n## Building for constant change with a platform approach\n\nEnterprises that build [orchestration infrastructure](https://selfcommunity.co/craft/software-development-enters-the-orchestration-era) now will be better able to scale AI and adopt new tools as capabilities evolve. Your developers will have the freedom to innovate and experiment while the organization gets assurance that security protocols are enforced, compliance requirements are met, and code quality is consistent regardless of origin.\n\nSomeone needs to play the role of air traffic control in the AI development landscape. You have the choice of implementing that control through a platform approach that enables innovation, or through restrictions that drive development underground into shadow IT operations.\n\nThe future belongs to enterprises that can move fast without breaking things, that promote developer creativity within clear guardrails, and treat platform orchestration as the foundation for sustainable innovation. The organizations that build this foundation today will define the next era of software development.",[501,504,507,510,513],{"header":502,"content":503},"What is the AI paradox in enterprise software development?","The AI paradox refers to how AI accelerates code creation while creating bottlenecks everywhere else in the development lifecycle. Faster code generation leads to more reviews, tests, security checks, and technical debt, ultimately slowing teams down rather than speeding them up.",{"header":505,"content":506},"How much productivity do DevSecOps teams lose to AI tool sprawl?","DevSecOps professionals lose roughly seven hours per week—nearly a full workday—to disconnected workflows and context-switching between platforms. With 60% of development teams using more than five tools and 49% using more than five AI tools, fragmentation is a major productivity drain.",{"header":508,"content":509},"Why does vibe coding fail at enterprise scale?","Vibe coding breaks down at enterprise scale because LLMs are non-deterministic, producing different outputs from identical prompts. Combined with legacy codebases, compliance requirements, and layered security protocols, this creates validation challenges. 73% of organizations have already experienced significant problems with vibe coding.",{"header":511,"content":512},"What is shadow AI and why is it a governance risk?","Shadow AI occurs when teams adopt AI tools without IT oversight, evolving from traditional shadow IT. It creates governance and compliance issues including intellectual property breaches and customer data leaks. 70% of organizations report AI is making compliance management more challenging, not easier.",{"header":514,"content":515},"How does a platform approach act as air traffic control for AI development?","A platform approach provides a single point of control where all code flows through unified policies, regardless of which AI tool generated it. It delivers comprehensive SDLC context to AI agents, builds validation loops for non-deterministic outputs, ensures data privacy by design, and maintains provider-agnostic developer freedom within guardrails.",{},"/en-us/the-source/ai/your-enterprise-ai-stack-needs-air-traffic-control",{"config":519,"title":484,"description":492},{"noIndex":488},"your-enterprise-ai-stack-needs-air-traffic-control","en-us/the-source/ai/your-enterprise-ai-stack-needs-air-traffic-control","article","pIf764Vzv42hATv8MnnRRNbV8OlxNkT8MUfXYSIXFQ4",{"id":525,"title":526,"body":6,"category":106,"config":527,"content":529,"description":531,"extension":23,"meta":560,"navigation":25,"path":561,"seo":562,"slug":563,"stem":564,"type":522,"__hash__":565,"date":530,"timeToRead":493,"heroImage":532,"keyTakeaways":533,"articleBody":537,"faq":538},"theSource/en-us/the-source/platform/from-toolchain-chaos-to-business-roi-a-5-step-roadmap.yml","From toolchain chaos to business ROI: A 5-step roadmap",{"layout":8,"template":487,"author":28,"featured":25,"sourceCTA":528,"isHighlighted":488,"authorName":5},"transform-your-software-development",{"title":526,"date":530,"description":531,"timeToRead":493,"heroImage":532,"keyTakeaways":533,"articleBody":537,"faq":538},"2025-03-11","Reduce complexity by standardizing tools, processes, and practices and aligning every team with broader business objectives.","https://res.cloudinary.com/about-gitlab-com/image/upload/v1751463923/joqzi3uwfbqptjynlkbs.jpg",[534,535,536],"Standardizing your software development platform reduces operational costs while increasing delivery speed and security, transforming tech from a cost center to a competitive advantage.","The five-step standardization process (assess, set standards, leverage AI, centralize, and train) creates a framework for sustainable innovation without the burden of technical debt.","A unified development platform doesn't just streamline operations — it enables faster market response, better decision-making, and future-proofed technology investments.","As companies grow, teams often rush to deliver software quickly, which can lead to a mix of different software development tools and methods. Each team might develop custom solutions for quick fixes, creating a [messy work setup](https://about.gitlab.com/the-source/platform/devops-teams-want-to-shake-off-diy-toolchains-a-platform-is-the-answer/). The hidden costs add up quickly: duplicate tooling licenses, increased maintenance overhead, security vulnerabilities from inconsistent practices, and countless hours lost to integration challenges between disparate systems. All of this isn’t just inefficient - it could directly impact your organization’s bottom line.\n\nA [standardized development platform](https://about.gitlab.com/the-source/platform/driving-business-results-with-platform-engineering/) eliminates these inefficiencies. You can align technology investments with broader business goals by creating a unified workspace where all software development teams operate with consistent tools and processes. The result: reduced costs, accelerated delivery, improved security, and a clear competitive advantage.\n\n## Benefits of a standardized development platform\n**Save money**: A standardized platform can significantly cut costs. You’ll spend less on licenses, upkeep, and connecting different systems by using one system instead of many separate tools. You’ll also depend less on outside vendors and spend less time and effort training teams on multiple tools.\n\n**Launch faster**: A centralized platform also speeds up your development process. By streamlining the entire process and bringing tools and workflows together, you can remove the delays you’d find when using many different tools.\n\n**Improve security and compliance**: When applying the same safety measures across the whole platform, you can reduce vulnerabilities and simplify following regulations.\n\n**Get better insights**: With a platform approach, you can get precise, accurate data about the entire software development lifecycle, enabling you to improve your teams’ workflows and make data-driven decisions that help the business.\n\n**Future-proof your business**: Finally, a standardized software development approach ensures you can grow and adapt for the future. As your organization expands, this framework allows teams to grow smoothly without disruption.\n\n> Read more: [How to accelerate developer onboarding (and why it matters)](https://selfcommunity.co/culture/how-to-accelerate-developer-onboarding-and-why-it-matters)\n\n## 5 steps to creating a standardized software platform\nCreating a standard software platform is possible for almost any company, but it takes careful planning. Here are five steps leaders can follow to successfully standardize their tools and workflows.\n\n### 1. Assess your existing tools\nFirst, take a good look at your existing tools and processes. This review should include input from everyone involved, including developers, security experts, and [platform engineering teams](https://about.gitlab.com/the-source/platform/driving-business-results-with-platform-engineering/). The goal is to find areas where tools overlap or don’t work well together, and identify ways to improve the development processes for your customers.\n\n### 2. Create clear standards and goals\nBased on your review, create a set of internal standards and best practices. These should include coding rules, deployment pipelines, and security policies. Make sure these standards support your company’s main goals and that all teams can easily follow them. This is also the time to decide what you want to achieve, like improving teamwork, cutting costs, or making it easier to grow.\n\n### 3. Use AI to work smarter\nAI tools are becoming key to modern software development. Developers can focus on more strategic work by automating routine tasks with AI. AI can also improve security by checking code throughout development, catching problems early before they reach production environments.\n\n### 4. Create one central system\nOnce you have standards, you need a place to keep them. A centralized platform can store all documentation, code, and project management tools. With everything in one place, everyone works from the same standards, reducing friction and improving collaboration.\n\n### 5. Invest in training\nStandardization only works if teams know how to follow the standards. Invest in thorough training programs covering all aspects of your standard processes. Ongoing education is key to keeping teams updated with the latest practices across different programming languages, practices, and technologies.\n\n## The ROI of platform standardization\nThe transition to a standardized software development platform is more than a technical improvement - it’s a strategic business investment with measurable returns. Organizations that successfully implement this approach can see up to a [483% overall return on investment](https://about.gitlab.com/resources/study-forrester-tei-gitlab-ultimate/), 400% improvement in developer productivity, and 25% savings in software toolchain costs. The result is a more unified, agile, and secure software development process with less technical debt.\n\nAs you consider this transformation, remember that the most significant costs often lie in maintaining the status quo. The question isn’t whether you can afford to standardize your development platform, but whether you can afford not to in a market where software capabilities increasingly determine competitive positioning. Begin with a focused assessment of your current environment, build stakeholder alignment around clear goals, and approach implementation as a strategic initiative rather than a technical project.",[539,542,545,548,551,554,557],{"header":540,"content":541},"What is a standardized software development platform?","A standardized software development platform brings together all tools, workflows, and processes into a unified environment. It eliminates fragmentation across teams by promoting consistent practices, reducing tool overlap, and enabling collaboration across departments, all while aligning development efforts with overarching business goals.",{"header":543,"content":544},"Why do companies face toolchain chaos as they scale?","As organizations grow, different teams often adopt their own sets of tools and custom workflows to solve immediate problems. This leads to duplication, inconsistent processes, and integration issues that not only create inefficiencies but also introduce higher costs and security risks.",{"header":546,"content":547},"What are the business benefits of platform standardization?","Standardizing development tools and processes helps reduce software licensing and integration costs, accelerate delivery times, improve security posture, and simplify compliance. It also makes it easier to scale development operations while maintaining control and alignment with business objectives.",{"header":549,"content":550},"How does platform standardization improve developer productivity?","By eliminating redundant tools and streamlining workflows, developers spend less time switching contexts or resolving integration issues. A centralized platform supports self-service and consistent processes, enabling developers to focus more on innovation and value delivery.",{"header":552,"content":553},"Can AI enhance platform standardization?","Yes. AI helps by automating repetitive tasks, improving security with real-time code scanning, and providing intelligent insights across the software lifecycle. This reduces operational overhead and enhances development velocity while aligning with standardized practices.",{"header":555,"content":556},"What steps should companies take to begin standardizing their platform?","Organizations should begin by assessing their current tools and identifying overlaps. From there, they can define clear internal standards, implement a centralized platform to enforce them, and invest in training programs to ensure consistent adoption across teams.",{"header":558,"content":559},"Is standardizing development tools only for large enterprises?","No. Any organization, regardless of size, can benefit from standardizing its development platform. In fact, smaller companies may see faster returns due to simpler toolsets and more agile implementation. Over time, the approach supports growth and reduces technical debt at scale.",{},"/en-us/the-source/platform/from-toolchain-chaos-to-business-roi-a-5-step-roadmap",{"title":526,"description":531,"ogImage":532},"from-toolchain-chaos-to-business-roi-a-5-step-roadmap","en-us/the-source/platform/from-toolchain-chaos-to-business-roi-a-5-step-roadmap","Fu5zYvqy8q0AFnWN1bATbBE3Cn3tdVDjBIIa8bXUlak",{"id":567,"title":568,"body":6,"category":106,"config":569,"content":571,"description":573,"extension":23,"meta":594,"navigation":25,"path":595,"seo":596,"slug":597,"stem":598,"type":522,"__hash__":599,"date":572,"timeToRead":574,"heroImage":575,"keyTakeaways":576,"articleBody":580,"faq":581},"theSource/en-us/the-source/platform/driving-business-results-with-platform-engineering.yml","Driving business results with platform engineering",{"layout":8,"template":487,"author":28,"featured":488,"sourceCTA":570,"isHighlighted":488,"authorName":5},"gitlab-2024-global-devsecops-report",{"title":568,"date":572,"description":573,"timeToRead":574,"heroImage":575,"keyTakeaways":576,"articleBody":580,"faq":581},"2024-10-29","Platform engineering accelerates time to market, reduces security risk, and improves developer experience. Learn how to set your DevOps team up for success.","7 min read","https://res.cloudinary.com/about-gitlab-com/image/upload/v1751463790/xmrjm5ztb49zx5bggima.png",[577,578,579],"Platform engineering is emerging as a key strategy in modern software development to help businesses do more with less.","The benefits of platform engineering include improved efficiency, faster time to market, reduced security and compliance risk, improved software quality, and better developer experience.","Establishing a product-oriented culture and setting clear business goals are critical for success in platform engineering.","Platform engineering, which centralizes best practices and components for software development teams, is gaining prominence as DevSecOps practices and frameworks become increasingly embedded across organizations. The goal of platform engineering is to normalize and standardize developer workflows by providing developers with optimized “golden paths” for most of their workloads and flexibility to define exceptions for the rest.\n\nGartner® predicts that “by 2026, 80% of large software engineering organizations will establish platform engineering teams as internal providers of reusable services, components, and tools for application delivery, up from 45% in 2022” [1]. Platform engineering allows organizations - especially larger organizations with many engineering initiatives happening in parallel - to scale DevSecOps principles and tooling more easily. This approach is incredibly important when businesses are pressured to do more with less.\n\n## Key benefits of platform engineering\n**Increase speed to market:** Platform engineering promises to help organizations deliver better-quality software faster and more cost-efficiently. Building a platform engineering team will pay off over the long term, enabling large organizations to achieve faster release cycles with less tooling, resulting in significant cost savings.\n\n**Reduce security and compliance risks:**  By reducing tool sprawl and creating more normalized workflows, organizations can reduce compliance overhead and their potential attack surface. According to [IBM’s Cost of a Data Breach Report](https://www.ibm.com/reports/data-breach), the global average data breach cost in 2023 was $4.45 million. Still, organizations that managed their attack surface effectively could contain breaches faster.\n\n**Improve developer experience:** [DevEx](https://about.gitlab.com/developer-experience/) is a growing priority, with companies competing to attract and keep the best developer talent. Platform engineering teams can help improve the developer experience by building efficient, automated workflows or golden paths and lifting some repetitive tasks from developers’ workloads. This improves developer productivity and simplifies their day-to-day, allowing them to efficiently build, test, and deploy applications and focus on more impactful, business-critical work.\n\n## Platform engineering best practices\n\n### Start with the culture\nIf “platform” describes what we should build, then “engineering” describes how it should be built. Too many organizations leap into buying and installing technology without considering how they’ll need to evolve their organizational culture to make platform adoption a success.\n\nPlatform engineers should consider themselves product owners, with software developers as their customers. They should conduct discovery to understand developers’ needs and then reach out to end users to help them become successful with the resources provided. This requires internal marketing, communication, and customer support skills, which are often lacking in technical teams.\n\nThe key here is a product-oriented mindset and culture, which allows platform teams to focus on creating value for their end users (developers) by listening to user feedback and continuously iterating and improving their product (the internal developer platform). Leaders should create a collaborative environment where team members feel empowered to seek ways to help their specific (internal) customers. They’ll be focused on making it as easy as possible for people to consume their services - likely through self-service tools or programmable APIs.\n\n### Stay focused on delivering business value\nWhen starting a platform engineering initiative, organizations may be tempted to look at highly productive teams and copy what they do. Unfortunately, there’s often too much initial emphasis on the team's structure or the tools it uses. These are often the results of a highly productive team, not the cause. Instead of team structure and tools, leaders should focus on the business outcomes they want to see and then identify the right tools and team structures to achieve those goals.\n\nDefine the goal of your platform engineering practice in terms of business impact. Developing software faster is great - but why? What business goal does it serve?\n\nIncreasing speed and agility, for instance, is a common objective - but there could be several business goals behind it. Slow time to market has an obvious opportunity cost, as organizations must make difficult choices about what products to prioritize. Organizations that can move more quickly are also better equipped to respond to fast-moving markets. And there are security implications - organizations must know they can respond quickly and efficiently if a security incident occurs.\n\nCommon productivity and efficiency metrics are helpful, but leaders should try translating those metrics into dollar values to clarify the business value. For example, suppose a platform engineering effort reduces the time a new developer takes to perform their first commitment to production. In that case, the organization is saving a certain percentage of that developer’s year-one salary and part of the salary of those around them who are helping them onboard. The organization will also likely increase retention, reducing the need for expensive hiring (including advertising, recruiters, and lengthy interview cycles).\n\nLeaders can optimize platform engineering initiatives by staying laser-focused on business value to drive the right results.\n\n### Keep it measurable\nIt’s important to have metrics that help track the platform team’s progress and understand how developers are using (or not using) the services provided. This allows for continuous improvement, identifies areas of success or need for additional resources, and helps with internal marketing efforts.\n\nSome potential metrics to consider include:\n\n- **Adoption rate:** How many developers are actively using the platform?\n\n- **Time to value:** How long does it take for a new developer to start delivering code on the platform?\n\n- **Community engagement:** What percentage of components within the platform were provided by the community? (For example, when a team develops a new CI job that could benefit others, do they share it with the platform team for broader application and maintenance?)\n\n### Build for everyone\nThe early adopters of a developer platform might be the most visible (and vocal) early in the process. However, remember that early adopters - who typically make up less than 20% of an organization - may have very different needs than most users who will eventually leverage the platform. As you define the golden paths that make sense for your organization, ensure you’re building for the majority, not just early adopters.\n\nOne common golden path worth investing in early is an end-to-end continuous integration and continuous delivery (CI/CD) pipeline supporting a particular type of workload on one set of target platforms (such as Kubernetes). Once this base workload is supported, it provides a strong foundation for others and confidence that the platform can deliver value. Define your organization’s priority golden paths regarding the business outcomes they enable.\n\n## The DevSecOps platform: A foundation for platform engineering\nA DevSecOps platform provides one user interface, a unified data store, and security embedded within the DevSecOps lifecycle. With a DevSecOps platform, organizations can build a foundation for platform engineering with workflows-as-a-service for the entire software development process.\n\nHere are a few critical elements of a DevSecOps platform that set teams up for success with platform engineering:\n\n- **Planning and collaboration:** Platform engineering won’t work without transparency. [Bringing everyone into the same platform](/solutions/agile-delivery/) streamlines communication fosters collaboration between teams - enabling more efficient planning, building, testing, securing, deployment, and monitoring of code.\n\n- **CI/CD and orchestration:** Orchestration sits at the heart of platform engineering. A platform helps developers [check code quality and get it to production](/solutions/continuous-integration/). It also provides a templating mechanism to ensure common best practices are baked in, and every change goes through a consistent quality process.\n\n- **Developer experience:** DevEx is all about simplifying developers’ day-to-day by automating repetitive tasks and abstracting away unnecessary decisions. With a DevSecOps platform, all code is in a single place, making it easier for developers to find what they need with minimal context switching. In addition, providing developers with reusable tools and templates and AI-powered features such as code suggestions and code explanations removes obstacles so developers can onboard quickly and start creating value immediately.\n\n- **Integrated security:** With a DevSecOps platform, [automated security scanning](https://about.gitlab.com/solutions/application-security-testing/) ensures that all code meets a baseline policy - and, more importantly, developers have self-service access to that data. They're not waiting until the day of a production rollout to find out that the security team has found a critical vulnerability.\n\n- **Metrics and analytics:** For a platform engineering initiative to be successful, organizations need to identify the business goals behind the project and be able to monitor their progress towards those goals. [Dashboards and analytics that pull data from across the software development lifecycle](https://about.gitlab.com/solutions/visibility-measurement/) enable organizations to easily track key metrics, assess the impact of process improvements, and drill down into roadblocks. That empowers leaders to quickly identify trends and bottlenecks so they can focus efforts on at-risk projects.\n\n[Learn more](https://about.gitlab.com/solutions/platform-engineering/) about how GitLab can support your platform engineering journey by providing DevSecOps teams with a single self-service portal for standardized tools and workflows - reducing cognitive overload and making software delivery more scalable.\n\n*[1] Gartner, Top Strategic Technology Trends for 2024, Bart Willemsen, Gary Olliffe, and Arun Chandrasekaran, 16 October 2023. GARTNER is a registered trademark and service mark of Gartner, Inc. and/or its affiliates in the U.S. and internationally and is used herein with permission. All rights reserved.*",[582,585,588,591],{"header":583,"content":584},"How does platform engineering improve developer productivity?","Platform engineering creates streamlined workflows, known as \"golden paths,\" that automate repetitive tasks and simplify decision-making for developers. By reducing complexity and improving self-service access to tools, developers can focus on innovation, coding, and business-critical work.",{"header":586,"content":587},"What key metrics should organizations track for platform engineering success?","Organizations should measure platform adoption rates, time to value for new developers, community engagement in contributing platform components, and overall impact on software delivery speed and quality. Tracking these metrics helps optimize platform performance and drive business results.",{"header":589,"content":590},"What is platform engineering, and why is it important?","Platform engineering centralizes best practices, tools, and workflows to improve developer efficiency and standardize software development. It helps organizations accelerate time to market, enhance security, and improve developer experience by providing optimized workflows and reducing toolchain complexity.",{"header":592,"content":593},"How does platform engineering enhance security and compliance?","By embedding security policies, automated scanning, and compliance frameworks directly into the software development platform, platform engineering ensures that security is consistently enforced across all applications. This reduces risk exposure and prevents vulnerabilities from reaching production.",{},"/en-us/the-source/platform/driving-business-results-with-platform-engineering",{"title":568,"description":573,"ogImage":575},"driving-business-results-with-platform-engineering","en-us/the-source/platform/driving-business-results-with-platform-engineering","hg3eq3G5ZHZqHu3xj3LU95hwrK0zLqsZK1ZNdSlD1Ts",1794911807934]