Google Cloud's decision to hand VMware lifecycle control back to its customers on bare metal is a quiet admission that not everyone wants a babysitter for their infrastructure. The new self-managed VMware Cloud Foundation 9.x offering runs on dedicated Z3 bare metal with root access across ESXi, vCenter, and NSX in 22 regions, sitting beside the existing Google-managed VMware Engine. This mirrors what AWS and Oracle already offer, but it carries a specific message: Google is willing to let you own the patching, the licensing, and the operational risk, provided you want that control. For teams that have been frustrated by the rigidity of fully managed services, this is a direct invitation to take the wheel.
What makes this move worth watching is how it reframes the relationship between cloud providers and their users. Compare it to what we saw with Explore How GitLab 19.5 Brings Governed AI Agents Into Your Workflow. GitLab is pushing agentic software development into the hands of developers while layering governance on top, control with guardrails. Google Cloud is doing something similar here, but in reverse: they are giving you the keys to the infrastructure stack and saying, "You handle the lifecycle, we handle the metal." The practical upshot is that organizations with mature VMware operations can now run their existing Broadcom-licensed environments on Google's hardware without the overhead of a managed layer they never asked for. That is not a trivial option when you consider how many enterprises have spent years tuning their vSphere deployments.
There is also a direct tension here with the approach we saw from AWS Debuts Continuum to Automate Code Fixes and Prove Exploitability. AWS is automating vulnerability remediation to take work off your plate; Google Cloud is handing patching responsibility back to you for your VMware stack. Neither is wrong, but they reflect different philosophies about where autonomy belongs. The self-managed VMware option assumes you have the operational maturity to handle your own patching and upgrades. If you do, you avoid the premium that comes with Google's managed engine. If you do not, the managed option still exists. The choice is yours, and that is the point.
The specific takeaway here is straightforward: if your organization runs VMware at scale and has the in-house expertise to manage lifecycle and licensing, this offering likely saves you money and gives you back control over your upgrade cadence. The open question is whether Google will extend this model to other workloads. For now, the self-managed VMware path is a concrete alternative to the fully managed default, and it signals that Google understands not every customer wants a black box. Watch how quickly the 22-region footprint expands, because that will tell you how strong the demand really is.