Google Cloud Cost Calculators
Free Google Cloud tools for GKE, Cloud SQL, Cloud Storage, Cloud Run, logging and commitments, counting the charges that matter.
7 free tools · 25 reference pages · no login
Pick by question
- Which Cloud Storage class is cheapest for my bucket?Cloud Storage Class Calculator
- Request-based or instance-based billing for my Cloud Run service?Cloud Run Cost Calculator
- Will a committed use discount save money, or just replace sustained use?GCP Sustained & Committed Use Discount Calculator
- What will my Cloud SQL database cost with HA, replicas and extended support?Cloud SQL True Cost & Upgrade Calculator
- Would GKE Autopilot cost less than my Standard nodes?GKE Cost Check & Autopilot Advisor
- Why is my logging bill so high, and what would cut it?Cloud Logging Cost Calculator
- What is this line on my Google Cloud bill?GCP Billing SKU Dictionary
Tools
Calculator
Cloud Storage Class Calculator
Compare Google Cloud Storage classes on your own data and access pattern, with read and write charges included.
Cloud Run Cost Calculator
Compare the two Cloud Run billing models on your own traffic and see which one costs less each month.
GCP Sustained & Committed Use Discount Calculator
Find out whether a Compute Engine commitment saves money once you count the sustained use discount it replaces.
Cloud SQL True Cost & Upgrade Calculator
Estimate your Cloud SQL bill with availability, replicas, storage and support, then see what delaying an upgrade could cost.
Cloud Logging Cost Calculator
See your log bill on Google Cloud Logging, CloudWatch or Datadog, and what filtering, sampling and shorter retention save.
What drives the cost
Google Cloud prices a few things differently from AWS, and the difference can reverse a decision.
Cloud Storage: reads can outweigh storage
Colder classes cost less to store but more to read. An Archive read costs $0.05 per 1,000 operations, 125 times Standard's $0.0004, plus $0.05 per GiB retrieved. Read much of it back and the lowest rate per gigabyte is often not the cheapest class.
Cloud Run: pick the billing model
Request-based billing charges while an instance starts, serves requests or shuts down, at a higher rate (a third more for CPU in Tier 1) plus a fee per request. Instance-based billing charges every second an instance exists, at the lower rate. The busier each instance, the more instance-based wins.
Compute Engine: discounts do not stack
Sustained use discounts apply only to self-serve (online) billing accounts; invoiced accounts get none. A commitment replaces that discount rather than adding to it, and bills every hour, used or not. Compare it with the price after sustained use.
Cloud SQL: more than the machine
High availability roughly doubles compute and disk for MySQL and PostgreSQL (backups bill once), each read replica is a separate instance, SQL Server adds a license per vCPU (four at least), and versions in extended support pay a fee per vCPU-hour.
GKE: nodes or Pods
Standard bills nodes whether or not Pods use them; Autopilot bills what Pods request, at a higher unit rate. Node capacity that no Pod requests often favors Autopilot; a tightly packed cluster usually does not.
Cloud Logging: each bucket copy is billed
Logging bills each GiB stored in a log bucket (30 days included, 50 GiB free per project), and a second bucket bills it again. VPC Flow, firewall and Cloud NAT logs pay a generation fee too, even when excluded.
Your bill: what each line means
The SKU dictionary starts from the bill: what a line such as "Network Internet Egress from Americas to China" is, what triggers it and how to shrink it. It shows no rates, and each write-up is dated.
Reference libraries
Pages behind these tools, one per column, recipe, pattern or SKU. They are worth reading on their own and they are what the tools above check against.
Other categories
Google Cloud is where this product started.
Finitizer reads your Google Cloud billing export and BigQuery job history directly. It finds the sustained use discounts you already earn, commitments that overlap them, storage classes that do not match how the data is read, and Cloud Run services paying for idle instances.
See how Finitizer works