DevoteamInsightsExpert ViewGoogle Cloud VMware Engine: End of License-Included VCF Nodes After October 2025

Google Cloud VMware Engine: End of License-Included VCF Nodes After October 2025

Author

  • Anis Zekri
    Google Cloud VMware Engine Lead EMEA

Share

Since October 2025, a major turning point has begun for Google Cloud VMware Engine (GCVE) customers. Broadcom is changing the rules of the game, and Google is adapting its offer. Here’s what this means for GCVE customers and the key actions to take before October 15, 2025.

Before Broadcom’s Announcement: a Simple, Integrated Model

Until now, Google Cloud VMware Engine customers could choose between two commercial models:

License-Included GCVE

Google offered an all-in-one package that included:

  • the physical nodes,
  • VMware Cloud Foundation (VCF) licenses,
  • and the fully managed GCVE support.

This model could be purchased:

  • on-demand,
  • or with a Committed Use Discount (CUD) for 1 or 3 years.

GCVE in BYOL Mode (Bring Your Own License)

The customer purchased VMware Cloud Foundation licenses directly from VMware/Broadcom. Google only provided the GCVE infrastructure.
This model offered contractual flexibility but required separate license management.

After Broadcom’s Announcement: a New Paradigm

Broadcom has introduced a global distribution model for VMware Cloud Foundation (VCF) licenses. From now on, hyperscalers (including Google Cloud) will no longer be able to sell integrated VMware licenses.

What changes as of October 15, 2025:

  • Google will no longer sell new “License-Included” nodes. Only the BYOL (Bring Your Own License) model will remain available for new GCVE environments.
  • Customers will have to purchase their VCF licenses directly from Broadcom.
  • GCVE remains a fully managed Google Cloud service — only the licensing model changes.

Official Google Cloud Announcement — October 3, 2025

Impact on CUDs (Committed Use Discounts)

Customers can still subscribe to a CUD (1 or 3 years), but with new rules:

  • 1-Year CUDs remain available for VE1 or VE2, in any region.
  • 3-Year CUDs are now restricted to VE2 nodes, as GCVE ve1 3-year CUDs are end-of-sale
  • Exception: the France region (europe-west9) and Milan region (europe-west8) may still order ve1 3-year CUDs. Since September 29th Google Cloud has adapted the discount rate for ve1 1-year CUDs to be identical to the discount rate for 3-year CUDs:

SKU References:

What This Means for Customers

  • All existing CUDs will be honoured until their term ends, with no service disruption.
  • After October 15, 2025, no new License-Included orders can be placed.
  • Customers can still expand capacity via BYOL, using Broadcom-issued licenses.
  • Those wishing to lock in current pricing can still sign a new CUD before the deadline.
  • Customers can sign a 1-year CUD on ve1 or ve2 in any region, and a 3-year CUD on ve2 or ve1 in Paris/Milan only. And this is completely independent of whether the node has a license or not
  • If the customer signs a 1-year CUD now, it’s essential to note that, after the first year, Google will no longer provide the license.
  • After contract expiration, customers will have two options:
  • Migrate to native Google Cloud services (GCE, GKE, etc.), or
  • Continue with GCVE using the BYOL model.

My Expert Opinion

As a GCVE EMEA Lead at Devoteam and a Google architect, I see this as a natural evolution, not a disruption. Broadcom’s move to centralise VMware licensing is expected; it’s about control and consistency, not limitation.

From Google Cloud’s perspective, GCVE remains fully stable and managed, and this shift does not affect the platform’s reliability or performance. Most importantly, customers lose nothing operationally:

  • Performance, security, and management remain the same.
  • And it is entirely possible to migrate to a new Private Cloud or BYOL model with zero downtime.

In practice:

  • Workloads keep their existing IPs,
  • Only management stack IPs (vCenter, NSX Manager, HCX, etc.) change,
  • Using native migration tools like HCX, the transition can be completely transparent to production.

This is a critical reassurance: continuity of service can be fully maintained during this transition. In the long run, this move will encourage organisations to rethink their strategy:

  • Some will gradually modernise by adopting native Google Cloud services (GCE, GKE, AlloyDB, etc.),
  • Others will consolidate their VMware footprint on GCVE, using BYOL, keeping the best of both worlds.

My Recommendations: 6 Actions to Take

  1. Anticipate now — don’t wait until October 15, 2025. Start planning renewal and migration early.
  2. Sign a CUD before the deadline to secure pricing and extend the license-included model if needed.
  3. Prioritise VE2 nodes for higher performance and longevity (VE1 is end-of-sale).
  4. Evaluate the BYOL model with Broadcom, especially for long-term workloads.
  5. Modernise selectively by moving certain workloads to native Google Cloud services to diversify the architecture.
  6. Work with a certified Google Cloud partner, such as Devoteam, to ensure a smooth, zero-downtime migration and cost optimisation.

Key Takeaways

1

October 15, 2025: End of License-Included node sales.

2

November 1, 2025: Only BYOL licenses via Broadcom will be valid.

3

1-year and 3-year CUDs remain available with the same discount.

4

VE2 recommended for cost stability and performance.

5

BYOL required for all new capacity. • Existing CUDs honoured until their term ends.

6

Zero downtime possible, depending on configuration.