Google Cloud has a structure that is simple once you see it and confusing until you do. Identity, billing and resources are three separate objects, joined by links you can change. Credits live in one place, quotas in another, and resources in a third. This article explains each layer and how the options on the Buy Google Cloud Account page map onto them.
The layers, from identity to resources
- Google identity. A personal Google account or a Cloud Identity / Google Workspace account used to sign in to the console.
- Organization (optional). The top-level node for companies using Workspace or Cloud Identity. Individual developers often have no organization at all.
- Cloud Billing account. The payment profile. It can be self-serve, funded by a card, or invoiced.
- Projects. The containers that hold resources: virtual machines, buckets, Kubernetes clusters, Vertex AI endpoints.
The key relationship is the link between a project and a billing account. A project with no active billing link cannot run most billable resources, and resources are shut down once any trial period ends. For the generic version of this model, see how cloud accounts work.
Projects: where resources and quotas live
A project is the working unit of Google Cloud. APIs are enabled per project, IAM roles are granted per project, and most quotas are applied at the project or region level. Compute Engine CPU and GPU quotas, and certain AI-related quotas, are the ones that most often need an increase request on a new setup.
Because quotas are project-scoped, a listing that mentions raised limits should tell you which project carries them. Ask for an export from the Quotas page of that specific project rather than a general statement about the account.
Billing accounts: where credits and payment live
The Cloud Billing account is the object that pays. Credits, whether from the Free Trial welcome credit, a startup program award or a partner allocation, are attached to the billing account and applied against eligible usage from every project linked to it.
This is why the listed Google Cloud options are best understood as billing accounts with a balance. The Google Cloud Prepaid $300 Credit Account ($70) matches the size of Google’s standard welcome credit for new users. The larger tiers, the Google Cloud $1K Credit Account ($220), $5K Credit Account ($950), $10K Credit Account ($1800) and $25K Credit Account ($4000), describe billing accounts with progressively larger balances. Planning around each is covered in Google Cloud prepaid and credit accounts.
Linking projects to a billing account
One billing account can fund many projects, and a project can be moved from one billing account to another by someone with the right roles on both. This flexibility is useful:
- An agency can keep one billing account per client and link each client’s projects to it.
- A team can run dev, staging and production as separate projects under one billing account and still see cost per project.
- A project can be relinked to a paid billing account when a trial billing account is exhausted, keeping resources intact.
The billing console breaks cost down by project and by SKU, and labels on resources add a second dimension. The approach in tagging and cost allocation works well on Google Cloud because the project already provides a coarse boundary before you add labels.
Which layer answers which question
| Question | Where to look |
|---|---|
| How much credit is left? | Billing account |
| Can I launch a GPU VM in this region? | Project quotas |
| Who can create resources? | Project IAM (or organization IAM) |
| Which card is charged? | Billing account payment profile |
Free Trial billing and the upgrade step
New users who have never paid Google Cloud, Google Maps Platform or Firebase are commonly eligible for the Free Trial, which provides a welcome credit spendable on eligible products over a limited window. During the trial the linked payment method is not charged for covered usage. After the credit is used or the window closes, the billing account must be upgraded to a paid account to keep resources running.
An upgraded billing account is therefore a meaningful attribute of any listing. Ask whether the billing account has already been upgraded to paid status, since that changes how remaining credit and future charges behave.
What this means for securing an account
Because identity, billing and projects are separate, securing an account after a change of control has three parts. Update recovery options and enable multi-factor authentication on the Google identity. Review who holds Billing Account Administrator roles on the billing account. Then audit IAM roles, service accounts and keys on every project, rotating anything you did not create. Google Cloud accounts and billing accounts are intended for the party that created them, so read the current terms and confirm the account came from legitimate channels. Shorter answers are collected in the Google Cloud section of the Cloud FAQ.
