If you run a UK SMB and you have a website, an internal tool, or any custom software, you have a hosting decision to make. That decision is usually made once, badly, by accident, when the original developer recommended whatever they were comfortable with.
Three years later, the bills are out of control, the application is slow, or the server has fallen over twice this quarter. Someone asks "should we move to the cloud?" and the conversation gets confusing, because "the cloud" means at least four different things depending on who is talking.
This post is the plain-English version. Three hosting tiers exist for SMB applications. Each one wins in a specific scenario. Most UK SMBs are paying for the wrong tier.
The three tiers, in one paragraph each
Shared hosting and serverless platforms. A cheap or free environment where many websites run on the same underlying machine, sharing resources. Your site is one of hundreds. Performance and uptime depend on what your neighbours are doing. Examples: GoDaddy, Bluehost, 123 Reg, Vercel, Netlify, Cloudflare Pages. Costs from £0 to about £30 a month for a small site.
Managed VPS. A dedicated virtual server that is yours alone. You get a real Linux box (virtually), with predictable resources, real isolation, and someone watching the box on your behalf. The "managed" part means somebody else is responsible for patches, backups, monitoring, and incident response. Costs roughly £100 to £300 a month for a small SMB application, depending on capacity.
Full cloud. Running on AWS, Google Cloud, or Azure with autoscaling, regional failover, complex networking, and a per-second billing model. Designed for large applications with unpredictable load. Costs anywhere from £200 a month for a small workload to many thousands for serious traffic. The complexity is real and so is the bill.
There is a fourth tier (running your own physical server in a rack somewhere) that almost no UK SMB should be choosing in 2026. We will skip it.
When shared / serverless wins
You should be on shared or serverless hosting if your application is one of these:
- A static brochure website. The pages do not change between visitors. Vercel or Netlify run static sites for free or close to it, with global CDN, fast loads, and zero maintenance.
- A simple Next.js or React marketing site. Same logic. The site is almost entirely static, with maybe a contact form.
- A WordPress blog with light traffic. Shared hosting is genuinely fine if traffic is under a few thousand visits a month.
- A small e-commerce site that runs entirely inside Shopify or Squarespace.
If your application is in this list, do not pay for a managed VPS. The bureau will tell you that at the triage. Vercel handles a marketing site better than any custom server setup, costs less, and removes all the operational work.
When a managed VPS wins
You should be on a managed VPS if your application is one of these:
- A custom web application with a database. The kind of thing the bureau builds: an internal tool, a customer portal, a bespoke business application.
- An automation pipeline running on a schedule. A Python script that runs every night, an integration that processes events all day, a job queue handling work in the background.
- A site or service that needs predictable performance. Where slow or erratic response times directly hurt the business and shared hosting's "you might get good performance, you might not" is unacceptable.
- An application where you genuinely need a Linux box and root access. Bespoke configuration, niche software, anything that does not fit the constraints of shared platforms.
For most UK SMB custom applications, this is the right tier. £150 a month for a managed VPS gives you a server that is yours, predictable in cost, and looked after by someone whose job is to look after it. The bureau's managed hosting service sits at this tier.
When the full cloud wins (and when it does not)
You should be on the full cloud (AWS, GCP, Azure) if your application is one of these:
- Highly variable load. Traffic spikes from 100 requests per minute to 10,000 and back. The cloud's autoscaling absorbs the spike; a fixed-size VPS would either struggle during the spike or be vastly oversized for the baseline.
- Geographic distribution requirements. Customers across multiple continents who need low latency in their region. Edge networks and multi-region deployment are genuine cloud strengths.
- Compliance frameworks the cloud providers ship out of the box. Sectors where the regulator wants to see ISO certifications, region locks, immutable audit logs, and the cloud provider's compliance attestations are part of the answer.
- Genuine large scale. Hundreds of thousands of users, terabytes of data, dozens of microservices. Real platforms.
Most UK SMBs are not in any of those situations.
The trap: a developer recommends AWS because it is what they know, the application gets deployed onto a small EC2 instance with an RDS database, and the bill comes in at £400 a month for a workload that would run comfortably on a £150 VPS. The cloud's per-second billing is a feature when usage is variable; it is a tax when usage is steady.
The other trap: the operational complexity. Managing a real cloud deployment requires someone who actually understands IAM roles, VPCs, security groups, autoscaling configs, CloudFront distributions, and the subtle ways AWS bills you for things you forgot you were running. For a UK SMB without a dedicated DevOps person, that complexity costs more than the hosting itself.
How to tell which tier you should be on
A short diagnostic:
1. Is the application mostly static content? If yes, shared or serverless hosting is the answer. Stop paying for more.
2. Does the application have a database, run code that processes events, or need a Linux server you can configure? If yes, you need at least a VPS. Shared hosting will not work.
3. Are you running into performance problems on the VPS that more capacity would not solve? If yes, you might be the rare SMB where cloud's elasticity actually matters. Most "performance problems" turn out to be application-level issues that scaling the box does not fix.
4. Do you have a person on your team whose actual job is managing infrastructure? If no, the full cloud is going to cost you more in operational time than its hosting cost difference saves. Stick with managed VPS where someone else handles the operations.
The "cloud feels more professional" trap
A common pattern: an SMB owner feels like they should be on AWS because that is what serious companies use. They migrate, the application now lives on a more expensive platform, the deployment is harder, the bill is higher, and the application is not measurably better.
What actually happened: they moved from a tier they could afford to manage to a tier they cannot. The complexity is now somebody else's full-time job, and that somebody is either paid (expensive) or absent (the application is now an undermanaged risk).
The bureau's honest take: serious companies use AWS because they have problems AWS solves. UK SMBs usually do not have those problems. A managed VPS at £150 a month is not a downgrade from AWS; it is the right tool for the workload.
How to think about cost realistically
Over five years, on a small custom SMB application:
- Shared / serverless: total cost £0 to £1,800. Realistic for static or near-static sites.
- Managed VPS at £150/month: total cost £9,000 over five years, with someone watching the box and handling all the operational work.
- Full cloud, lightly managed: easily £30,000 over five years for the same workload, and that is before counting the time of whoever has to manage the cloud configuration.
The maths is rarely close, except when the workload genuinely needs cloud capabilities. Most UK SMB workloads do not.
What to do next
If you currently pay for cloud hosting and you are not sure why, the 15-minute triage will tell you in fifteen minutes whether you can move down a tier and save money. The bureau is honest about this; if AWS is genuinely the right tier, that is the answer.
If you are running custom applications on shared hosting and feeling the pain, the managed hosting page covers what the £150/month tier actually includes (provisioning, OS patching, daily backups, uptime monitoring, SLA-backed incident response).
If you are about to commission a custom build and the developer is recommending AWS, the operational audit is the place to challenge that decision before the spend gets locked in. A wrong-tier hosting choice on a new build is a five-year tax. The audit is fixed-fee and the audit fee credits against any build the bureau does afterwards.