Independent Research · Unvarnished Reviews
Unvarnished Reviews Research
Amazon Web Services is the market leader with approximately 28% global cloud share (Synergy Research, Q2 2026: AWS 28%, Microsoft 20%, Google 15%), $115 billion in FY2025 revenue, and the broadest service catalog in the category, 200+ services across 38 geographic regions. It is also the most complex to cost-model accurately, the most dependent on FinOps expertise to manage well, and the provider generating the most billing surprise complaints in practitioner communities. Its Trainium3 AI training instances (launched Q1 2026) are 3x faster than Trainium2, repositioning AWS as a credible AI infrastructure competitor to GCP.
Microsoft Azure is the natural choice for Microsoft 365 organizations, where Azure Hybrid Benefit, EA contract bundling, and exclusive OpenAI enterprise access (GPT-5 natively integrated across Azure enterprise services as of Q1 2026) deliver advantages that no independent pricing comparison captures. Azure grew 25% year-over-year in FY2025 and now holds approximately 21% global market share.
Google Cloud Platform grew 28% year-over-year in FY2025, the fastest of the three, and now holds approximately 14% market share, up from 12%. GCP's March 2026 completion of the $32 billion Wiz acquisition, the largest in Google's history, materially changes its enterprise security positioning. Wiz continues to support all major clouds, but its integration into GCP gives Google a cloud security platform with multi-cloud visibility that AWS and Azure cannot replicate natively.
The central finding across all sources: 95% of IT leaders report unexpected cloud charges that disrupted budgets, slowed projects, or restricted operations, according to the Backblaze 2025 survey of enterprise cloud buyers. The published pricing page is the entry point. Egress fees, support tier costs, reserved instance strategy, idle compute, and service sprawl determine 60%-80% of enterprise cloud TCO.
Hyperscale cloud platforms are tracked on G2 per individual service, not as a single unified product the way SaaS tools are. The figures below use each provider's flagship compute service as the most representative comparison point.
| Provider | G2 Rating (Flagship Compute Service) | Reviews (G2) | Trustpilot | Primary Market Segment |
|---|---|---|---|---|
| AWS (Amazon EC2) | 4.6 / 5 | ~1,158-1,177 | No Trustpilot listing located | Small-Business (40.5% of reviews) |
| Azure (Azure Cloud Services) | 4.3 / 5 | ~73 | 1.7 / 5 (60 reviews, Microsoft Azure listing) | Enterprise (48.4% of reviews) |
| GCP (Google Cloud Infrastructure) | 4.3 / 5 | ~15 | No Trustpilot listing located | Mid-Market (46.7% of reviews) |
AWS carries by far the largest review volume, consistent with its market-leading install base and longer service history. Azure and GCP's user review counts on core infrastructure services are thin relative to their real enterprise adoption, most enterprise buyers evaluate these platforms through analyst relationships and proof-of-concept engagements rather than leaving public reviews.
| Provider | Market Share | FY2025 Revenue | Growth Rate |
|---|---|---|---|
| AWS | ~28% | ~$115B | 18% YoY |
| Azure | ~21% | ~$100B | 25% YoY |
| GCP | ~14% | ~$48B | 28% YoY |
AWS is the market leader losing ground in growth rate to both competitors. Azure is gaining share driven by OpenAI exclusivity and Microsoft enterprise relationships. GCP is gaining share fastest, driven by AI workload demand and the Wiz acquisition positioning it as the multicloud security platform.
Multi-cloud adoption hit 89% among enterprises in 2026, up from 76% in 2024. The question for most organizations is no longer which single provider to choose, it is how to allocate workloads intelligently and manage the egress costs that multi-cloud architectures generate.
95% of IT leaders have encountered unexpected cloud charges that disrupted budgets, slowed projects, or restricted operations, Backblaze 2025 survey.
This is not an edge case. It is the defining operational reality of enterprise cloud economics. The charges that produce this finding are consistent across all three providers:
Egress fees, the most impactful hidden cost. Data leaving a cloud provider's network is billable. Data entering is free. This asymmetry is deliberate, it creates switching costs and lock-in while generating revenue that doesn't appear on the headline pricing page.
Current egress rates (June 2026):
CloudZero's 2025 analysis of enterprise cloud bills finds egress fees account for 6%-12% of typical cloud bills, and significantly more for data-heavy workloads. A team serving 75TB per month pays over $6,700 per month in egress fees alone. A media company serving 100TB monthly from AWS S3 faces over $9,000 in monthly egress charges separate from storage costs.
The NAT Gateway double-billing trap. AWS NAT Gateways charge per GB processed in addition to the egress fee on whatever leaves through the gateway. Workloads pulling from public APIs, container registries, or package repositories all flow through these gateways. NAT Gateway processing fees alone can exceed $2,000 per month on accounts that never notice them, and they appear on a separate line item from egress.
Inter-AZ traffic. AWS charges $0.01/GB each direction ($0.02/GB round-trip) for traffic crossing availability zones within the same region. In multi-AZ Kubernetes deployments where service mesh traffic crosses availability zones continuously, inter-AZ fees accumulate significantly and are almost never modeled at architecture design time.
What changed in 2025 on egress:
Google closed its acquisition of Wiz on March 11, 2026, the largest acquisition in Google's history. Wiz is the leading cloud security platform, providing cloud-native application protection across all major cloud environments.
What this means for enterprise buyers:
Wiz continues to support AWS, Azure, GCP, and Oracle Cloud, it is not being made GCP-exclusive. However, integration depth will be deepest on GCP over time. Wiz's AI Application Protection Platform, announced at Google Cloud Next 2026, supports AWS AgentCore, Azure Copilot Studio, Salesforce Agentforce, and Databricks alongside Gemini Enterprise.
The strategic positioning: Google is explicitly marketing GCP as "the multicloud enabler", using Wiz's multi-cloud security roots to appeal to organizations running workloads across multiple clouds who want a single security visibility layer. This is a credible differentiator. AWS and Azure do not have an equivalent multi-cloud security platform with Wiz's breadth and market reputation.
The competitive implication: Organizations evaluating GCP in 2026 should include Wiz integration in the evaluation, it is a meaningful security capability addition that earlier evaluations lacked.
Microsoft integrated GPT-5 natively across Azure enterprise services in Q1 2026, extending its exclusive OpenAI enterprise partnership. For organizations where AI inference on GPT models is a workload, customer service, document processing, code generation, Azure's exclusive access to OpenAI's most capable commercial models is a differentiator.
GCP's Gemini Enterprise and Gemini 3 (launched December 2025) are the primary competition. Google's Ironwood TPU (7th generation, 10x performance improvement over predecessor) and the announced TPU 8 provide GCP with AI hardware infrastructure advantages for model training.
AWS launched Trainium3 instances in Q1 2026, 3x faster than Trainium2 for AI training workloads. Combined with Amazon Bedrock's foundation model marketplace, AWS is repositioning itself as a serious AI infrastructure competitor to GCP's established TPU advantage.
AWS's 200+ services, 38 geographic regions, and the largest community of certified engineers represent infrastructure depth that Azure and GCP have not matched.
AWS leads on:
AWS limitations:
Azure's single most important competitive advantage is the Microsoft enterprise relationship, not a technical capability.
Azure leads on:
Azure limitations:
Google Cloud has built a distinct market position: the platform for data-intensive workloads, AI/ML infrastructure, and, post-Wiz, multi-cloud security.
GCP leads on:
GCP limitations:
It has the broadest catalog, 200 or more services across 38 regions, the largest pool of certified engineers and the deepest partner ecosystem, with Graviton processors delivering 15% to 25% better price and performance than comparable x86 instances.
Its flagship compute service has the largest review base, about 1,158 to 1,177 reviews at 4.6 out of 5.
It has the highest pricing complexity and the most expensive support tiers, with Enterprise On-Ramp at $5,500 a month minimum and Enterprise at $15,000.
Its egress rate of $0.09 per GB is the highest baseline, NAT Gateway and inter-AZ fees add separate line items, and FinOps expertise is effectively mandatory at enterprise scale.
Azure Hybrid Benefit cuts compute costs by up to 80% for organizations with existing Windows Server and SQL Server licenses, and it integrates natively with Microsoft 365, Entra ID and Defender.
Its AKS cluster management is free, Azure Arc is the most mature hybrid management platform, and GPT-5 is natively integrated.
Equivalent compute runs 8% to 10% more than AWS Graviton or GCP instances, and documentation spanning the whole Microsoft stack creates navigation challenges.
Service breadth is thinner than AWS outside Microsoft integration, and its flagship service has a thin review base of about 73 reviews at 4.3 out of 5.
BigQuery is the consensus choice for data warehousing, GKE is rated the most mature managed Kubernetes service, and automatic Sustained Use Discounts of 30% need no commitment.
Reviewers and independent sources rate it the easiest to start with, and its Wiz acquisition adds multi-cloud security visibility.
Its enterprise footprint and partner ecosystem are smaller than AWS's, and Premium support is $12,500 a month minimum or 4% of spend.
Its service catalog is narrower outside AI, data and security, and its flagship service has only about 15 reviews at 4.3 out of 5.
| Provider | On-Demand | 1-Year Committed | 3-Year Committed |
|---|---|---|---|
| AWS (m6a.xlarge) | ~$0.1728/hr | ~40% off | ~60% off |
| Azure (D4s v5) | ~$0.192/hr | ~37% off | ~66% off |
| GCP (n2-standard-4) | ~$0.1906/hr | ~37% off | ~55%-70% off (+ auto SUDs) |
At on-demand, the three providers are within 10% of each other. The real differentiation is in commitment structures and workload-specific pricing:
| Provider | Standard Object Storage | Archive |
|---|---|---|
| AWS S3 Standard | $0.023/GB/month | $0.004/GB/month |
| Azure Blob Hot | $0.018/GB/month | $0.00099/GB/month |
| GCP Cloud Storage Standard | $0.020/GB/month | $0.004/GB/month |
Azure Blob Hot is 22% cheaper than AWS S3 per GB, for organizations storing 1PB, that's $5,000/month cheaper. Azure Archive at $0.00099/GB/month is the cheapest cold storage of the three.
| Provider | Mid-Tier | Enterprise Minimum |
|---|---|---|
| AWS Business | $100/month or ~7% of spend | $15,000/month (Enterprise) |
| Azure Professional Direct | $1,000/month | Custom (Unified ~10% of spend) |
| GCP Enhanced | $500/month or 3% | $12,500/month (Premium) |
For an organization spending $1M/month on cloud, support adds $70,000-$150,000+ annually, a cost almost never included in initial business cases.
For organizations running many Kubernetes clusters, Azure AKS's zero cluster fee is a meaningful cost advantage.
Most enterprises under-model cloud cost growth by 35%-60% over five years. The consistent sources of underestimation:
1. Egress not modeled at architecture design time. Teams choose where to run workloads without calculating the network cost of those choices. The bill arrives monthly, grows with data volume, and is discovered quarterly rather than prevented at design.
2. Support costs not in the initial business case. Business-tier support at $100,000-$250,000+ annually for mid-enterprise deployments appears as a separate line item discovered after deployment.
3. Idle compute is the largest waste category. Forgotten test clusters, overprovisioned reserved instances, idle staging environments, all three providers bill for compute that is provisioned but unused. Switching cloud providers does not solve idle compute.
4. Service sprawl adds cost without central governance. Teams adopt managed databases, caches, queues, and AI services independently. Each addition is individually justified; the cumulative billing impact is discovered at the quarterly review.
5. Data gravity creates compounding egress. As data accumulates in a cloud provider's object storage, the egress cost of analytics, reporting, and inter-service data movement grows. Data gravity is the mechanism that makes multi-cloud strategies expensive and single-cloud exits painful.
Modeled scenario: 50 compute instances (4 vCPU/16GB, 3-year committed pricing), 50TB of standard object storage, 30TB of monthly egress traffic, and mid-tier business support, using the pricing figures published above.
| Cost Component | AWS | Azure | GCP |
|---|---|---|---|
| Compute (3-yr committed, 50 instances) | $90,824 | $85,778 | $87,657 |
| Storage (50TB, 36 months) | $41,400 | $32,400 | $36,000 |
| Egress (30TB/month, 36 months) | $96,876 | $93,960 | $107,640 |
| Support (business tier, 36 months) | $16,037 | $36,000 | $18,000 |
| 3-Year Total | $245,137 | $248,138 | $249,297 |
At this representative mid-size scale, all three providers land within roughly 1.7% of each other on total 3-year cost, close enough that raw price should not be the deciding factor for a workload like this one. Egress is the single largest cost component for all three, roughly 39%-43% of total spend, reinforcing that architecture decisions about data movement matter more than the provider's headline compute rate. This scenario excludes Azure Hybrid Benefit savings for organizations with existing Windows licensing, which can materially shift Azure's total below the other two.
The three providers land within 1.7% of each other on the TCO scenario above, close enough that operational complexity, how much a team has to learn and manage day to day, is often the more decisive factor than raw cost.
| Dimension | AWS | Azure | Google Cloud |
|---|---|---|---|
| Implementation | Independently documented as the most involved of the three; its 200+ service catalog gives it the broadest capability but also the most surface area to configure correctly, teams new to AWS face real setup overhead getting IAM, networking, and service selection right | Independently rated easier for organizations already standardized on Microsoft, with Active Directory and Microsoft 365 integration reducing identity and access setup; organizations without existing Microsoft investment don't get that advantage and face a comparable learning curve to AWS | Fastest and cleanest of the three per nearly every independent source checked for this report; a smaller, more focused service catalog and a consistently praised, simpler console reduce initial setup complexity |
| Admin dependency | Highest of the three; AWS's IAM model provides granular control but independently documented as requiring real expertise to manage securely, and its scale (200+ services) means ongoing governance work grows with adoption breadth | Lower for Microsoft-standardized organizations, since Azure AD and existing enterprise agreements reduce duplicate identity management; independently documented as adding real complexity once an environment extends beyond core Microsoft technologies | Lowest of the three per independent sources; consistent APIs and tooling across on-premises and cloud reduce operational overhead, though this benefit is most pronounced for organizations already comfortable with Google's approach to networking and identity, which differs enough from AWS and Azure to require its own ramp-up |
| Learning curve | Steepest of the three, independently and consistently documented across nearly every source checked for this report; extensive documentation and training resources (AWS Skill Builder) help, but the underlying platform remains the most complex to master | Moderate; independently rated easier than AWS for teams with existing Microsoft familiarity, comparable to AWS for teams without it | Rated easiest to get started with by multiple independent sources, attributed to a cleaner UI and more developer-friendly design, though its distinct approach to networking and identity management still requires real onboarding time even for experienced cloud teams |
The pattern is consistent with each provider's broader positioning. AWS's complexity is the direct cost of its breadth, the same 200+ services that make it the most capable general-purpose platform also make it the hardest to learn and administer well. Azure's complexity is conditional: lower for organizations already inside the Microsoft ecosystem, comparable to AWS for those outside it. Google Cloud's simpler onboarding is real, but it's not simplicity in an absolute sense, its networking and identity model differs enough from the other two that switching to it, not just starting with it, carries its own real learning cost.
Every finding below is independently documented and material enough to influence a purchasing decision.
AWS
|
Azure
|
Google Cloud
|
1. Model egress explicitly, require your architecture team to estimate egress before any major deployment
2. Map NAT Gateway and inter-AZ traffic, the two most commonly missed line items
3. Negotiate support into the initial contract, cheaper than purchasing after go-live
4. Right-size before committing, commit to 70%-80% of expected utilization, not 100%
5. Get the 5-year TCO in writing, the 1-year business case underestimates 5-year cost by 35%-60%
6. For AWS: Evaluate Graviton instances, 15%-25% better price/performance over x86 for most workloads
7. For GCP: Model Sustained Use Discounts against AWS Savings Plans, GCP's automatic model often wins for variable workloads
8. For Azure: Calculate Azure Hybrid Benefit before any compute comparison, the savings can be decisive
AWS is designed for breadth, and its complexity is the direct cost of that breadth: the most involved implementation, the highest admin dependency, and the steepest learning curve. Azure is designed around the Microsoft ecosystem, so its complexity is lower for Microsoft-standardized organizations and comparable to AWS for those outside it. Google Cloud is designed for clarity and data, rated the easiest to start with, though its networking and identity model differs enough to need a ramp-up.
Choose by existing investment and workload. AWS fits teams with deep AWS expertise that need the broadest services. Azure fits Microsoft-stack enterprises, hybrid architectures, and OpenAI workloads. Google Cloud fits analytics, AI/ML, Kubernetes, and multi-cloud security priorities. With multi-cloud adoption at 89% of enterprises, many buyers will split workloads across providers.
Raw compute prices sit within about 10% of each other, so price is decided elsewhere. Azure Hybrid Benefit can cut Windows compute costs by up to 80%, GCP's automatic Sustained Use Discounts reward unpredictable workloads, and AWS carries the most expensive support tiers and the steepest FinOps requirement. Egress, NAT Gateway fees, inter-AZ traffic, support, and idle compute make up the costs enterprises under-model by 35%-60% over five years.
Free trials and test-drives. AWS offers a Free Plan for up to six months with $100 in credits and up to $100 more for exploring services, plus 30-plus always-free services within monthly limits. Azure offers a $200 credit for 30 days, 12 months of free services for new customers and 65-plus always-free services, and it requires a card. Google Cloud offers a $300 credit over 90 days with a card required, plus a Free Tier of 20-plus products that has no end date. All three free offers suit testing a workload, not pricing a production estate, so model egress and support costs against a real quote.