GitLab Inc., the intelligent orchestration platform for DevSecOps, announced new capabilities for the governed software factory, a connected system for moving software from idea to production under an organization's own policies and standards. These new innovations are designed to help organizations ship more AI-generated software to production without taking on more risk or cost.
More than 70 million developers and over 10,000 enterprises innovate on GitLab today. Over the last three months on GitLab, active users of agentic software development grew 200 per cent year over year, while secure repositories grew 100 per cent, user namespaces grew 80 per cent, and CI/CD pipelines grew 40 per cent.
Yet most organizations are running a shadow software factory built from separate tools for coding, issue tracking, source code management, CI/CD pipelines, security, artifact management, and deployment.
These systems have no shared identity, common policy, or a record of how a change was made. That fragmentation slows handoffs, breaks context between stages, and prevents engineering leaders from tracing changes from plan to production or measuring the true impact of their AI investments.
GitLab connects those steps so agents can work within an organization's context, workflows, and guardrails, while creating an evidence chain that records how changes move from intent to production. Together, these capabilities form the foundation of a governed software factory, helping organizations move from intent to production with fewer handoffs, stronger safeguards, and clearer visibility into what AI delivers.
Agentic software development can stall after coding when reviews, tests, security checks, approvals, and deployments require handoffs between people, tools, and stages.
Goal-driven flows in GitLab Duo Agent Platform, powered by /goal in Duo CLI, in headless mode and in Duo Agentic Chat, and the GitLab for Slack app, eliminate waits between handoffs across the software lifecycle.
Custom Flows and flow triggers automate multi-step work under the same identity, policy, and evidence chain. Teams can start and follow the same flows from the tools and channels they already use, under the same identity and policy.
Most software that organizations ship is assembled from open-source packages, base images, and libraries. Builds fail when pipelines assemble the wrong or missing components, and agents multiply that failure rate by publishing packages at machine speed across vendor and project registries that carry their own rules.
