Every CTO Is Asking How to Move Engineering Work to the Cloud

Every engineering leader is circling the same question right now: how do we move some of our engineering work to the cloud? The keyword is some. Talk to a startup and the question changes to all of it. A few months ago startups only wanted background agents, async tasks running while real work stayed local. Now they want every session in the cloud, synchronous work included, no local dev, laptops reduced to review terminals. Enterprises will get there too, starting with a smaller ask, tag an agent in chat and get a pull request back, but the direction is not in doubt.

What slows the enterprise version down is not the tooling. It is the codebase. Running a coding agent in the cloud means cloning your repositories into the environment where the agent executes, and source code is about the most sensitive IP a company owns. For many security teams, shipping it into a vendor's cloud is a non-starter. That constraint does not kill the shift. It dictates its shape: the agents come to the code, running inside the company's own cloud, rather than the code going to the agents. The one external dependency left is model access, and security teams already have an answer for that in the LLM gateways the big clouds provide, dedicated endpoints like Bedrock and Vertex they have vetted and approved.

The buying pattern here is familiar from a decade of data infrastructure. Most teams prefer SaaS because it is less to operate. The same buyer flips to self-hosted the moment their security team requires it. The engineering team picks the product. The security team picks the deployment model. Any platform that only offers one of the two is invisible to half the market.

This is why cloud dev environments are the unlock for the whole agent story. Parallel sessions, background execution, work that continues while humans sleep, none of it happens on a MacBook. The background layer is still underbuilt, and the companies that build it in a form security teams can approve are the ones that will carry enterprises across.

If you lead engineering, stop debating whether this shift happens and start scoping your version of some. Pick the workflows that move to cloud environments this quarter, and start the security conversation now, because it is the longer pole than the technology.