Google Cloud is Google's umbrella brand for its business cloud products. Google Cloud Platform (GCP) is the infrastructure and developer part of it: Compute Engine, Cloud Storage, BigQuery, GKE and the rest. Google has sold everything under the Google Cloud name since 2016, so today "GCP" and "Google Cloud" usually mean the same services, on the same bill.
Key takeaways
- GCP is the older name for Google's infrastructure, data and developer services. Google's own documentation now just calls them "Google Cloud".
- Google Cloud, the brand, launched in September 2016. It covers GCP, Google Workspace (formerly G Suite), Google's AI and machine learning APIs, and the enterprise Maps APIs.
- There is no separate GCP price list or contract model. Compute Engine, Cloud Storage or BigQuery cost the same whichever name you use.
- The GCP label survives in contracts and tooling: Google's terms of service still define "GCP Services", and many job titles, certifications and partner pages use it.
- Google Workspace (Gmail, Docs, Drive, Meet) belongs to the Google Cloud brand but not to GCP. It is licensed per user, while GCP services are billed on usage.
Is GCP the same as Google Cloud?
Mostly, yes. When an engineer says "we run on GCP", they mean the infrastructure services you manage in the Google Cloud console. Google Cloud as a brand is slightly wider, because it also includes Google Workspace and some industry products.
The confusion comes from a rebrand. In September 2016, Google's then cloud chief Diane Greene introduced Google Cloud as one brand. The announcement said it spans "all of Google Cloud Platform", the productivity apps (renamed G Suite at the same time), Google's machine learning tools and APIs, the enterprise Maps APIs, and the Android and Chrome devices that access the cloud. Over the following years Google stopped using "Google Cloud Platform" in most marketing and docs. Its Google Cloud overview for developers no longer mentions GCP at all.
What the names cover
A simple way to keep the terms apart is to ask who uses the service and how it is billed.
| Term | What it covers | How it is billed | Where you still see the name |
|---|---|---|---|
| Google Cloud (brand) | All of Google's business cloud offerings: infrastructure, data and AI services, Google Workspace, Maps Platform and more | Depends on the product | Google's website, docs, events and sales teams |
| GCP (Google Cloud Platform) | Infrastructure, data, AI and developer services: Compute Engine, GKE, Cloud Run, Cloud Storage, Cloud SQL, BigQuery, Vertex AI, networking and security services | Pay for what you use, through a Cloud Billing account, with optional committed use discounts | Contracts ("GCP Services"), job ads, certifications, older docs, third-party tools |
| Google Workspace (formerly G Suite) | Gmail, Calendar, Drive, Docs, Sheets, Meet, Chat | Per-user subscription | Admin console, licence invoices |
Cloud Storage and Cloud SQL are GCP services, not something separate from GCP. And there is no "traditional, pay upfront" GCP pricing model next to a pay-as-you-go Google Cloud model. It is one platform with one pricing approach: on-demand usage, plus discounts if you commit to a level of spend or resources for one or three years.
Why does the GCP name still matter?
Because legal and technical documents change more slowly than marketing. Three places where you will still meet it:
- Contracts. The Google Cloud terms of service still use the defined term "GCP Services" for the infrastructure products, separately from Google Workspace and other services. If you are reviewing a contract or a data processing addendum, check which service group a clause applies to.
- Skills and hiring. Many CVs, job ads and training courses say "GCP". A "GCP engineer" works on infrastructure and data services, not on Gmail or Drive administration.
- Partners and tooling. Monitoring, security and cost tools often label their integration "GCP". It is the same connection to your Google Cloud projects.
How Google Cloud is organised
Whatever you call it, the platform works the same way. According to Google's overview documentation, every resource you create belongs to a project, which acts as a namespace. Each project is linked to one billing account, and several projects can share a billing account. Resources live in geographic regions, and regions are split into zones; some resources, such as persistent disks, can only attach to machines in the same zone.
You manage it through the Google Cloud console, the Google Cloud CLI (gcloud) or client libraries in common programming languages. For a buyer, that means one place to see GCP usage and cost, separate from Workspace licences.
Where Google Workspace fits
Google renamed G Suite to Google Workspace in October 2020. Workspace is part of the Google Cloud business, but it is a software-as-a-service suite, not infrastructure. You buy it per user, you administer it in the Workspace admin console, and it has its own terms.
In practice many organisations use both: Workspace for email and documents, and GCP for applications and data. They can share an identity setup, but the cost, operations and compliance work are separate tracks.
How GCP compares with AWS and Azure naming
The other two large providers have similar layers. Amazon Web Services is both the brand and the platform, while Microsoft separates Azure (infrastructure and platform services) from Microsoft 365 (productivity software). GCP lines up with AWS and Azure; Google Workspace lines up with Microsoft 365. If you are comparing providers, our AWS vs Azure vs GCP comparison looks at services, pricing and support side by side.
Getting started on Google Cloud
Google's free programme currently offers new customers $300 in free credit and a free tier on more than 20 products, such as one e2-micro Compute Engine instance per month and 1 TB of BigQuery queries per month. Free tier limits do not expire but Google says they can change, so check the page before you plan around them.
For production use, set up the basics before workloads arrive: an organisation and folder structure for your projects, billing accounts and budgets, identity and access policies, and a choice of regions that matches your data residency needs. For EU organisations, region choice is usually the first compliance question.
How Opsio helps
Opsio runs Google Cloud environments alongside AWS and Azure for organisations in the Nordics, the EU and India. We help with Google Cloud architecture and setup, migration to Google Cloud, and ongoing operations through our GCP managed services, including 24/7 monitoring, security and cost reviews.
Frequently asked questions
Is GCP Google Cloud?
Yes. GCP is the infrastructure and developer part of Google Cloud. Google now markets those services simply as Google Cloud, but the products, console and pricing are the same.
Is Google Cloud Platform still called GCP?
Informally, yes. Google itself mostly says "Google Cloud", but the term "GCP Services" remains in Google's terms of service, and engineers, recruiters and tool vendors still use GCP every day.
Is Google Workspace part of GCP?
No. Google Workspace (Gmail, Drive, Docs, Meet) is part of the Google Cloud brand, but it is a separate per-user subscription product. GCP covers infrastructure, data and AI services billed on usage.
Is Google Drive part of Google Cloud?
Google Drive for business is part of Google Workspace, which sits under the Google Cloud brand. For storing application data on infrastructure you control, the GCP service is Cloud Storage.
Does GCP cost more or less than Google Cloud?
Neither. They are the same services. What you pay depends on the products you use, the region, your usage and any committed use discounts you sign up for. Google's pricing calculator gives estimates per service.
Related reading
Written By
Country Manager, Sweden
Johan leads Opsio's Sweden operations, driving AI adoption, DevOps transformation, security strategy, and cloud solutioning for Nordic enterprises. With 12+ years in enterprise cloud infrastructure, he has delivered 200+ projects across AWS, Azure, and GCP — specialising in Well-Architected reviews, landing zone design, and multi-cloud strategy.
Editorial standards: This article was written by the cloud practitioner named in the byline above. We revise it when the technology or regulation it covers changes; the dates on this page show the latest update. Opsio maintains editorial independence.