Compute

Name: Compute
Brand: Google
Rating: 4.4 (1054 reviews)

Compute is Google Cloud's Infrastructure-as-a-Service offering that runs customizable Linux and Windows virtual machines, provides a broad catalog of machine families and accelerators (GPUs/TPUs), and integrates with Google Cloud networking, IAM, and managed services.

Est 1998|Valuation $4081.3B|Raised $26.1M|2 Ref Customers

LinkedIn 41.9M|Website|Web traffic 3.3M|FTEs 198,933|HQ Mountain View, California, US

MarketsCloud Infrastructure Providers (IaaS/PaaS)Cloud Infrastructure Providers (IaaS/PaaS)

Platform CoversInfrastructure Monitoring Infrastructure as Code (IaC)

01Competitive Landscape

| Aspect | Google Compute Engine | Amazon EC2 | Azure Virtual Machines | |--------|-----------------------|-----------|------------------------| | Starting Price | Usage-based; varies by VM family and region; detailed pricing tables published by the vendor | Usage-based; On-Demand and other purchasing models published by the vendor | Usage-based; VM instance pricing plus separate storage costs for attached disks | | Typical Use Cases | Workloads that benefit from Google Cloud networking characteristics and integration with GCP data/AI services; flexible VM configurations | Broad IaaS ecosystem adoption; organizations standardizing on AWS services and procurement | Microsoft-centric enterprises; workloads that rely on Windows and Active Directory integration | | Key Strengths | Platform security controls at the VM layer (Shielded VMs, OS Login), broad machine catalog, alignment with GCP ecosystem | Large service catalog and mature enterprise adoption; multiple purchasing options and committed-use alternatives | Integration with Microsoft enterprise stack; governance and Windows licensing alignment | | Key Weaknesses | Reported billing complexity and pricing-modeling friction; occasional zone capacity constraints reported by users | Complexity across many offerings and potential variability in GPU/capacity products | Cost optimization can be complex; storage and network add-ons can increase TCO unexpectedly | - Pricing comparison (evidence-backed pointers) - Each provider publishes VM pricing pages and billing model documentation. Organizations should validate pricing-model changes and how those changes apply to the specific instance families and regions under consideration. - Competitor perspectives - Alternative vendors document their pricing models and cost management guidance; procurement teams should compare published pricing details, purchase options, and tooling for cost visibility. - Areas where alternatives may excel - AWS EC2: broader third-party marketplace ecosystem and a larger pool of practitioners with operational experience across regions. - Azure VMs: closer default alignment for Microsoft-first enterprise environments and licensing models. - Areas of differentiation for Compute Engine - VM-layer security controls such as Shielded VMs and OS Login are concrete, configurable controls available at the VM layer.

01Competitive Landscape

Aspect	Google Compute Engine	Amazon EC2	Azure Virtual Machines
Starting Price	Usage-based; varies by VM family and region; detailed pricing tables published by the vendor	Usage-based; On-Demand and other purchasing models published by the vendor	Usage-based; VM instance pricing plus separate storage costs for attached disks
Typical Use Cases	Workloads that benefit from Google Cloud networking characteristics and integration with GCP data/AI services; flexible VM configurations	Broad IaaS ecosystem adoption; organizations standardizing on AWS services and procurement	Microsoft-centric enterprises; workloads that rely on Windows and Active Directory integration
Key Strengths	Platform security controls at the VM layer (Shielded VMs, OS Login), broad machine catalog, alignment with GCP ecosystem	Large service catalog and mature enterprise adoption; multiple purchasing options and committed-use alternatives	Integration with Microsoft enterprise stack; governance and Windows licensing alignment
Key Weaknesses	Reported billing complexity and pricing-modeling friction; occasional zone capacity constraints reported by users	Complexity across many offerings and potential variability in GPU/capacity products	Cost optimization can be complex; storage and network add-ons can increase TCO unexpectedly

Pricing comparison (evidence-backed pointers)
- Each provider publishes VM pricing pages and billing model documentation. Organizations should validate pricing-model changes and how those changes apply to the specific instance families and regions under consideration.
Competitor perspectives
- Alternative vendors document their pricing models and cost management guidance; procurement teams should compare published pricing details, purchase options, and tooling for cost visibility.
Areas where alternatives may excel
- AWS EC2: broader third-party marketplace ecosystem and a larger pool of practitioners with operational experience across regions.
- Azure VMs: closer default alignment for Microsoft-first enterprise environments and licensing models.
Areas of differentiation for Compute Engine
- VM-layer security controls such as Shielded VMs and OS Login are concrete, configurable controls available at the VM layer.

Aspect

Google Compute Engine

Amazon EC2

Azure Virtual Machines

Starting Price

Usage-based; varies by VM family and region; detailed pricing tables published by the vendor

Usage-based; On-Demand and other purchasing models published by the vendor

Usage-based; VM instance pricing plus separate storage costs for attached disks

Typical Use Cases

Workloads that benefit from Google Cloud networking characteristics and integration with GCP data/AI services; flexible VM configurations

Broad IaaS ecosystem adoption; organizations standardizing on AWS services and procurement

Microsoft-centric enterprises; workloads that rely on Windows and Active Directory integration

Key Strengths

Platform security controls at the VM layer (Shielded VMs, OS Login), broad machine catalog, alignment with GCP ecosystem

Large service catalog and mature enterprise adoption; multiple purchasing options and committed-use alternatives

Integration with Microsoft enterprise stack; governance and Windows licensing alignment

Key Weaknesses

Reported billing complexity and pricing-modeling friction; occasional zone capacity constraints reported by users

Complexity across many offerings and potential variability in GPU/capacity products

Cost optimization can be complex; storage and network add-ons can increase TCO unexpectedly