Ticking "unmanaged" on a dedicated-server quote to save the fee is a staffing decision dressed up as a hardware one. The server rarely breaks. What breaks is the assumption that somebody on your team has the time to patch it, watch it and restore it when something goes wrong, and that gap is a cost whether or not anyone has written it down.
We provision both managed and unmanaged dedicated servers for clients across Kenya and East Africa, so this is a straight answer on what each one actually gets you.
What managed actually covers
Managed is not a markup on the same box. It is a specific, ongoing list of work someone has to do, whether you pay us for it or do it yourself:
- Patching and security updates on a schedule, with a way back if an update breaks something
- Monitoring and alerting on CPU, disk, memory and the services that matter, routed to a person
- Daily backups, with restores tested periodically rather than assumed
- Hardening: firewall rules, SSH or RDP locked down, brute-force protection
- An engineer to call on WhatsApp, phone or email, with a one-hour response when the system is down
That list is the same whether the box runs Linux or Windows Server. It is just more work on Windows, because there is a license sitting on top of everything above.
Where unmanaged genuinely makes sense
Unmanaged is not a trap. It is the right call for a specific kind of buyer: a team with its own systems engineer, already running configuration management, who wants the hardware and the network and nothing else. You get root, we get out of the way, and the price reflects that we are not doing the ongoing work.
The honest test is simple. If a senior engineer on your payroll already owns patch cadence, backup verification and incident response for your other infrastructure, unmanaged saves you real money. If nobody does, unmanaged is not cheaper. It is a cost you have not counted yet.
The license that tips the decision
Here is where the math stops being close. Windows Server is licensed by core, and Microsoft's own pricing page quotes Standard edition at a suggested USD 1,176 for 16 cores, before a single Client Access License. Every user or device that touches the server needs a CAL, and staff connecting over Remote Desktop need RDS CALs on top. cPanel and Plesk carry their own license fees too. Get any of that wrong on an unmanaged box and you are either out of compliance or paying for licenses nobody uses.
On a managed server the licensing goes into the one monthly figure we quote, itemized, so tracking it stops being your problem. The full breakdown of what Windows Server licensing costs is worth reading before you decide unmanaged Windows is the cheap option.
How unmanaged boxes actually get hurt
Not dramatically. Patches slip because nobody owns the calendar, and the server sits exposed to a flaw that already had a fix. CISA's Known Exploited Vulnerabilities catalog is a running list of exactly those: vulnerabilities attackers are using in the wild, and the action printed under each one is to apply the vendor's mitigation. The fix existed. Nobody applied it.
The CIS benchmarks that define a hardened baseline are free and public too. Reading them is not the hard part. Applying them every patch cycle, on every box, for as long as the server runs, is the part that quietly stops happening without someone owning it.
So tell us honestly, through the quote form, whether anyone owns patching and backups today. If they do, we will tell you unmanaged is the smarter spend. If they do not, the management fee is the cheaper of your two options. WhatsApp +254 713 403 044 works too.