What It Actually Means
Physically it is an ordinary computer without a screen, in a data centre, doing one job reliably. Most businesses rent a share of one rather than owning anything.
The Questions That Actually Matter
Not the specification. Three operational questions decide whether a server is an asset or a liability.
Who maintains it? Operating system updates, security patches, expiring certificates, disk space, log rotation. This work is continuous and invisible, and unmaintained servers are how most small business compromises happen. The distinction between managed and unmanaged hosting is exactly this, and it is worth understanding which you bought.
Who can reach it? Administrative access should be limited and reviewed. Former contractors and old keys accumulate, and nobody removes them because nobody is looking.
What happens when it fails? Not if. Hardware fails, providers have outages, disks fill. The answer should involve tested backups and a known route back rather than an assumption.
Managed Or Not
This is the decision that matters most for a smaller business, and it is frequently made by accident.
Unmanaged means you get a machine and everything on it is your responsibility. Cheaper on paper and it assumes somebody competent is doing the maintenance. If nobody is, you have a server accruing unpatched vulnerabilities indefinitely.
Managed means the provider handles the operating system, patching and monitoring. More expensive and considerably cheaper than the alternative for a business without in-house capability.
The common failure is buying unmanaged hosting on price, having a developer set it up once, and nobody touching it again for three years. That server is a liability, and its cost is not the monthly fee.
What Actually Goes Wrong
Rarely the hardware. In practice: the disk fills with logs and everything stops; a certificate expires and browsers refuse the site; an unattended update breaks something; someone reaches an administrative interface that should not have been public; or a manual change made months ago is silently undone by a deployment.
All are prevented by ordinary monitoring and discipline rather than by better hardware, which is why operational practice matters more than specification.
What To Ask
- Is this managed or unmanaged, and who patches it? If the answer is nobody, that is the finding.
- What is exposed to the internet? Administrative interfaces and database ports frequently answer badly.
- Who has access, and when was that last reviewed?
- Is anything monitored? Disk space, uptime, certificate expiry and error rates cover most real incidents and cost nothing.
- When did we last restore from backup? Not whether backups run.
Choosing The Shape
For most small business systems the sensible option is managed hosting or a modest virtual server with someone responsible for it, at a predictable monthly cost.
Cloud platforms are worth the complexity when the workload genuinely varies or specific managed services are needed. Choosing the largest platform for a steady small system is a common default that costs more and introduces configuration nobody in the business understands.
More terms are in the glossary.
