Today, I am stepping in as CEO of CloudBees. You should hear what that means directly from me, because you are the reason it means anything at all.
I have spent my career building tools developers actually want to use. Years ago, I started a company called Codeship. At Codeship, we relentlessly focused on great developer experience. CloudBees believed in what we were building and acquired the company in 2018. So I am not new to this company, and I am certainly not new to the belief at the heart of it: that software should be easier and safer to ship, and that you should never be forced to choose between the two.
That belief matters more today than ever.
Historically, writing code was always the bottleneck. But writing code is a means to an end. You are doing it to solve a problem, help a customer, delight a user, and ultimately to make your business successful. We weren’t limited by ideas, but by how much we could architect, design and build. This is changing. Software development is being “industrialized”. We are moving from a world where every line of code matters to a future where outcomes matter more than ever. Yet, we are not ready for this new world. The systems designed to build, test, and release software already struggled with human scale. Now, in the era of agentic coding, they need to fundamentally change. This does not mean that craftsmanship doesn’t exist in the era of AI. It just moves up the stack. Agents may perform the work, but humans define the objectives and constraints. We won’t move to fully autonomous agents overnight, but there’s no doubt in my mind that the end-to-end process will increasingly resemble a high-tech factory, instead of a manual assembly line.
Let me be clear about what we will and will not do as part of this transformation.
Enterprise Jenkins is what made CloudBees successful. It remains core to our product offering. We will continue to invest in it and support you and our many other customers, because we understand it remains fundamental to your operational reality today. We also learned from our two decades of working on Jenkins. Its ideals are integral to how we build all our products: open and flexible.
We will not ask you to abandon the tools your teams rely on and migrate onto ours. I don’t believe consolidating your stack to a single vendor is wise or necessary. Flexibility and choice are more important than ever, especially when you look at how quickly the models are evolving. Two years ago, GitHub Copilot was seen as the future. At the end of 2025, Claude Code was taking the world by storm. Over the last few months, Codex has improved significantly. Just last weekend, the US Government directed Anthropic to suspend all access to Fable 5 and Mythos 5 by any foreign national. Innovation and protectionism are moving too fast to bet on a single vendor or workflow. Organizations need the freedom to adopt the latest AI coding tools and engineering platforms as they emerge, alongside a governance layer that provides visibility, control, and compliance across the entire toolchain.
That’s our promise to you. We will give you one place to see, govern, and control how software gets built, secured, and released across every tool in your stack, not just the ones with our name on them. In this new world, what matters more than ever is that you know a code change is well-tested, secure, compliant but most importantly, delivering the intended business impact and customer value. Finally, we can close the full loop from customer feedback and the intent of writing code in the first place, to code being delivered and running in production. Your developers ship faster. Your security and compliance leaders keep their control. Neither side has to lose for the other to win.
CloudBees has earned the trust of some of the most demanding engineering organizations in the world. I do not take that lightly. There is real work ahead, and I am genuinely energized to do it alongside you.
I would love to talk with you directly about how you are building with agents. Please reach out to me and I will make time.
Thank you for betting on us. Let’s build what comes next together.
Moritz Plassnig
CEO, CloudBees
