VCF for platform engineering
VMware Cloud Foundation is being used to build platform engineering experiences that bring cloud-native developer workflows to on-premises environments, with claims of reduced provisioning friction and fewer IT tickets. The framing treats platform engineering as a way to deliver consistent developer experiences across hybrid estates. (x.com)
Platform engineering is moving into the data center, with Broadcom and VMware pitching VMware Cloud Foundation as a self-service layer for developers on premises. (blogs.vmware.com) In a VMware Cloud Foundation blog post published April 10, 2026, Broadcom said the stack can give developers a “platform-to-data” experience on private infrastructure instead of routing routine environment requests through information technology ticket queues. (blogs.vmware.com) The company’s pitch is that VMware Cloud Foundation supplies the infrastructure layer, while Tanzu Platform supplies the application platform layer, so teams can offer cloud-style workflows on hardware they still run themselves. Broadcom described that pairing in a November 6, 2024 Tanzu post about delivering platform as a service on private cloud. (blogs.vmware.com) Platform engineering is the practice of building an internal product for developers: a standard set of templates, services, and guardrails that hides infrastructure setup the way a hotel front desk hides the plumbing. Broadcom’s 2025 “golden path” material framed it as a way to give developers approved defaults instead of bespoke handoffs. (blogs.vmware.com) That matters for companies that kept sensitive workloads in their own facilities even as developers got used to public-cloud speed. Broadcom said VMware Cloud Foundation 9.0, released in June 2025, was designed to give those private-cloud environments a consistent operating model across data centers, managed clouds, hyperscalers, and edge sites. (broadcom.com) The self-service piece is not entirely new. VMware published a “Self-Service Private Cloud” overview before the Broadcom era, and current VMware Cloud Foundation material still describes policy-based governance and out-of-the-box private-cloud services for application teams. (vmware.com) What has changed is the packaging around developers. Broadcom’s April 2026 post tied VMware Cloud Foundation directly to database provisioning, warned that slow approvals can push teams into “shadow information technology,” and argued that platform teams can centralize control while cutting manual requests. (blogs.vmware.com) The technical building blocks are also familiar. Broadcom’s validated “Developer Ready Infrastructure” guidance for VMware Cloud Foundation centers on vSphere with Tanzu, which runs Kubernetes workloads inside the software-defined data center and gives administrators a designed path for a workload domain built for developers. (techdocs.broadcom.com) Tanzu Platform extends that by adding higher-level application services. Broadcom’s product and documentation pages describe Tanzu Platform as a platform-as-a-service offering for Cloud Foundry, Kubernetes operations, build services, and data services such as Postgres, MySQL, RabbitMQ, and Valkey. (blogs.vmware.com) (techdocs.broadcom.com) Broadcom’s claim is straightforward: if internal teams can click to get approved infrastructure and app services, they file fewer tickets and spend less time waiting on operations. The test now is whether enterprises standardize on that model across hybrid estates, or keep mixing public-cloud tooling with older on-premises workflows. (blogs.vmware.com) (broadcom.com)