The software for your own UniFi controller is free – and that single sentence is where most cost calculations go wrong. There genuinely is no licence fee, yet running it is not free. If you want to compare the real self-hosted UniFi cost against managed hosting, you have to look past the purchase price and calculate the total cost of ownership over three years: platform, working hours, downtime risk and migration. This guide walks through the items that belong in that calculation and how to fill them with your own numbers.
Why the software price is the wrong number
Ubiquiti provides the UniFi OS Server – the current self-hosting software – licence-free to all UniFi users. It is the new standard for self-hosting and replaces the older UniFi Network Server, which lacked capabilities such as Organizations and IdP support.
So the software is free; operating it is not. Total cost of ownership means every cost incurred across the whole service life, not just the ones that arrive as an invoice. For a controller there are five blocks, and only the first one ever shows up in your accounting.
Block 1: The platform – what Ubiquiti actually requires
The controller needs a system that runs around the clock. For the UniFi OS Server, Ubiquiti states minimum requirements of an x86-64 processor, at least 2 GB of RAM, at least 10 GB of free storage and a 100 Mbps wired Ethernet connection. Supported operating systems include Linux (Ubuntu 24.04 or later, Debian 13 or later), Windows 10 or later and Windows Server 2022.
Two notes from the official documentation matter more for your calculation than the numbers themselves:
- The UniFi OS Server must keep running at all times for adopted devices to remain visible and manageable. A workstation that gets shut down in the evening is not an option.
- You will need to increase your system specs as you adopt and manage more devices. The minimum values are a starting point, not a target.
For TCO purposes, budget for the specification your network will need in three years, not the minimum it boots on today. Whether that is a mini PC in the rack, a VM on existing hardware or a rented VPS only changes which line the cost lands in – power and depreciation for your own hardware, rent for a VPS, a share of host costs for a VM.
Block 2: The hours nobody budgets for
This is the block that usually flips the result. A self-hosted installation is not an appliance you set up once; it is a system that needs looking after. The recurring tasks are manageable individually – they simply never stop:
| Task | Frequency | What it involves |
|---|---|---|
| Initial setup | one-off | Build the host, install UniFi OS Server, open ports, set up the account and remote access |
| Operating system updates | ongoing | Host security patches – separate from UniFi and entirely your responsibility |
| Controller updates | per release | Apply the update, then verify that every device came back online |
| Backup verification | regular | Creating a backup is one thing; knowing it restores is another |
| Monitoring | ongoing | Noticing that the service is down – ideally before anyone else does |
| Incidents | irregular | Devices that don’t return after an update, full disks, expired certificates |
Put your own realistic estimate against each row and multiply by your internal hourly rate. This is not a theoretical exercise: a single afternoon of troubleshooting costs more than a year of VPS rental for a small instance. And because that effort arrives unpredictably, it reliably lands on a day when something else is already on fire.
Block 3: Downtime risk and recovery
A controller outage does not switch off your Wi-Fi – access points keep serving their last configuration. What you lose is management, statistics, guest portal functionality and the ability to change anything at short notice. And if the configuration dies with the disk, a hardware fault turns into a rebuild.
Ubiquiti provides automated system backups, which you enable under Settings > Control Plane > Backups; backups can be restored from the same place. For a TCO calculation, the feature matters less than the question of where the backups go: a backup stored on the same host is worthless against exactly the failure it is supposed to cover. So budget for a second location and the occasional test restore – the hours plus, if you store externally, the storage cost. Our guide on UniFi controller backup and restore covers how to set that up properly.
Block 4: Remote access and hardening
Self-hosted no longer has to mean port forwarding. The UniFi OS Server works with the Site Manager at unifi.ui.com, and remote management is enabled by default during setup. The prerequisite is that outbound connections on TCP 443 and TCP 8883 are allowed – if a firewall or ISP device blocks that path, Site Manager cannot reach your console.
Locally, discovery, adoption and the guest portal need TCP 8080, TCP 8843, UDP 3478 and UDP 10001 open – on the host and in its firewall, not on the internet. Those rules are quick to write; the effort lies in keeping them tight and maintaining the hardening over time. Our guide on securing your UniFi controller covers what belongs in that.
Block 5: Migration and exit cost
The last block is almost always forgotten: what does it cost to get out again? Anyone still running the old UniFi Network Server has this item ahead of them already – moving to the UniFi OS Server is supported, but it is manual work. Ubiquiti notes that the Network Server must be closed before installation; on Windows and macOS the installer offers to migrate an existing setup automatically if it sits in the default location, while on Linux the path runs through the Site Export tool.
Budget for changes like this: once in three years is a realistic assumption, whether it’s driven by a new software generation, a server move or a hardware refresh.
What the comparison looks like
Line up the blocks for both options over 36 months. The structure matters more than the exact figures – you know those for your own operation better than any table can:
| Cost block | Self-hosted | Managed hosting |
|---|---|---|
| Licence | none | none |
| Platform | Hardware or VPS rent over 36 months, growing with device count | included in the fee |
| Setup | hours × hourly rate | handled by the provider |
| Updates & maintenance | hours × hourly rate × 36 months | included in the fee |
| Backups | setup, storage location, test restores | included in the fee |
| Incidents | hard to plan, but real | provider’s responsibility |
| Migration | budget for at least one | handled by the provider |
For a sense of scale, look at the vendor itself: Ubiquiti’s own hosted offering, “Official UniFi Hosting”, starts at 29 US dollars per month in the US store and manages up to 1,000 UniFi Network devices. The point is not the price tag but what it implies – a hosted controller sits in a range that a single hour of troubleshooting per month already outweighs.
What a specialist provider adds on top are criteria that never appear in an hourly calculation: data centre location, GDPR compliance and a named contact who answers the phone. Our guide on UniFi cloud controller cost goes deeper into the pricing factors.
When self-hosting is still the right call
The TCO comparison does not always favour managed hosting. Self-hosting pays off when you already run a virtualised environment with monitoring, patch management and verified backups – then the operating hours are marginal cost rather than new cost. The same applies when internal policy requires operation in your own data centre, or when the network has to work entirely without internet access.
It tips the other way wherever the controller is the only server system in the building. In that case a single application carries the full weight of operational discipline – and that is the most expensive way to run it.
Conclusion
Licence-free does not mean free of charge. The real cost of a self-hosted UniFi controller sits in the platform, the operating hours, the downtime risk and the migrations – and over three years those items are almost always larger than a glance at the server rent suggests. Work through both routes honestly, using your own hourly rate, device count and availability expectations. If you would rather compare the result against a concrete offer for a managed controller operated in Germany, get in touch with us and describe your setup.
Frequently asked questions
Does the UniFi OS Server cost anything?
No. Ubiquiti provides the UniFi OS Server licence-free to all UniFi users. Costs come from the platform it runs on and from ongoing operation, not from the software itself.
What hardware does a self-hosted UniFi controller need?
Ubiquiti’s stated minimum is an x86-64 processor, at least 2 GB of RAM, at least 10 GB of free storage and a 100 Mbps wired Ethernet connection. Importantly, the specification has to grow as you adopt more devices.
Does the server have to run permanently?
Yes. The UniFi OS Server must keep running at all times so that adopted devices remain visible and manageable. A machine that gets switched off in between is not suitable.
Do I need port forwarding for remote access?
Not necessarily. The UniFi OS Server works with Site Manager at unifi.ui.com, and remote management is enabled by default during setup. It requires outbound connections on TCP 443 and TCP 8883 – no inbound port forwarding is needed for that path.
When does managed hosting beat self-hosting?
As soon as the controller is the only server system you would have to run and maintain for it. Setup, updates, backups and incident handling then rest on that single application – and over three years those hours usually exceed the monthly fee of a managed service.
