Governance for agentic coding is the missing piece for enterprises that want to industrialize software delivery. Moritz Plassnig, the newly returned CEO of CloudBees, joins Alan Shimel to explain what he saw in five years away and why he came back. Furthermore, he lays out the shift large organizations must make now.

About Moritz Plassnig

Moritz co-founded CodeShip in Europe, joined CloudBees through acquisition and then spent five years at data governance company Immuta. There he watched large language models change how customers work with data. Consequently, the DevOps fire came back and he returned to CloudBees as CEO.

Agentic coding is DevOps's second chance

Everyone knows DevOps is real, but Moritz argues most companies never fully adopted it. As a result, agentic coding is exposing every gap. Builds still run for hours. Tests are flaky. Releases are manual. Meanwhile, an agent that has to wait eight hours for feedback is an expensive agent.

Governance for agentic coding across every tool

Moritz's recipe is direct. Take the rules your company already lives by, such as two-human review on any code change, and bake them into versioned policies. Then, enforce those policies through a central governance engine that works across CloudBees, Jenkins, GitHub, GitLab or whatever tool a team chooses. In short, governance for agentic coding is the layer that unifies the stack.

He then shares a striking data point from a very large bank. The pace of change is now so fast that enterprise buyers plan technology decisions for two to three years, not five or ten. Therefore, standardization is giving way to a curated menu of approved tools, all governed centrally. Explore more DevOps coverage and the latest TechStrong TV interviews.

The next bottleneck is getting to production

If code generation is no longer the constraint, the next bottleneck is getting software into production safely. Alan and Moritz agree that AI scale needs AI-scale governance, or the mismatch becomes a catastrophe. In addition, supply chain risk grows with every automated step. Governance for agentic coding is what makes the whole pipeline defensible.