ESTIMATE · published-list estimate · runs in your browser
Google Cloud Cost Optimization Calculator
Model Google Cloud Committed Use Discounts, rightsizing, persistent disk, and egress savings on list pricing. Published-list estimate only. The math runs in your browser — your numbers never leave this page.
source currentPublished-list scenario. Not your bill, not a quote, not financial advice.verified 2026-09-09 · valid before 2026-10-12view sources ↓
▮ Assumptions
🔒Computed on your device. No accounts, no bill upload, nothing sent to a server or any vendor.
▮ Scenario result
Worked example
Example inputs: a fixed Google Cloud scenario, evaluated by the same engine used by this calculator.
The modeled baseline is $50,837.40/mo; the bounded scenario models $17,220.95/mo in savings and ends at $33,616.45/mo.
Cost classification: Modeled savings
Dominant cost driver: compute ($23,637.40/mo)
Decision rule: Commitment sized to post-rightsize compute. Committing to the original baseline would over-commit ~15% to capacity you're removing — binding for the term.
Scope / sensitivity: rightsize→storage→egress→commit so commitment is sized to real need. Commitments are binding; rates are representative scenarios, not quotes.
Signal
Result
Scenario monthly cost
$33,616.45/mo
Modeled monthly change
$17,220.95/mo savings
rightsize compute
$3,545.61/mo — compute -15% (applied first)
storage migration
$2,100.00/mo — 30000 GB pd_ssd→pd_balanced
reduce egress
$3,840.00/mo — egress -40% (tiered recompute)
commit:cud 3yr
$7,735.34/mo — 70% of rightsized compute @ ~55% (scenario)
Example inputs only, not a quote or your bill. Static output is generated from the real calculator engine at build date 2026-09-14 and carries the same valid-before boundary 2026-10-12. If source evidence becomes stale or the example contains an unpriced resource, this block suppresses the computed total instead of publishing a confident number.
Decision guidance
Google Cloud cost decisions this calculator can test
This page models Compute Engine, persistent disk, snapshots, network egress, and Committed Use Discount scenarios using representative us-central1 prices. It recomputes tiered meters and applies commitment coverage only after removable capacity has been taken out.
Questions it answers
What Compute Engine baseline remains after rightsizing the current machine mix?
Which persistent-disk or snapshot changes move a real storage meter rather than only changing architecture?
How does lower network egress change the bill after the free allowance and price tiers are recomputed?
When it returns zero or refuses a claim
An unverified machine type or disk product suppresses the total rather than borrowing a neighboring SKU price.
Storage migrations that exceed the source inventory or move to a costlier class are rejected.
Committed Use Discount coverage is applied last; the page warns when the pre-rightsize baseline would create overcommitment risk.
Verify against your invoice
Match machine types, counts, and hours to Cloud Billing export rows for Compute Engine.
Match persistent-disk and snapshot quantities to their billing SKUs rather than estimating from logical volume size alone.
Check network egress destination and tier, then compare CUD coverage with the stable post-rightsize hourly baseline.
The calculator remains a published-list scenario, not a quote or your actual bill. Use the source links and invoice lines below before acting.
Representative published-list prices, re-verified on a freshness schedule. When a rate goes stale or a resource is not in the verified table, the total is suppressed rather than guessed.