# Google Cloud Launches Self-Managed VMware Cloud Foundation on Bare Metal New deployment model grants customers full root access to VMware stacks on Google Cloud. - **Source:** [InfoQ](https://brifing.si/source/68ac18af-a4f3-4f7c-9c2c-44d4af8f89dd) - **Published:** 2026-11-08 - **Topic:** [technology](https://brifing.si/c/technology) - **Original article:** - **On Brifing:** https://brifing.si/s/682516d3-430c-4e57-a3b4-12c2f6f99656 ## New Self-Managed VMware Option Google Cloud has introduced a self-managed VMware Cloud Foundation solution, allowing customers to run VCF 9.x on dedicated bare metal instances. This offering provides root access across ESXi, vCenter, and NSX environments. It is currently available in 22 regions, positioning Google alongside AWS and Oracle in providing customer-operated VMware infrastructure services. ## Technical Specifications and Hardware The service utilizes z3-highmem-192-highlssd-metal instances, each equipped with 96 physical cores on 4th-generation Intel Xeon processors. These nodes feature 1.5 TB of memory, 72 TB of local NVMe storage, and 200 Gbps networking. This hardware configuration is designed to support demanding enterprise workloads while allowing customers to drive their own patching and upgrades. ## Managed vs. Self-Managed Models Google now offers two distinct models for VMware. The existing VMware Engine remains a Google-managed service running VCF 5.2 with restricted privileges. Conversely, the new self-managed model shifts lifecycle management responsibilities to the customer or their partners, enabling the use of the latest VCF major versions without waiting for provider certification. ## Deployment and Configuration Requirements Provisioning is handled via a VMware solution toolkit, accessible through the console or Terraform. The environment requires specific prerequisites, including VLAN-based networking, an 8896-byte MTU for the VPC, and pre-configured management subnets. Once the VCF Installer appliance is deployed, the customer assumes full control over the entire software stack and its ongoing maintenance. ## Storage and Performance Claims Storage is primarily vSAN on local NVMe, with support for NetApp Volumes as an external datastore. Google claims potential server TCO reductions of up to 40% through NVMe memory tiering and 39% storage TCO savings via vSAN ESA. However, these figures lack specific methodology, and current feedback remains limited to early assessments. ## Industry Context and Competition Google joins a competitive landscape where AWS offers Amazon Elastic VMware Service and Oracle provides customer-controlled vSphere. Microsoft’s Azure VMware Solution remains a fully managed service. This divergence highlights a market split between organizations seeking provider-managed simplicity and those requiring the flexibility to manage their own VMware release cadence and licensing. ## Role of Managed Service Partners Recognizing that many firms lack the internal capacity for 24/7 patching, Google has engaged fifteen launch partners. Companies like Accenture, HCL, IBM, Infosys, TCS, and Wipro offer managed operations on top of the customer-owned stack. This ecosystem allows businesses to retain control while outsourcing the operational burden to specialized third-party service providers. ## Operational Transparency and Future Outlook The initial announcement lacks specific pricing, service level agreements, and a defined migration path from the managed VCF 5.2 service. Google plans to expand availability to more regions in upcoming quarters. Customers are currently directed to account teams or authorized partners to evaluate the suitability of this self-managed model for their infrastructure. ## Sources covering this story - https://www.infoq.com/news/2026/11/google-cloud-self-managed-vmware/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=global — --- _Summary written by Brifing from the original reporting. Copyright in the original article belongs to its publisher; read the full piece at the link above._