Billing Accounts and How Charges Accrue
A GCP Billing Account holds a payment method (credit card or invoicing for enterprise customers) and is linked to one or more Projects; every resource's usage is metered continuously and rolled up into a daily cost report, with an invoice generated monthly. Most compute and storage resources are billed per-second or per-GB-per-month with a minimum usage floor (e.g., Compute Engine bills a 1-minute minimum), and prices vary by region, machine type, and whether you use on-demand, committed-use, or spot (preemptible) pricing. Understanding that billing is metered continuously — not just when you actively use the Console — is essential, since a forgotten running VM accrues cost 24/7 until it's stopped or deleted.
Cricket analogy: Continuous metering is like a stadium's floodlight electricity bill running the whole time the lights are on, even between overs when no ball is being bowled — you pay for uptime, not just active play.
# Link a project to a billing account
gcloud billing projects link my-gcp-project-id \
--billing-account=012345-6789AB-CDEF01
# View current billing account details
gcloud billing accounts list
# Stop a VM to avoid ongoing compute charges
gcloud compute instances stop my-first-vm --zone=us-central1-aBudgets, Alerts, and Cost Controls
GCP lets you set Budgets on a Billing Account or Project that trigger email alerts at configurable thresholds (e.g., 50%, 90%, 100% of a monthly budget), and you can wire these alerts to Pub/Sub for automated responses like disabling billing or notifying a Slack channel. Budgets are advisory by default — they notify but don't automatically stop spending unless you build that automation yourself, which is a common point of confusion for beginners who assume a budget cap is a hard limit like a prepaid card.
Cricket analogy: A GCP budget alert is like a stadium's crowd capacity warning light that flashes at 90% full — it warns the ground staff, but doesn't automatically lock the gates unless someone acts on it.
To build a true hard stop, pair a Budget alert with a Cloud Function triggered via Pub/Sub that calls the Billing API to disable billing on the project — this is the standard pattern for students and hobbyists who want a guaranteed spending ceiling.
The Free Tier and Free Trial
New GCP customers get a time-limited free trial credit (commonly $300 for 90 days, subject to change) usable across almost any service, separate from the Always Free tier, which provides a fixed monthly allotment of specific resources — such as one e2-micro Compute Engine instance in select US regions, 5 GB-months of Cloud Storage, and 1 GB of BigQuery queries per month — that remains free indefinitely as long as usage stays within those limits, even after the trial ends. Exceeding an Always Free limit doesn't stop the resource; it simply starts billing for the excess usage, so it's important to monitor usage rather than assume you're automatically protected.
Cricket analogy: The Always Free tier is like a stadium offering free general-admission seating for every match indefinitely, but charging for anything beyond that — like premium box seats — the free portion never expires, but extras cost money.
The Always Free tier's regional restrictions matter: an e2-micro instance is only free in specific US regions (e.g., us-west1, us-central1, us-east1). Deploying the same instance type in asia-south1 will be billed even though it looks identical in the Console.
- A Billing Account holds the payment method and links to one or more Projects; usage is metered continuously.
- Most resources bill per-second or per-GB-per-month with a small minimum usage floor.
- Budgets trigger alert emails at configurable thresholds but do not automatically stop spending by default.
- A true spending hard-stop requires wiring a Budget alert to a Cloud Function that disables billing via Pub/Sub.
- The free trial gives a time-limited credit (commonly $300/90 days), separate from the ongoing Always Free tier.
- The Always Free tier provides fixed monthly allotments (like one e2-micro VM) that remain free indefinitely within limits.
- Always Free resources are often region-restricted, and exceeding limits triggers billing rather than blocking usage.
Practice what you learned
1. Does a GCP Budget alert automatically stop resource spending once the threshold is reached?
2. What is the key difference between the free trial credit and the Always Free tier?
3. What happens if you exceed an Always Free tier limit, such as using more than 5 GB-months of Cloud Storage?
4. How is most GCP compute and storage usage billed?
Was this page helpful?
You May Also Like
What Is Google Cloud Platform?
An introduction to Google Cloud Platform, its core service categories, and how it compares to running your own infrastructure.
GCP Resource Hierarchy
How Organizations, Folders, Projects, and resources nest together in GCP, and how IAM policies inherit down this hierarchy.
The GCP Console and gcloud CLI
How to manage Google Cloud resources through the web-based Console, the gcloud command-line tool, and Cloud Shell.