CloudBees just committed to an AI-first pivot. Here’s why it matters for enterprise DevOps teams
The New Stack Chris J. Preimesberger
CloudBees’ new CEO is turning the company into an AI-first shop. Why it matters: enterprises need help handling the flood of machine-written code, not more hype.
Based on reporting by The New Stack, Chris J. Preimesberger — read the original for the full story.
Summary, retelling and take written by AI under human oversight; images are AI-generated illustrations. How we work · Report an error
CloudBees has picked a side. New CEO Mo Plassnig says the enterprise CI/CD company is moving into an AI-first phase, because standing still while generative AI rewrites software creation would be a fast way to fade out.
Plassnig laid out the shift at the WeAreDevelopers Conference in San Jose, California, in a chat with The New Stack podcast. The message from his board was blunt: don’t keep the old plan. CloudBees, he says, has to transform itself to survive a world where machines are producing far more code than before.
This is not just a strategic slogan for him. Plassnig first joined CloudBees eight years ago after the company acquired CodeShip, the DevOps CI/CD startup he co-founded. He later stepped away to work in security, then came back when generative AI lit the fuse again. That return says a lot about where he sees the real opportunity now.
His pitch is aimed less at the online debate around autonomous coding agents and more at the people running large businesses. After spending his first months as CEO talking with Fortune 500 enterprises, large public organizations, and global enterprises, he says the reality on the ground looks very different from the noise online. The hard part is not just adopting AI tools. It is changing process, governance, and security to cope with the output.
That is the crux of it. AI is not merely helping teams write code faster; it is pushing up the volume to a level that existing DevOps habits may not handle cleanly. CloudBees is betting that its future lies in helping enterprises manage that mess, while also reshaping its own identity around the same force.
My take — AI-written commentary, not fact-checked reporting
The sensible read is simple: enterprises do not need more AI theatre, they need guardrails. The open-vs-closed argument matters less than whether the system can survive contact with governance, security, and real workflow pain. Europe would probably call that regulation; most CTOs just call it not getting fired.
Read more about this at: The New Stack