Skip to content
Tutorials Center
My learning

Topics

Lesson 4 of 45 Β· Getting Started

Account, Free Tier and Billing Setup

Set up a Google Cloud account safely: free trial vs Always Free, billing accounts, budgets and alert thresholds, with a budget-alert calculator to practice.

To use Google Cloud you need a Google account, a billing account and at least one project. Billing is the part beginners fear, and with good reason: cloud bills can grow quietly. The good news is that Google Cloud offers a free way to learn, and tools that warn you before spending gets out of hand.

This lesson walks through what to expect when signing up, the difference between the free trial and the Always Free tier, how billing accounts relate to projects, and how to create budgets with alerts. Offers, amounts and limits change over time, so always confirm current details on Google's free-program and pricing pages before relying on a number.

Creating the account

  1. Sign in with a Google account (a personal Gmail address works for learning; companies use Google Workspace or Cloud Identity accounts).
  2. Open the Cloud console at console.cloud.google.com and accept the terms.
  3. Activate the free trial if you are eligible. You are asked for a payment method to verify that you are a real person. Google states that you are not charged automatically when a trial ends; you must upgrade yourself.
  4. A first project is often created for you. You will learn how projects work in Projects and the Resource Hierarchy.

Use a separate Google account or a clearly named personal project for practice, so experiments never touch a company's resources.

Free trial vs Always Free

Two different free offers

Free trial Credits for new customers, for a limited time.
Always Free Small monthly usage limits on selected products.

Both have conditions. Read the current terms.

1 / 2

The free trial gives new customers an amount of credit to spend within a fixed period. The Always Free tier does not expire but covers only specific products and small usage amounts, such as a tiny VM in particular regions, a few gigabytes of storage, a monthly allowance of BigQuery queries, and generous request allowances on serverless products. Because the exact products, amounts and regions change, look at the current "Free cloud features" page before you design anything around them. Remember: many products are not covered, and an always-on resource outside the free allowance will cost money.

Billing accounts

A Cloud Billing account is the payment record: it holds the payment method and receives the invoice. Projects do not pay by themselves; each project is linked to a billing account, and the project's usage is charged to it. If a project has no billing account linked, paid services stop working in it.

Common arrangements:

  • One billing account for a hobbyist, linked to a few projects.
  • A company billing account shared by many projects, so finance gets one invoice.
  • Several billing accounts for separate departments or clients.

Billing permissions are separate from project permissions. Roles such as Billing Account Administrator and Billing Account User control who can create or link billing; they are covered in IAM: Principals, Roles and Policies.

Terminal
# List billing accounts you can see, and link one to a project (needs a real account)
gcloud billing accounts list
gcloud billing projects link my-practice-project --billing-account=XXXXXX-XXXXXX-XXXXXX

Budgets and alerts

A budget is an amount you expect to spend over a period, usually a month, for a billing account or a filtered set of projects and services. You attach threshold rules, for example at 50%, 90% and 100% of the budget, and each rule sends an email (or a message to Pub/Sub) when spending crosses it.

The most important fact: a budget alert does not stop spending. By default it only informs you. Alerts are also based on cost data that can arrive with a delay, so a runaway resource may spend more before the email arrives. If you need hard limits, you can build automation that reacts to the budget's Pub/Sub notifications (for instance by disabling billing on a practice project), but that is an advanced step and must be tested carefully because disabling billing stops running services.

Good habits for beginners:

  1. Create a small budget (for example, the amount you are comfortable losing) the first day.
  2. Add several thresholds, including a forecast-based one if offered.
  3. Add a second person's email if the account is shared.
  4. Delete practice projects when finished: deleting the project removes its resources.
  5. Check the billing reports page weekly during the first month.

More tools are in Cost Management and Optimization, and the pitfalls are in Common Mistakes and Troubleshooting.

A stand-in budget-alert calculator

Google's real budgets are configured in the console and checked by Google's systems. The code below is only a model of the arithmetic: given a budget, threshold percentages and daily spending, which alerts fire and on what day? It also projects the month-end cost, similar in spirit to a forecast alert. All amounts are invented.

JS Which budget alerts fire?

Press Run (or Ctrl + Enter) to see the console output here.

No output.

The second half of the month shows why early thresholds matter: by the time spending reaches 100%, the cause has been running for days. The "alert, don't stop" behavior is modelled too, because nothing in the code ever halts the spending.

JS Free allowance vs billed usage

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Check your understanding

Quick check Β· 4 questions

of 4 answered You scored / 4 Β· perfect!

  1. 1. What does a Cloud Billing budget do by default when spending crosses a threshold?

    Budgets inform; they do not cap spending. Stopping resources requires extra automation that you build and test yourself.
  2. 2. How does a project pay for paid services?

    The billing account holds the payment method; each project is linked to one, and its charges go there.
  3. 3. How is the Always Free tier different from the free trial?

    The trial is credit for a limited time; Always Free is a small, ongoing allowance on specific products. Check current terms for details.
  4. 4. Which is the safest way to avoid paying for finished experiments?

    Resources that exist keep costing money (or using allowance). Deleting the project removes the resources inside it.

Summary

  • You need a Google account, a billing account linked to a project, and ideally a payment method verified through the trial.
  • The free trial is time-limited credit; Always Free is a small ongoing allowance on selected products. Terms change, so verify them.
  • Billing accounts hold payment; projects are linked to them, and billing roles are separate from project roles.
  • Budgets send alerts at thresholds but do not stop spending, and cost data may lag.
  • Create a budget on day one and delete practice projects when done.

Next: Projects and the Resource Hierarchy