[{"data":1,"prerenderedAt":576},["ShallowReactive",2],{"/en-us/the-source/authors/brian-wald/":3,"footer-en-us":34,"the-source-navigation-en-us":342,"the-source-newsletter-en-us":369,"brian-wald-articles-list-authors-en-us":381,"brian-wald-articles-list-en-us":412,"brian-wald-page-categories-en-us":575},{"_path":4,"_dir":5,"_draft":6,"_partial":6,"_locale":7,"config":8,"seo":10,"content":12,"type":26,"slug":27,"_id":28,"_type":29,"title":11,"_source":30,"_file":31,"_stem":32,"_extension":33},"/en-us/the-source/authors/brian-wald","authors",false,"",{"layout":9},"the-source",{"title":11},"Brian Wald",[13,24],{"componentName":14,"type":14,"componentContent":15},"TheSourceAuthorHero",{"config":16,"name":11,"role":19,"bio":20,"headshot":21},{"gitlabHandle":17,"linkedInProfileUrl":18},"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":11,"config":22},{"src":23},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1751463417/fugpbux9miqbdx3wewtu.jpg",{"componentName":25,"type":25},"TheSourceArticlesList","author","brian-wald","content:en-us:the-source:authors:brian-wald.yml","yaml","content","en-us/the-source/authors/brian-wald.yml","en-us/the-source/authors/brian-wald","yml",{"_path":35,"_dir":36,"_draft":6,"_partial":6,"_locale":7,"data":37,"_id":338,"_type":29,"title":339,"_source":30,"_file":340,"_stem":341,"_extension":33},"/shared/en-us/main-footer","en-us",{"text":38,"source":39,"edit":45,"contribute":50,"config":55,"items":60,"minimal":330},"Git is a trademark of Software Freedom Conservancy and our use of 'GitLab' is under license",{"text":40,"config":41},"View page source",{"href":42,"dataGaName":43,"dataGaLocation":44},"https://gitlab.com/gitlab-com/marketing/digital-experience/about-gitlab-com/","page source","footer",{"text":46,"config":47},"Edit this page",{"href":48,"dataGaName":49,"dataGaLocation":44},"https://gitlab.com/gitlab-com/marketing/digital-experience/about-gitlab-com/-/blob/main/content/","web ide",{"text":51,"config":52},"Please contribute",{"href":53,"dataGaName":54,"dataGaLocation":44},"https://gitlab.com/gitlab-com/marketing/digital-experience/about-gitlab-com/-/blob/main/CONTRIBUTING.md/","please contribute",{"twitter":56,"facebook":57,"youtube":58,"linkedin":59},"https://twitter.com/gitlab","https://www.facebook.com/gitlab","https://www.youtube.com/channel/UCnMGQ8QHMAnVIsI3xJrihhg","https://www.linkedin.com/company/gitlab-com",[61,88,161,229,291],{"title":62,"links":63,"subMenu":69},"Platform",[64],{"text":65,"config":66},"DevSecOps platform",{"href":67,"dataGaName":68,"dataGaLocation":44},"/platform/","devsecops platform",[70],{"title":71,"links":72},"Pricing",[73,78,83],{"text":74,"config":75},"View plans",{"href":76,"dataGaName":77,"dataGaLocation":44},"/pricing/","view plans",{"text":79,"config":80},"Why Premium?",{"href":81,"dataGaName":82,"dataGaLocation":44},"/pricing/premium/","why premium",{"text":84,"config":85},"Why Ultimate?",{"href":86,"dataGaName":87,"dataGaLocation":44},"/pricing/ultimate/","why ultimate",{"title":89,"links":90},"Solutions",[91,96,101,106,111,116,121,126,131,136,141,146,151,156],{"text":92,"config":93},"Digital transformation",{"href":94,"dataGaName":95,"dataGaLocation":44},"/topics/digital-transformation/","digital transformation",{"text":97,"config":98},"Security & Compliance",{"href":99,"dataGaName":100,"dataGaLocation":44},"/solutions/security-compliance/","security & compliance",{"text":102,"config":103},"Automated software delivery",{"href":104,"dataGaName":105,"dataGaLocation":44},"/solutions/delivery-automation/","automated software delivery",{"text":107,"config":108},"Agile development",{"href":109,"dataGaName":110,"dataGaLocation":44},"/solutions/agile-delivery/","agile delivery",{"text":112,"config":113},"Cloud transformation",{"href":114,"dataGaName":115,"dataGaLocation":44},"/topics/cloud-native/","cloud transformation",{"text":117,"config":118},"SCM",{"href":119,"dataGaName":120,"dataGaLocation":44},"/solutions/source-code-management/","source code management",{"text":122,"config":123},"CI/CD",{"href":124,"dataGaName":125,"dataGaLocation":44},"/solutions/continuous-integration/","continuous integration & delivery",{"text":127,"config":128},"Value stream management",{"href":129,"dataGaName":130,"dataGaLocation":44},"/solutions/value-stream-management/","value stream management",{"text":132,"config":133},"GitOps",{"href":134,"dataGaName":135,"dataGaLocation":44},"/solutions/gitops/","gitops",{"text":137,"config":138},"Enterprise",{"href":139,"dataGaName":140,"dataGaLocation":44},"/enterprise/","enterprise",{"text":142,"config":143},"Small business",{"href":144,"dataGaName":145,"dataGaLocation":44},"/small-business/","small business",{"text":147,"config":148},"Public sector",{"href":149,"dataGaName":150,"dataGaLocation":44},"/solutions/public-sector/","public sector",{"text":152,"config":153},"Education",{"href":154,"dataGaName":155,"dataGaLocation":44},"/solutions/education/","education",{"text":157,"config":158},"Financial services",{"href":159,"dataGaName":160,"dataGaLocation":44},"/solutions/finance/","financial services",{"title":162,"links":163},"Resources",[164,169,174,179,184,189,194,199,204,209,214,219,224],{"text":165,"config":166},"Install",{"href":167,"dataGaName":168,"dataGaLocation":44},"/install/","install",{"text":170,"config":171},"Quick start guides",{"href":172,"dataGaName":173,"dataGaLocation":44},"/get-started/","quick setup checklists",{"text":175,"config":176},"Learn",{"href":177,"dataGaName":178,"dataGaLocation":44},"https://university.gitlab.com/","learn",{"text":180,"config":181},"Product documentation",{"href":182,"dataGaName":183,"dataGaLocation":44},"https://docs.gitlab.com/","docs",{"text":185,"config":186},"Blog",{"href":187,"dataGaName":188,"dataGaLocation":44},"/blog/","blog",{"text":190,"config":191},"Customer success stories",{"href":192,"dataGaName":193,"dataGaLocation":44},"/customers/","customer success stories",{"text":195,"config":196},"Remote",{"href":197,"dataGaName":198,"dataGaLocation":44},"https://handbook.gitlab.com/handbook/company/culture/all-remote/","remote",{"text":200,"config":201},"GitLab Services",{"href":202,"dataGaName":203,"dataGaLocation":44},"/services/","services",{"text":205,"config":206},"TeamOps",{"href":207,"dataGaName":208,"dataGaLocation":44},"/teamops/","teamops",{"text":210,"config":211},"Community",{"href":212,"dataGaName":213,"dataGaLocation":44},"/community/","community",{"text":215,"config":216},"Forum",{"href":217,"dataGaName":218,"dataGaLocation":44},"https://forum.gitlab.com/","forum",{"text":220,"config":221},"Events",{"href":222,"dataGaName":223,"dataGaLocation":44},"/events/","events",{"text":225,"config":226},"Partners",{"href":227,"dataGaName":228,"dataGaLocation":44},"/partners/","partners",{"title":230,"links":231},"Company",[232,237,242,247,252,257,262,266,271,276,281,286],{"text":233,"config":234},"About",{"href":235,"dataGaName":236,"dataGaLocation":44},"/company/","company",{"text":238,"config":239},"Jobs",{"href":240,"dataGaName":241,"dataGaLocation":44},"/jobs/","jobs",{"text":243,"config":244},"Leadership",{"href":245,"dataGaName":246,"dataGaLocation":44},"/company/team/e-group/","leadership",{"text":248,"config":249},"Team",{"href":250,"dataGaName":251,"dataGaLocation":44},"/company/team/","team",{"text":253,"config":254},"Handbook",{"href":255,"dataGaName":256,"dataGaLocation":44},"https://handbook.gitlab.com/","handbook",{"text":258,"config":259},"Investor relations",{"href":260,"dataGaName":261,"dataGaLocation":44},"https://ir.gitlab.com/","investor relations",{"text":263,"config":264},"Sustainability",{"href":265,"dataGaName":263,"dataGaLocation":44},"/sustainability/",{"text":267,"config":268},"Diversity, inclusion and belonging (DIB)",{"href":269,"dataGaName":270,"dataGaLocation":44},"/diversity-inclusion-belonging/","Diversity, inclusion and belonging",{"text":272,"config":273},"Trust Center",{"href":274,"dataGaName":275,"dataGaLocation":44},"/security/","trust center",{"text":277,"config":278},"Newsletter",{"href":279,"dataGaName":280,"dataGaLocation":44},"/company/contact/","newsletter",{"text":282,"config":283},"Press",{"href":284,"dataGaName":285,"dataGaLocation":44},"/press/","press",{"text":287,"config":288},"Modern Slavery Transparency Statement",{"href":289,"dataGaName":290,"dataGaLocation":44},"https://handbook.gitlab.com/handbook/legal/modern-slavery-act-transparency-statement/","modern slavery transparency statement",{"title":292,"links":293},"Contact Us",[294,299,304,309,314,319,324],{"text":295,"config":296},"Contact an expert",{"href":297,"dataGaName":298,"dataGaLocation":44},"/sales/","sales",{"text":300,"config":301},"Get help",{"href":302,"dataGaName":303,"dataGaLocation":44},"/support/","get help",{"text":305,"config":306},"Customer portal",{"href":307,"dataGaName":308,"dataGaLocation":44},"https://customers.gitlab.com/customers/sign_in/","customer portal",{"text":310,"config":311},"Status",{"href":312,"dataGaName":313,"dataGaLocation":44},"https://status.gitlab.com/","status",{"text":315,"config":316},"Terms of use",{"href":317,"dataGaName":318,"dataGaLocation":44},"/terms/","terms of use",{"text":320,"config":321},"Privacy statement",{"href":322,"dataGaName":323,"dataGaLocation":44},"/privacy/","privacy statement",{"text":325,"config":326},"Cookie preferences",{"dataGaName":327,"dataGaLocation":44,"id":328,"isOneTrustButton":329},"cookie preferences","ot-sdk-btn",true,{"items":331},[332,334,336],{"text":315,"config":333},{"href":317,"dataGaName":318,"dataGaLocation":44},{"text":320,"config":335},{"href":322,"dataGaName":323,"dataGaLocation":44},{"text":325,"config":337},{"dataGaName":327,"dataGaLocation":44,"id":328,"isOneTrustButton":329},"content:shared:en-us:main-footer.yml","Main Footer","shared/en-us/main-footer.yml","shared/en-us/main-footer",{"_path":343,"_dir":9,"_draft":6,"_partial":6,"_locale":7,"logo":344,"subscribeLink":349,"navItems":353,"_id":365,"_type":29,"title":366,"_source":30,"_file":367,"_stem":368,"_extension":33},"/shared/en-us/the-source/navigation",{"altText":345,"config":346},"the source logo",{"src":347,"href":348},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1750191004/t7wz1klfb2kxkezksv9t.svg","/the-source/",{"text":350,"config":351},"Subscribe",{"href":352},"#subscribe",[354,358,361],{"text":355,"config":356},"Artificial Intelligence",{"href":357},"/the-source/ai/",{"text":97,"config":359},{"href":360},"/the-source/security/",{"text":362,"config":363},"Platform & Infrastructure",{"href":364},"/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":370,"_dir":9,"_draft":6,"_partial":6,"_locale":7,"title":371,"description":372,"submitMessage":373,"formData":374,"_id":378,"_type":29,"_source":30,"_file":379,"_stem":380,"_extension":33},"/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":375},{"formId":376,"formName":377,"hideRequiredLabel":329},1077,"thesourcenewsletter","content:shared:en-us:the-source:newsletter.yml","shared/en-us/the-source/newsletter.yml","shared/en-us/the-source/newsletter",{"amanda-rueda":382,"andre-michael-braun":383,"andrew-haschka":384,"ayoub-fandi":385,"bob-stevens":386,"brian-wald":11,"bryan-ross":387,"chandler-gibbons":388,"dave-steer":389,"ddesanto":390,"derek-debellis":391,"emilio-salvador":392,"erika-feldman":393,"george-kichukov":394,"gitlab":395,"grant-hickman":396,"haim-snir":397,"iganbaruch":398,"jlongo":399,"joel-krooswyk":400,"josh-lemos":401,"julie-griffin":402,"kristina-weis":403,"lee-faus":404,"ncregan":405,"rschulman":406,"sabrina-farmer":407,"sandra-gittlen":408,"sharon-gaudin":409,"stephen-walters":410,"taylor-mccaslin":411},"Amanda Rueda","Andre Michael Braun","Andrew Haschka","Ayoub Fandi","Bob Stevens","Bryan Ross","Chandler Gibbons","Dave Steer","David DeSanto","Derek DeBellis","Emilio Salvador","Erika Feldman","George Kichukov","GitLab","Grant Hickman","Haim Snir","Itzik Gan Baruch","Joseph Longo","Joel Krooswyk","Josh Lemos","Julie Griffin","Kristina Weis","Lee Faus","Niall Cregan","Robin Schulman","Sabrina Farmer","Sandra Gittlen","Sharon Gaudin","Stephen Walters","Taylor McCaslin",{"allArticles":413,"visibleArticles":574,"showAllBtn":329},[414,457,500,541],{"_path":415,"_dir":416,"_draft":6,"_partial":6,"_locale":7,"config":417,"seo":421,"content":425,"type":452,"slug":453,"category":416,"_id":454,"_type":29,"title":422,"_source":30,"_file":455,"_stem":456,"_extension":33,"date":426,"description":423,"timeToRead":427,"heroImage":424,"keyTakeaways":428,"articleBody":432,"faq":433},"/en-us/the-source/ai/how-agentic-ai-unlocks-platform-engineering-potential","ai",{"layout":9,"template":418,"articleType":419,"author":27,"featured":329,"gatedAsset":420,"isHighlighted":6,"authorName":11},"TheSourceArticle","Regular","source-lp-getting-started-with-ai-in-software-development-a-guide-for-leaders",{"title":422,"description":423,"ogImage":424},"How agentic AI unlocks platform engineering potential","Explore how agentic AI elevates platform engineering by automating complex workflows and scaling standardization.","https://res.cloudinary.com/about-gitlab-com/image/upload/v1751463908/zz7ifau6dya2fn2eyuij.png",{"title":422,"date":426,"description":423,"timeToRead":427,"heroImage":424,"keyTakeaways":428,"articleBody":432,"faq":433},"2025-05-12","6 min read",[429,430,431],"Agentic AI systems go beyond code assistance, helping organizations overcome platform engineering challenges by automating complex workflows and scaling standardization efforts across development teams.","Technical leaders must consider interoperability, security governance, and workflow integration when implementing autonomous agents to ensure they work seamlessly within existing enterprise systems.","Organizations can leverage agentic systems to address “tech mandatory” initiatives like reducing technical debt and security vulnerabilities, where dense contexts have traditionally posed barriers to automation.","Many organizations have embraced artificial intelligence (AI) tools to boost developer productivity, typically in the form of code assistants that help individual developers write code faster. While these tools deliver welcome efficiency gains, they only scratch the surface of AI’s potential to transform your development organization.\n\nAt the same time, organizations are investing in platform engineering - building integrated toolchains, establishing workflows, and creating standardized processes for software development. However, platform engineering teams will inevitably run into issues with scale: traditional approaches to platform engineering are fundamentally limited by the capacity of human engineers to maintain the platform.\n\nThis is where [agentic AI](https://about.gitlab.com/the-source/ai/agentic-ai-unlocking-developer-potential-at-scale/) becomes a game-changer for your platform engineering investments.\n\n## Why your current platform engineering investment isn’t delivering its full potential\nImagine this: You’ve invested in a [platform engineering approach](https://about.gitlab.com/the-source/platform/driving-business-results-with-platform-engineering/) with tightly integrated tools and processes. However, you’re not yet seeing the expected return on this investment due to challenges such as:\n- Manual processes that can’t scale across the organization\n- Difficulty maintaining and updating platform components\n- Inconsistent adoption of standards across different teams\n- Valuable engineering time spent on routine maintenance instead of innovation\n\nThese challenges exist because traditional approaches to platform engineering are fundamentally limited by human capacity. No matter how well-designed your platform is, you need human engineers to implement, maintain, and scale it.\n\nCode development in enterprise software is also highly context-dependent. Languages can have vastly different performance challenges. Junior developers may not have enough context to write prompts effectively. Security and compliance policies may also create unknown restrictions. No single platform engineer can fully grasp every security, network, and application-layer concern across all these scenarios.\n\n## How agentic AI transforms platform engineering\nAgentic AI systems fundamentally change the equation. Unlike traditional AI assistants that respond only to direct prompts, AI agents have full context into a team’s software development infrastructure. They can initiate actions based on triggers and states, making them the perfect complement to platform engineering frameworks. These autonomous systems can work with minimal human intervention to automate repetitive tasks while still allowing for human oversight on more critical issues.\n\nAI agents can:\n- **Automatically identify and implement standardization opportunities** across your entire organization, ensuring consistency without manual intervention\n- **Maintain and update platform components** by monitoring for security vulnerabilities, performance issues, or outdated dependencies\n- **Create issue descriptions, reusable templates, and implementation plans** based on your existing codebase\n- **Support developers in generating and updating documentation**, including README files, code flow diagrams, and architecture documentation\n\n> Learn how [agentic AI built on top of a comprehensive DevSecOps platform](https://about.gitlab.com/blog/gitlab-duo-workflow-enterprise-visibility-and-control-for-agentic-ai/) can help development teams navigate everything from project bootstrapping and deployment to debugging and cross-team coordination.\n\n## What to keep in mind when implementing AI agents\nAsk yourself these questions when thinking about how to incorporate agentic AI into platform engineering workflows:\n\n### Interoperability, scalability, and reliability\n- How will AI agents communicate with other agents, including across third-party products?\n- How will agents self-correct when they produce unexpected or unwanted results?\n- Will the agents be capable of concurrency (working on multiple tasks at the same time)?\n\n### Security, governance, and observability\n- How will AI agents interact with existing network policies to define what they can and cannot access?\n- How will agents interact with multiple data sources?\n- Will the use of data by AI agents comply with existing data governance, security, and privacy policies?\n- How will agents’ telemetry data be collected, how will their performance be measured, and what will remediation look like when they behave incorrectly?\n\n### Developer workflows\n- How will developers adapt their processes to integrate with agent-based systems?\n- What human supervision mechanisms need to be in place for critical business processes?\n\n## Enabling team velocity with AI agents and platform engineering\nAs AI-powered agents mature, organizations can proactively use these tools to identify patterns, standardize practices, and share knowledge across different development teams without manual coordination.\n\nAfter participating in a recent early access program for [GitLab Duo with Amazon Q](https://about.gitlab.com/blog/gitlab-duo-with-amazon-q-agentic-ai-optimized-for-aws/) - an agentic AI solution for the entire software development lifecycle - Osmar Alonso, DevOps Engineer at Volkswagen Digital Solutions, shared how AI agents have transformative potential for development workflows. “Even in its early stages, we saw how the deeper integration with autonomous agents could streamline our process, from code commit to production,” said Alonso. “We're excited to see how this technology empowers our team to focus on innovation and accelerate our digital transformation.”\n\nAgentic systems show particular promise in “tech mandatory” budget areas that most teams are committed to today, such as reducing technical debt, fixing security vulnerabilities, refactoring automation or infrastructure, and re-platforming legacy apps. These areas are filled with context-rich data and pose barriers to automation that agentic AI can help remove.\n\nFor example, platform engineering teams often create templates to standardize and automate processes such as CI pipelines. This traditionally involves significant manual work to identify the right processes to target - those that are widely used, have repeatable steps, and will have the most significant impact across teams. Agentic AI reduces those manual steps.\n\nRather than relying on human effort to identify processes for standardization, an agentic system can identify all Java-based projects from the past year, analyze the build processes across each, and identify the best candidates for AI-based automation. The system can then create draft templates the team can customize and build on.\n\nAgentic AI is also poised to transform how developers access organizational knowledge and tools. Many companies have invested in internal developer portals (IDPs) as abstraction layers to provide insights and portfolio visibility. However, IDPs are generally static artifacts - someone needs to maintain them and notify developers when new versions of reusable components are available. It's possible that AI agents, as part of a DevSecOps platform, will make IDPs increasingly irrelevant by proactively analyzing context across multiple data sources and tools to provide real-time insights directly within the platform. Agents will also be able to pair with the generative AI capabilities within the platform to deliver personalized, contextual information - such as vulnerability explanations or code suggestions - to each developer based on their role, project, and needs.\n\nPlatform engineering has delivered significant value, but many organizations have hit a ceiling in realizing its full potential. Agentic AI plays a crucial role in upgrading platform engineering efforts by automating complex processes, applying contextual understanding at scale, and enabling true team velocity rather than just individual productivity.",[434,437,440,443,446,449],{"header":435,"content":436},"What is agentic AI, and how does it differ from traditional AI assistants?","Agentic AI refers to autonomous systems that can make decisions, initiate actions, and adapt to context with minimal human input. Unlike traditional AI assistants that respond to prompts, agentic AI agents operate proactively within development workflows, enhancing efficiency and scalability across engineering teams.",{"header":438,"content":439},"Why is agentic AI important for platform engineering?","Agentic AI enhances platform engineering by automating routine and complex tasks such as template creation, vulnerability monitoring, and standardization across teams. This allows organizations to scale their DevSecOps efforts while reducing manual workload and accelerating delivery cycles.",{"header":441,"content":442},"How can agentic AI support standardization across development teams?","Agentic AI can analyze organizational codebases, identify repeatable patterns, and automatically generate templates or process improvements. This helps enforce consistency in CI pipelines, security practices, and documentation without requiring manual coordination across teams.",{"header":444,"content":445},"What should platform teams consider when implementing AI agents?","Successful implementation of agentic AI depends on factors such as interoperability across tools, secure data access, compliance with governance policies, and visibility into agent behavior. Teams must also ensure human oversight is embedded into workflows for critical processes.",{"header":447,"content":448},"Can agentic AI help reduce technical debt?","Yes, agentic AI is particularly effective in “tech mandatory” areas like refactoring outdated code, identifying security vulnerabilities, and automating infrastructure updates. By handling these context-heavy tasks, AI agents free up teams to focus on innovation and strategic initiatives.",{"header":450,"content":451},"Will agentic AI replace internal developer portals (IDPs)?","Agentic AI has the potential to augment or even replace static IDPs by delivering real-time, personalized insights directly within a DevSecOps platform. These agents can proactively provide relevant code suggestions, vulnerability analysis, and workflow guidance based on developer context.","article","how-agentic-ai-unlocks-platform-engineering-potential","content:en-us:the-source:ai:how-agentic-ai-unlocks-platform-engineering-potential:index.yml","en-us/the-source/ai/how-agentic-ai-unlocks-platform-engineering-potential/index.yml","en-us/the-source/ai/how-agentic-ai-unlocks-platform-engineering-potential/index",{"_path":458,"_dir":459,"_draft":6,"_partial":6,"_locale":7,"config":460,"seo":462,"content":466,"type":452,"slug":496,"category":459,"_id":497,"_type":29,"title":463,"_source":30,"_file":498,"_stem":499,"_extension":33,"date":467,"description":464,"timeToRead":468,"heroImage":465,"keyTakeaways":469,"articleBody":473,"faq":474},"/en-us/the-source/platform/high-performing-development-teams-your-business-advantage","platform",{"layout":9,"template":418,"articleType":419,"author":27,"featured":6,"gatedAsset":461,"isHighlighted":6,"authorName":11},"source-lp-building-a-resilient-software-development-practice",{"title":463,"description":464,"ogImage":465},"High-performing development teams: Your business advantage","Building high-performance software development teams accelerates delivery, improves code quality, and drives innovation to meet key business objectives.","https://res.cloudinary.com/about-gitlab-com/image/upload/v1751463980/zj2aimb3oznkxhkh9l2a.png",{"title":463,"date":467,"description":464,"timeToRead":468,"heroImage":465,"keyTakeaways":469,"articleBody":473,"faq":474},"2025-03-13","5 min read",[470,471,472],"High-performing software engineering teams drive innovation by producing quality code while navigating complex organizational challenges, balancing priorities, and adapting to new technologies.","Teams with autonomy and ownership deliver more value faster, accelerating progress toward business objectives while fostering engagement that places them at the forefront of innovation.","Beyond creating software, these teams become models of excellence, spreading best practices that raise performance standards across the entire organization.","What’s the difference between organizations that consistently outpace competitors and those that struggle to keep up? The answer often lies not in their technology stack or market strategy, but in the caliber of their teams.\n\nHigh-performing teams are the driving force behind innovation and efficiency in any software organization. Their success comes from creating quality software while effectively working within complex company structures. They balance competing needs, adapt to changing technologies, and work well with the organization's diverse, often siloed parts.\n\nWhen given more responsibility and freedom, high-performing teams deliver better results in less time, helping the organization reach its goals faster. Increased ownership makes team members more engaged and motivated, often putting them at the front of innovation and leading the development of new features and products.\n\nThe benefits of these teams go beyond just the software they build. They serve as examples for other teams, sharing best practices and improving the organization’s overall performance.\n\n## Creating excellence in software teams\nThese teams don’t just happen by chance; they are built through careful planning, strong leadership, and a culture that values excellence. Engineering leaders can develop high-performing teams by following these essential strategies:\n\n### Identify your star performers\nTrack which development teams consistently exceed performance standards. Spend time with their leaders to learn how they’ve improved their processes. This also builds relationships with these teams, setting them up as examples for other teams.\n\n### Set clear, achievable team goals\nHigh-performing teams thrive when they have clear, achievable goals aligned with the organization’s vision. These goals should be specific, measurable, attainable, relevant, and time-bound.\n\n### Give teams decision-making power\nEmpowered teams are more flexible and adaptable. Give them control over decision-making processes that directly impact their work, such as choosing tools, designing workflows, and setting priorities. This creates a more effective development environment and significantly improves the overall developer experience.\n\n### Build psychological safety and accountability\nTrust is the foundation of any high-performing team, and honest communication is essential for creating a strong sense of trust among team members. Foster a culture where team members feel comfortable sharing ideas, providing feedback, and holding each other accountable. Regular team meetings and feedback sessions help teams reflect on their performance and find ways to improve.\n\n### Invest in continuous learning\nHigh-performing teams are always looking for ways to improve. Help team members develop their technical skills by providing access to ongoing training, certifications, and other learning resources. This creates valuable opportunities for team members to grow professionally, even for experienced developers who want to expand their skill sets.\n\n### Foster a collaborative environment\nCollaboration within and between teams is crucial for success. Project management tools and real-time communication platforms facilitate teamwork, document sharing, and project tracking. A collaborative environment brings together diverse perspectives to solve complex problems, fostering innovation through combining human creativity and modern technology. The most forward-thinking teams are now exploring how generative AI tools can enhance collaboration and [boost productivity in thoughtful, strategic ways](https://about.gitlab.com/the-source/ai/devops-leaders-fix-this-productivity-blocker-before-adding-ai/#-thoughtfully-incorporate-ai-into-workflows).\n\n### Recognize and reward excellence\nHigh-performing teams thrive in environments where their efforts are recognized. Establish a system for acknowledging achievements, both big and small. This could include formal recognition programs, performance bonuses, or simply public acknowledgment of a job well done. Recognizing excellence motivates teams and reinforces the behaviors and practices that lead to success.\n\n## Why high-performing teams are a strategic imperative\n[Research shows](https://about.gitlab.com/developer-survey/) that organizations that have taken steps to build high-performing software teams - such as by adopting a DevSecOps platform - see benefits ranging from faster developer onboarding to more streamlined vulnerability resolution. And all of that translates into a competitive advantage for the business.\n\nThe strategic value goes beyond immediate productivity gains. Cross-functional teams with diverse perspectives become innovation engines that solve complex problems, often identifying new market opportunities that more siloed approaches miss. Perhaps most compelling for the C-suite is the multiplier effect: when you invest in creating one high-performing engineering team, you establish a blueprint that scales as effective team practices become templates that elevate performance organization-wide.\n\nCompany culture that supports excellence and provides the right resources is the foundation upon which all high-performing software teams are built. When the entire team shares a common goal and has the autonomy to achieve it, remarkable results follow.",[475,478,481,484,487,490,493],{"header":476,"content":477},"What defines a high-performing software development team?","A high-performing development team consistently delivers quality software efficiently while adapting to complex organizational needs. These teams are characterized by strong collaboration, clear goals, empowered decision-making, continuous learning, and a shared commitment to improvement and accountability.",{"header":479,"content":480},"How do high-performing teams contribute to business growth?","These teams accelerate product delivery, improve code quality, and foster innovation, all of which directly impact time-to-market and customer satisfaction. Their ability to solve complex problems and drive continuous improvement gives organizations a competitive edge.",{"header":482,"content":483},"What role does team empowerment play in performance?","Empowering teams to make decisions about their tools, workflows, and priorities fosters autonomy and accountability. This leads to higher engagement, faster problem-solving, and more effective development cycles.",{"header":485,"content":486},"How can companies identify high-performing teams?","Organizations can track performance metrics and look for teams that consistently exceed expectations. Engaging with these teams provides insight into best practices that can be replicated across other teams to elevate organizational performance.",{"header":488,"content":489},"Why is psychological safety important for team success?","Psychological safety enables open communication, honest feedback, and shared learning. When team members feel safe to express ideas or raise concerns, it strengthens collaboration and drives innovation.",{"header":491,"content":492},"What is the connection between DevSecOps and high-performing teams?","DevSecOps platforms streamline workflows, automate security checks, and promote collaboration across development, security, and operations. This improves developer productivity and creates an environment conducive to high performance.",{"header":494,"content":495},"How can companies scale high-performance team practices?","Once a high-performing team is established, its processes and cultural habits can be shared as templates for others. This multiplier effect helps embed a culture of excellence across the engineering organization.","high-performing-development-teams-your-business-advantage","content:en-us:the-source:platform:high-performing-development-teams-your-business-advantage:index.yml","en-us/the-source/platform/high-performing-development-teams-your-business-advantage/index.yml","en-us/the-source/platform/high-performing-development-teams-your-business-advantage/index",{"_path":501,"_dir":459,"_draft":6,"_partial":6,"_locale":7,"config":502,"seo":504,"content":508,"type":452,"slug":537,"category":459,"_id":538,"_type":29,"title":505,"_source":30,"_file":539,"_stem":540,"_extension":33,"date":509,"description":506,"timeToRead":468,"heroImage":507,"keyTakeaways":510,"articleBody":514,"faq":515},"/en-us/the-source/platform/from-toolchain-chaos-to-business-roi-a-5-step-roadmap",{"layout":9,"template":418,"articleType":419,"author":27,"featured":329,"gatedAsset":503,"isHighlighted":6,"authorName":11},"transform-your-software-development",{"title":505,"description":506,"ogImage":507},"From toolchain chaos to business ROI: A 5-step roadmap","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",{"title":505,"date":509,"description":506,"timeToRead":468,"heroImage":507,"keyTakeaways":510,"articleBody":514,"faq":515},"2025-03-11",[511,512,513],"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://about.gitlab.com/the-source/platform/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.",[516,519,522,525,528,531,534],{"header":517,"content":518},"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":520,"content":521},"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":523,"content":524},"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":526,"content":527},"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":529,"content":530},"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":532,"content":533},"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":535,"content":536},"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.","from-toolchain-chaos-to-business-roi-a-5-step-roadmap","content:en-us:the-source:platform:from-toolchain-chaos-to-business-roi-a-5-step-roadmap:index.yml","en-us/the-source/platform/from-toolchain-chaos-to-business-roi-a-5-step-roadmap/index.yml","en-us/the-source/platform/from-toolchain-chaos-to-business-roi-a-5-step-roadmap/index",{"_path":542,"_dir":459,"_draft":6,"_partial":6,"_locale":7,"config":543,"seo":545,"content":549,"type":452,"slug":570,"category":459,"_id":571,"_type":29,"title":546,"_source":30,"_file":572,"_stem":573,"_extension":33,"date":550,"description":547,"timeToRead":551,"heroImage":548,"keyTakeaways":552,"articleBody":556,"faq":557},"/en-us/the-source/platform/driving-business-results-with-platform-engineering",{"layout":9,"template":418,"articleType":419,"author":27,"featured":6,"gatedAsset":544,"isHighlighted":6,"authorName":11},"gitlab-2024-global-devsecops-report",{"title":546,"description":547,"ogImage":548},"Driving business results with platform engineering","Platform engineering accelerates time to market, reduces security risk, and improves developer experience. Learn how to set your DevOps team up for success.","https://res.cloudinary.com/about-gitlab-com/image/upload/v1751463790/xmrjm5ztb49zx5bggima.png",{"title":546,"date":550,"description":547,"timeToRead":551,"heroImage":548,"keyTakeaways":552,"articleBody":556,"faq":557},"2024-10-29","7 min read",[553,554,555],"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/security-compliance/) 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/value-stream-management/) 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.*",[558,561,564,567],{"header":559,"content":560},"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":562,"content":563},"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":565,"content":566},"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":568,"content":569},"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.","driving-business-results-with-platform-engineering","content:en-us:the-source:platform:driving-business-results-with-platform-engineering:index.yml","en-us/the-source/platform/driving-business-results-with-platform-engineering/index.yml","en-us/the-source/platform/driving-business-results-with-platform-engineering/index",[414,457,500,541],{"ai":355,"platform":362,"security":97},1753475369407]