· published-list estimate · runs in your browser
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.
Computed on your device. No accounts, no bill upload, nothing sent to a server or any vendor.
Monitoring is a separate line item. Use the Datadog pricing calculator to model log, metric, trace, RUM and synthetic-check usage before comparing monitoring plans. Published-list scenarios are not an invoice or vendor quote.
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.
| 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-10-13 and carries the same valid-before boundary 2026-10-25. 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
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.
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 or clearly labeled assumptions, 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.