UniFi OS: How to self-host?
With the release of UniFi OS Server, Ubiquiti now lets you run the full UniFi stack on your own hardware. No Cloud Key. No Dream Machine. No license required.
If you're an MSP or IT admin and want to manage multiple sites from one control plane (or just want full control of your infrastructure) self-hosting UniFi OS is finally possible.
Here’s how it works, what you need, and what to watch out for.
What is UniFi OS?
UniFi OS is Ubiquiti’s platform for running the full suite of UniFi applications:
- UniFi Network (AP, switch, and gateway management)
- UniFi Identity (SSO, RBAC, device access)
- SiteMagic VPN (site-to-site SD-WAN mesh)
- InnerSpace (Wi-Fi planning and floorplans)
- UniFi Protect / Access / Talk (not supported yet)
Until now, you could only run this stack on official UniFi hardware (UDM Pro, Cloud Key etc). But with UniFi OS Server, you can run it on your own VM, mini PC, or cloud server.
Self-hosting UniFi OS: what you’ll need
Supported platforms
- Linux (Debian/Ubuntu) — requires Podman 4.3.1+
- Windows 10/11 — requires WSL2
- macOS — Intel or ARM build
- ARM64 / x86_64 hardware — bare metal or virtualized
Minimum system requirements
- CPU: 2+ cores
- RAM: 2–4 GB minimum (more if you manage many sites)
- Disk: 20 GB+
- Network: open ports like
8080,8443,10001,11443, etc.
There’s no Docker support yet. Podman is required on Linux.
Step-by-step setup
1. Install Podman or WSL2
Linux:
sudo apt update && sudo apt install podman curl -y
You need Podman v4.3 or higher.
Windows:
Install WSL2 and Ubuntu from the Microsoft Store. Then download the .msi installer for UniFi OS Server.
2. Download the installer
Use Ubiquiti’s official links:
Windows
macOS
Linux
3. Run the installer
- On Linux, run the downloaded binary and follow the prompts.
- On Windows, launch the MSI; it will install in WSL2 automatically.
- On macOS, drag to Applications and open it.
After install, the server becomes available at:
https://localhost:11443
4. Initial configuration
- Assign a server name
- Sign in with a Ubiquiti account (optional but recommended)
- Restore a
.unfor.uossbackup if you're migrating from a UDM or Cloud Key - Install apps like Network, Identity, or SiteMagic from the Control Plane section
You can skip the UI login for offline-only mode, but you’ll lose features like Site Manager, Teleport, and remote backups.
Common issues to watch for
- No Protect or Access support yet
- SSL must be configured manually
- Some versions report UniFi Network as offline briefly at startup
- No native Docker support
- No built-in update mechanism. You’re responsible for upgrades
Should you self-host?
Self-hosting UniFi OS gives you full control, no licensing costs, and flexible deployment. It’s a strong option if:
- You manage dozens of sites and want centralized control
- You need local-only hosting for compliance or policy reasons
- You prefer full ownership over cloud-managed infrastructure
To weigh the upkeep, compare self-hosting with managed hosting.
But running it yourself also means owning the infrastructure:
- Keeping containers patched and secure
- Setting up SSL and backups
- Managing uptime, monitoring, and recovery
- Handling updates, networking, and resource scaling
For MSPs managing client networks, UniHosted offers paid managed UniFi OS Server hosting with daily backups, tested updates and migration assistance.
Related guides
Keep reading
Self-hosting vs managed UniFi controller hosting
Compare running a UniFi controller on your own hardware, a cloud VM or managed hosting, including maintenance, backups, costs and responsibility.
Read guideHow to self-host UniFi Controller
By the end of this guide, you’ll know how to install, configure, secure, and maintain your own UniFi controller.
Read guideSelf-hosting a UniFi Controller on Debian
Self-host a UniFi Controller on Debian for full control and lower costs. Step-by-step setup, device adoption tips, and security best practices.
Read guide