Google CloudGoogle Cloud VMware EngineCompute

`google_vmwareengine_cluster` cost estimation

A dedicated VMware vSphere cluster running on Google Cloud. Priced per ESXi node-hour, with a multi-node minimum that makes this one of the largest standing costs.

A google_vmwareengine_cluster provisions dedicated, bare-metal ESXi nodes running a full VMware Cloud Foundation stack (vSphere, vSAN, NSX) inside Google Cloud, used to lift VMware workloads to the cloud without re-platforming. It is among the most expensive single resources you can declare, because it provisions dedicated hardware with a node minimum.

Each ESXi node bills per hour at a high rate, around $8/node-hour for a ve2-standard-72 (about $5,860/month per node), and a standard production cluster has a three-node minimum. So a minimal cluster is roughly $17,500/month on-demand. Committed 1- and 3-year terms cut the node rate substantially and are how most production deployments are priced. Storage (vSAN) and networking are included in the node cost.

c3x reads node_count and prices node-hours at 730 hours/month at the on-demand rate. Given the magnitude, this is a resource where seeing the number before apply genuinely matters, an accidental extra node is ~$5,860/month. Commitments are modelled via purchaseOption in c3x-usage.yml.

Terraform example

A minimal but realistic configuration that C3X can estimate.

resource "google_vmwareengine_cluster" "prod" {
  name       = "prod-cluster"
  parent     = google_vmwareengine_private_cloud.pc.id
  node_type_configs {
    node_type_id = "standard-72"
    node_count   = 3
  }
}

Pricing dimensions

What you actually pay for when you provision google_vmwareengine_cluster.

Dimension	Unit	What's being charged
ESXi node hours	per node-hour	Per-node hourly rate for the bare-metal ESXi hosts. Three-node minimum for standard clusters. c3x assumes 730 hours/month. ~$8.03/node-hour (ve2-standard-72, ~$5,860/month)
Commitment discount	1-year / 3-year	Committed-use terms cut the node rate significantly versus on-demand. Most production clusters run committed.

Sample C3X output

Example output from c3x estimate (3-node minimum cluster, on-demand):

google_vmwareengine_cluster.prod
└─ ESXi nodes (standard-72 x 3)   2,190  node-hours    $17,585.70

OVERALL TOTAL                                         $17,585.70

Optimization tips

Common ways to reduce google_vmwareengine_cluster cost without changing the workload.

Commit for 1 or 3 years on production clusters

Large (commitment discount)

On-demand node rates are the most expensive way to run VMware Engine. A 1- or 3-year commitment cuts the per-node rate substantially. Production clusters are steady, making commitments the default choice.

Right-size node count to real capacity need

~$5,860/month per node

Each node is ~$5,860/month on-demand. Scale the cluster to actual vSphere resource demand plus failover headroom (N+1), not a round number. One excess node is a major line.

Re-platform candidates off VMware where feasible

Workload-dependent (often large)

VMware Engine is for workloads that must stay on vSphere. Anything that can move to native GKE or Compute Engine usually runs far cheaper. Estimate the native alternative for migratable workloads.

FAQ

How does c3x estimate VMware Engine cost?

It reads node_count and prices ESXi node-hours at 730 hours/month at the on-demand node rate. Commitments are modelled via purchaseOption in c3x-usage.yml. Storage and networking are included in the node cost.

Why is the minimum cost so high?

VMware Engine provisions dedicated bare-metal ESXi hosts with a three-node minimum for standard clusters. At ~$5,860/node-month on-demand, a minimal cluster is roughly $17,500/month.

Is storage billed separately?

No. vSAN storage and NSX networking are included in the per-node price. The node count is effectively the entire cost driver.

How much do commitments save?

Substantially. 1-year and 3-year committed-use terms cut the per-node rate well below on-demand. Because production VMware clusters run continuously, commitments are the standard pricing path.

When should I avoid VMware Engine?

When the workload doesn't actually require vSphere. Re-platforming to native Compute Engine or GKE is usually far cheaper. VMware Engine earns its cost only for lift-and-shift of genuine VMware dependencies.