Google Cloud account options: the $300 trial, billing accounts and credits

Google Cloud puts resources in projects and money in billing accounts, and keeps the two loosely coupled. It is a good design that confuses almost everyone on first contact, because the credit you were granted is not in the place you are looking.

The structure

• Organisation. Optional, tied to a Cloud Identity or Google Workspace domain. It provides a policy root and central ownership of projects. Personal accounts often have none.
• Folder. Optional grouping inside an organisation, used for policy inheritance.
• Project. The resource container. Every VM, bucket, service account and API enablement belongs to exactly one project. Quotas are mostly here.
• Billing account. The payment relationship. Credits attach here. One billing account can pay for many projects; a project without a linked billing account cannot create billable resources.

So when someone says their credit is missing, the usual answer is that the project they are working in is linked to a different billing account, or to none at all.

The free trial

New billing accounts receive a credit balance valid for a fixed window, commonly quoted as $300 over 90 days. Two properties matter more than the number:

• It is time boxed. Whichever runs out first, the balance or the days, ends the trial. Unused credit does not carry over.
• It has restrictions. Some resources, particularly certain GPU and high vCPU quotas, are unavailable or heavily limited while an account is in trial status. Upgrading to a paid account lifts most of these.

Separately, Google Cloud maintains an always free tier: modest but permanent monthly allowances on a specific list of products and regions. Those continue after the trial ends and are genuinely useful for small always on services.

Quotas live in the project

Compute Engine quotas are enforced per project and per region: total CPUs, CPUs per machine family, in use IP addresses, persistent disk capacity, and separate quotas for each GPU type. New projects start from the defaults, which are conservative.

The consequence is that raising a quota does not travel. A project with 500 CPUs available in europe-west1 tells you nothing about a second project created next week, or about us-central1 in the same project.

Quota increases are requested from IAM and Admin, then Quotas. Requests on billing accounts with payment history are approved faster and larger, which is the same pattern every major cloud follows.

Credits and how they are consumed

Google Cloud credits come in several forms: the free trial credit, programme credits from partner or startup schemes, and commitment or negotiated credits on larger agreements. They apply to the billing account and reduce the invoice for eligible usage.

The usual exclusions apply. Marketplace purchases from third parties, support plan fees and certain premium services frequently sit outside the credit. The specific terms come with the credit itself. The general mechanics across providers are in how cloud credits work.

Billing hygiene worth setting up on day one

1. Create a separate project per environment rather than one project holding everything. Deleting a project is the cleanest way to remove an experiment completely.
2. Set a budget with alerts on the billing account. Budgets are notifications, not caps, so treat them as an early warning.
3. Enable billing export to BigQuery if you will ever need to explain the bill in detail. It is close to free and impossible to backfill.
4. Label resources consistently. Labels are the only reliable way to attribute cost inside a shared project.
5. Restrict who holds the Billing Account Administrator role. It is a powerful one.

Picking the right starting point

• Learning or evaluating. A trial credit account, used against the products you actually want to test rather than the ones that are already free.
• A time boxed project with a known budget. A larger credit balance, with the expiry date checked against your timeline.
• Something continuous and small. A paid billing account plus the always free allowances, with a budget alert.
• GPU or high CPU work. A paid account, because trial restrictions on those quotas are the usual blocker.

For how Google Cloud prices the resources once you are running them, see Google Cloud pricing explained, and for the machine naming, Compute Engine machine types. If you are choosing between platforms, AWS vs Google Cloud covers the practical differences.