With the UniFi OS Server, Ubiquiti has reworked how you self-host UniFi. It’s the official successor to the older UniFi Network Server and the new standard if you want to run your UniFi controller on your own hardware. But does self-hosting actually pay off for you, or are you better served by a hosted controller in the cloud? This article lays out the facts so you can decide.
What is the UniFi OS Server?
The UniFi OS Server is software from Ubiquiti that lets you run UniFi OS and its applications (including UniFi Network) on your own hardware or in a virtual machine — without having to buy a Cloud Console, a Cloud Key or a UniFi gateway. It replaces the older UniFi Network Server (previously known as the controller software) and brings the familiar UniFi OS interface, the same one you get on UniFi consoles, to systems you run yourself.
In short: you get the same central management for your access points, switches and gateways — but the controller runs on a system that you provide and maintain.
UniFi OS Server: requirements for self-hosting
To run the UniFi OS Server, you need a system that meets the following requirements:
- Operating system: Linux (for example Ubuntu 24.04+ or Debian 13+), Windows (via WSL 2) or macOS
- Container runtime: Podman 4.3.1 or higher — Docker is not supported
- Storage: at least 20 GB of free disk space
- Network: the required ports must be reachable (including TCP 8080 and UDP 3478)
- Always on: the UniFi OS Server must run continuously so your adopted devices stay managed and reachable
That last point is the decisive one — and it leads straight to the real question.
The advantages of self-hosting
- Full control over your hardware and software
- No recurring hosting fees (at the cost of your own hardware, power and time)
- Data stays in-house — relevant for specific compliance requirements
- Flexibility in how you set up the environment
The drawbacks that often get underestimated
Self-hosting sounds cheap at first — but the real cost is in day-to-day operation:
- 24/7 availability: if your server, VM or internet connection goes down, you lose central management of your network. UniFi devices keep passing traffic on their own, but management, statistics, portal features and remote access all depend on a running controller.
- Maintenance and updates: the operating system, Podman and UniFi OS all need regular updating and testing.
- Backups: a controller without a working, tested backup is a total-loss risk. Backups have to be set up, monitored and — when it counts — actually restorable.
- Security: exposing the controller to the internet opens an attack surface. Firewall, access control and DDoS protection are then your responsibility.
- Remote access and stable reachability: a home connection often lacks a static public IP, and port forwarding plus dynamic DNS are error-prone.
In short: the UniFi OS Server is quick to install — running it reliably, securely and around the clock is the actual work.
When does a UniFi controller in the cloud make sense?
This is exactly where a hosted UniFi controller comes in. Instead of running a server yourself, your controller runs in a data centre — continuously reachable, secured and maintained.
A hosted controller is worth it if you:
- don’t want to keep your own hardware running around the clock,
- need stable public reachability without port forwarding at home,
- would rather not deal with updates, backups and security yourself,
- manage multiple sites or clients from a single place,
- value hosting in Germany (GDPR-compliant) and support in your own language.
At clevendo, that’s exactly what we host: your UniFi controller in the cloud, operated in Germany — with a dedicated firewall, DDoS protection, automated backups and live support. Existing UniFi devices can be migrated, and if the worst happens, we restore your controller from backup. Get in touch if you’d like to talk it through.
Self-hosting vs. hosted controller at a glance
| Criterion | UniFi OS Server (self-hosted) | UniFi controller with clevendo |
|---|---|---|
| Hardware required | Yes, your own system 24/7 | No |
| Maintenance and updates | Do it yourself | Included |
| Backups | Set up yourself | Automated |
| Reachability / static IP | Sort it out yourself | Included |
| Firewall / DDoS protection | Do it yourself | Included |
| Support | Community | Live support |
| Hosting location | Home / your own data centre | Germany (GDPR-compliant) |
Conclusion
The UniFi OS Server is a big step for anyone who deliberately wants to self-host UniFi and has the time, the know-how and the infrastructure to back it up. If instead you want a worry-free controller that’s reachable around the clock without running your own server, a hosted solution is usually the more relaxed choice — and often cheaper overall once you honestly account for your own effort.
Want to run your UniFi controller without your own server? Contact us to discuss your setup, or take a look at the help center to see how migration works.
Frequently asked questions
What is the UniFi OS Server?
The UniFi OS Server is Ubiquiti’s official software for self-hosting UniFi OS and applications such as UniFi Network on your own hardware or in a VM. It’s the successor to the previous UniFi Network Server.
Do I need a Cloud Key or a gateway for the UniFi OS Server?
No. The UniFi OS Server runs on a system you provide yourself (Linux, Windows via WSL 2 or macOS) and doesn’t require a dedicated UniFi console.
Does the UniFi OS Server have to run continuously?
Yes. For central management and remote access to your adopted devices, the server has to be reachable around the clock.
What’s the alternative to self-hosting?
A hosted UniFi controller in the cloud — for example with clevendo — where operation, updates, backups and security are handled for you and the controller is reachable 24/7.