Hosting, Decoded: A Jargon-Free Guide to What Your Hosting Partner Actually Does
You don’t need to speak fluent server to make good decisions about your hosting, but you do need to know the right questions to ask. From uptime and auto-scaling to patching and private LLMs, here’s our plain-English guide to the hosting terms you’ll hear most, and what each one actually means for your business.
By Maddi Nuttall
You don't need to speak fluent server to make good decisions about your hosting. But you do need to know enough to ask the right questions.
Hosting is full of acronyms and buzzwords, and it's easy to nod along without knowing what you're paying for. That matters, because your hosting decides how fast your site loads, how well it copes on your busiest day, and how quickly you recover when something goes wrong.
So here's our plain-English guide to the terms you'll hear most, and what each one actually means for your business.
Hosting basics
Managed hosting
With managed hosting, your provider looks after the servers for you: updates, security, monitoring and fixing things when they break. You focus on running your business, not on keeping the lights on.
Why it matters: Unmanaged hosting is cheaper on paper, but someone still has to do the work. Usually that's your developer, at developer rates, at 2am.
Uptime
Uptime is the percentage of time your site is online and working. Most providers quote something like 99.9%.
Why it matters: 99.9% sounds close to perfect, but it still allows almost nine hours of downtime a year. If those hours land on Black Friday, that's a very expensive 0.1%.
CDN (content delivery network)
A CDN stores copies of your site's images, scripts and pages on servers around the world. Visitors are served from whichever location is nearest to them.
Why it matters: Faster pages mean better search rankings and fewer abandoned baskets, especially if you sell internationally.
SSL certificate
An SSL certificate is what puts the padlock in your browser bar. It encrypts the data travelling between your site and your visitors, such as passwords and payment details.
Why it matters: Without one, browsers warn visitors your site is "not secure". Few people will check out after seeing that.
Staging environment
A staging environment is a private copy of your live site where you can test changes, updates and new features before customers see them.
Why it matters: It's the difference between finding a bug in testing and finding it when orders stop coming in.
Cloud and infrastructure
AWS (Amazon Web Services)
AWS is Amazon's cloud platform. Instead of renting one fixed server, you draw on a huge pool of computing power and pay for what you use.
Why it matters: AWS is incredibly powerful, but it isn't simple. Without someone managing it properly, costs can creep up quietly and settings can be left less secure than they should be.
Auto-scaling
Auto-scaling means your hosting automatically adds capacity when traffic spikes, then scales back down when things quieten.
Why it matters: You get the power you need for a sale or a viral moment, without paying for peak capacity all year round.
Microservices
A microservice architecture splits a platform into small, independent parts, such as search, checkout and stock, rather than one big application.
Why it matters: Each part can scale on its own, and if one part has a problem it doesn't take the whole site down with it. We used this approach for I Want Fabric's platform.
Load balancer
A load balancer is a traffic controller. It spreads incoming visitors across several servers so no single one gets overwhelmed.
Why it matters: It keeps your site fast under pressure, and if one server fails, traffic simply flows to the others.
Security
Patching
Patching means applying security fixes to the software your site runs on, such as PHP, Magento or WordPress, as soon as they're released.
Why it matters: When a vulnerability is announced, attackers start looking for unpatched sites within hours. It isn't glamorous work, but speed is everything. When a critical PHP vulnerability landed recently, our team patched every site across our clients' servers in a day. One client told us that when their own customers got in touch worried, they could say it was already handled.
DDoS attack
A DDoS (distributed denial of service) attack floods your site with fake traffic from thousands of sources, aiming to knock it offline.
Why it matters: Good hosting can spot and filter that traffic before it reaches your site, so real customers can still get through.
WAF (web application firewall)
A WAF sits in front of your site and inspects incoming requests, blocking ones that look malicious, such as attempts to inject code or steal data.
Why it matters: It's an extra layer of protection that can stop many attacks, even before a patch is available.
Backups vs disaster recovery
A backup is a copy of your data. Disaster recovery is the tested plan for actually getting your site back online, and how quickly.
Why it matters: Plenty of businesses have backups and still lose days of trading, because nobody knew how to restore them. Ask your provider not just "do you back up?" but "how long would it take to get us back?"
AI hosting
GPU hosting
GPUs (graphics processing units) were built for gaming graphics, but they're also brilliant at the heavy maths that AI models rely on. GPU hosting gives you servers with these processors built in.
Why it matters: If you want to run or train AI models yourself, ordinary servers will be painfully slow. GPU hosting gives you the horsepower without buying expensive hardware.
Private LLM
An LLM (large language model) is the technology behind AI assistants. A private LLM is one hosted securely for your business alone, rather than a public tool shared with everyone.
Why it matters: Every prompt typed into a public AI tool leaves your organisation. With a private LLM, your customer data, contracts and ideas stay under your control.
Data sovereignty
Data sovereignty is about where your data physically lives, and whose laws apply to it.
Why it matters: For businesses handling personal or sensitive data, keeping it in the UK can make GDPR compliance far simpler, and gives your customers more confidence.
The questions worth asking
You don't need to memorise every term on this list. But next time you review your hosting, these questions will tell you a lot:
Who patches our servers, and how quickly after a vulnerability is announced?
What happens to our site when traffic suddenly doubles?
How long would it take to get us back online after a disaster?
Where does our data actually live?
Are we paying for AWS capacity we don't use?
If the answers are vague, or you're not sure who to ask, that's worth fixing before your next busy period.
At Nublue, we handle all of this for our clients, from patching and security to AWS management and private AI hosting, and we explain it in plain English. If you'd like a straight-talking review of your current setup, get in touch at [email protected].