VCF license management
To run VMware Cloud Foundation (VCF) software on Google Cloud VMware Engine, you must use Bring Your Own License (BYOL) subscriptions from Broadcom.
For VMware Engine administrators and billing managers, this document covers per-node license calculations and compliance policies following the Broadcom blog post VMware Cloud Foundation: Cloud on your terms.
On-demand (pay-as-you-go) usage with included licenses ends on June 30, 2027. Existing committed use discounts (CUDs) with bundled licenses continue through their full terms. Before your licenses expire, transition to customer-managed BYOL subscriptions to maintain continuous service coverage.
To register and manage license keys in the Google Cloud console, see Register and manage VCF BYOL license keys.
VCF license management lifecycle
Maintaining continuous license coverage across your VMware Engine operations involves a recurring cycle of three stages:
- Usage audit: You review all Cloud Billing account IDs in your organization. This review tracks node counts, core density per node family, vSAN usage, firewall usage, and expiration dates for active CUDs.
- License procurement: You acquire portable VCF licenses from Broadcom that match your total resource consumption in VMware Engine.
- Key registration: You register your VCF license keys with Google Cloud in the Google Cloud console. For step-by-step instructions, see Register a license key.
VCF license calculation model
VMware Engine calculates BYOL requirements for each Cloud Billing account ID. Calculations factor in active core consumption across clusters, existing CUDs, vSAN usage, firewall usage, and registered VCF entitlements.
Transition deadlines depend on your billing model:
- CUDs: When your CUD term expires, transition to customer-managed BYOL subscriptions.
- On-demand (pay-as-you-go): Complete BYOL onboarding before June 30, 2027.
Each node type requires a specific number of licenses based on its CPU core count and storage capacity. You can choose between two licensing options for your environment:
- Option 1 (VCF only): Cover the entire node for both compute and storage by using only VCF core licenses.
- Option 2 (VCF and vSAN): License the base CPU cores by using VCF core licenses, and cover additional storage requirements separately by using standalone vSAN licenses.
The following table lists the VCF and vSAN license requirements for each
VMware Engine node type, including hyperconverged infrastructure (HCI)
and storage-only (-so)
nodes:
| Node type | Option 1: Total VCF core licenses | Option 2: VCF core and vSAN storage licenses |
|---|---|---|
ve1-standard-72 |
36 VCF cores | 36 VCF cores (no extra vSAN needed) |
ve2-mega-128 |
64 VCF cores | 64 VCF cores (no extra vSAN needed) |
ve2-mega-112 |
56 VCF cores | 56 VCF cores (no extra vSAN needed) |
ve2-mega-96 |
48 VCF cores | 48 VCF cores (no extra vSAN needed) |
ve2-mega-80 |
47 VCF cores | 40 VCF cores and 7 TiB vSAN |
ve2-mega-64 |
47 VCF cores | 32 VCF cores and 15 TiB vSAN |
ve2-large-128 |
64 VCF cores | 64 VCF cores (no extra vSAN needed) |
ve2-large-112 |
56 VCF cores | 56 VCF cores (no extra vSAN needed) |
ve2-large-96 |
48 VCF cores | 48 VCF cores (no extra vSAN needed) |
ve2-large-80 |
40 VCF cores | 40 VCF cores (no extra vSAN needed) |
ve2-large-64 |
35 VCF cores | 32 VCF cores and 3 TiB vSAN |
ve2-standard-128 |
64 VCF cores | 64 VCF cores (no extra vSAN needed) |
ve2-standard-112 |
56 VCF cores | 56 VCF cores (no extra vSAN needed) |
ve2-standard-96 |
48 VCF cores | 48 VCF cores (no extra vSAN needed) |
ve2-standard-80 |
40 VCF cores | 40 VCF cores (no extra vSAN needed) |
ve2-standard-64 |
32 VCF cores | 32 VCF cores (no extra vSAN needed) |
ve2-small-128 |
64 VCF cores | 64 VCF cores (no extra vSAN needed) |
ve2-small-112 |
56 VCF cores | 56 VCF cores (no extra vSAN needed) |
ve2-small-96 |
48 VCF cores | 48 VCF cores (no extra vSAN needed) |
ve2-small-80 |
40 VCF cores | 40 VCF cores (no extra vSAN needed) |
ve2-small-64 |
32 VCF cores | 32 VCF cores (no extra vSAN needed) |
ve2-mega-so |
Matches HCI node core licenses in the cluster | Matches Option 2 for the HCI node type in the cluster |
ve2-large-so |
Matches HCI node core licenses in the cluster | Matches Option 2 for the HCI node type in the cluster |
ve2-standard-so |
Matches HCI node core licenses in the cluster | Matches Option 2 for the HCI node type in the cluster |
ve2-small-so |
Matches HCI node core licenses in the cluster | Matches Option 2 for the HCI node type in the cluster |
ve1-standard-so |
Matches HCI node core licenses in the cluster | Matches Option 2 for the HCI node type in the cluster |
Service behavior for noncompliant environments
If your VMware Engine environment doesn't have enough VCF licenses from Broadcom for its operational footprint, then Google Cloud designates the environment as noncompliant under the VMware Engine Service Specific Terms.
Noncompliance results in the following consequences:
- Service disruptions
- Loss of coverage under the VMware Engine Service Level Agreement
- Loss of functionality
- Restricted access to management appliances
- Potential suspension of service
What's next
- Register and manage VCF BYOL license keys
- Review VMware Engine node types
- Learn about VMware Engine committed use discounts
- Review VMware Engine pricing