Choosing between AWS, Azure and Google Cloud is less about which one is "best" and more about which one fits the shape of your business. A three-person studio running a dozen client WordPress sites has very different needs from a fintech startup with an audited infrastructure. Cost is where small teams get caught out, because the headline price per hour is rarely the number that lands on the invoice. What follows is a practical comparison of pricing, UK regions and support, written for teams without a dedicated cloud architect on the payroll.
What actually drives your monthly bill
Compute is the easy part to compare. All three providers sell virtual machines by the hour or second, with discounts for committing to a year or three. The bill rarely goes wrong there. It goes wrong in the parts nobody models on day one.
- Data egress. Moving data out to the internet, or between regions, is charged. Inbound is usually free. A site with heavy video or large file downloads can spend more on egress than on the servers themselves.
- Managed services. A managed database, queue or search service is convenient, but each one has its own pricing model and its own minimums.
- Storage operations. You pay for capacity, and often per thousand read or write requests. A badly written loop hitting object storage can quietly rack up charges.
- Logging and monitoring. Log ingestion is billed in most setups, and verbose debug logging left switched on is a common source of waste.
- Non-production environments. Staging, a preview environment per pull request, a forgotten test cluster. They all run all month.
- Support. The tier that gives you a real response time when production is down is a paid add-on.
UK regions: where your data actually sits
All three providers have UK regions, which matters if you work with clients in regulated sectors or have promised data residency in your contracts.
- AWS runs its London region as eu-west-2, with Ireland (eu-west-1) as the nearest neighbour.
- Azure has two UK regions: UK South, near London, and UK West, in South Wales.
- Google Cloud serves the UK from europe-west2 in London.
The catch is that a UK region does not guarantee every service is available there. Newer managed services often launch in the United States first, and some never reach smaller regions. If a specific service matters to your architecture, check its regional availability before you plan around it. Latency is the smaller issue: for a brochure site or a business application, the difference between London and Ireland is imperceptible to users. For real-time trading or gaming, it is not.
How the three pricing models differ
AWS
The most granular and, frankly, the most complicated. Savings Plans and Reserved Instances cut the cost of steady workloads, Spot instances suit batch jobs, and almost every service has several pricing tiers. That flexibility rewards teams who will actually tune it, and punishes those who will not.
Azure
Broadly comparable to AWS on compute. The standout saving for small UK businesses is Azure Hybrid Benefit: if you already own Windows Server or SQL Server licences with Software Assurance, you can apply them to Azure rather than paying for that licence twice. Some Microsoft developer subscriptions also include a monthly Azure credit. If you are a Microsoft shop, the effective discount can outweigh any headline price difference.
Google Cloud
Generally the simplest to reason about. Sustained use discounts apply automatically to VMs that run for most of a month, with committed use discounts on top for longer commitments. There is less to configure, which reduces the chance of an expensive mistake.
On all three, egress pricing changes periodically and free allowances come and go. Check the current pricing page rather than a blog post from three years ago.
Support: the line item small teams forget
Free support tiers on all three clouds generally cover billing and account issues, not technical problems. If your production database goes down at 2am, free support will not help you.
Paid tiers differ in shape rather than principle. AWS charges a percentage of your monthly spend, with a minimum, so the cost scales as you grow. Azure and Google Cloud offer flat monthly fees for their mid-tier plans, which is easier to budget when usage is small but growing quickly. Below the enterprise tiers, expect response-time commitments measured in hours rather than minutes, and check whether you get a named contact or a queue.
For most small teams, one paid tier below enterprise level is the right answer. It costs less than an hour of a consultant's time each month, and it means someone is contractually obliged to answer.
A sensible way to compare them
- List your workloads honestly. Two web servers, a managed database, object storage for uploads, a CDN. Not "a scalable microservices platform" if that is not what you run.
- Price the same architecture three times. Each provider publishes a pricing calculator. Enter identical specifications in all three, in a UK region.
- Add egress and support. These are the two lines that most often flip the result.
- Check your dependencies. Confirm the services you rely on exist in your chosen region, and understand how each one is charged.
- Run a two-week pilot. Deploy something small and real, then read the bill carefully. Actual usage teaches you more than any calculator.
Making the call
If your team already lives in Microsoft tooling, Azure is usually the cheapest to operate once licence benefits and existing skills are counted. If you are building data-heavy or Kubernetes-based products and want predictable pricing, Google Cloud is the least fiddly. AWS has the widest ecosystem, the most third-party tooling and the deepest hiring pool, which matters when you need to bring someone in.
Two closing thoughts. The provider your developers already know is almost always cheaper than the one with a marginally lower list price, because mistakes and slow work cost more than compute. And resist multi-cloud for its own sake: a small team running one cloud well will spend less than the same team running two adequately.
Cloud spend is an operating cost, and if you are VAT-registered it is worth asking your accountant how each provider invoices UK VAT, since the timing affects cash flow.
Photo: panumas nikhomkhai / Pexels
